Home · Learn · What Is EPCIS? The Supply Chain Visibility Standard
What Is EPCIS? The Supply Chain Visibility Standard
EPCIS lets manufacturers, wholesalers, and pharmacies share supply chain events in a common format. Required for DSCSA and EU FMD compliance, used heavily in healthcare and retail traceability.
EPCIS (Electronic Product Code Information Services) is a GS1 standard for capturing and sharing visibility data about supply chain events. Where EDI tells you 'this purchase order moved between these two companies', EPCIS tells you 'this specific serial number was commissioned at this factory, packed into this case at 14:32 UTC, shipped to this distributor, received at this dock, and dispensed at this pharmacy'. It's event-based traceability at the unit level.
EPCIS is now mandatory in two regulated supply chains: DSCSA in the US pharmaceutical industry (full enforcement May 28, 2026) and EU FMD in European pharma (live since February 2019). Outside pharma, it's used in food traceability under FSMA Section 204, in luxury goods anti-counterfeit programs, and increasingly in apparel supply chains tied to sustainability and forced-labor compliance.
The 4 dimensions of an EPCIS event
Every EPCIS event answers four questions. (1) What — which products or logistics units (identified by GTIN, SSCC, or LGTIN). (2) When — timestamp in ISO 8601 with timezone. (3) Where — read point (the specific location/sensor that triggered the event) and business location (the broader facility). Both expressed as GLNs. (4) Why — business step (e.g., 'commissioning', 'packing', 'shipping', 'receiving', 'dispensing') plus a disposition (the state of the product after the event: 'active', 'in_transit', 'destroyed'). This 'what+when+where+why' structure is what makes EPCIS different from EDI — EDI describes transactions; EPCIS describes events.
The 5 EPCIS event types
EPCIS 1.2 defines five event types. (1) ObjectEvent — covers reads of individual items or batches (e.g., a serial scanned at receiving). (2) AggregationEvent — parent-child relationships (this case contains these units, this pallet contains these cases). Used heavily in DSCSA aggregation. (3) TransactionEvent — links physical objects to business documents (this shipment fulfills purchase order 12345). (4) TransformationEvent — used when raw inputs become outputs (manufacturing, repackaging, mixing). (5) AssociationEvent (added in EPCIS 2.0) — physical-digital associations like attaching a sensor to a pallet. Most pharma DSCSA traffic uses ObjectEvent + AggregationEvent.
EPCIS 1.2 vs 2.0 — what changed
EPCIS 1.2 (released 2016) is XML-only and the version most DSCSA trading partners support today. EPCIS 2.0 (ratified 2022) adds JSON-LD encoding as a first-class peer to XML, adds the AssociationEvent type, and aligns with web-standard REST APIs. Most pharma platforms now support both. New implementations starting in 2026 should target EPCIS 2.0 JSON-LD — it integrates better with modern APIs and supports the AssociationEvent type needed for sensor-equipped supply chains. Legacy XML support is kept for backward compatibility with older trading partners.
How EPCIS gets exchanged
Two patterns dominate. (1) Direct peer-to-peer (most common in US DSCSA) — manufacturer's EPCIS repository pushes events to wholesaler's repository when a shipment leaves; wholesaler pushes downstream to dispenser when delivered. AS2 or REST API are the transports. (2) Hub-and-spoke (EU FMD model) — manufacturers upload events to the EU Hub, which syncs to national repositories (NMVSs), and dispensers query the national repository at the point of dispense. The two patterns coexist because they evolved separately; some pharma manufacturers run both to cover US + EU markets.
Major EPCIS platforms
Five vendor platforms hold the majority of the regulated pharma market: TraceLink (largest, used by ~30% of US Rx manufacturers), SAP ATTP (heavyweight pharma manufacturers running SAP ERP), Antares Vision, RFXcel, and Adents. Implementation cost ranges $200k-$2M+ depending on plant volume and integration complexity. DIY EPCIS is possible — the standard is open and there are open-source libraries — but every production pharma operation uses a vendor platform because the trading-partner integration matrix is too complex to maintain in-house.
EPCIS vs EDI — they're not the same thing
EDI describes business transactions (purchase orders, shipping notices, invoices) — flat document formats designed in the 1970s, exchanged between accounting/ERP systems. EPCIS describes physical events at the unit level — what happened to specific serial numbers, when, where. A typical pharma shipment uses BOTH: EDI 856 advance ship notice tells the wholesaler 'these cases are coming and here's the invoice'; the matching EPCIS shipping event tells the wholesaler 'these specific serial numbers are in those cases, here's their full lineage'. EDI is transactional; EPCIS is forensic.
FAQ
What does EPCIS stand for?
Electronic Product Code Information Services. It's a GS1 standard for capturing and sharing visibility data about events that happen to physical objects in the supply chain — commissioning, packing, shipping, receiving, dispensing.
What is EPCIS used for?
Three primary use cases: (1) DSCSA pharmaceutical traceability in the US — mandatory for unit-level Rx tracking from manufacturer to pharmacy. (2) EU FMD compliance — required for European pharma since 2019. (3) Food and luxury-goods traceability — FSMA Section 204 (US food), forced-labor compliance in apparel, anti-counterfeit programs. It answers the question 'where exactly has this specific unit been?'
Is EPCIS the same as EDI?
No. EDI describes business TRANSACTIONS (purchase orders, ship notices, invoices) at the document level. EPCIS describes physical EVENTS (this serial was packed at this location at this time) at the unit level. A pharma shipment typically uses both: EDI for the business paperwork, EPCIS for the unit-level visibility. They complement each other rather than overlap.
Do I need EPCIS for DSCSA?
Yes — from May 28, 2026, when the FDA Stabilization Period ended. Every authorized trading partner in the US Rx supply chain must exchange EPCIS event data: manufacturers send events to wholesalers, wholesalers send to dispensers. Small dispensers (≤25 pharmacist FTEs) have a separate FDA waiver extending some EPCIS receiving requirements through November 27, 2026 — beyond that, no exemptions for the regulated supply chain.
What's the difference between EPCIS 1.2 and EPCIS 2.0?
EPCIS 1.2 (2016) is XML-only — the version most current DSCSA trading partners support. EPCIS 2.0 (2022) adds JSON-LD as a peer encoding, adds the AssociationEvent type (for sensor-equipped supply chains), and aligns with REST API conventions. Most pharma platforms now support both. New implementations starting in 2026 should target EPCIS 2.0 JSON-LD.
Can I implement EPCIS without a vendor platform?
Technically yes — EPCIS is an open standard with open-source libraries (GS1 publishes a free EPCIS Test Bed). In practice, every production pharma operation uses a vendor platform (TraceLink, SAP ATTP, Antares Vision, RFXcel, Adents). The reason: the trading-partner integration matrix is too complex — every wholesaler and pharmacy has slightly different routing requirements, retry behavior, and validation rules. The vendor platforms maintain those integrations on your behalf. Implementation cost is $200k-$2M+ depending on plant volume.
Related generators
Need a real barcode now?
Generate a valid Data Matrix barcode in seconds — no signup, no watermark. Free for casual use; paid plans from $9/mo for higher volume.