Every day, pharmacies, hospitals and wholesalers across Europe scan genuine medicine packs and get an alert from their national medicines verification system (NMVS) that says the pack may be falsified. The European Medicines Verification System (EMVS) handles about 14 billion transactions a year, and EMVO reported an alert rate of 0.08% in December 2025, according to its EMVO and EMVS update at the EMVS Forum 2026. If that rate held across all transactions, it would mean roughly 11 million alerts a year (our arithmetic). The European Commission says plainly that many automated alerts are not subsequently confirmed as falsified medicines.
Each alert costs the marketing authorisation holder (MAH) investigation time and holds a pack out of stock, which in tight supply can delay a patient's medicine. Alert handling is one part of the wider set of serialisation and verification rules covered in Zelthy's guide to global pharmaceutical traceability.
Zelthy is an AI-native Platform-as-a-Service for pharmaceutical and life sciences operations, built on the open-source Zango framework, and its Traceability & Supply Chain vertical covers serialized tracking, GS1 data and track and trace workflows. This post covers what an EU FMD alert is under Delegated Regulation (EU) 2016/161, what the 2025 to 2026 statistics show, a root-cause table with the owner and fix for each alert type, and a reduction playbook for manufacturers and wholesalers.
A note on terms: "false positive" is industry shorthand. Legally, every alert is a potential incident of falsification until an investigation finds a technical or procedural cause.
What is an EU FMD alert, and why are most not falsifications?
An EU FMD alert is raised when the repositories system cannot confirm that a pack's unique identifier is authentic. Most alerts are not falsifications because the system compares a scan with uploaded data: any mismatch in the data, the scanner or the pack's recorded status triggers the same alert as a fake would.
Article 36(b) of Commission Delegated Regulation (EU) 2016/161 requires the system to trigger an alert "when such verification fails to confirm that the unique identifier is authentic", and states that "such an event shall be flagged in the system as a potential incident of falsification". Article 37(d) requires "the immediate investigation of all potential incidents of falsification flagged in the system". Articles 24 and 30 bar wholesalers and persons supplying the public from supplying a product they have reason to believe is not authentic.
In EMVO's terminology these are Level 5 alerts. EMVO's Best Practice on Alert Handling (v2.0, 2021) defines a Level 5 alert as one "generated when the EMVS detects a potential suspected falsification". The common codes are:
- A2: batch not found for the product code.
- A3: pack (serial number) not found.
- A7: pack already in the requested state, for example already supplied.
- A24: status change could not be performed, typically an attempt to decommission a pack already decommissioned.
- A52: expiry date mismatch with the uploaded data.
- A68: batch number mismatch with the uploaded data.
EMVO itself is clear about the limits of the signal. Its Best Practice on Alert Handling states that "the EMVS can never determine the falsified status of the pack with absolute certainty."" Leonie Clarke, Chief Executive of the Irish Medicines Verification Organisation (IMVO), put the balance this way in an October 2025 presentation: falsification is "very rare but has to be considered if no plausible root cause can be identified".
What the EMVS alert statistics show in 2025 and 2026
EMVS alert rates have fallen to 0.08% in December 2025, a 56% drop since January 2023, according to EMVO. The European average is still above EMVO's 0.05% target, and some countries remain well above it.
Two caveats apply. NMVOs do not all measure alert rate the same way (per scan, per transaction, end users only), so compare trends within a source rather than across sources. And the remaining alerts are harder to remove: IMVO reports that Ireland's end-user rate has settled at about 0.01% to 0.02% "as controllable factors are now well managed", with medicine shortages and borrowed packs now driving alerts.
The most detailed recent breakdown comes from Bulgaria. A peer-reviewed 2026 study in Pharmacia classified Q4 2024 alerts as 73.57% technical and 26.43% procedural. By code, A3 (pack not found) made up 40.26%, A68 (batch mismatch) 27.33%, A7/A24 (status conflicts) 26.43%, A2 (batch not found) 5.75% and A52 (expiry mismatch) 0.23%.

What causes NMVS alerts? Root causes by owner
NMVS alerts come from four places: MAH master and pack data, end-user scanners and software, procedural errors in pharmacies, hospitals and wholesalers, and, rarely, the systems themselves. The fastest fix is to route each alert code to the party that owns the defect.
The table below draws on EMVO's Best Practice on Alert Handling, the Commission's 2024 report, IMVO's 2025 data and BeMVO's alert management guidance.
Three newer drivers deserve attention. First, shortages push pharmacies to borrow stock from each other, and IMVO now calls borrowed packs the most common procedural issue in Ireland. Second, since the Windsor Framework arrangements for medicines took effect on 1 January 2025, UK packs scanned in Ireland generate alerts or exceptions, according to IMVO. Third, inter-market transactions (IMT), where a pack is scanned outside the market it was uploaded for, can raise alerts in more than one national system, and the EAMS Handbook assigns the investigation to the initiating market.
How to reduce EU FMD alerts: a playbook for manufacturers and wholesalers
To reduce EU FMD alerts, manufacturers should make EU Hub upload confirmation a batch release condition and respond to every alert within two working days, while wholesalers should run alerts through their quality complaints process and control repeat scans. Both should track alert rate by code and owner each month.
For manufacturers (MAHs and their OBPs):
- Gate release on upload. EMVO lists late or incorrect pack data uploads as an MAH root cause. Make the EU Hub upload confirmation, for every target market, a release checklist item.
- Reconcile master data. Compare product code, batch, expiry and market assignment in the master data against the packaging record. EMVO's 2026 work programme includes a Master Data Office, a sign of how much this still matters.
- Meet the response clock. EMVO best practice expects MAH feedback "within 2 working days of the alert being generated". This is guidance, not a regulatory deadline, and national rules differ: BeMVO escalates unresolved alerts to the national competent authority after five days.
- Use the alert management system. The European Alert Management System (EAMS) links the AMS Hub with national AMSs for Level 5 alerts. The EAMS Handbook notes it is "not a mandatory system", so check which markets use it.
- Trend by code. Rising A68 points to the packaging line; rising A3 in one market points to uploads or scanners there.
For wholesalers:
- Treat alerts as quality events. EMVO states that "alerts generated by wholesalers should be managed as part of their product quality complaints processes."
- Control repeat scans and hospital aggregation steps, which IMVO lists among current wholesaler errors.
- Keep decommissioned returns out of saleable stock, and use the Article 13 window: a decommissioned status can be reverted "not more than 10 days after the unique identifier was decommissioned" under Delegated Regulation 2016/161.
For pharmacies, hospitals and software vendors: test scanners after every setup change, check keyboard layout and case handling, and automate the undo where the national system allows it.

The same discipline applies in the US, where serialisation exceptions under DSCSA need a comparable owner-based process; see the Zelthy post on DSCSA exception handling. Zelthy's executive guide to traceability implementation covers the organisational side.
On Zelthy, teams can configure an alert triage workflow that takes alert notifications from their OBP or alert management system, assigns each alert by code to an owner, tracks the response clock and records root cause and corrective action. Teams can also configure a release check that compares released batches against upload confirmations and market assignments. Zelthy works at the data, workflow and reporting layer; it does not replace the EMVS, the NMVS or the OBP connection. See the Zelthy traceability solution for the wider scope.
What teams have delivered on Zelthy in supply chain
Zelthy does not yet have a published metric for EU FMD alert reduction, so this section uses only results that have been approved for publication. A blockchain-based supply chain platform deployed on Zelthy delivered 15% fewer stockouts and 25% faster inventory turnover. A vaccine ordering portal built on Zelthy served 3,000+ clinics and processed 12,000+ orders in six months, with 15% faster order-to-delivery and 25% more repeat orders. Across verticals, more than 300 applications have been deployed on Zelthy in 12+ countries, reaching more than 1 million patients. Zelthy customers include Roche, AstraZeneca, Pfizer, Cipla and DKSH.
The relevance is the pattern, not the number: shared data and workflow in one place make exceptions visible and owned, which is what alert routing needs.
If your team is rebuilding how serialisation alerts and exceptions are triaged across markets, talk to Zelthy about a workflow review.
Frequently asked questions
What is a Level 5 alert in the EMVS?
A Level 5 alert is raised when the EMVS detects a potential suspected falsification, for example an unknown serial number or a batch mismatch. It notifies the user who scanned the pack, the national verification organisation, EMVO and the product's marketing authorisation holder. It must be investigated before the pack is supplied.
Why do genuine medicine packs trigger EU FMD alerts?
The system compares each scan with the data the manufacturer uploaded and with the pack's recorded status. Missing or wrong uploads, scanner settings that change characters, and packs scanned or decommissioned twice all produce the same alert as a fake pack would. In Bulgaria in Q4 2024, 73.57% of alerts were technical and 26.43% procedural.
What is the current EU FMD alert rate?
EMVO reported an EMVS alert rate of 0.08% in December 2025, down 56% since January 2023, across about 14 billion transactions a year. The target agreed in EMVO is 0.05% or lower. National rates vary, from about 0.01% to 0.02% in Ireland to 1.17% in one country in March 2024.
How fast must a manufacturer respond to an NMVS alert?
EMVO best practice expects the marketing authorisation holder to give feedback within two working days of the alert being generated, with progress reports if it is not resolved. This is guidance rather than a rule in the regulation, and national timelines differ. In Belgium, for example, unresolved alerts escalate to the competent authority after five days.
Can a pharmacy dispense a pack after an FMD alert?
The pack should be withheld until the alert is investigated. If the investigation finds a technical or procedural cause and falsification is not suspected, national rules generally allow the pack to be supplied. Check your national verification organisation's guidance, because practices differ between member states.
This article is for information only and is not legal advice. Check national NMVO rules and your competent authority's requirements for your markets.
Sources
- Commission Delegated Regulation (EU) 2016/161, EUR-Lex, 2 October 2015.
- Report on trends in the falsification of medicinal products, COM(2024) 274 final, European Commission, 4 July 2024.
- EMVO and EMVS Update, EMVS Forum 2026, EMVO (hosted by the Council of Europe), 2026.
- Best Practice on Alert Handling, EMVO-00306 v2.0, EMVO, June 2021.
- EAMS Handbook for MAHs, EMVO-01392 v3.0, EMVO, September 2023.
- Leonie Clarke, FMD refresher and update, IMVO presentation to IIOP, 8 October 2025.
- Alert management and quarantine under full EU FMD, BeMVO webinar, December 2023.
- Milushewa P., Alexandrova J., Paunova I., Todorova A., Effectiveness of the medicines verification system in Bulgaria: analysis of system connectivity and verification alerts, Pharmacia 73: e192565, 2026. doi.org/10.3897/pharmacia.73.e192565



