What moved.
Not a line on an invoice and not an SKU: the individual item, identified by its GTIN, its serial and its lot, so the thing in the dispute is the exact thing you can point to. visibility.cloud will track what moved down to the serial number, on every link of the chain.
The item, not the line.
A pallet is not a product and a case is not an item. Each is a distinct identity with its own custody: an SSCC on the pallet, a GTIN and serial on the unit inside it, an association between them recorded as an event. You can ask where this serial is; you can ask what was on that pallet when it crossed the dock.
Identified by the standard's own hash.
Every event carries the standardized EPCIS event hash from CBV 2.0 §8.9, with GS1 Digital Link normalization, so the same event captured twice is the same event and a changed one is different. What the item is stays stable across every system that records it.
What, by entity.
Seven kinds of thing, each with its own identity and its own custody.
- ProductsThe individual unit, by GTIN and serial number.
- PalletsThe SSCC load and what was on it when it crossed the dock.
- PackagesThe parcel, from pickup through receipt, on the record.
- ContainersThe reusable container, tracked through every custody change.
- AssetsReturnable and fixed assets, tracked through every custody change.
- ShipmentsThe consignment, from dispatch to receipt, seam by seam.
- ServicesThe field, repair and returns events, against the same serial.
The standard gives you this dimension. Here is what it still can't tell you.
EPCIS 2.0 §7.2.2 defines five event dimensions — and no performer is among them. The record can say a company did a process. It cannot say who observed the event. That answer has its own door.
what: answered — sgtin:0614141.107346.2017 · lot 7A-4412 who: (no field exists in the standard)
See your first trace.
Your capture workspace is provisioned from the seat list — we write when your seat is ready.