Interoperability includes meaning
Two systems can exchange a file successfully and still interpret its content differently. A field called “location” might mean a facility, a shelf or a legal address. A “batch” field may refer to a supplier lot in one system and a production run in another.
Start with a shared mapping of objects, events and relationships. Identify which system creates each record and which systems consume it. Define what happens when a reference is unknown or ambiguous.
Preserve identifiers across boundaries
Map local references deliberately and retain their original context. Document whether a partner can resolve your internal lot reference, or whether the exchange must include the supplier’s identifier as well.
A new interface should not silently truncate codes, strip leading zeroes or change case where these differences matter. Test the full range of real identifiers, including legacy records and corrections.
Where standards help
GS1 EPCIS provides a common model and interfaces for exchanging visibility events. GS1’s Core Business Vocabulary supplies shared vocabulary used with EPCIS. These tools can reduce bespoke interpretation when partners agree on their use.
They do not remove the need to map your processes correctly. An event with a valid structure can still carry the wrong identifier or describe the wrong business step. Follow the authoritative specification and the agreed implementation profile.
Plan for unreliable exchange
Define retries, duplicate handling, late delivery and monitoring. Use stable references so repeated transmission does not create duplicate activity. Keep error details useful enough for the sending party to correct the problem.
Consider offline production and receiving. A delayed event should retain its occurrence time and provenance. Reconcile events when connectivity returns rather than rewriting the physical sequence around upload time.
A partner acceptance test
Exchange a receipt, a transformation, a dispatch and a correction. Ask the receiving team to explain what happened using its own interface. Compare its interpretation with the sending system and source evidence.
Repeat the test for an unknown identifier and an incomplete relationship. Good interoperability makes these failures visible. Continue with event design and software evaluation before extending the integration to more partners.
Frequently asked questions
Does a successful API request prove interoperability?
It proves a technical exchange succeeded. Partners still need to interpret identity, units, time and business context consistently. Test the receiving application’s explanation of the event against its source.
Is EPCIS itself a legal requirement?
EPCIS is a formal GS1 standard. Whether an operation must use a particular standard depends on its applicable legal, contractual or scheme requirements. Do not infer a legal duty merely from the existence of the standard.
Sources and scope
Primary references checked on 4 October 2026. The process examples and implementation suggestions are editorial guidance. Formal standards are distinct from legal requirements.