# Barcode and QR acceptance test sheet

> Compare expected and decoded payloads, symbol size, scanner profiles, scan outcomes, and record lookups in the barcode and QR acceptance sheet.

Canonical page: https://datacenterlabeling.com/templates/barcode-qr-scan-quality

Download: https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx

Workbook tab: 25 Barcode checks. The workbook includes all 30 registers.

Rackstamp provides editorial field guidance. IDs, cases, and worksheet entries are fictional examples unless identified otherwise. Distinguish local conventions from adopted standards. Source notes describe the evidence scope; a linked overview is not the full standard or a project approval.

## Before you start

1. Establish the physical object's identity and the complete human-readable ID before generating or repairing its machine symbol.
2. Write the exact payload contract, intended application or environment, and expected resolved object record.
3. Gather symbol, printer, actual device/profile, and relevant version-specific instructions plus the intended installed reading conditions.
4. Agree the operational acceptance plan and required device coverage, keeping formal symbol verification requirements separate where applicable.

## Complete the register

1. Enter Human ID and Expected payload separately and compare both with the approved object record and generation source.
2. Record Symbol type and Print size with the actual layout/margin reference, avoiding generic dimensions copied from an example.
3. Identify the actual Scanner/profile and installed viewpoint, including any approved aids or offline conditions.
4. Capture Returned text exactly enough to reveal prefixes, suffixes, missing characters, spaces, or other contract differences.
5. Record Scan result and Lookup result separately, distinguishing no decode, payload mismatch, access denial, service failure, and wrong-object resolution.
6. Link Evidence, Owner, and Verification date to each relevant configuration or placement revision and the actual acceptance observation.

## Walk through the example

In fictional DC01 / H1, the recurring asset AST-008421 is associated with the verified location R014/U23. Enter AST-008421 in Human ID and Expected payload. The example's QR dimensions and five bench attempts describe only that fictional proof; replace them with the actual layout and agreed review plan. Capture the returned text, which matches AST-008421, and record a successful payload comparison. The lookup nevertheless displays AST-008412. Enter that distinct wrong-record outcome instead of marking the whole test passed. Preserve EX-Q25 and refer the association to the application or records owner. After the approved correction, scan the same physical label if its payload remains valid and confirm the intended record. Repeat the required installed-position checks with the actual device/profile. Record the final verifier and date only for checks completed, leaving any unresolved device coverage or access result visible. Correct decoding alone does not establish that the application found the intended asset.

## Handle common exceptions

### The payload matches but the application is unavailable.

Record capture success and service failure separately; retain lookup acceptance as pending instead of reprinting unchanged data.

### The normal view contains more than one machine symbol.

Capture the returned value and target context, then review permitted placement or selection behavior without concealing required manufacturer markings.

### One required device fails while another succeeds.

Keep per-device outcomes, inspect actual hardware/profile support, and leave full workflow acceptance open until required coverage is resolved.

## Review and close

1. Confirm that the human-readable ID, approved encoded value, and returned payload agree for the intended object.
2. Check that the applied label meets the agreed operational criterion across the required device/profile and viewpoint combinations.
3. Verify the resolved record identity rather than treating a scan tone, login screen, or generic search page as successful lookup.
4. Retain failed attempts and any separate formal verification result without calling the operational worksheet a symbol-quality grade.
5. Close the verified print, configuration, or records issue specifically and leave outstanding access or service obligations under named owners.

## Fields and fictional filled example

| Field | What to record | Fictional example |
| --- | --- | --- |
| Human ID | Visible complete object identifier. | AST-008421 |
| Expected payload | Exact encoded text. | AST-008421 |
| Symbol type | Barcode symbology selected. | QR Code |
| Print size | Symbol dimensions and margin reference. | 20 mm square; layout Q2 |
| Scanner/profile | Actual reading device and configuration. | Example imager / asset profile |
| Returned text | Captured scanner output. | AST-008421 |
| Scan result | Attempts and decoding observation. | 5 of 5; bench example only |
| Lookup result | Record identity or access outcome. | Wrong record AST-008412; review |
| Evidence | Proof and captured-output reference. | EX-Q25 |
| Owner | Person coordinating acceptance. | Example scan reviewer |
| Verification date | Date the test was observed. | 2026-09-12 |

## Sources

- [Zebra: Barcode input documentation](https://techdocs.zebra.com/datawedge/11-1/guide/input/barcode/): DataWedge 11.1 hardware, decoder, formatting, and quiet-zone context; payload/lookup workflow is editorial.