visibility.cloud

EDI is what the supply chain already speaks, and a standard that ignores it does not get adopted. visibility.cloud is built to interoperate with the EDI and legacy XML already in production, translating them into EPCIS 2.0 rather than asking every partner to rip out what works.

The shipment and receipt messages that move on EDI today, the advance ship notices and their equivalents, carry the same facts a capture event does: who, what, where, when and the business step. Reading those facts in and emitting them as validated EPCIS 2.0 events is how a partner still on EDI joins the record without a rebuild on their side.

Translation of EPCIS 1.1, 1.2 and 2.0 XML into 2.0 JSON-LD, with a round-trip fidelity report per job so the translation is reviewable rather than trusted, is written, verified, and live at epcis.dev/translate today. The point of this page is that the legacy formats are treated as something to translate, not something to pretend away.

← How it's captured

The ASN and the event record: where each EDI 856 fact lands in EPCIS 2.0.

EDI 856 (ASN)EPCIS 2.0What changes
BSN — shipment id, date, timebizTransactionList (the ASN as a business transaction)The paper trail joins the event instead of replacing it.
HL loops — shipment → order → packaggregation events: parentID (SSCC) ↔ child EPCsHierarchy becomes events, so breakdown and re-packing are recorded, not re-declared.
SN1 — item detail, quantitiesepcList / quantityListA count becomes serials where the goods are serialized; a count stays a count where they are not.
DTM — shipped dateeventTime — and recordTime, stamped by the gatewayTwo times, kept distinct: what the sender says happened, and when the door recorded it.
N1 — ship-from / ship-toreadPoint / bizLocation; organization-grain party fieldsPlaces and organizations, as the standard defines them; the party at every hop is derived at read time from grant chains, never stamped.
(no segment exists)who — the attested observer · capturedBy — the warrantor accountThe performer. The 856 cannot carry it, and the standard as written has no field for it; the spine’s envelope does, and the two grains are never collapsed.
Reading these facts in and emitting them as validated events is how an EDI partner joins the record without a rebuild; translation of EPCIS XML with per-job fidelity reports is live at epcis.dev/translate. Illustrative — rendered from the tested event model, the same corpus the conformance tests pass on. Not customer data, and not a customer's record: a worked figure in the record's own grammar.

See your first trace.

Capture workspaces are provisioned from the seat list — we write when your seat is ready.