First EU DPP deadline (Batteries): 89 days Get compliant now
Language
EN DE FR IT ES NL PL BG CS DA EL ET FI HR HU LT LV MT PT RO SK SL SV
Product
Features After-sales How It Works Demo Enterprise Pricing
Sectors
All Sectors Textiles Electronics Batteries
Resources
Blog Compare DPP Software Country Requirements DPP timeline Readiness Assessment Green claims checker Free Downloads Glossary
Company
Partners Contact
Sign in Get Started Free

GS1 EPCIS and Supply Chain Event Data for DPPs

MyProductPassport 14 Aug 2025 Updated 20 Nov 2026 11 min read

Why Supply Chain Event Data Matters for Digital Product Passports

Digital Product Passports are far more than static product descriptions. They are living records that must capture what happened to a product, where it happened, when it happened, and why. This event-driven approach to product data is precisely what the GS1 EPCIS standard was designed to deliver. As the EU's Ecodesign for Sustainable Products Regulation moves towards full implementation, understanding how EPCIS underpins supply chain traceability becomes essential for every manufacturer and brand.

The challenge facing businesses today is not simply collecting product data but capturing the dynamic journey of goods as they move through complex, multi-tier supply chains. A garment might pass through cotton farms, spinning mills, dyeing facilities, cut-and-sew factories, distribution centres, and retail outlets before reaching the consumer. Each of these touchpoints generates event data that contributes to the product's full provenance story. Without a standardised framework for capturing this information, businesses are left with fragmented, incompatible data silos that cannot support meaningful transparency.

EPCIS, the Electronic Product Code Information Services standard, provides exactly this framework. It offers a common language for describing supply chain events in a way that is interoperable across organisations, industries, and geographies. For Digital Product Passports, EPCIS serves as the event backbone, transforming a passport from a simple data sheet into a comprehensive, verifiable record of a product's entire lifecycle.

What Is GS1 EPCIS and How Does It Work

GS1 EPCIS is an open, royalty-free standard that enables trading partners to share information about the physical movement and status of products as they travel through the supply chain. At its core, EPCIS answers four fundamental questions about any supply chain event, often referred to as the four dimensions of visibility:

  • What, which specific products or items were involved in the event, identified using GS1 identifiers such as GTINs, SGTINs, or SSCCs
  • When, the precise date and time the event occurred, recorded in a standardised timestamp format
  • Where, the physical or digital location where the event took place, identified using GLN (Global Location Numbers)
  • Why, the business context of the event, such as shipping, receiving, transforming, or destroying goods

The current version, EPCIS 2.0, represents a significant advancement over earlier iterations. It introduces a RESTful web API, JSON and JSON-LD data formats alongside traditional XML, and improved support for Internet of Things (IoT) sensor data. These enhancements make EPCIS far more accessible to modern software architectures and align it naturally with the technical requirements of Digital Product Passport systems.

EPCIS operates through a capture-and-query model. At each point in the supply chain, an EPCIS Capturing Application records events and stores them in an EPCIS Repository. Downstream, an EPCIS Accessing Application queries these repositories to retrieve event histories. This decentralised architecture means that no single organisation needs to hold all the data, instead, authorised parties can access the specific event information they need.

The Four EPCIS Event Types Explained

EPCIS defines four primary event types, each capturing a different aspect of supply chain activity. Understanding these event types is critical for designing DPP data architectures that can faithfully represent a product's journey from cradle to grave.

The ObjectEvent records actions performed on one or more physical or digital objects. This is the most commonly used event type and covers scenarios such as commissioning a new product (assigning it an identifier for the first time), observing it at a checkpoint, or decommissioning it at end-of-life. Every time a product is scanned at a warehouse dock door or counted during inventory, an ObjectEvent captures that moment.

The AggregationEvent describes the packing and unpacking of items, when individual products are placed into cases, cases onto pallets, or pallets into containers. This hierarchical containment information is vital for logistics efficiency and for understanding how individual items relate to their shipping units. For DPPs, aggregation data helps trace which specific products were part of which shipments.

The TransactionEvent links physical products to business transactions such as purchase orders, invoices, or despatch advices. This connection between the physical and commercial worlds enables businesses to reconcile what was ordered with what was actually shipped and received, providing an audit trail that supports ESPR compliance requirements.

The TransformationEvent captures manufacturing and processing steps where input products are consumed to create output products. A furniture manufacturer, for example, would use TransformationEvents to record how timber, adhesive, and hardware components were combined to produce a finished table. This event type is particularly important for DPPs because it establishes the material composition and provenance links that regulators require.

Mapping EPCIS Events to DPP Data Requirements

The ESPR regulation mandates that Digital Product Passports contain specific categories of information, many of which map directly to EPCIS event data. Understanding these mappings helps businesses design efficient data collection strategies that serve both operational and regulatory purposes simultaneously.

Provenance and origin information, a core DPP requirement, is captured through the chain of ObjectEvents and TransformationEvents that trace a product's components back to their source. When a cotton bale is observed at a farm (ObjectEvent), processed at a spinning mill (TransformationEvent), and the resulting yarn is observed at a fabric mill (ObjectEvent), each event contributes to the complete provenance record.

Manufacturing and processing history is similarly documented through TransformationEvents. These events record not just what went in and what came out but can also capture process parameters through EPCIS sensor data extensions, temperature profiles during curing, energy consumption during processing, or emissions generated during manufacturing. This granular operational data directly supports the environmental footprint disclosures that the ESPR requires.

Chain of custody and ownership transfers are captured through combinations of ObjectEvents (with business steps like "shipping" and "receiving") and TransactionEvents. For products where serialisation is required, this event chain creates an unbroken record of every party that handled the product, from manufacturer through to the point of sale.

End-of-life and circularity data, increasingly important under the ESPR's circular economy objectives, can be recorded through ObjectEvents documenting collection, sorting, and recycling activities, as well as TransformationEvents capturing the conversion of waste materials into secondary raw materials.

Implementing EPCIS Data Collection Across Supply Chains

Deploying EPCIS across a multi-tier supply chain is a significant undertaking that requires careful planning, stakeholder engagement, and phased implementation. The following approach has proven effective for organisations building DPP-ready supply chain visibility:

  • Start by mapping critical supply chain nodes, identify the key points where event data must be captured to satisfy DPP requirements, focusing initially on your own operations before extending to suppliers
  • Establish GS1 identification at every level, ensure products, locations, and logistics units are identified using GTINs, GLNs, and SSCCs before attempting to capture events
  • Deploy capture infrastructure at priority nodes, install barcode scanners, RFID readers, or IoT sensors at the locations you have identified as critical, beginning with facilities you directly control
  • Implement EPCIS repositories, set up centralised or federated EPCIS data stores that can receive, validate, and persist event data from capturing applications
  • Onboard supply chain partners systematically, work with first-tier suppliers to extend EPCIS capture to their operations, providing technical guidance and potentially shared infrastructure

One of the most challenging aspects of EPCIS implementation is achieving consistency across diverse supply chain partners with varying levels of technical maturity. Cloud-based EPCIS platforms have emerged as a practical solution, offering hosted repositories and simplified capture interfaces that lower the barrier to entry for smaller suppliers. Many of these platforms provide pre-built integrations with common enterprise resource planning and warehouse management systems, reducing the development effort required.

Data quality governance is equally important. EPCIS events are only valuable if they are accurate, timely, and complete. Organisations should establish clear data quality metrics, implement automated validation rules in their EPCIS infrastructure, and conduct regular audits to identify and remediate data gaps.

EPCIS and Interoperability with DPP Systems

One of EPCIS's greatest strengths for Digital Product Passport implementations is its inherent interoperability. As an open standard maintained by GS1, EPCIS provides a vendor-neutral data format that any system can produce and consume. This is critically important in the DPP context, where data must flow between manufacturers, suppliers, regulators, recyclers, and consumers.

EPCIS 2.0's support for JSON-LD is particularly significant for DPP systems. JSON-LD (JavaScript Object Notation for Linked Data) enables EPCIS events to be published as semantic web data, making them discoverable and queryable by machines without prior agreement on data schemas. This aligns with the European Commission's vision for a decentralised DPP ecosystem where product data can be accessed through standardised interfaces.

The combination of EPCIS with GS1 Digital Link creates a particularly powerful architecture for DPPs. Digital Link provides the URI-based product identifiers that serve as the entry point for accessing passport data, while EPCIS provides the event history that populates the passport's traceability sections. Together, these standards enable a consumer to scan a product's QR code and access not just static product information but a verified record of that specific item's journey through the supply chain.

Platforms like MyProductPassport are designed to integrate with EPCIS data feeds, enabling businesses to automatically populate their Digital Product Passports with supply chain event data as it is captured. This integration eliminates the manual data entry that would otherwise be required and ensures that passport information remains current and accurate.

Sensor Data and IoT Integration Through EPCIS

EPCIS 2.0 introduced formal support for sensor data, recognising that modern supply chains generate vast quantities of environmental and condition monitoring data that is relevant to product traceability. This capability is particularly valuable for DPPs, which may need to document the conditions under which products were manufactured, stored, and transported.

Sensor data elements in EPCIS can capture temperature, humidity, pressure, shock, tilt, and numerous other physical measurements. For food and pharmaceutical products, this cold chain monitoring data provides evidence that products were maintained within required temperature ranges throughout distribution. For industrial products, sensor data can document the environmental conditions during manufacturing processes that affect product quality and durability.

The integration of IoT devices with EPCIS infrastructure creates opportunities for automated, continuous event capture without human intervention. Smart factory equipment can generate TransformationEvents as products move through production lines, while connected logistics assets can generate ObjectEvents with sensor readings as goods transit between facilities. This automation improves data completeness and timeliness while reducing the labour cost of supply chain visibility.

Challenges and Best Practices for EPCIS Adoption

Despite its clear benefits, EPCIS adoption is not without challenges. Supply chain complexity, legacy infrastructure, and the need for cross-organisational coordination all present obstacles that businesses must navigate thoughtfully.

  • Data sovereignty and privacy, EPCIS events may contain commercially sensitive information about supplier relationships, production volumes, and logistics routes, requiring careful access control and data sharing agreements
  • Legacy system integration, many supply chain partners operate older systems that were not designed to generate EPCIS events, necessitating middleware solutions or manual capture processes
  • Scalability, high-volume supply chains can generate millions of events daily, requiring robust infrastructure for capture, storage, and query performance
  • Standardisation of business context, while EPCIS defines event structures, organisations must agree on the specific business steps, dispositions, and master data vocabularies they will use

Best practices for successful EPCIS adoption include starting with a focused pilot that demonstrates value before scaling, investing in training and change management for supply chain partners, and leveraging industry-specific implementation guidelines published by GS1 member organisations. The GS1 CBV (Core Business Vocabulary) standard provides a ready-made set of business step and disposition identifiers that promote consistency across implementations.

As the ESPR regulation moves from policy to practice, businesses that have already invested in EPCIS-based supply chain visibility will find themselves well positioned to meet DPP requirements efficiently. Those that have not should begin planning their EPCIS strategy now, recognising that building comprehensive supply chain traceability is a multi-year journey that cannot be rushed when compliance deadlines arrive.

Looking Ahead: The Future of Event-Driven Product Passports

The convergence of EPCIS, Digital Product Passports, and emerging technologies such as blockchain, artificial intelligence, and digital twins points towards a future where product traceability is continuous, automated, and verifiable. EPCIS events recorded on distributed ledger technologies could provide immutable proof of supply chain activities, while AI could analyse event patterns to identify anomalies, predict risks, and optimise supply chain performance.

For businesses preparing for DPP compliance, the message is clear: invest in standardised event data capture today, and you will build a foundation that supports not only regulatory requirements but also operational excellence, consumer trust, and competitive differentiation. EPCIS is not merely a compliance tool, it is a strategic asset that transforms supply chain data from a cost centre into a source of value.

Link copied to clipboard
MP

MyProductPassport

Digital Product Passports

Helping businesses navigate Digital Product Passport requirements, ESPR compliance, and sustainable product transparency.