Services.
A product's life does not end at the shelf: it is serviced, repaired and returned, and each of those is an event that belongs on the same record. visibility.cloud will record service and returns events against the same serial as the shipment, so an item's history is whole rather than split across a warranty system and a supply-chain one.
A repair, an inspection or a warranty action is a business step in the standard's own vocabulary, captured against the item it happened to. A returned unit's disposition, where it has been and whether it can be resold, is a custody question the record answers.
Because these events share the item's identity and the same event hash, the after-sale history and the supply-chain history are one continuous record.
The envelope, after the shelf: a repair event on the same serial the shipment used.
{ "bizStep": "repairing", "disposition": "active", "epcList": ["urn:epc:id:sgtin:0614141.107346.2017"], "eventTime": "2026-07-30T06:12:04Z", "recordTime": "(stamped by the gateway — the sender cannot set it)", "who": { "kind": "human", "role": "bench technician", "grade": "attested" }, "capturedBy": "(service-center account — the warrantor account whose key opened the door)", "party": "(derived at read time from grant chains — never stamped)" }
See your first trace.
Capture workspaces for the returns desk are provisioned from the seat list — we write when your seat is ready.