Picture a supermarket group with stores in Dubai and Riyadh. A supplier introduces a pack carrying both a familiar linear barcode and a new QR code. Marketing sees a route to richer product information. Procurement asks whether the scanners need replacing. The store manager asks the useful question: will Saturday's checkout queue still move? 2D barcode readiness begins with that question. A phone opening a product page proves very little about a retail transaction.
My argument is straightforward: approve the transition against a completed sale, then add richer uses of the data. A scanner purchase, packaging redesign and customer information page may all be sensible investments. None should become a substitute for proving that the item reaches the basket correctly across the equipment and software the business actually operates.
2D barcode readiness has a specific first finish line
GS1 describes Ambition 2027 as an industry goal: retail point-of-sale systems should read and process a defined set of GS1 2D barcodes alongside existing linear barcodes by the end of 2027. It is a capability goal, with transition timelines varying across markets. Do not turn that statement into an unsupported claim that every Gulf pack must lose its existing barcode on one deadline.
Set two separate investment decisions. First, can stores accept the product identifier reliably? Second, which additional information would change an operating decision enough to justify the work? Expiry handling, batch information and customer content have different owners and dependencies. Combining them into one transformation promise makes basic checkout acceptance harder to judge.
The adjacent note on digital product passports deals with product claims and the evidence behind them. This decision is narrower: can the checkout process the pack correctly? Keep those acceptance criteria separate even if the same packaging programme serves both.
Use a five-part store acceptance test
1. Inventory the complete lane
Ask IT and store operations for one shared equipment list. Include scanner model, firmware, connection mode, POS software version and any software between scanner and till. Add handheld devices, self-checkout and returns desks. A group can buy one scanner brand and still operate several materially different checkout configurations.
Choose pilot lanes because they represent that variation. Include an older store, a busy store and a format with different handling conditions. Record the configuration that passed so another branch can reproduce it. A vendor demonstration on its own laptop should start the conversation, not close the purchase order.
GS1's solution-provider readiness criteria distinguish creation and printing, POS scanning, verification and connected data services. They are criteria for supplier self-assessment. Use them to ask precise questions about the supplied capability; then require evidence on your own configuration.
2. Define one item entering the basket once
The GS1 retail implementation guideline explains that baseline readiness includes processing the GTIN, the global trade item number, from supported linear and 2D symbols. Where multiple barcodes identify the same trade item, the final transaction must process one desired data set. The guidance also warns that some imaging scanners cannot support the necessary updates.
Turn that into a visible business test. Pass a dual-marked pack across the scanner at different angles and ordinary cashier speed. Inspect the basket and receipt, rather than listening only for a beep. Then scan two physical units deliberately. The system must distinguish duplicate recognition of one pack from a legitimate purchase of two packs. Suppressing repeated product identifiers indiscriminately would hide sales.
Ask the team to demonstrate a void, a quantity change and a return as well. These are proposed acceptance cases for the retailer, not claims that a barcode standard supplies every business rule. Finance and store operations should agree what the transaction record must show.
3. Follow the identifier into the product record
A correctly decoded identifier can still meet a bad item mapping. Test single units and multipacks, discontinued packaging and products supplied through more than one distributor. Follow each result into the local assortment, price and receipt description. Confirm that the same item has not silently become two stock records.
For a Gulf group, inspect Arabic and English product descriptions and the correct market's price configuration. Do not let the project team declare success because the central product name looked right in a test database. The customer pays against the branch's operating setup.
Keep an explicit distinction between the data present in a symbol, the data received by the POS and the data actually used by a business rule. An expiry field that disappears before reaching the till cannot support an expiry decision. Equally, richer data should not begin blocking sales until the rule, exception and store authority are agreed.
4. Test packaging under handling conditions
Bring real production samples to the pilot. Include curved bottles, glossy wrappers and labels likely to crease or collect condensation. Use ordinary lighting and counter space. Record failed reads by packaging type and device configuration, with photographs or sample references that the supplier can investigate.
Agree how staff recover when a pack does not scan. Which identifier may they enter manually? How do they verify the selected product? Who reviews repeated failures? A quiet manual workaround can conceal a rollout problem for weeks if nobody counts it.
Also test an unavailable customer information website. The retailer should understand whether any part of its checkout implementation depends on a network lookup and what happens when that dependency fails. Do not discover a new availability dependency during a weekend promotion.
5. Release by evidence, with a way back
Before the pilot starts, agree local acceptance thresholds for scan failures, manual lookups, incorrect basket additions and checkout time. Measure the current lane first. Compare equivalent baskets and conditions; a quiet demonstration cannot tell you whether a busy store became slower.
Name who can pause expansion, restore the previous configuration and notify suppliers. Preserve the tested configuration and sample set for later firmware or POS changes. This is ordinary business automation discipline: the input, decision, exception and evidence must remain connected after launch.
Buy against the receipt
Ask each supplier for a clear statement of what is supported now, what needs an update and what requires replacement. Price the rollout by store configuration, including testing, staff instructions and support. Keep additional data use cases outside that first commitment until they have their own owner and acceptance evidence.
2D barcode readiness earns its budget when the retailer can accept changing packaging without losing transaction control. Put one physical product through a real lane. Check the basket, receipt and stock movement. Expand only when those agree. The customer should never have to understand the barcode programme to finish buying dinner.