Guides
GS1-128 data will not scan
Check AI syntax, FNC1 handling, field lengths and the chosen barcode symbology before changing valid product identifiers.
Separate data problems from print problems
Check AI syntax, FNC1 handling, field lengths and the chosen barcode symbology before changing valid product identifiers. First validate the encoded value independently. If the number is correct, changing GTIN digits will not fix low contrast, missing quiet zones, distortion or printer-resolution problems.
Inspect the final physical symbol
Measure the printed output rather than the on-screen artwork. Check module/bar width, quiet space, contrast, clipping and whether the printer produced clean whole-dot edges.
Remove scaling surprises
Use SVG/vector output or render for the target printer. Disable browser or PDF “fit to page” options when they change the intended physical size, and avoid stretching a raster barcode in an image editor.
Test with the destination scanner
Scan several real production samples in the same orientation, lighting and packaging condition expected in use. One successful phone-camera scan is not a complete production verification.
Escalate without changing identity
If a symbol still fails, keep the original product identifier intact while a barcode-quality or trading-partner specialist reviews the print. Identifier ownership and print performance are separate issues.
Evidence to keep
Capture a before-and-after record for gs1-128 data will not scan: the original input, the validation or calculation result, the change made, and the result after the change. That evidence prevents a second system or spreadsheet from silently reintroducing the same problem and gives support teams something concrete to compare.
A small verification routine
Before scaling gs1-128 data will not scan, test three records: one normal item, one edge case and one intentionally invalid input. Confirm that the expected failure is caught, then verify the successful output in the destination workflow. This simple routine is especially useful before a bulk label print, marketplace import, ERP update or purchasing-rule change because it exposes assumptions while only a few records are affected.
Operational scenario
When gs1-128 data will not scan is part of packaging work, freeze the identifier and data content before final artwork approval. Late manual edits in design software are difficult to audit. Regenerate the symbol from the approved source data instead of editing bars, modules or human-readable digits directly in the artwork.
Downstream hand-off
Downstream, gs1-128 data will not scan should be stored in the field that matches its meaning. Do not put a GTIN into a SKU field, a supplier part number into a GTIN field, or a percentage into a unit-count field just because the destination allows free text. Correct field semantics make later validation and migration much easier.
Technical references
Sources used on this page
- GS1 Application Identifiers — GS1
Current GS1 Application Identifier browser and dataset covering AI meanings, formats, separator requirements and Digital Link roles.
QiiChain summarizes source material and applies it to the tool or workflow. The linked source remains authoritative for its own standard or product documentation.