
A barcode or QR code can be designed correctly and still become unreliable after it is rendered on a particular electronic shelf label, resized by a template, viewed at a shelf angle, or scanned with a different device. That is why a production ESL program needs a scanability acceptance test in addition to symbol-design rules.
This guide deliberately focuses on validation and regression testing. The existing ESL Barcodes and QR Codes design guide owns the upstream task of creating and laying out reliable symbols. This page starts after a candidate template exists and answers a different question: how do you prove that the rendered symbol continues to scan across label variants, shelf geometry, device populations, content changes, and software revisions?
Freeze the test object before measuring scanability
A scan result is only comparable when the test configuration is identifiable. Record:
- symbol type and application profile;
- encoded test payload or payload class;
- template ID and revision;
- ESL model, display size, resolution, and display technology;
- rendering software or platform revision;
- product text and other content competing for template space;
- shelf fixture, label angle, and bezel/holder condition;
- scanner or phone model and software version used in the test.
Do not describe a result as "QR works on ESL" when it was proven on one label size, one template, and one phone. The approved object is the specific rendering and use condition.
Use the applicable symbology rules as a design gate before acceptance
Acceptance testing should not compensate for an invalid symbol. QR Code is specified by ISO/IEC 18004:2024, which covers symbol characteristics, dimensions, error correction, decoding, and production quality requirements. If the code is used in a GS1 retail application, follow the applicable GS1 2D barcode implementation guidance and General Specifications rather than borrowing dimensions from a generic web example.
GS1's retail guidance explains that a 2D symbol needs an adequate quiet zone and that undersized modules can reduce reliable decoding. Those requirements apply to the symbol design. The acceptance test then asks whether the symbol remains usable after it is rendered on the real ESL and installed in the real scanning workflow.
Build a scan test matrix around the real user task
Different tasks need different test populations. A store associate using a dedicated imager at close range is not the same as a shopper using a phone camera from an oblique angle. Define the primary workflow first, then test the devices that matter to it.
| Dimension | Examples to include | What it reveals |
|---|---|---|
| Label variant | Every production size/template combination that displays the symbol | Pixel-grid and layout effects |
| Payload | Short, typical, and approved worst-case data lengths | Changes in symbol density or size |
| Shelf geometry | Normal angle plus difficult but permitted shelf positions | Perspective, glare, and working-distance sensitivity |
| Scanner population | Approved handheld imagers or fixed scanners | Decoder and optical diversity |
| Phone population | Representative supported phone/camera combinations where customer scanning is required | Autofocus, exposure, and camera diversity |
| Lighting | Representative store lighting and known difficult fixtures | Reflection and contrast sensitivity |
| Display state | Freshly rendered and the normal stable e-paper state | Rendering/refresh artifacts or incomplete update conditions |

Measure first-read behavior, not only eventual success
A code that scans after six attempts is not equivalent to a code that decodes immediately in the normal workflow. Choose metrics that match the operation. Useful measures can include:
- first-attempt decode result;
- number of attempts before success;
- time to first successful decode where the test method can measure it consistently;
- working-distance and angle envelope for the approved user task;
- failure category: no symbol detection, detected but not decoded, wrong target selected, glare/occlusion, or application-handling failure.
Do not publish one universal pass percentage or scan-time threshold. Set acceptance criteria from the retailer's workflow, selected scanners, applicable standards, supplier evidence, and pilot data.
Keep scanner failure separate from payload and application failure
A successful optical decode can still produce a failed workflow. Record the layers separately:
- symbol detected;
- payload decoded;
- payload syntax accepted;
- product or task record found;
- business action completed.
If the scanner returns the correct payload but the retail app says "unknown item," the barcode image is not the root cause. Conversely, if the application never receives a decode, the team needs scanner-level evidence before changing product data.
The ESL Data Readiness Audit covers identifier and source-data prerequisites that sit downstream or upstream of the visual symbol.
Test the rendered pixel grid, not the source artwork
Vector or high-resolution source artwork can be valid while the final ESL bitmap is not. Capture or export the actual rendered image sent to the label when the platform permits, and compare it with the intended symbol.
- Look for module or bar widths that become uneven after rasterization.
- Check that the quiet zone is not reduced by template borders, text, icons, or bezel masking.
- Avoid resampling or anti-aliasing that creates gray edges where crisp modules are expected.
- Check for partial refresh or stale pixels intruding into the symbol area.
- Verify that automatic template scaling triggered by long product names or localized text does not compress the symbol.
- Keep the symbol far enough from the physical display edge or holder to preserve the approved layout.
These are template/rendering QA issues even when the source barcode generator is correct.

Use a fixed regression pack for template and software changes
Once a symbol/template combination passes, preserve the exact test cases as a regression pack. Rerun it after changes that can alter rendering or scan geometry:
- template revision;
- font or localization change that shifts layout;
- barcode/QR generation library update;
- ESL platform rendering update;
- new label size or resolution;
- firmware or display-driving change that affects the rendered image;
- new shelf holder, angle, or bezel;
- new scanner or phone population;
- payload format or maximum data-length change.
The regression pack should include difficult cases, not only the easiest symbol. A long product name, dense approved payload, small label, difficult shelf angle, and older supported scanner often reveal regressions before a fleet rollout does.

Compare template revisions with the same test population
When a layout changes, keep the scanner/phone population and shelf geometry constant so the effect of the template can be measured. If the device population also changes, separate the experiments. Changing several variables at once makes a failed regression difficult to diagnose.
A simple release record can show template revision, label model, symbol/payload test case, device, angle/distance condition, result, failure category, and disposition. This is more useful than screenshots that show a code "looks fine."
Use GS1 rules only when the workflow is actually a GS1 application
Retailers often mix internal location codes, product identifiers, URLs, and GS1 identifiers. The applicable symbol and data rules depend on the use case. If the code is intended for GS1 retail scanning, apply GS1 requirements to the correct application. If it is an internal QR code linking to a store workflow, do not label it "GS1 compliant" merely because it is a QR Code.
The same distinction applies to verification equipment. A formal barcode verifier and a practical phone-camera test answer different questions. Use standards-based verification when required for the symbol/application, and use workflow scan testing to prove real operational usability.
Define the release gate for an ESL template
A barcode-bearing template should not be approved solely by graphic design. The release gate should require:
- symbol-generation rules approved for the intended application;
- actual rendered output reviewed on every supported label variant;
- quiet-zone and edge clearance preserved after final layout;
- defined scan test population and field geometry;
- acceptance results meeting the project's approved criteria;
- known exceptions documented;
- regression pack stored with the template revision;
- rollback path to the previous approved template.
For broader ESL data transactions and rollback concepts, use ESL POS and ERP Integration. Product context belongs to Electronic Shelf Labels and the ESL solution hub.
FAQ
Q: Why keep this page if another article already explains ESL barcode and QR design?
A: The design article owns symbol creation, sizing, layout, and general scanning principles. This page owns acceptance and regression QA after a candidate template exists: test populations, field geometry, first-read behavior, rendered-pixel inspection, revision control, and release gating.
Q: Does a QR code that scans on one phone pass?
A: Only for that exact test condition. Approval should cover the phone or scanner population, label variants, payloads, shelf geometry, and lighting required by the intended workflow.
Q: Should a formal barcode verifier replace real-store scan tests?
A: No. Formal verification can assess standards-related symbol quality where applicable. Workflow testing proves whether the rendered ESL can be used by the real scanners, phones, angles, and store conditions. Many projects need both.
Q: What should trigger regression testing?
A: Any change that can alter the rendered symbol, available template space, display pixel grid, physical viewing geometry, scanner population, or encoded payload should trigger the relevant part of the stored regression pack.
Q:
A: Scanability is a release-quality property, not a screenshot review. Freeze the rendered configuration, test it with the real device and shelf population, separate optical decode from application logic, and rerun the same hard cases whenever the template or platform changes.
