EU-FMD Revision: IT & Supply Chain Impact
5 Min. Reading Time
Since February 9, 2019, pharmaceutical serialization has been mandatory in the EU. Every pack of prescription drugs carries a 2D data matrix code and a tamper-evident seal, with the data being fed into the European Medicines Verification System (EMVS). Six years later, the EU Commission is working on a revision of the Falsified Medicines Directive. What’s emerging is less of a break than a consolidation – with noticeable consequences for manufacturers’ IT and supply chain architecture.
The Essentials at a Glance
- Compliance becomes architecture. The FMD revision elevates serialization from a track-and-trace bolt-on to a strategic data platform – with API exposure for regulators and coupling to the European Health Data Space.
- Data model is consolidating. In addition to the current data matrix code, structured supply chain events, aggregation at the carton level, and harmonized interfaces to national hubs are coming.
- Mid-sized businesses beware. Those planning now should build along the upcoming supply chain events – not along today’s EMVS fields. Standard suite upgrades alone won’t be enough.
RelatedCritical Medicines Act: Reshoring in the pharmaceutical supply chain / Medtech SMEs: MDR, NIS2, and PFAS in interplay
The FMD was adopted in 2011, specified in 2016 by Delegated Regulation 2016/161, and has been operational since 2019. The revision discussion initiated by the EU Commission in 2024 with a consultation aims not to replace the system but to improve data quality and tighten its connection to regimes like the European Health Data Space. For IT decision-makers, this means: the infrastructure is in place, but the data points are becoming denser.
What the FMD revision specifically changes
The EU Commission proposed the revision of the pharmaceutical legislation in 2023 and launched a public consultation on supply chain and counterfeit protection in 2024. The FMD is one of several building blocks in this package. What is emerging from the consultation documents and the accompanying statements from the EMA can be summarized in three key developments.
Firstly, an increase in data quality density. The current FMD requires minimum data to be sent to the hub: product code, serial number, batch, and expiration date. The discussion is now around structured supply chain events – i.e., notifications when a batch leaves the manufacturer, arrives at a wholesaler, or undergoes repackaging. This is not a new data type, but rather a different level of granularity.
Secondly, a closer coupling with the European Health Data Space and supply chain transparency initiatives such as the Critical Medicines Act. The idea is that if a medicine needs to be tracked during a shortage, the path from the EMVS to aggregation dashboards should be shorter than it is today.
Thirdly, a harmonization of national hubs. The consultation raises the question of whether data schemas and interfaces should be more centrally prescribed in the future. For manufacturers operating in multiple markets, this would be a simplification – but only if their own systems are adapted to a uniform schema.
| Aspect | FMD today (as of 2019) | FMD revision (discussion status 2026) |
|---|---|---|
| Data depth | Product code, serial number, batch, expiration date | Plus structured supply chain events (manufacturer exit, wholesaler receipt, repackaging) |
| Aggregation | Individual packaging, national repositories | Case level under discussion, harmonized interfaces |
| Coupling | EMVS only | Connection to European Health Data Space and Critical Medicines Act |
| IT impact | Track-and-trace bolt-on, ERP interface | Serialization layer as a strategic data platform with API exposure |
Source: EU Commission Pharma Package 2023, public consultation 2024, EMVO materials. Classification: Discussion and draft status, not final legal situation.
The Regulatory Roadmap
The FMD didn’t come into being overnight. To understand the revision, it’s essential to look at the journey since 2011.
What Manufacturers’ IT Must Adjust Now
The operational systems for serialization have been in operation at almost all manufacturers since 2019. The question is not whether a line can code, but how robust the data chain is from the packaging process through the Level 4 repository to the national hub.
What Breaks First
- Mask integration in ERP (SAP ATTP, Oracle OPM) for new event types
- Aggregation logic when the carton level becomes mandatory
- Repackaging workflows for parallel importers
- Monitoring dashboards that only look as far as the national hub
What Already Works Today
- Event-based architectures (Kafka, Pub/Sub) instead of batch uploads
- Clean separation of master data from transactional data in serialization
- Versioned interface contracts with hubs and wholesalers
- Mock hub tests as part of the release pipeline, not as an annual exercise
In a standard setup, a Level 4 solution like SAP ATTP or TraceLink takes on the role of the central serialization repository. ATTP is tightly integrated with SAP S/4HANA, while TraceLink is often chosen for heterogeneous ERP landscapes or strong CMO networking and provides EU hub connectivity as a managed service. Both cover today’s FMD requirements in a standardized manner.
The new effort comes less from new functions than from what’s beneath the surface: Master Data Governance (are product codes and GTINs consistent?), EDI connections to wholesalers, interfaces for batch release from MES and QMS, aggregation at the pallet and shipping level. If the revision demands additional events, these transitions are the bottlenecks.
Standard Suite or Custom Development
For mid-sized companies, the architecture question regularly arises: Is the in-house solution from 2019 sufficient for the next stage of expansion, or is it time to switch to a standard suite?
Serialization is no longer just a compliance requirement. Anyone who treats the revision as a simple add-on to the existing track-and-trace solution is building a system that will be replaced again in 2028.
Standard Suite (SAP ATTP / TraceLink)
- EU hub connection as a managed service; release changes follow regulatory requirements.
- Established EDI connectors to major wholesalers and CMO networks.
- Support contracts and audit trail according to GxP logic.
- High licensing and integration costs; dependence on the vendor’s roadmap.
Custom Development / Minimal Setup
- Lower ongoing licensing costs; full control over the data model.
- Often sufficient as long as only FMD mandatory data points are relevant.
- Weakness in scaling – new events, new market connections, and EHDS interfaces require custom development.
- Validation effort and GxP documentation remain with the manufacturer.
The decisive factor rarely lies in the company size, but rather in the number of production sites, CMO partners, and target markets. The more fragmented the network, the more expensive custom development becomes, especially when the revision demands additional data points.
Where Mid-Sized Companies Realistically Struggle
In discussions with IT decision-makers at mid-sized manufacturers, a common pattern emerges. The line connection works, the hub upload runs smoothly, and verification alerts are handled. The pain point lies further back: in the data pipelines that connect serialization information to the rest of the company.
Typical gaps include inconsistent master data between ERP, MES, and Level 4 solutions. Batch information that is only partially automated from QMS releases into the serialization chain. EDI routes to wholesalers that still export shipping notices via CSV or PDF. And a repository that serves the EU hub but cannot provide clean evaluations of batch and serial number histories when a regulatory authority requests them.
When the FMD revision adds structured supply chain events in the coming years, these are exactly the points that will break. Those who manage without master data governance today will have to rework each new data point individually tomorrow. The proposed EHDS connection does not simplify the picture – it assumes that a manufacturer internally knows which data they actually have clean.
Data Points Under Discussion
The consultation responses and position papers from the EFPIA, generics associations, and the European Medicines Verification Organisation (EMVO) highlight recurring themes. These are not yet finalized changes, but they indicate the direction of the ongoing discussions.
Firstly, structured shipping events along the wholesale route. Currently, manufacturers report when a product is placed on the market, and pharmacies report when it’s dispensed. The EMVS is “blind” to the events in between. The discussion is centered around aggregation reporting at the pallet and carton level to enable faster access to inventory data during recalls and shortages.
Secondly, a cleaner integration with supply chain transparency regimes. The Critical Medicines Act aims to keep critical active ingredients and finished products under surveillance across Europe. Those already required to maintain origin data per batch will be able to provide this information from the serialization repository – assuming master data hygiene is in order.
Thirdly, closer integration with the European Health Data Space. For pharmaceuticals, this doesn’t mean verification data will be transferred to patient dossiers. The discussion revolves around aggregated consumption and inventory data, which should be made available in a structured manner to authorities and secondary research. The FMD infrastructure is a logical source for this data.
Shifting Cost Dynamics
The initial FMD investments between 2016 and 2019 were substantial for many manufacturers, ranging from six-figure to low seven-figure sums per site – including line equipment, Level 3 cameras, Level 4 repository, hub connection, and validation. Ongoing operations are significantly cheaper but still run into the mid-six-figure range per year, depending on the setup and product portfolio.
A revision will primarily alter this structure at two points. For standard suites, additional data points typically arrive via release upgrades covered by the maintenance contract – the actual work lies in customizing and validating the new configuration. For custom developments, the effort falls entirely in-house and scales with the number of connections and markets. Depending on the expansion stage, this can significantly drive up ongoing costs.
The strategic question for mid-market IT leaders is less about whether a standard suite makes financial sense, but rather when. Those who start in 2026 and plan for a two-year migration period will hit a new FMD expansion stage with a robust platform. Those who react only when the delegated acts are in place risk running into the classic bottleneck of license negotiations, integrator capacity, and audit appointments.
What this means for the next 24 months
Panic is not the right mode. The FMD infrastructure is in place, and the standard suites are delivering. The revision will come with lead times that allow for planning. What makes sense now is an honest inventory: Which data points are currently passing through the serialization repository, which ones are only partially processed, and which ones are not at all? Where are the EDI and ERP interfaces fragile?
Those who conduct this inventory properly will have a realistic basis to decide in two to three years whether the existing solution can be adapted with manageable adjustments – or whether the revision is the moment when switching to a standard suite makes more sense than the next custom-built release.
As of April 2026, no final dates have been set for extended FMD data points. Those who use the time to consolidate master data, EDI routes, and repository connections will have a solid foundation for any conceivable expansion stage, rather than patchwork solutions.
Frequently Asked Questions
What exactly is the EU Falsified Medicines Directive (FMD)?
The FMD is the EU directive to combat counterfeit medicines in the legal supply chain. Since 2019, it has obligated manufacturers of prescription human medicines to equip every pack with a unique 2D datamatrix code and a tamper-evident device. Pharmacies and clinics verify the packs via the European verification system before dispensing.
What role does the 2D code play in serialization?
The 2D datamatrix code carries the serialized pack data, typically GTIN, serial number, batch number, and expiry date. It is the central interface between manufacturers, the EU hub, and national repositories. Without a cleanly printed, machine-readable code, a pack cannot be resolved in the verification process and is considered non-dispensable.
What is the EU hub and what function does it have in the architecture?
The EU hub is the central hub operated by the European Medicines Verification Organisation, into which manufacturers upload their pack data. From there, the data is distributed to national repositories, where pharmacies and clinics perform verification. The hub is the technical foundation for any discussion about expanded data points or new verification steps.
What does aggregation mean in the pharmaceutical supply chain?
Aggregation describes the hierarchical linking of individual packs, cartons, bundles, and pallets via the serialization infrastructure. The goal is that a single scan at the pallet level can retrieve all contained packs. In several US and Asian markets, aggregation is already mandatory; in Europe, it remains optional as of April 2026 and is the subject of ongoing discussions.
What steps should IT and supply chain managers take in 2026?
An honest inventory of the serialization landscape is the starting point. Which lines print which data points, which systems write to which repository, where are EDI and ERP interfaces fragile? Based on this, it can be decided whether an existing solution can be adapted or if the upcoming revision is the right moment to switch to a standard suite.
Source title image: Pexels / Tiger Lily (px:4483941)
Editor’s Picks
More from the MBF Media Network
