LillyDirect integration for UK pharmacies: OneScript and Pharmacy2U

The Mounjaro market has changed. At Pharmacy Mentor, we’re being asked more and more about connecting pharmacy websites to LillyDirect through OneScript or Pharmacy2U.

The questions are usually straightforward. Can we keep our website? Who takes the payment? Who sends the medicine? And what will our team need to do differently?

This article explains the main decisions for pharmacy owners. It also sets out what to ask before paying for development. The details of your connection will depend on your prescribing system, your chosen dispensing partner and the arrangement you agree with them.

Start here

What pharmacy owners need to know

• LillyDirect sits after prescribing. Your clinical team still makes the prescribing decision.
• OneScript and Pharmacy2U offer different ways to connect. Check which fits your website and payment arrangements.
• A working connection is only part of the job. Patients need clear information, and staff need a way to handle problems.
• Agree requirements before a launch date. Onboarding, security checks and provider approval can affect the schedule.

Written for UK pharmacy owners and healthcare providers. Service information checked on 12 November 2026.

What is LillyDirect?

LillyDirect is a UK service for dispensing and delivering medicine after a prescription has been issued. Your clinical team retains responsibility for prescribing decisions and the patient relationship. The dispensing partner receives the prescription and handles fulfilment. Lilly explains the service here.

For a pharmacy website, this means passing information to another organisation and receiving information back. Your team needs to know whether the prescription arrived, whether the dispensing partner accepted it and whether the medicine has been dispatched.

Those are different stages. An order should not be marked as dispatched just because your website successfully sent a request. Getting this distinction right helps staff answer patient queries and avoids sending misleading delivery updates.

Who can use it?

Lilly’s published criteria cover eligible UK-regulated private healthcare providers, including GPhC or PSNI-regulated pharmacies offering private weight-management services. Its entry threshold is no more than 10,000 private Mounjaro packs across the provider’s corporate group in the previous calendar month. That threshold does not cap growth after onboarding.

PGD supply is outside the current service because it does not involve an individual prescription. Dispensing partners may have additional requirements. Check Lilly’s current eligibility guidance before commissioning work.

OneScript and Pharmacy2U: what is the difference?

Both are named LillyDirect dispensing partners. The useful question is which arrangement fits the way your pharmacy already works. Start with your prescribing software, how you collect payment and the work you want your team to retain.

OneScript

OneScript describes a service built around an API: a connection that lets software systems exchange information. Its published model allows partners to retain prescribing, payments and patient relationships while OneScript handles prescription review, dispensing and delivery.

It also describes order tracking and onboarding that covers screening, clinical assurance, contracts and integration. Ask its team what your organisation and website must provide. Read OneScript’s service information.

Pharmacy2U

Pharmacy2U offers connections through existing prescribing platforms and its direct Gateway API. It publishes two payment models. With Clinic Pay, the patient pays your clinic and Pharmacy2U invoices it for the medicine. With Patient Pay, the patient pays Pharmacy2U directly.

Its application includes clinical assurance and prescriber verification. Read Pharmacy2U’s onboarding and payment information.

This is not a full comparison of contractual terms. Confirm the details directly with each provider before choosing a route.

What are you trying to improve?

Before discussing development, be clear about why you want the connection. Perhaps you want another dispensing option, less fulfilment work for your team or a way to support a growing clinic. Each objective leads to slightly different questions.

If your priority is saving staff time, ask which tasks will actually disappear and which will remain. Someone may still need to deal with prescription queries, reconcile invoices and answer delivery questions. Include that work when comparing the options.

An integration will not bring more visitors to your website on its own. Pricing, the consultation experience and patient support still matter. Judge the connection by whether it makes your chosen service easier to run and easier for patients to understand.

What needs to change on your website?

You may be able to keep much of your existing website. The amount of work depends on how it handles consultations, prescriptions, payments and orders today. Your developer should review those parts before recommending changes.

1. Sending the prescription at the right time

A payment is not a prescribing decision. Your website needs to distinguish an order awaiting assessment from an issued prescription that can be sent to the dispensing partner.

Decide whether staff will choose which approved orders to send or whether the system will send them automatically. Either way, staff need a record of what was sent and the response received. Ask your developer to show you that record during testing.

2. Making payment clear

Agree who collects payment before changing checkout. If your pharmacy takes it, you need a reliable way to match orders against the dispensing partner’s invoices. If the partner takes it, decide how your team will know whether the patient has paid.

Lilly requires invoices to separate medicine charges from consultation and other fees. After prescribing, patients must be told that Lilly funds the service and that they can opt out without losing access to treatment. Funding applies to the licensed weight-management indication in line with the UK product information. See Lilly’s requirements.

Work out where the relevant information appears and how an opt-out is handled. Your team should be able to explain the alternative arrangement without having to improvise when a patient asks.

3. Handling baskets with more than one item

A patient might buy a medicine fulfilled through LillyDirect alongside a product your pharmacy sends itself. One basket can then produce two deliveries.

Your website needs to make that clear. Agree how delivery charges, tracking and order confirmations will work. Staff must also be able to cancel or refund one item without accidentally changing the other. Test a mixed basket, not just a straightforward single-item order.

4. Keeping patients informed

Ask which updates the provider can send back to your website. These might include a prescription awaiting clarification, acceptance for dispensing or dispatch. The available information will depend on the connection.

Then decide who sends each patient message. Two organisations sending overlapping emails can create confusion. A clear confirmation should tell the patient what has happened, what to expect next and who to contact if they need help.

5. Dealing with problems

Consider what happens if your website sends a prescription but does not receive a reply. The request might have failed, or it might have arrived successfully. Sending it again without checking could create a duplicate.

Your developer should explain how the system handles that uncertainty. Your team also needs a process for rejected prescriptions, unavailable products and cancellations. In particular, establish what can still be cancelled after dispensing has started.

Security requirements: ask before you book testing

Ask the provider to confirm the security evidence it needs for your specific website. Approval of another pharmacy’s connection does not automatically cover yours. Hosting, plugins, staff access and custom features can all differ.

For the OneScript work discussed with our development team, a recent client-specific penetration test forms part of the planned onboarding process. Get the required scope and acceptance criteria confirmed directly with OneScript before commissioning a test.

A penetration test looks for weaknesses that an attacker could exploit. If one is required, ask which website, APIs and environments it must cover, how recent the report must be and which findings need fixing before approval. Check whether the tester must return to verify the fixes.

Do not assume that Pharmacy2U has identical requirements, or that no test is needed simply because one has not yet been requested. Obtain its requirements for your connection in writing too.

Also agree which patient and prescription details will be transferred, where they will be stored and who can access them. Ask how corrections are handled after information has been sent. These answers should inform the build and the agreements between the organisations.

What should you test before launch?

Testing should cover what staff and patients experience, as well as whether the connection works. Use the provider’s approved test environment and test data. Do not use real patient records just because they are available.

Ask your team to demonstrate these six situations:

1. A normal order. The correct prescription reaches the right partner, and staff can see what happened.
2. A prescription query. The request reaches the person responsible for answering it.
3. A failed or interrupted submission. Staff can establish whether the order arrived before trying again.
4. A mixed basket. Each item keeps the correct delivery information and fulfilment responsibility.
5. A cancellation. The system distinguishes a cancellation request from a confirmed cancellation.
6. A repeat order. The new assessment and prescription stay separate from previous orders.

Read the confirmation pages and emails during these tests. Check charges, contact details and delivery wording. A successful technical response does not prove that the patient received a clear or accurate message.

Keep one list of the results and any issues still to resolve. Agree who can sign off each part. Your clinical lead, operations team and developer may all need to check different things.

How long will it take, and what should the quote cover?

Separate the time needed to build the connection from the time needed to launch it. Development may be only one part of the schedule. Onboarding, contracts, test access, security work and provider approval may also need to be completed.

A useful estimate shows the stages and what each depends on. For example, testing cannot finish if the team is still waiting for access to the provider’s test system. Ask which dates are firm and which are provisional.

The quote should explain whether it includes checkout changes, payment reconciliation, patient messages and handling failed orders. “API integration” on its own is too vague to tell you what the finished website will do.

Clarify the cost of any security assessment, fixes and retesting. Ask about ongoing support too. If the provider changes its connection or your pharmacy changes its prescribing software, someone will need to assess the effect and carry out any necessary work.

Compare the full cost with the work the arrangement replaces. Include staff administration and patient support alongside supplier charges. A lower headline charge does not necessarily mean less work or a better overall return.

Prepare your team as well as your website

Before launch, choose the person responsible for monitoring orders and dealing with exceptions. Make sure they know how to contact the provider and when an issue needs clinical input.

Agree what happens if the connection becomes unavailable. Staff need to review outstanding orders and keep patients informed. Do not move an uncertain order to another dispensing route until you know whether the original partner has accepted it.

A supervised initial rollout can help your team learn the process. Review early orders closely, then look for recurring problems. If patients repeatedly ask where to pay or who is delivering their parcel, improve those messages.

For your first provider discussion, gather your regulatory and prescriber details, governance documents and the name of your prescribing platform. Add a brief description of your current patient journey and your preferred payment arrangement. Bring your clinical lead and developer into the discussion so questions reach the right person.

Common questions

Planning your LillyDirect integration?

At Pharmacy Mentor, we are developing integration options for our online prescribing websites. Scope and availability depend on your platform, the provider’s requirements and completion of testing.

If you are considering either route, start with a review of your current website. We can discuss what needs to change and what information your chosen provider will need. Explore the WooPW online prescribing platform or contact our team about your LillyDirect integration.

Stay informed through the app

Get updates like this through GrowthHub

GrowthHub is where we share Pharmacy Mentor announcements, including updates on integrations like LillyDirect. Use the app to keep up with what we are working on and the information we share with clients.

It is also our client hub for reporting, support and resources. Already have an account? Open GrowthHub and check the latest news. If you are new, you can register for free.

Get the GrowthHub app →Register for free

Confirm current eligibility, security requirements and contractual arrangements directly with your chosen provider.