EPCIS 2.0: every partner's events in one place

EPCIS 2.0: every partner's events in one place

Through Transpareo’s EPCIS 2.0 interface, your factory, carrier and warehouse report their events to where your product passports live.

Tuesday, 6.40 am, bay 3 at a warehouse near Basel. A lorry delivers a pallet of 48 e-bike batteries from the assembly plant, the scanner beeps, and the warehouse management system books the goods in. Three systems have seen these batteries by now: the production control system at the plant, the carrier’s shipment system and now the warehouse. Each knows its own stretch of the journey.

From now on, those stretches come together in Transpareo. Every workspace has an interface for EPCIS 2.0, GS1’s standard for supply chain events. The plant, the carrier and the warehouse report their events to where the batteries’ product passports live, and you build a separate integration for none of the three.

One format for plant, carrier and warehouse

EPCIS stands for Electronic Product Code Information Services. An EPCIS event answers four questions: which products, when, where and why. The why is the business step, such as commissioning, shipping or receiving, together with the state the product is in afterwards. Wherever systems exchange supply chain events today, and in pharmaceutical logistics they have done so for years, many of them already speak EPCIS.

Without a shared format, every partner needs its own route: a spreadsheet emailed from the plant, an export file from the carrier, a report from the warehouse, each with its own columns. In Transpareo, every partner gets its own access to your workspace’s interface and reports its events in EPCIS. The interface is part of Transpareo Connect, and the batteries’ master data from your ERP system keeps arriving the way it always has.

What a supplier knows about the batteries, such as their weight or where the cells come from, reaches you by a route of its own. With Transpareo Upstream you request that data directly from your suppliers, someone there enters it, and you review the answer before it goes into the passport. Through EPCIS, your partners’ systems report what happens to the batteries: assembled, shipped, received.

A new partner needs nothing more than an access.

The plant sends a whole shift’s assembly in one delivery, up to 10,000 events at once. Transpareo checks every event against GS1’s schema. At the partner’s choice, the delivery counts in full or not at all, or Transpareo takes every valid event and names the faulty ones.

Every event finds its product passport

An event names the products by their identifiers: the GTIN together with the serial number of a single battery, or with its batch. That is how Transpareo finds the product passport, and e-bike batteries need a passport of their own from 18 February 2027. Whether the carrier writes a battery as an EPC identifier or as a GS1 Digital Link, as in the passport’s QR code, both lead to the same passport.

If the plant reports batteries whose passport has not been created yet, nothing is lost. The events are kept, and once the passport exists, a query about it finds them too.

The same query also returns the passport’s own public events, such as its publication, a repair or its recycling. Each arrives as the passport’s events file signed it, with its signature, which the recipient can verify.

One query shows a battery’s whole journey: what the partners reported and what its passport signed.

What a partner reports stands beside the passport. A goods receipt therefore does not appear by itself in the public passport that customers, repair shops and authorities read. That would have been quicker to build, and we decided against it: a signed product passport is a document you stand behind, and a partner’s report remains that partner’s statement.

If a partner gets something wrong, it corrects its event with an error declaration, as EPCIS provides for. The original event stays, the correction stands beside it, and anyone who queries sees both.

Query, save, subscribe

Your own systems query the same events, and so do your partners, within the limits of their access. A query selects by product, serial number or batch, by period, business step, location or state. Your customer service can see when a customer’s battery left the warehouse without phoning the carrier.

A query you need again and again, you save under a name and subscribe to. Transpareo then delivers the new events as soon as they arrive, or on a schedule, say every morning at the same time. If the recipient sets a secret, every delivery carries a signature that shows it came from your workspace.

Your ERP system learns of the goods receipt in Basel without anyone forwarding a file.

Who sees what

Every access has its own rights, and reading events and reporting events are two separate rights. You can also limit an access to particular passports. The carrier then reads the events about the batteries whose passports you share with it, and what it has reported itself.

A partner sees exactly the products you share with it.

The events are held in the EU, in your workspace’s own database, like all your data in Transpareo.

Why the standard matters

A partner whose system is built to GS1’s description should be able to talk to your workspace with nobody adjusting anything. So the interface follows the binding GS1 publishes for EPCIS 2.0, down to its error messages.

A standard only helps you once your partner speaks it as it is written.

Before every new version, automated tests check the interface’s responses against GS1’s description and schemas. In a few places the description is incomplete or contradicts the text of the standard. There we follow the standard, and a test speaks up as soon as GS1 corrects the passage.

Where we depart on purpose, or leave out an option the standard makes optional, three points matter most for a partner about to connect its system:

  • The interface speaks JSON and JSON-LD, the two formats the standard requires for this binding. It does not offer XML, which the standard leaves optional.
  • Identifiers come back as GS1 Digital Links, the standard’s default, or on request as the partner reported them. Converting every identifier to the EPC notation is not on offer.
  • Subscriptions deliver to an address of your choice, and only over an encrypted connection (https). We do not offer the optional delivery over WebSocket.

Developers can read in the guide of Transpareo’s API documentation how a partner’s system signs in with its access and where else the interface departs from the standard.

Back at the loading bay

At 6.41 am the warehouse reported the goods receipt, and shortly afterwards your ERP system knows about it, through its subscription. Anyone who asks about the serial number of one of the 48 batteries sees its journey: assembled at the plant, packed onto the pallet, taken over by the carrier, arrived in Basel, and beside it the signed events of its passport.

All the carrier needed for this was an access, and it reports in the format its system speaks anyway.

Questions on this article

What is EPCIS 2.0?

EPCIS 2.0 is GS1’s standard for supply chain events, ratified in 2022. An event records which products were captured, when, where and at which business step, and the state they are in afterwards. Version 2.0 added JSON and JSON-LD as formats and a REST interface through which systems report and query events.

Do I need an EPCIS repository of my own?

No. Every workspace in Transpareo has one, at its own address. It accepts events, keeps them and answers queries. Your partners report to it, and your own systems query it.

Does a reported event change my product passport?

No. A reported event stands beside the passport and finds it by the passport’s identifier. The passport’s signed history, and the passport your customers read, stay as you published them.

How does a partner connect its system?

You create an access for programs for the partner and give it the right to report events, and the right to read them if you wish. With the key and secret, its system obtains an access token and reports its events as an EPCIS document to your workspace’s address. If its system already speaks EPCIS 2.0, all it needs is the address and the access.

How does Transpareo check that the interface follows the standard?

Before every new version, automated tests check the responses of every operation against the OpenAPI description and the JSON schemas GS1 publishes for EPCIS 2.0. Where the description is incomplete or contradicts the text of the standard, we follow the standard, and a test speaks up as soon as GS1 corrects the passage. Where the interface departs from the standard, the API documentation names each place.

News from Transpareo Connect, as soon as it ships

We write about what we build and why, in plain language.