India manufactures roughly one in five of every generic medicine consumed worldwide, and a meaningful share of that output is destined for the EU. For any Indian manufacturer or exporter in that supply chain, EU FMD — formally the safety features set out in Delegated Regulation (EU) 2016/161, made under Directive 2011/62/EU — isn't background regulatory context. It's a set of concrete, pack-level technical requirements that have to be satisfied before a shipment can legally be sold at an EU pharmacy counter.
Most explainers stop at "you need a 2D barcode and a tamper seal." That's true but not useful on its own, because the part that actually trips up new entrants isn't the barcode spec — it's the chain of custody around it: who has to register with EMVO, in what order data has to be uploaded, and what happens to that unique identifier at each handoff between your factory and a European patient.
The Two Safety Features, in Practice
Delegated Regulation (EU) 2016/161 requires exactly two physical features on the outer packaging of most prescription medicines, and both have to be verifiable independently of each other.
| Data Element | What It Carries | Notes for Indian Exporters |
|---|---|---|
| Product code | GTIN identifying the specific product and pack size | Must match the Product Master Data already on file with EMVO for that market |
| Serial number | Randomized, unique to this physical pack | Not sequential — must resist being guessed or regenerated |
| Batch/lot number | Manufacturing batch identifier | Same batch discipline as domestic CDSCO requirements, reused rather than duplicated |
| Expiry date | Format standardized across all EU markets | Must match the human-readable expiry printed elsewhere on pack |
| National Reimbursement Number | Required by some but not all EU markets | Varies by destination country — this is where multi-market SKUs get complicated |
Who Actually Touches EMVO — It's Usually Not the Factory
This is the point most guides for Indian manufacturers skip, and it's the one that matters most operationally. EU FMD obligations attach to the Marketing Authorisation Holder (MAH) — the entity legally placing the product on a given EU market — not to the physical manufacturing site. For an Indian company, the MAH is typically an EU-based affiliate, a licensed importer, or a distribution partner, and it's that entity, not the Indian plant, that has the direct relationship with EMVO.
That doesn't make the Indian manufacturer's role passive. The MAH can only upload what the manufacturer gives it, so the actual serialization — generating the unique identifier, applying the ATD, and producing commissioning data at the moment of release — still happens on the Indian production line. What changes is who carries the legal and administrative relationship with the European verification system.
The EMVO Onboarding Path, Step by Step
Whichever entity in your chain carries the MAH relationship, the onboarding sequence with the European Medicines Verification Organisation follows the same shape.
The Decommissioning Chain
A unique identifier isn't verified once and forgotten — it moves through a defined set of states from commissioning at the factory to final decommissioning, and each handoff point in the EU distribution chain has a different role to play.
Country-specific coding isn't optional detail. The National Reimbursement Number and other market-specific data elements genuinely vary by destination country, and Product Master Data has to reflect that per market, not just per product.
Onboarding fees scale with how many MAHs an OBP represents, and have been raised in stages industry-wide — worth confirming current terms directly with your OBP rather than budgeting off older figures.
Upload timing matters. Serial data has to reach the EMVS hub before release to market, and troubleshooting guidance from national verification organisations generally expects any data discrepancy to be flagged within 24 hours — which is a tight window if your serialization data is being reconciled manually after the fact rather than generated correctly at commissioning.
What Happens When a Pack Fails Verification
A failed verification — a scanned unique identifier that doesn't match what's on file, or a pack already marked as decommissioned somewhere else in the chain — doesn't quietly resolve itself. It triggers an alert within the national verification system, and the pack is treated as suspect until investigated, which in practice means it's pulled from the supply chain rather than dispensed while the discrepancy is checked.
For an Indian manufacturer, the two most common real-world causes of this aren't counterfeiting at all — they're process errors upstream. The first is a serial number uploaded to the wrong national system, which happens when a multi-market SKU's Retrospective Upload routing doesn't correctly separate destination countries. The second is a timing gap: stock released and shipped before its serial data finished propagating through the EMVS hub to the relevant NMVS, so the first verification attempt at the EU end finds nothing on file yet. Neither is a safety issue, but both create exactly the kind of shipment-held-at-port scenario that an EU FMD guide for Indian exporters needs to address directly, because they're avoidable with the right sequencing — serialize, upload, confirm propagation, then release — rather than treating the regulatory upload as a parallel paperwork step.
A Note on the UK and Northern Ireland
Indian manufacturers who built their EU FMD compliance process before 2021 should double-check it against current UK arrangements specifically, because this is an area that changed after the original rollout and still trips up exporters working from older documentation. Great Britain left the EU's verification system following its EU exit and the UK now runs its own medicines verification requirements, separate from EMVO and the EU hub. Northern Ireland, under the Windsor Framework, has followed a different path from Great Britain on medicines regulation. The practical takeaway: a serialization setup validated for "the EU" cannot be assumed to cover UK-bound shipments without a separate check, and Indian exporters shipping into both markets need to confirm which specific national system each destination actually requires — treating "Europe" as one compliance zone is exactly the kind of assumption that produces a held shipment.
How Ratifye Fits Into This Chain
The common failure pattern across every step above is the same one: serialization data generated separately from the actual commissioning event, then reconciled, cleaned, or corrected before it can be uploaded. That gap is where mismatches, missed country-specific fields, and late uploads all originate.
None of this replaces the legal relationship between your MAH and EMVO, or the OBP's role in that process. What it removes is the operational gap between what your production line generates and what your EU-side partner needs to upload correctly and on time — which is where most of the real-world EU FMD problems Indian exporters run into actually originate.
That same commissioning event, done once and done correctly, is also the foundation for CDSCO's domestic Top 300 QR requirement and DSCSA data for US-bound stock — the three regimes ask for overlapping but not identical data, and a manufacturer generating it three separate times, in three separate workflows, is tripling the chances of exactly the kind of mismatch that gets a shipment held. One commissioning event, structured to satisfy all three from the start, is the difference between regulatory compliance as a recurring fire drill and regulatory compliance as a byproduct of how production already runs.
Your EU shipments depend on serialization data someone else has to upload correctly. Make sure it's right at the source.
Ratifye generates commissioning-ready, market-specific serialization data at the point of production — built to move cleanly into your MAH's EMVO onboarding, not reconciled after the fact.
Talk to our pharma compliance team
