One run went bad.
You withdrew all of them.

Your record knows the lot, or the production day, or the shipment that left the dock. It does not know the case. So the boundary of the withdrawal gets drawn where the record stops resolving, and everything inside that boundary comes back — including all of it that was fine. The difference between the two boundaries is the whole bill: the product, the freight both ways, the disposal, the weeks of supply, and the conversation with the retailer afterward.

It is not a data-quality problem and it is not an integration problem. Both of those assume the information existed and something went wrong on the way to using it. More data does not fix it. Better data does not fix it. Fourteen more connectors do not fix it, and neither will the fifteenth. Every one of those systems is downstream of a barcode that names a kind, and a system cannot report a distinction its inputs never carried.

And the trace-back is worst exactly where you do not own the building. A co-manufacturer’s record says a legal entity received a pallet; a franchisee’s says the same. Both are true, both are useless the moment they are contested, and a company has no hands.

the validator door →

visibility.cloud will record the handoff at the grain you withdraw at — the case, the pallet, the unit — and will put an attested observer on every event, kept distinct from capturedBy, the account that stands behind the capture. That two-grain record is not a sketch: the capture spine already writes both, taking the observer from the capture and stamping capturedBy server-side, and the tests that hold that line pass today. What remains is the door: the hosted capture spine answers at api.epcis.dev to a capture key, and issuing those keys is not open yet. When it is, the trace-back that ran for days across a co-manufacturer or a franchise boundary is a query, and the boundary of the withdrawal is drawn where the goods actually went.

FSMA 204 is the return, never the urgency. The enforcement floor moved to July 2028 and FDA is actively soliciting further flexibilities, so the rule’s own record is softening rather than hardening. Anyone selling you that date as a gun to your head is one search away from being caught. Use FSMA 204 for operational return and GS1’s Sunrise 2027 for timing, never the reverse.

The answer products this read lands on — the trace, the custody evidence pack, the exception view — each carry a named entry in this page, and the answers page names which. What you can exercise today is on this page’s buildline.

From the end of December 2027, under GS1’s Sunrise program, retail point of sale is expected to scan and process 2D barcodes as well as the linear ones. A 2D symbol on a consumer pack can carry the GTIN, the serial, the batch or lot, and the expiry date, in one scan, at the same counter, on the same hardware. The register needs the GTIN. It has no field for the rest and no reason to keep it.

So the fork is the whole idea, and it is deliberately unambitious: the GTIN goes where it already goes, and the serial, the lot and the expiry go to your record instead of to the floor. Nobody scans differently. Nothing new is bought for the lane. The date is already on somebody’s plan in your company, because the artwork has to change anyway.

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