CartVisualCreate account

Why Can Two Valid Barcodes on One Package Cause a Duplicate Checkout Event?

A dual-marked pack can be read more than once unless the POS scanning and host workflow recognize both symbols as one item and process only one transaction data set.

Published · By CartVisual editorial team

Identify the duplicate-event layer

A pack may contain a valid EAN/UPC symbol and a GS1-compliant 2D barcode that both identify the same trade item. Validity of each code is not proof that the checkout system suppresses a second transaction event. GS1 specifies that systems process one set of desired data in the final transaction and recommends a single acknowledgement when multiple barcodes for the same item are scanned. Not every deployed scanner has equivalent capabilities.

Separate artwork from scanner behavior

First confirm that the two symbols encode the intended same GTIN, using the actual approved records rather than visually comparing bars. Then review their placement against the applicable GS1 guidance. Finally ask the retailer or POS provider how its scanner and host software recognize multiple barcodes on one trade item. An image designer can reserve and arrange space, but cannot configure deduplication in a checkout terminal.

Hypothetical soup pouch

Fictional pouch SOUP-R6 includes an EAN-13 on the rear and a 2D code on a nearby panel. A store reports that a sample may be counted twice. The editorial diagnostic plan requests the precise POS hardware/software configuration, transaction-event log and representative pack sample. It does not assert that a double scan actually occurred. The designer proposes no arbitrary relocation until the retailer explains the applicable placement and recognition requirements.

Branch on observed evidence

If the GTINs differ, stop and reconcile the master data before any scanner diagnosis. If the identifiers agree but two line items appear, escalate the scanner/host duplicate-processing path. If one line item appears but two audible signals occur, record that separately; audible feedback and final transaction state are not identical. If the problem happens only at a specific scanner, do not generalize the result to every retailer.

Exit conditions

Hold the affected rollout until the retailer or responsible provider confirms the expected one-item behavior on the actual supported configuration. Record the pack revision, symbol locations, scanner model, software mode, host result and owner decision from authorized testing. A phone scan and a digital proof cannot close this issue. Do not represent a suggested placement as a certified POS fix.

Sources

Scope and evidence

Prepared by CartVisual with AI assistance and checked against the listed sources. No real POS transaction, scanner model or retailer configuration was tested.

Related decisions

Explore the packaging mockup generator workflow