A pallet comes back to a pharmaceutical wholesaler's warehouse. A pharmacy over-ordered, the packs are unopened, and the paperwork is in order. The operator scans the first pack.
What should the system do?
It is a small question, and the team building the warehouse integration will probably answer it in an afternoon. But the answer is governed by three separate rulebooks. One is a European directive about falsified medicines. One is a set of guidelines about distribution practice. One is an industry standard about recording supply-chain events. They were written by different bodies, at different times, for different purposes, and each assumes the other two exist without saying how they fit.
Most serialisation programmes treat them as three workstreams. The result is three sets of documents and a system whose design satisfies each rulebook in a different place, described in different words. This post takes the opposite route: one decision, examined once, with all three in view.
The Three Rulebooks
EU FMD
Is this pack genuine? The unique identifier, the anti-tampering device, and verification against the European repositories.EU GDP
Was it handled properly? Quality system, storage, records, returns, recalls, and the Responsible Person.GS1 EPCIS 2.0
What happened to it? A standard record of each event: what, when, where and why.Figure 1 — Three rulebooks, each asking a different question about the same pack.
The Falsified Medicines Directive is Directive 2011/62/EU together with Commission Delegated Regulation (EU) 2016/161. It has applied to the serialisation of prescription medicines since 9 February 2019, with a later date, of up to 9 February 2025, allowed for Member States that already had a verification system of their own. Each pack carries a unique identifier in a two-dimensional barcode and an anti-tampering device. The identifier is uploaded by the manufacturer to a system of repositories, a European hub connected to national systems, and is verified and decommissioned at defined points on the way to the patient. The regulation sets out, actor by actor, who must verify what and when.
Good Distribution Practice is the European Commission's guidelines of 5 November 2013 (2013/C 343/01), binding on holders of a wholesale distribution authorisation. Where FMD asks whether a pack is genuine, GDP asks whether the distributor is in control: a quality system, a named Responsible Person, qualified suppliers and customers, temperature-controlled storage, complete records, and defined handling for complaints, returns, suspected falsified medicines and recalls.
EPCIS 2.0 is a GS1 standard, with its companion Core Business Vocabulary. It is not law. It is the common language for recording what happened to a physical object: it was commissioned, packed into a case, shipped, received. Each event states what, when, where and why. Version 2.0 added JSON and REST bindings alongside XML.
The first is a regulation about authenticity. The second is a guideline about conduct. The third is a data standard. A warehouse system has to satisfy all three at the moment the operator scans the pack.
One Scan, Read Three Ways
Go back to the returned pack. Here is what each rulebook says about that moment.
| What it requires at the returns dock | What the system must therefore do | |
|---|---|---|
| EU FMD | A wholesaler verifies the authenticity of the unique identifier of medicines returned to it (Delegated Regulation 2016/161, Article 20) | Call the national verification system for this pack before it can re-enter saleable stock |
| EU GDP | Returned products go back to saleable stock only if defined conditions are met and a competent person has assessed them (Chapter 6, section 6.3) | Hold the pack in a returns status until the assessment is recorded, with who made it and on what basis |
| EPCIS 2.0 | Nothing is mandated. It defines how a receiving event is expressed | Record the receipt as an event with the pack's identifier, the time, the location and the business step |
Figure 2 — The same scan, as each rulebook sees it.
Three obligations, one user action. A design that handles them in three separate places will work in the demonstration and fail in the edge cases: the pack that verifies as genuine but arrived outside its temperature range; the pack whose assessment was recorded but whose verification call timed out; the event that was written before either check completed.
A design that treats them as one decision gets those cases right, because it has to say in what order the three things happen and what the pack's status is between them.
Step 1
Scan
Step 2
Quarantine
Step 3
Verify
Step 4
Assess
Step 5
Release or reject
Read the unique identifier; record the receiving event
Pack is not saleable; status says why
Check the identifier against the national system
A competent person records the returns assessment
Both must pass; the outcome is a recorded event
Figure 3 — One flow that satisfies all three, in a stated order.
The Boundary Teams Get Wrong
The most expensive mistake in this area is not missing a requirement. It is confusing two systems that look alike.
A company that has implemented EPCIS has a repository full of events about every pack: when it was commissioned, which case it went into, where it shipped. It is tempting to treat that repository as the source of truth about the pack.
It is not. Whether a pack is genuine and still active is a question only the European repositories system can answer. Your internal event history is your own record of what you believe happened. A pack can have a perfect internal genealogy and still have been decommissioned elsewhere, or reported stolen, since you last saw it.
The reverse mistake is just as common. The national verification system answers one question about one pack at one moment. It does not tell you which case the pack was in, which pallet, which shipment, or what else was on the lorry. When a recall arrives and you need every pack from a batch that passed through your warehouse in March, the verification system cannot help. Your own event history can.
Your event repository
- Knows where the pack has been in your hands
- Knows its case, pallet and shipment
- Answers a recall in minutes
- Is never the authority on authenticity
The verification system
- Knows whether the pack is genuine and active
- Knows nothing of your warehouse
- Answers one pack at a time
- Is never a substitute for your genealogy
Figure 4 — Two systems that hold data about the same pack and answer different questions.
Stated as rules, these are two sentences. An internal event repository is never the authority on pack authenticity. The national verification system is never a substitute for internal genealogy. Almost every design flaw we have seen in serialisation integrations comes from quietly breaking one of them.
Where the Rulebooks Refer to Each Other
The three are not as separate as their origins suggest. They point at each other in specific places, and those are the places a design has to get exactly right.
GDP's chapter on complaints, returns, suspected falsified medicines and recalls is where a wholesaler's duties about falsified medicines sit in practice. A suspected falsified pack must be segregated and reported. FMD is what makes "suspected" a precise condition rather than a judgement: a failed verification is a defined trigger.
GDP also requires the batch number on the documentation that accompanies a supply, for products bearing the safety features. That one line ties the distribution record to the serialised pack.
And FMD's rules on decommissioning by wholesalers, for packs that are exported outside the Union, cannot be returned to saleable stock, or are to be destroyed (Article 22), describe exactly the transitions an event standard is built to express. EPCIS does not tell you that you must decommission. It gives you the vocabulary to record that you did, and its error-declaration mechanism lets you correct a wrong event without rewriting history, which is what an audit trail under GDP expects.
EU FMD
Verify and decommission at defined points.
A failed verification defines "suspected falsified"
EU GDP
Segregate, assess, report, record.
Batch number on supply documentation
EPCIS 2.0
Events with what, when, where and why.
Corrections declared, never overwritten
Figure 5 — How the three rulebooks hand off to one another.
Turning the Rulebooks Into Rules You Can Review Against
Reading three documents this closely is a specialist's job, and most organisations have one or two people who can do it. That is the real risk. The design is reviewed by whoever is in the room, and the person who knows that Article 20 applies to returns is on leave.
This is the problem architecture directives solve. A directive is one clear, approved statement of what your organisation requires, written once and applied to every review. For the returns dock, three are enough:
- Returned medicinal products are verified against the national verification system before re-entering saleable stock.
- No pack re-enters saleable stock without a recorded returns assessment by a competent person.
- Pack authenticity is decided by the verification system; internal event history is never used in its place.
All three frameworks are now in the cajeX framework catalogue: EU FMD with 150 directives, EU GDP with 135, and GS1 EPCIS 2.0 with 84. Each clause is treated as a question your organisation answers with a directive. cajeX suggests the mapping; your architect adopts it, changes the wording, or writes a different one. The crosswalk rules above, the two sentences about which system is the authority on what, are included as directives in their own right, because they belong to no single rulebook and are the ones most often missed.
Two notes on how the catalogue treats these sources. FMD and GDP were published in the Official Journal, so their clause text is quoted. GS1 publishes EPCIS freely but keeps the copyright, so those clauses are summarised by cajeX rather than quoted, with attribution, and the framework is labelled as summarised. And the parts of each regulation addressed to regulators rather than to you, such as the chapters for national competent authorities, are shown but marked out of scope with the reason, so the structure is complete when you browse it.
Once approved, the directives apply to every design that touches the returns flow. When the warehouse integration is submitted for AI review, a design that returns packs to stock on the strength of an internal lookup produces a finding, and the finding carries its trail: framework, clause, directive.
The returns flow restores packs to saleable stock after checking the internal event repository. No call is made to the national verification system.
Figure 6 — The boundary mistake, caught at design review rather than at inspection.
The same directive set covers the rest of the pharma supply chain already in the catalogue: EU GMP Volume 4, Annex 11 on computerised systems, Annex 15 on qualification and validation, GAMP 5 and 21 CFR Part 11. Serialisation and distribution sit above those. For how a validated system is traced from one of these rules to its test evidence, see from requirement to proof.
What to Take From This
If you run or build systems in the medicines supply chain, three things are worth checking this week.
First, find the decisions in your design that more than one rulebook governs. Returns, recalls, and the handling of a failed verification are the usual three. Ask whether each is documented once or three times.
Second, write down which system is the authority for which question. If the answer to "is this pack genuine?" is anything other than the verification system, you have found a problem before an inspector did.
Third, ask who would catch a mistake at design review if your serialisation specialist were away. If the answer is nobody, the knowledge is in a person and not yet in a rule.
The pack on the returns dock does not know which rulebook it falls under. The system scanning it has to satisfy all three at once, and the cheapest moment to make sure it does is before it is built. For more on governance in supervised environments, see regulated industries.
Sources
- Directive 2011/62/EU of the European Parliament and of the Council, amending Directive 2001/83/EC as regards the prevention of the entry into the legal supply chain of falsified medicinal products
- Commission Delegated Regulation (EU) 2016/161, laying down detailed rules for the safety features appearing on the packaging of medicinal products for human use, Articles 20, 22 and 50
- Guidelines of 5 November 2013 on Good Distribution Practice of medicinal products for human use (2013/C 343/01), European Commission, sections 5.8, 6.3 and 6.4
- EPCIS and Core Business Vocabulary (CBV), GS1, release 2.0, ratified June 2022
- European Medicines Verification Organisation, on the European Medicines Verification System