Guides
Barcode will not scan
Start with data validity, print resolution, quiet zones, contrast, physical damage and symbol size before replacing the encoded number.
Separate data problems from print problems
Start with data validity, print resolution, quiet zones, contrast, physical damage and symbol size before replacing the encoded number. 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 barcode 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.
Use the result downstream
After completing barcode will not scan, decide what consumes the output next. A scanner, POS, marketplace, warehouse system, resolver, purchasing team or spreadsheet can each transform data differently. Test that hand-off explicitly. The QiiChain result is most useful when it becomes a verified input to the next process rather than a value copied into several files without ownership or version control.
Operational scenario
For barcode will not scan, keep display text separate from encoded or calculated data. A product name can be edited for customers while the GTIN must remain exact; a formatted currency value can include symbols while the calculation needs a numeric amount. Separating display and source fields prevents presentation changes from altering machine-readable data.
Downstream hand-off
If the output of barcode will not scan is copied into another spreadsheet, mark the identifier column as text before paste/import. That is especially important for UPC, EAN, GTIN, GLN and SSCC values because spreadsheet numeric conversion can remove leading zeros or display long values in scientific notation.