Retail barcodes are changing from simple product identifiers into richer data carriers. GS1's Ambition 2027 calls for retail point-of-sale systems to be able to read and process a defined set of GS1 2D barcodes, alongside the linear EAN/UPC barcodes already used at checkout.
For retailers and POS solution providers, this is not just a label change. Scanner hardware, firmware, POS software, item databases and operating procedures must work together. A scanner may decode a symbol successfully while the POS host still rejects the data or creates the wrong transaction.
This guide explains how to assess retail barcode scanner readiness, plan a controlled pilot and avoid the most common integration problems.
Why GS1 2D barcodes matter at retail POS
A conventional EAN or UPC barcode normally identifies the trade item so the POS system can look up price and tax information. A GS1 2D barcode can carry the Global Trade Item Number (GTIN) plus additional attributes such as batch or lot number, expiry date and serial number. Depending on the implementation, it may also use GS1 Digital Link URI syntax.
That additional data can support practical retail use cases:
- Blocking the sale of expired or recalled products
- Applying date-based markdowns
- Improving batch-level traceability
- Authenticating serialized products
- Reducing food waste through better expiry management
- Connecting consumers to product information through a web-enabled code
Linear barcodes will not disappear immediately. During the transition, many packages will carry both a traditional retail barcode and a GS1 DataMatrix, QR Code with GS1 Digital Link, or Data Matrix with GS1 Digital Link. The checkout system must identify the intended symbol and avoid processing the same item twice.
1. Confirm that the scanner is an image-based 2D reader
Older laser scanners are designed for linear symbols and generally cannot decode DataMatrix or QR Codes. A camera-based 2D imager captures an image and uses decoding software to recognize both 1D and 2D symbols.
Do not rely only on the words “2D scanner” in a product description. Ask the supplier to confirm support for the exact barcode families and GS1 syntax required by the project. Test the production firmware version, because symbology support, parsing behavior and multi-code logic can change between firmware releases.
For a new retail deployment, also evaluate whether the scanner format fits the checkout workflow. A presentation scanner supports hands-free scanning at a busy counter. A handheld scanner can be useful for bulky items. Self-checkout and kiosk projects may require a fixed-mount or embedded scan engine with a carefully designed scan window.
2. Test real codes, not only perfect samples
A specification sheet cannot reproduce real packaging. Build a test set that represents the products, labels and screens used in the store. Include:
- EAN/UPC and other current linear barcodes
- GS1 DataMatrix samples
- QR Codes and Data Matrix using GS1 Digital Link syntax
- Different symbol sizes and module dimensions
- Glossy film, curved bottles and reflective packaging
- Low-contrast, wrinkled, damaged and partly obscured codes
- Mobile coupons at several screen brightness levels
- Packages carrying both linear and 2D symbols
Run the test at the normal presentation angle and checkout speed. Measure first-pass read rate and the time required to obtain a valid result. A scanner that eventually reads a difficult code may still be too slow for a high-volume lane.
3. Plan for multiple barcodes on one package
During coexistence, the scanner may see an EAN/UPC symbol, a GS1 2D barcode and a marketing QR Code at the same time. Without a clear rule, it may return an unintended code or transmit more than one result.
Define which symbologies are enabled, which data should be prioritized and how duplicate reads are suppressed. Some projects use preferred-symbol logic, output filters or formatting rules. Others depend on the POS host to select the valid trade-item identifier.
The correct approach depends on the packaging and software architecture. Test every approved package layout and confirm that one physical item creates exactly one transaction.
4. Verify scanner output and interface behavior
A successful decode is only the first step. The scanner must transmit the data in a form the POS software can accept. Common interfaces include USB HID keyboard, USB virtual COM and RS232. Retail installations may also use specialized host protocols.
Check the complete output string, including prefixes, suffixes, symbology identifiers, separators and termination characters. GS1 data may contain FNC1 or Group Separator control characters. If the interface, driver or middleware removes or changes them, downstream parsing can fail even though the scanner indicated a good read.
For USB HID implementations, verify keyboard layout and how non-printing control characters are handled. For serial or virtual COM connections, document baud rate, data bits, parity, flow control and message framing.
5. Make the POS host ready for GS1 data
The POS host must recognize the product and decide what to do with the additional attributes. At minimum, confirm that the system can accept a GTIN encoded in a GS1 2D barcode and map it to the same item record used by the existing linear barcode.
Review these software questions with the POS provider:
- Can the host accept 14-digit GTINs without truncation?
- Can it parse GS1 element strings and the required Application Identifiers?
- Can it accept or translate GS1 Digital Link URI syntax?
- Does it preserve FNC1 and Group Separator data?
- Can optional attributes be stored, acted on or safely ignored?
- Will the same item be found from both its linear and 2D barcode?
- Can it prevent a double transaction when two retail symbols are present?
Advanced use cases need explicit business rules. An expiry date has no operational value unless the POS system can interpret it, compare it with the transaction date and decide whether to warn, discount or block the sale.
6. Include backend systems in the project
The checkout lane is only one part of the data path. ERP, inventory, fulfilment, warehouse, returns and analytics systems may also receive the captured attributes. Decide which fields should be retained, how long they should be stored and which applications are allowed to use them.
Document the end-to-end route from scanner to POS host, middleware, store server and central systems. Check character limits, field formats and exception handling at every interface. A code that works in a lab can still fail when a legacy integration expects only a short numeric EAN value.
7. Design a production-like pilot
Start with a limited number of lanes and a controlled product group. Use the intended scanners, firmware, cables, POS software and backend configuration. Include cashier-operated checkout, self-checkout and returns workflows if they are in scope.
A useful pilot should verify:
- Reliable reading of approved linear and 2D symbols
- Correct item lookup from every permitted symbol
- Single-item behavior when multiple codes are visible
- Accurate parsing of GTIN, lot, expiry and serial data
- Expected action for expired, recalled or invalid items
- Normal operation after scanner, POS or network restart
- Performance during peak checkout volume
- Clear operator prompts and recovery procedures
Record the approved scanner configuration and lock it for rollout. Uncontrolled configuration changes—such as enabling extra symbologies or changing suffix characters—can create inconsistent behavior between lanes.
Retail POS scanner readiness checklist
- Image-based 2D scanner confirmed
- Required GS1 symbologies and syntax tested
- Real packaging and mobile screens included in validation
- Multi-barcode and duplicate-read rules defined
- Interface output, separators and identifiers documented
- GTIN lookup works from both linear and 2D symbols
- POS host can parse or safely ignore additional attributes
- Backend data flow and retention rules reviewed
- Production-like pilot completed
- Firmware, settings and support process standardized
Frequently asked questions
Will EAN and UPC barcodes stop working in 2027?
No. GS1 guidance describes coexistence between linear and 2D barcodes during the transition. Retail systems should continue supporting existing linear processes while adding the required 2D capabilities.
Is any QR code a GS1 retail barcode?
No. A consumer marketing QR Code and a GS1 Digital Link barcode may look similar, but their data structure and business purpose are different. Test the exact symbols and syntax defined for the retail program.
Can a 2D scanner alone make a POS system ready?
No. The scanner captures and transmits data, while the POS host and backend systems must interpret it and apply the correct business rules.
Should retailers replace every scanner immediately?
First audit the installed fleet. Many recent image-based scanners may already have suitable hardware but still need configuration, firmware validation or software integration. Replace hardware only where capability or performance is insufficient.
Prepare the complete checkout workflow
GS1 2D barcode readiness is an end-to-end project, not a scanner checkbox. Select an appropriate imager, validate real packages, control multi-code behavior and prove the complete data path before a large rollout.
Review the official GS1 2D Barcode Playbook for Retail POS Host and Backend Systems for standards guidance. To evaluate scanner samples for your checkout, kiosk or OEM project, explore WODEMAX barcode scanning solutions or contact our team with your barcode samples, interface and POS requirements.