Pharmaceutical ERP Consultant, UK

QP certification, RP oversight and what a status really means

In many UK pharmaceutical businesses, the ERP shows a batch as available long before anyone with authority has said it may be sold. The QP's certification is recorded in a register or on a signed form, and the system simply trusts that warehouse staff will not pick the batch too early. That gap is where errors and audit findings start.

I fix this at the design level. For manufacturers and importers, the status model usually needs at least: received and quarantined, under test, awaiting certification, certified and released for sale, rejected, and on hold for investigation. For wholesalers, the focus shifts to receipt checks, returns and suspect product, where the RP's judgment decides whether stock goes back to saleable inventory or is destroyed.

The requirements state who may change each status, whether a second person must approve, and what the system records about the change. Your quality team then decides what level of testing and validation those functions need under their own procedures and the MHRA context they work in. My pharmaceutical ERP page covers the general process map; here I focus on how UK roles shape it. Writing this clearly is the core of my requirements gathering work.

Wholesale dealers, specials and parallel distribution

UK wholesale is not one business model. A full-line wholesaler ships many lines to pharmacies daily. A short-line wholesaler focuses on a narrower range and often trades with other wholesalers. A specials manufacturer makes unlicensed products to a prescriber's request. A parallel distributor sources product from other markets and relabels or repacks it for UK sale under its own license.

Each brings specific ERP needs:

• Customer verification: holding license or registration details for each customer and checking them before first supply and periodically after.
• Specials orders: linking each order to the prescriber request, the batch made and the documentation that went with it.
• Relabeled stock: keeping the source batch, source expiry and supplier on every repacked batch, and printing the right UK label data.
• Returns: holding returned stock in a separate status until the RP decides, with reasons recorded.

Generic distribution software often assumes stock is fungible and simply moves it. In pharmaceutical wholesale, the batch and its history are what matter. I test these flows in scripted demos during ERP evaluation, so the platform you choose has shown it can handle your own cases rather than a vendor's showcase.

Great Britain, Northern Ireland and pack-level safety features

Since the UK left the EU, arrangements for medicines placed on the market in Great Britain and in Northern Ireland have diverged in several respects, including pack-level safety features and the related verification steps. The details continue to evolve, so I never design from memory. I ask your regulatory team for the current position for each market you supply and record it as a set of business rules.

For the ERP, the practical questions are:

• Do you need separate item codes or pack variants for stock destined for Great Britain and for Northern Ireland?
• Which dispatch or receipt events must trigger a verification or decommissioning step in an external system?
• How are packs that fail verification held and reported?
• Which warehouse locations hold stock for which market?

Serialization and pack verification normally run in specialist systems connected to packaging lines and national repositories. The ERP supplies product, batch and expiry data and receives back exceptions. Getting the interface right matters more than the choice of ERP, and I specify it with the same care as any ERP integration. If you also export finished goods to the EU, the customs and origin data that my UK manufacturing ERP page discusses will also apply.

Cold chain, controlled drugs and recall readiness

Refrigerated and frozen products put the most pressure on a UK distributor's systems. Stock can leave the safe range in a cold room, in a van or at a customer's door, and when that happens the affected batches must be identified and held at once. I write requirements for storage conditions on each item and location, an interface to temperature monitoring so excursions are logged against locations and time windows, and an automatic hold on affected stock until quality makes a decision. Delivery routes for cold chain lines often need their own picking and dispatch rules.

Controlled drugs bring licensing and register obligations that differ by schedule. In ERP terms, that usually means restricted locations, extra approval on receipts and adjustments, and reports that match the registers your compliance staff keep. The exact rules are theirs to define.

Recall readiness ties everything together. A good test is to pick a batch at random and ask how quickly you can list every customer who received it, every source batch it came from and every unit still in stock. I build that exercise into UAT and repeat it after go-live. Where returns, complaints and deviation handling sit is a boundary decision: those records usually belong in a QMS, with the ERP holding batch status and movements.

Moving from Sage and spreadsheets, delivered remotely

Smaller UK pharmaceutical businesses often run Sage or another accounting package for finance, a separate wholesale or warehouse tool for orders, and spreadsheets for batch registers, returns and temperature logs. Moving to an ERP means bringing those registers across with their history intact: open batches with status and remaining shelf life, customer license records, supplier approvals and open orders. I plan migration with reconciliation steps that quality, warehouse and finance each sign off, so nobody discovers after go-live that a held batch has become available.

VAT and Making Tax Digital setup belong in the finance design, and your accountant confirms treatment. Data protection matters where you hold prescriber or patient details for specials, and your data protection lead decides how. My role is to keep such data to the minimum the process needs.

All work runs online, with sessions scheduled inside the UK working day: video workshops, process diagrams everyone can comment on, a requirement list with reference numbers, a scored fit-gap and recorded test sessions. For other UK engagements, see my ERP consultant UK page, or the United Kingdom hub for wider market notes.