Every scan is a question.

The barcode is not unreadable. It is read constantly — more often than any other act in your business. It is not inaccurate; it is one of the most reliable pieces of engineering in commercial history. It is not proprietary, or hidden, or withheld by anybody.

It answers what kind of thing is this with total precision and total reliability, and it has no capacity whatsoever to answer which one.

Inside your own four walls, you can reconstruct a run. The trouble starts at the door.

The carrier's system says one thing. The 3PL's says another. The four hours between pickup and cross-dock exist properly in neither, because each side recorded its own half and nobody recorded the seam. When the auditor asks who had custody of this lot at 14:20, that seam is what you hand them.

And the fix has a way of going quiet. Visibility programs tend to stop the month the capture bill lands — not because anyone decided the evidence was worthless, but because the line item grew with volume and the answers did not.

The barcode that could not say which one, and the record that cannot say who, are the same defect at two different grains.

A record that names a kind of thing, performed by a kind of party. Categories all the way down, in a world where the questions being asked are about individuals.

Energy and silicon become tokens, and that trade is metered, invoiced, and growing every quarter. A print, a scan and a read are the same trade at the other end of the economy — a physical act, and a record that could come out of it — and your building performs thousands of them a day.

Where they do not, something is being lost, and there is no line for it anywhere.

You rent reasoning by the token, and every token is billed to a request, a key and an owner. You rent production by the case, and the case is billed to nobody.

The plant that makes your product is a generating station too — raw material in, finished units out, all day. It counts what comes off the line. It cannot tell one unit from another, because nothing about a case distinguishes it from the case behind it, so what the line reports is a total and never a unit. Owning the plant instead of renting it changes what you can do about that, and nothing about the meter.

A unit that was only ever counted in a total cannot be priced apart, insured apart, financed apart, recalled narrowly, or preferred by a machine.

The hard problem in this category has never been the run. It is the handoff — and the reason handoffs are hard is that they are between two companies who will not, and should not, pool their records.

So sharing runs on grants, not on a merge. Your 3PL grants you scope on the events they captured; you grant them scope on yours. Two records stay two records. Neither party is principal, whichever one is larger. A grant is narrow, dated, and withdrawable, and withdrawing it rewrites nothing either side already holds — because nothing in this system rewrites.

Sunrise 2027 is the timing. It is GS1's program, not ours: by the end of December 2027, retail point-of-sale is expected to scan and process 2D barcodes as well as the linear ones. That changes who generates supply-chain events. Today it is scanners, on docks, run by staff. After it, the same carton is scannable by a shopper on a sidewalk, by a returns clerk, by a partner's agent — humans and devices, most of them not yours.

FSMA 204 is the return, never the urgency. The largest public RFID rollout in food service — roughly 3,200 restaurants — is attributed to FSMA 204's compliance requirements by the deploying software vendor's own president: a third party carries the causal claim, not us. And the rule's own record is softening, not hardening — the enforcement floor moved to July 2028, and FDA is actively soliciting further flexibilities. Use FSMA 204 for operational ROI and Sunrise 2027 for timing, never the reverse. Anyone selling you the deadline as a gun to your head is one search away from being caught.

For the brand that owns the GTIN, the same square points both ways. The 2D code on your own carton will make every shopper scan and every returns scan an item-level signal attributable to your GTIN and your lot, in a record the retailer does not own and cannot withhold — which is also what turns a full recall into a lot-level withdrawal. Which barcode you print is your decision as GTIN owner — not your co-manufacturer's, and not Sunrise's. Whether shoppers scan at volume is a hypothesis, and we say so: a bet we are asking you to shoot down, not a number we can cite.

A public GS1 Digital Link resolved through id.gs1.org answers what the item is; by policy it will not tell you who touched it — that resolver is anonymous by design (see GS1's own conformant-resolver standard for what a public resolver returns). visibility.cloud is the private, brand-owned counterpart that names who touched each item: for the brand that owns the GTIN, item-level visibility that names the party at every step, not the anonymized trace the public resolver returns. Resolving a party from that record is unbuilt and listed as unbuilt on What ships today; what the spine writes today is the attested observer the resolution will read. You see your own product move, down to the individual item, by serial number, with a who on every link.

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.

Your agents will reason over anything you hand them. What they get handed is fourteen systems, a credential each, and no two of them describing the same object the same way.

visibility.cloud will onboard those sources as one surface: modern SaaS platforms through their own APIs, Apache Iceberg lakes read and written in both directions, the EDI mailbox that has been running since before anyone there was hired, and the print, scan and read events coming off the floor — landing as one event record with an attested observer on it, at the grain a question is actually asked at.

Then the agents get one secure place to explore it, under a seat with a written mandate: scope named, ceiling named, every read evaluated against the same grants every human read is. The point is not a chat window over a warehouse. It is that the answer comes back actionable — a bounded set of cases, a named handoff, a specific gap — instead of an integration project per source.

Your capture workspace is provisioned from the list. We write when your seat is ready, and follow up about it from there.