During a retail move from linear to 2D barcodes, a pack that carries both symbols must still produce the intended one item transaction. Two successful decodes are not enough. Specify the applicable GS1 symbol and data syntax, the scanner’s treatment of multiple codes on the same item, the host POS mapping and the transaction result; then test the finished pack in the actual lane. A second beep, duplicate line item or the wrong product record is a failed acceptance result even when both codes are readable.
This is a retail-POS integration decision, not merely choosing one intended code from a multi-code label or parsing a Digital Link value in a handheld application. The buyer must prove that packaging, scanning software and POS processing agree while both old and new symbols coexist.
Define the two symbols and the one desired outcome
List each consumer-unit SKU, the existing linear symbol, the proposed 2D symbol, its GS1 data syntax and the application fields expected from each. Do not assume that a QR Code, a Data Matrix and a GS1 DataMatrix carry or are interpreted as the same data. Determine whether the POS needs only the GTIN or must also capture attributes such as lot or expiry, and whether the host can store and act on them. The barcode’s data, a scanner’s decoded output and the accepted POS line item are three separate checkpoints.
The GS1 2D Barcodes at Retail Point-of-Sale Implementation Guideline, Release 1.1.0, sections 4.1.2, 5.5.1 and 7.5, addresses dual-marking placement, transition and POS scanner modes. It says the retail transition requires systems to handle the relevant linear and 2D symbols and ensure only one desired data set is processed for a trade item. Apply its rules to the stated retail consumer-unit scope; do not import a retail placement or POS mode requirement into a warehouse carton or proprietary code without checking the applicable standard.
For retail trade items, keep the approved linear symbol during a dual-marking phase unless the relevant GS1 guidance and trading-partner readiness support a different path. Request current packaging artwork, symbol verification results, scanner software mode and version, POS parser specification and trading-partner acceptance conditions. A statement that the scanner is “2D capable” does not establish the required syntax handling or a one-item transaction.
Test the complete lane, not a loose code
Editorial example; not a customer deployment or real test: Item A has a linear symbol and a GS1-compliant 2D symbol representing the same intended trade item. In a proposed lane, the reader decodes both during one pass. If the POS shows two units or a mismatched item record, the rollout fails even though both decodes were correct. The team records scanner output and host events separately, configures the documented scanner mode or POS mapping, then repeats the pass in every permitted orientation. If the 2D data includes an attribute the host cannot yet use, the buyer explicitly decides whether an approved GTIN-only mode is acceptable for that lane; silently discarding required attributes is not an acceptance rule.
Use production-representative packages, not only artwork displayed on a screen. Check symbol size, clear areas, sheen, curvature, adjacent placement and damaged-but-permitted handling samples against the applicable GS1 rules. Curvature and quiet-zone placement remain physical constraints, while the one-transaction rule is a separate software and business constraint. A print verification grade does not prove that a web destination is correct or that the POS processed only one item.
Use an acceptance matrix that includes failure branches
- Test a linear-only pack, a 2D-only approved sample where relevant, and the finished dual-marked pack. For each, capture the raw scanner event, the interpreted GTIN or attributes and the final POS line item. Preserve symbol and software versions.
- Move the dual-marked pack through the lane in normal orientations and speed ranges for that installation. Verify one intended acknowledgement and one accepted item transaction. If the scanner emits two events but a middleware layer deduplicates them, record that dependency; do not attribute the behavior to the scanner alone.
- Deliberately make one symbol unreadable while leaving the other valid, within an approved test sample. Confirm the documented fallback and reject path. A mistaken or missing product master record is a host-data issue even when the decoded GTIN is correct.
- Test a change to the scanner mode, POS parser or packaging artwork under version control. Re-run the one-item test after any such change; successful decoding from an earlier configuration does not qualify the changed combination.
Ask the supplier which exact scanner model and firmware implements the proposed mode and which component prevents duplicate transactions. GS1’s guideline describes multiple software modes and possible middleware for limited scanners; it does not certify an unspecified reader or guarantee that all retail hosts can parse Digital Link syntax. If the lane cannot pass, hold the dual-marked rollout until the owner of scanner configuration, middleware or POS mapping resolves the evidenced failure.
AIDC GO’s barcode handheld category is relevant to backroom capture and sample investigation, not proof of retail POS lane suitability. For a procurement project, provide sample packs, the required output and the host specification to Integration Support, or contact AIDC GO to define what can actually be evaluated. No AIDC GO POS scanner mode or retail certification is claimed here.
Source and applicability
The retail-specific principles above come from the official GS1 2D Barcodes at Retail Point-of-Sale Implementation Guideline, Release 1.1.0, checked 2026-09-24. Consult the current GS1 General Specifications and trading-partner requirements for the exact symbol, artwork and market. The example is hypothetical, contains no constructed GTIN presented as valid, and establishes no AIDC GO POS compatibility.