For the head of brand looking at the Sunrise 2027 line item and thinking "if I have to print a scannable square anyway, can I make it earn its keep as a channel?" The answer is yes, with a discipline most vendors won't give you: the part that is true today is separated cleanly from the part that is a hypothesis nobody has proven — including us.

The instinct is right. You are being made to print a square that a phone can read, on every unit, at no incremental media cost. Of course it should be a channel. The reason to be careful is not that the instinct is wrong — it is that the space is about to fill with people selling you the bet as if it were the fact, and once you can tell the two apart you will never be sold the wrong one again.

So we split it, hard, and we put the true half first.

The half that is true today — and you can verify it without us

A 1D UPC was never consumer-scannable. It is a lane token: a fixed-orientation stripe pattern built for a fixed scanner, and a phone camera makes nothing of it. That is why, for the entire history of your category, the mark on your pack talked only to someone else's checkout and never to your customer.

A 2D barcode carrying a GS1 Digital Link URI is web-resolvable. A native phone camera opens it like any link. This is not a product feature of ours and not a forecast — it is GS1's published design for 2D at point of sale, and you can read the programme yourself: GS1 — 2D barcodes at point of sale.

So the true, checkable, today statement is exactly this and no more:

The same square you are printing for the checkout lane can resolve in your customer's phone camera to a destination you control. The mark changes from a checkout token into something that can carry an address.

That alone is real, and it is already enough to justify choosing the phone-readable symbology (QR over a lane-only DataMatrix) and pointing its resolution at experience you actually want a scanning shopper to land on — provenance, authenticity, how-to, reorder, registration. Every bit of that works with technology GS1 has already published. No hedge required.

The half that is a bet — and we are asking you to shoot it down

Here is where most of the value would be, and here is where we refuse to pretend.

We think that once your pack carries a mark a phone can read, most scans happen off your properties, by people who do not work for you — in aisles, in kitchens, in the hands of a shopper who will never touch your DTC site. And we think the pattern of those scans is a new first-party signal class: which SKUs got scanned, in which markets, how many times, how long after they shipped. Repeat scans on the same GTIN in one market look like repeat rate. First scans in a market you don't sell into look like diversion. A promo week with no scan lift looks like a promo that didn't land — read from your own pack, not resold to you by a syndicated panel eight weeks late at category grain.

We have no evidence for that, and neither does anyone else. It is a hypothesis — the single question this whole exercise exists to test. It carries no authority reference because there is none to cite; a citation would be a lie. If you tell us shoppers will never scan at volume in your category, that is the most useful thing that can happen this quarter, and we would rather hear it now than sell around it.

And the honest limit on us specifically, to your face: we do not deliver consumer-scan analytics — that product is on no build path here, ours included — and no customer or adoption claim appears anywhere on this site. What exists is the record layer — translate, validate, hash — live at epcis.dev, one curl each. If you want the signal capability, you are joining a seat list, not a pipeline.

Why the discipline matters more here than anywhere

Because the failure mode is silent and expensive. The square prints either way. Treat it as a compliance line item, choose a symbology in a pure compliance frame, and you will very likely default to a mark no shopper can read — you will have paid for a touchpoint and switched it off, and nothing will alert you, because compliance passed. Meanwhile the true half above was free the whole time.

The correct posture is not "believe the bet." It is: capture the true half now — at essentially zero marginal cost, because you are printing the square regardless — and structure it so that if the bet pays off you are already positioned, and if it doesn't you have lost nothing. That is a very different sell from "scan data is the future, sign here," and the difference is the entire point of reading this instead of a vendor deck.

The two questions to bring to any vendor who pitches you "scan engagement"

  1. "Which half of this is GS1's published design, and which half is your hypothesis about shopper behavior?" If they can't or won't draw the line — if it all comes back as one confident story — they are selling you the bet as the fact.
  2. "What does it cost me to capture the true half now and decide on the rest later?" If the answer requires a platform commitment before a single unit ships, they have inverted the risk onto you. The phone-readable square is a symbology choice in your next artwork cycle; that is where the cheap option lives.

If your gap is compliance and ops, not customer-blindness

Some readers arrive here running a large enough operation that the acute pain isn't "I can't see my customer" — it's programme-office reality: Sunrise readiness across a broad SKU set, GDSN and EPCIS in the same breath, retailer mandates on a clock. That is a different hero with a different pillar. If that's you, start there instead: Sunrise 2027 for enterprise CPG brand owners. The consumer-signal thesis on this page is the mid-market, co-manufactured brand's angle; take the seat that fits your delta.

For everyone whose real ache is customer-blindness, the full frame — one square, two jobs, the honest limit — lives on the parent pillar: Your barcode was a checkout token. The same square can be a line to your customer.

Put me on the seat list → /first-trace?segment=manufacturer

Your capture workspace is provisioned from this list, in order — one email when your seat is ready, which is not the consumer-signal capability, but the one event we can honestly promise to tell you about. The named human sender and the verified sending address are a launch gate — P0-V4 in the open P0 ledger, not softened copy. The deeper door is the live get-started interview.