Shopify barcode not scanning: five checks to make
Start by separating a barcode that cannot be read from a code that scans but finds no product. Then check the value, format, label, scanner setup, and catalog match.
Five common areas to check
1. Check digit and length
EAN and UPC formats use specific lengths and a calculated check digit. Validate the full value for the format you intend to print. A bad check digit or incorrect length can prevent encoding or scanning.
Keep leading zeros when exporting and importing codes. Losing a zero can change the expected length or representation; it does not always change the calculated check digit. Do not repair a code by guessing a missing digit.
2. Hidden or unsupported characters
Copied values can contain non-breaking spaces, zero-width characters, typographic dashes, or full-width digits. Similar-looking Cyrillic and Latin letters are different characters. Compare the stored value with the supplier’s source rather than relying on its appearance.
Markio identifies unsupported characters in relevant audit findings so you can inspect the value before changing it.
3. Barcode format and scanner configuration
Numeric formats such as EAN cannot carry letters. GS1 formats have additional structure requirements. The scanner must support and have the chosen format enabled; a 1D-only scanner cannot read a 2D symbol.
Long values need more space in a linear barcode. There is no universal character count that fits every label: format, data, printer resolution, and bar width all matter.
4. Label size and print quality
Print at the intended dimensions, usually at 100% scale, and check that the driver’s paper size matches your labels. Preserve the quiet zones around the symbol and avoid placing text or borders inside them.
Inspect narrow bars, gaps, contrast, smudges, and damage. For thermal printers, adjust darkness and speed using the printer’s guidance. Excessive darkness can make bars spread into one another, so darker is not always better.
5. Scanner connection and product matching
Confirm that the scanner is paired or connected in the mode your POS requires. Test a known-good label. If codes are read but products are not found, check the stored barcode value, product availability, and any shared codes.
A successful read confirms that a symbol can be decoded. It does not establish that the right product, variant, or price will be selected in every app.
A practical test sequence
- Scan a known-good label. If that also fails, check the scanner’s connection, settings, and supported formats first.
- Compare the decoded value. Where your scanner and app allow it, inspect the actual value read, including leading zeros and any prefixes or suffixes.
- Make a larger test print. Use the same valid code with adequate quiet zones. If the test works, investigate size, scaling, media, and print quality.
- Check the product match. Search for the exact value in the catalog and review any duplicate matches.
- Test the final label in its real workflow. Use the same scanner, POS, and label material your staff will use.
A failed test alone does not prove that the catalog value is wrong. Some scanners cannot read phone screens, some formats are disabled by default, and damaged labels can obscure otherwise valid data.
How Markio helps
The catalog audit checks stored codes for supported validation rules, including missing values, duplicates, invalid lengths, check digits, and unsupported characters. The label editor can warn about narrow barcode elements, and scan verification shows how a decoded value matches Markio’s catalog.
Those checks complement a physical print test. They cannot inspect your printer’s thermal output, label damage, or the configuration of a separate scanning application.
Check the stored code and the product it matches
Markio is coming soon to the Shopify App Store.
Catalog audit reports and scan verification are free. Pro adds supported bulk fixes, scheduled audits, and additional printing workflows.