India manufactures roughly one in five of every generic medicine consumed worldwide, which means a meaningful share of Indian pharma output never touches a domestic pharmacy shelf at all — it ships to the US, the EU, or both. For a plant exporting to all three markets, track-and-trace isn't a single compliance project. It's three overlapping regimes, each written by a different regulator, each with its own identifier rules, its own verification model, and its own deadline calendar: CDSCO's domestic track-and-trace mandate, the US Drug Supply Chain Security Act (DSCSA), and the EU Falsified Medicines Directive (FMD).

The frustrating part for a packaging and quality team is that these three regimes agree on more than they disagree on — all three want a unique identifier, a 2D barcode, and batch and expiry data on the pack. But the places where they diverge are exactly the places that determine your system architecture, your data flows, and which markets a single production run can serve. This guide puts all three next to each other, then covers what Ratifye actually does to collapse them into one serialization layer instead of three.

1 pack, 3 regulators, 1 serial
A single SGTIN-serialized unit, generated once at the point of packaging, can carry everything CDSCO, DSCSA, and EU FMD each require — the difference between the three regimes is what happens to that serial downstream, not what the serial itself needs to contain.

The Core Difference in One Sentence Each

Before the detail, it's worth holding the structural difference in mind, because it explains almost everything else in this guide:

Side by Side: Identifier, Carrier, Verification, and Architecture

Dimension CDSCO (India) DSCSA (United States) EU FMD (European Union)
Scope Top 300 brand formulations (Schedule H2), with phased expansion planned to vaccines, antimicrobials, and narcotics Prescription drugs for human use moving through the US supply chain Prescription medicines, with a defined list of exempted OTC products
Identifier GTIN, brand and generic name, manufacturer details, batch, mfg/expiry dates, licence number Product identifier: NDC + unique serial number, lot, expiry (SNI) Unique identifier: product code, serial number, batch, expiry, national reimbursement number where required
Data carrier 2D barcode (QR) on primary or secondary pack 2D Data Matrix; linear/2D on homogeneous cases 2D Data Matrix, plus a mandatory anti-tampering device
Verification model Patient/pharmacist scan for authentication — no mandated repository check Transaction-based data exchange between trading partners at change of ownership Mandatory scan-and-decommission at point of dispense against a central repository
Repository / hub No domestic central repository requirement; iVEDA portal applies to export consignments Decentralized — partners exchange EPCIS data directly or via networks, no single national hub Centralized — national/supranational repositories connected through the EMVS hub
Aggregation (case/pallet) Not mandated Not legally required; widely used internally for inference Not legally required; often implemented for scanning efficiency
Status as of 2026 Top 300 rule effective since August 2023; expansion phases pending DTAB timelines Enhanced drug security requirements in force since Nov 2023; final dispenser exemptions lapsing through Nov 2025–2027 In force since Feb 2019 across most member states; a small number of national transition deadlines run through Feb 2027

What Each Regime Actually Requires, in Practice

Domestic · India
CDSCO's Top 300 / Schedule H2 Mandate
The rule under G.S.R. 823(E) requires a 2D barcode or QR code on 300 named high-selling brand formulations, carrying the GTIN, brand and generic names, manufacturer identity, batch number, manufacturing and expiry dates, and the manufacturing licence number. The code sits on the primary pack where space allows, the secondary pack otherwise. Enforcement runs through State Licensing Authorities with CDSCO oversight. Crucially, the domestic rule stops at the barcode and the data it carries — it does not mandate a central verification database or a required scan event at any specific point in the chain. For export consignments, a separate requirement applies: serialization and aggregation data must be submitted through the iVEDA portal, which is where CDSCO's export rules start to resemble DSCSA's data-exchange model more than its own domestic one.
United States
DSCSA Enhanced Drug Distribution Security
DSCSA builds unit-level traceability through transaction data, not a central lookup. Every covered transaction — manufacturer to wholesaler, wholesaler to dispenser — must carry electronic transaction information, transaction history, and a transaction statement, interoperably exchanged, typically via EPCIS. The product identifier (NDC plus unique serial number, lot, and expiry) must be verifiable on request, but DSCSA does not require a scan at the pharmacy counter for every dispensed unit the way EU FMD does. Temporary stabilization exemptions the FDA granted while industry caught up with interoperable data exchange have been lapsing through 2025, with final exemptions for qualifying small dispensers running to November 2027.
European Union
Falsified Medicines Directive (FMD)
FMD is the strictest of the three on verification. Every pack carries a unique identifier and a tamper-evident feature, uploaded by the manufacturer or marketing authorisation holder to the European Medicines Verification System (EMVS) before release. At the point of dispense, the pharmacist (or hospital, if dispensing from stock) must scan the pack, verify it against the relevant national repository connected through the EMVS hub, and decommission the identifier — the one step in any of these three regimes that is both mandatory and happens at the final point of sale. A small number of member states had deferred national transition deadlines running as late as February 2027, and Northern Ireland's safety-feature requirements lifted under the Windsor Framework from January 2025.

Where the Three Actually Conflict for a Manufacturer

None of these regimes is individually complicated once you understand its logic. The friction shows up when one plant has to serve all three at once, and it tends to show up in the same three places.

Separate serial pools per market. The most common mistake is generating a different serial number range for domestic, US, and EU-bound stock — usually because three different vendor integrations were bolted on at three different times. This multiplies the commissioning workload and makes it impossible to redirect stock between markets if a shipment is rejected or a market shifts, because the serial was never market-agnostic to begin with.

Non-GS1 serial formats. DSCSA and EU FMD both lean on GS1 standards (GTIN, SSCC) even though neither mandates GS1 by name, and CDSCO's own GTIN requirement already assumes GS1 numbering. A serialization system built on a proprietary or non-GS1 identifier scheme works until a US or EU trading partner's system can't parse it — at which point the fix is a re-serialization project, not a configuration change.

Aggregation treated as optional everywhere. Technically true — none of the three regimes legally requires case or pallet aggregation. Practically false — EU wholesalers and US trading partners increasingly expect it for operational efficiency, and without it, DSCSA's "inference" exception (which lets a dispenser infer a higher-level package's contents from its parent) stops being usable, forcing manual unit-level data entry downstream.

The compliance work is never the hard part. The hard part is that CDSCO, DSCSA, and EU FMD were each written by a regulator who had never heard of the other two, and a single packaging line has to satisfy all three without anyone noticing the seams. — Ratifye regulatory engineering team

A Single Packaging Line Strategy

The fix isn't three compliance projects running in parallel. It's one serialization layer, built to the strictest common denominator (GS1 GTIN + unique serial, 2D Data Matrix, batch and expiry) at the point of commissioning, with market-specific data and routing applied downstream rather than baked into the identifier itself. A pack commissioned this way can be:

The unit's identity never changes. Only the downstream data flow and the verification event it participates in changes, based on which market it's actually shipped to — decided as late in the process as the dispatch decision itself, not locked in at the point of printing.

How Ratifye Helps Across All Three

This is the specific problem Ratifye's serialization layer is built to collapse. Instead of three vendor integrations — one for CDSCO's domestic QR, one for DSCSA's EPCIS exchange, one for EU FMD's EMVS upload — a single commissioning event on the Ratifye platform generates a GS1-compliant SGTIN that's usable across all three regimes from day one.

CDSCO
Generates the Top 300-compliant QR payload (GTIN, names, manufacturer, batch, dates, licence number) at commissioning, and supports the iVEDA portal data format for export consignments — so domestic and export-bound stock share the same serialization event instead of two separate processes.
DSCSA
Produces EPCIS 2.0-formatted transaction events at every commissioning and shipping step, structured for interoperable exchange with US trading partners — the exact data shape DSCSA's transaction-based verification model expects, generated automatically rather than mapped manually per partner.
EU FMD
Supports upload-ready serialization data formatted for EMVS submission ahead of release, so a pack destined for an EU market carries everything its national repository needs before it ever leaves the warehouse, with decommissioning events tracked back into the same audit trail as every other market.
All Three
One audit trail across every market a product ships to, so a regulatory inspection — CDSCO, FDA, or an EU national authority — draws from the same underlying commissioning and scan-event history, instead of three disconnected systems that each tell a partial story.

The practical effect for a plant exporting to all three markets: one packaging line change, one serialization vendor relationship, and a single source of truth for every regulator who asks to see it — rather than reconciling three systems every time an auditor from a different market shows up.

Take Action

Running CDSCO, DSCSA, and EU FMD on three different systems?

Ratifye's team can map your current serialization setup against all three regimes and show exactly where a single commissioning layer replaces the separate integrations you're maintaining today.

Talk to Ratifye about export compliance

Sources: CDSCO notification G.S.R. 823(E) and published FAQs on Top 300 / Schedule H2 barcode implementation; US FDA Drug Supply Chain Security Act enhanced drug distribution security requirements and exemption timelines; EU Falsified Medicines Directive (2011/62/EU) and European Medicines Verification System (EMVS) architecture, including Windsor Framework provisions for Northern Ireland. Figures and deadlines are the most recent publicly available information at time of writing; consult primary regulatory texts and legal counsel for compliance decisions specific to your products and markets.