The end of the digital leaflet vendor race — why pharma needs a standard, not a supplier.

1 · The vendor race is a trap

Walk into any European Reg Affairs or QA team today and ask about their digital leaflet plans. You will hear the same sentence: "we are benchmarking three-to-five vendors". Some are packaging specialists that bolted NFC onto existing hardware. Some are software vendors that produce ePI XML. Some are marketing agencies selling scan-to-landing-page experiences. Each holds a piece of the problem. None holds the whole.

This is the familiar pharma reflex: a new technology category emerges, procurement runs an RFP, the RFP asks for features and pricing, a winner takes the contract, the losers become a different brochure. Sixteen months later the "winning" vendor is partially deployed, does not talk to the artwork workflow, does not integrate with pharmacovigilance, does not meet the evolving CMDh readability specs — and a new RFP begins.

Digital leaflets are not a vendor category. They are infrastructure. And in infrastructure debates, the right question is not "which vendor" but "which standard".

Digital leaflets are not a vendor category. They are infrastructure.

2 · What the EU regulation is quietly forcing

Five overlapping EU instruments make the infrastructure argument unavoidable:

• EMA Mobile Scanning Guidance (EMA/493897/2015 Rev.1, November 2018) — officially authorises NFC, QR and 2D barcodes as acceptable mobile technologies in the labelling and package leaflet of centrally authorised medicines. In force today, for all centralised procedures.
• The EMA / HMA / EC Key Principles on ePI (January 2020) — establishes harmonisation, interoperability and technology neutrality as foundational requirements.
• The 2023 Pharma Package revision (COM(2023) 192, proposed Article 58(3)) — mandates that "Package leaflets made available electronically must comply with the EU ePI Common Standard once this standard is operational." One technical standard for all electronic leaflets, EU-wide. No per-vendor variants.
• The EU Accessibility Act (Directive 2019/882, enforced since 28 June 2025) — requires WCAG-compliant access, TTS audio, multi-language support. Not optional, not vendor-specific.
• Political agreement · 11 December 2025 — the Council and the European Parliament politically agreed on the pharma reform. Formal approval follows. As Commissioner Várhelyi put it: "The EU pharmaceutical reform will redefine this sector for decades to come." The reform is no longer speculative.

These texts converge on one architectural truth: every compliant digital leaflet in the EU must speak the same protocol, ingest the same regulatory signals, produce the same patient experience, maintain the same lot-level traceability, and protect the same privacy boundary.

That is not a vendor profile. That is a standard. And a standard, by definition, cannot be proprietary to 50 different suppliers.

For the complete regulatory briefing — with verbatim passages from the EMA / HMA concept papers and the COM(2023) 192 / 193 texts — see our EU ePI Regulation 2026 guide.

3 · Why fragmentation kills pharma economics

Imagine a Marketing Authorisation Holder with 60 SKUs across 12 EU Member States. The vendor logic says: contract a vendor, deploy 60 NFC-or-QR implementations, manage 720 SKU-country combinations in a custom CMS, re-negotiate pricing at each variation.

Now imagine two years pass. CMDh updates the readability guidance. The vendor has to implement — but prioritises a bigger customer. The Commission publishes v2 of the ePI Common Standard. The vendor retrofits. A product recall requires lot-level URL retirement. The vendor has no lot-level traceability, so the MAH recalls entire stock instead of affected lots. Cost: millions.

Multiply this across every MAH in Europe. Multiply it across the supply chain of printers, packagers, artwork houses. The waste is staggering — and it is precisely what happens when every actor picks a different vendor for what should be a shared standard.

Serialisation (Falsified Medicines Directive, 2019) faced the same debate. The industry picked harmonisation over vendor choice. Every MAH adopted GS1 + EMVS + NMVS. Ten years later, the fragmented alternatives have vanished. The standard won.

4 · The standard logic — and why it always wins

In every adjacent pharma infrastructure debate of the last thirty years — GS1 for barcodes, SPOR for master data, PSUR for pharmacovigilance reports, eCTD for submissions, FMD serialisation — the same pattern has repeated:

• Early phase: multiple vendors, each proprietary, each promising "full compatibility".
• Middle phase: a subset of vendors starts aligning to a common spec, while others fight for vendor lock-in.
• End phase: the standard consolidates, the standard-aligned vendors survive, the others become case studies at pharma conferences on "what not to pick".

Digital leaflets are in early-to-middle phase right now. The ePI Common Standard will consolidate. The question for pharma MAHs is not "which vendor should we pick" — it is "do we adopt the standard directly, or through a proxy vendor that may or may not survive".

5 · What makes PharmaTag the standard, not a vendor

PharmaTag is built on five architectural principles that make it a standard, not a supplier:

1. EU ePI Common Standard first. Every layer of our content stack complies with the EU ePI Common Standard as it is operationalised. No proprietary XML. No custom schema.
2. Infrastructure, not a CRM. Zero first-party patient data collection. Only anonymous scan behaviour, aggregated at SKU / lot / country / language level. GDPR Article 6(1)(f) legitimate interest by design.
3. Lot-level NFC-chip URL, not SKU-level. Every chip is unique per lot — enabling surgical recalls, expiry management and pharmacovigilance signal integrity.
4. Pharma-native integrations. Variation procedures (Type IAin / IB / II), PSUR integration, artwork workflow bridge. Not a generic IoT platform — a pharma-native stack.
5. EU-wide by default. One SaaS, 27 Member States, multi-language auto-detect, multi-SmPC synchronisation. No "international version coming Q3 2027".

6 · The call to action — and how to act on it

If you are a Reg Affairs, QA or CDO director at a pharma or Consumer Health lab in Europe, your next move is not to launch an RFP. It is to ask three questions internally:

1. Are we picking a vendor, or are we adopting the standard that will define this category for the next decade?
2. What is the architectural test that separates a vendor from a standard? Can we write that test into our procurement?
3. If the vendor we pick goes bankrupt, pivots, or is acquired, how does our ePI strategy survive?

Answer those three honestly. If the answers make the RFP logic look fragile, you are in the right frame of mind.

The follow-up reading for the next two steps is spelled out across our resources hub. Article 2 defines what an actual digital leaflet infrastructure looks like — the five-layer stack and the 10-criteria test. Article 3 gives you the eight RFP questions that separate standards from patches, ready to copy-paste.

Continue the journey