MHRA compliance and GDP documentation: why UK pharma distributors need a purpose-built ERP

A UK wholesale dealer’s licence is not a certificate you frame. It is a continuing obligation to demonstrate, on demand, that every medicine you have handled moved through a controlled and documented chain.

Most distributors we assess can demonstrate this. It just takes them three weeks and two people.

What GDP actually asks for

Good Distribution Practice is often discussed as though it were a filing requirement. It is closer to an evidentiary standard. For any unit you have handled, you should be able to produce:

• The batch it belonged to and where that batch came from
• Every location it occupied, with dates
• The temperature conditions it was held under throughout
• Who authorised each movement
• What was done if any condition fell outside its limits
• Where it went, and to whom, under what licence

The Responsible Person carries personal accountability for this. That is the part that changes the character of the requirement. It is not a departmental process, it is a named individual’s liability.

Why generic ERP does not cover it

A general-purpose ERP tracks stock. It knows quantities, locations, and values. Ask it what it was built to answer and the answer is how much do we have and what is it worth.

GDP asks a different question: what happened to this specific unit, and can you prove it.

Those are not the same data model. Batch-level traceability can be bolted onto a generic system, and it frequently is, but the bolt-on is where the failure modes live:

Temperature records live outside the stock record. The most common arrangement we find is data loggers producing their own reports, filed separately, reconciled to movements by hand when an audit is announced. The records exist. The link between a specific excursion and the specific units affected does not. It is reconstructed on demand, by a person, from two sources.

Expiry is a field rather than a rule. In a generic system expiry is an attribute you can report on. In a pharma system it drives picking order. If FEFO is a report rather than a constraint, someone eventually ships the longer-dated stock and the short-dated stock becomes a write-off.

Credit blocks and dispatch blocks are the same mechanism. They should not be. A generic ERP treats a hold as a commercial state. A distributor needs quarantine, recall, and credit hold to be distinct states with different authorities to release them.

The audit trail is configurable. In a generic system, someone with admin rights can usually amend a historical record. Under GDP the trail must be immutable and attributable. This is the single most common finding in the assessments we run.

What a purpose-built system does differently

In PharmFlow the compliance requirements are not features. They are constraints on what records can exist.

A movement cannot be written without an authorising user. A batch cannot be dispatched past its expiry. A temperature excursion attaches to the affected units automatically at the moment it is logged, because the logger feed and the stock record are the same system rather than two systems reconciled later. Historical records cannot be amended, only superseded, with both versions retained.

The practical effect is that audit preparation stops being a project. The inspection asks a question, someone runs a query, the answer is on screen. The three weeks and two people go back to their actual jobs.

The commercial argument, since compliance alone rarely wins the budget

Compliance is why the Responsible Person wants this. It is usually not why it gets funded. Three things generally do:

Short-dated stock caught early. When expiry drives picking and reporting rather than sitting in a field, short-dated stock surfaces while there is still time to redistribute it rather than write it off. For most distributors we work with this alone covers the system.

Recalls that take hours. A recall against a generic system means identifying affected batches by hand and calling customers from a list. Against a traceability-native system it is a query and a generated notification set.

Audit readiness as a commercial asset. Distributors bidding for contracts with larger manufacturers are increasingly asked to evidence their systems, not just their licence. Being able to demonstrate it in a meeting rather than promise it has won our clients work.

What to ask a vendor

If you are evaluating systems, the question that separates them quickly is this: show me the temperature excursion record for a unit, starting from the unit.

A pharma-native system does this in one step. A generic system with traceability bolted on will show you the stock record, and then someone will open a different application.