Barcode readiness checker

Check your product list before the count starts. Bad barcode data is cheaper to fix before people are walking the aisles.

Paste or upload a CSV. The browser-only checker validates barcode rows, GS1 element strings, scanner output, Digital Links, and SSCC data, then gives repair and proof reports you can download or print.

Barcode check

Check your barcode list

Paste or upload a CSV to catch missing IDs, duplicate barcodes, GTIN errors, bad locations, print-readiness gaps, and GS1 2D or SSCC mismatches before counters scan. Keep clean rows moving and send proof exports to owners when needed.

Paste CSV Upload CSV

Delimiter: , GTIN checked: 0 Readiness score: 0/100

80+ is ready; below 80 needs review. GTIN, location, collision, quantity, GS1 2D syntax, row-match, and SSCC checks stay in the exports.

Barcode list CSV Paste headers and rows, or upload a CSV. Keep SKU, barcode, location, quantity, and count-pack evidence together.

SKU,Barcode,Lot number,Use by date,Expiration date-time,Best before date,Sell by date,Production date,Packaging date,Serial number,Count of items,Logistic count,Net weight kg,GS1 2D data,Description,Location,Expected qty,Batch,Scope,Assigned counter,Reason,Location confirmed by,Counter signed off at,Supervisor reviewed at
A1001,0123456789012,LOT-A,2026-09-30,2026-09-30 14:30,2026-09-15,2026-09-10,2026-03-15,2026-03-16,SN1001,10,48,1.950,(00)000123456789012343(02)00123456789012(37)48,Widget A,A01-01,10,Batch 1,A items - warehouse A,Alex,,Alex,,
A1002,0123456789029,,2026-08-31,2026-08-31 14:30,2026-08-15,2026-08-10,2026-02-10,2026-02-11,SN1002,12,24,0.500,https://id.gs1.org/01/00123456789029/21/SN1002?17=260831&7003=2608311430&15=260815&16=260810&11=260210&13=260211&30=12&37=24&3103=000500,Widget B,A01-02,,Batch 1,A items - warehouse A,Priya,,Priya,,
A1003,0123456789029,LOT-B,2026-10-15,2026-10-15 08:45,2026-10-01,2026-09-28,2026-04-01,2026-04-02,,5,36,1.250,https://id.gs1.org/01/00123456789029/10/LOT-B?17=261016&7003=2610160845&15=261001&16=260928&11=260401&13=260402&30=5&3103=001250,Widget C,A01-03,5,Batch 1,A items - warehouse A,Sam,Found stock,Sam,Sam 09:24,Lee 10:02
A1004,,LOT-C,2026-11-01,2026-11-01 09:00,2026-10-20,2026-10-15,2026-04-15,2026-04-16,,8,,2.000,,Widget D,A01-04,8,Batch 2,A items - warehouse A,Alex,,Alex,,
A1005,0123456789000,LOT-D,2026-12-31,2026-12-31 16:15,2026-12-15,2026-12-10,2026-05-01,2026-05-02,,3,18,0.750,https://id.gs1.org/01/00123456789000/10/LOT-D?17=261231&7003=2612311615&15=261215&16=261210&11=260501&13=260502&30=3&3103=000750,Widget E,0123456789012,3,Batch 2,A items - warehouse A,Priya,Moved stock,Priya,,
,0123456789074,LOT-E,,May 1 2026 08:00,2026-09-30,2026-09-20,May 1 2026,2026-05-01,SN1006,3,12,0.750,https://id.gs1.org/01/00123456789074/10/LOT-E/21/SN1006?15=261001&16=260921&11=260502&13=260503&30=4&3103=000700,Widget F,A01-6,3,Batch 2,A items - warehouse A,Sam,,Sam,,

Import requirements

Keep count-pack columns in the import

Run the barcode check before scanning, but do not strip fields that supervisors need after the count.

Batch and scope: Keep the assignment batch or count scope so the variance reviewer can group follow-up work.
Counter and location: Keep assigned counter, location, bin, or aisle fields so rows trace back to the person and place counted.
Label durability: Replace worn rack or bin labels. Keep one full-height, high-contrast scanner-readable label with quiet zones, edge clearance, and a smooth glare-free scan surface.
Cycle handoff: Keep bin-first scan proof, count attempt policy, reason-code prompt, pending-review owner, and release status with the scan-proof export.
Quantity and evidence: Keep expected quantity, reason, location confirmation, counter sign-off, and supervisor review columns for the count pack.
2D barcode data: Keep lot, date, serial, count, weight, element-string, scanner-output, and Digital Link fields when labels need QR, Data Matrix, or SSCC data; the 2D audit checks decoded values before label work.

The import CSV keeps source values exact. Use the spreadsheet-safe CSV when people will open clean rows in spreadsheet software.

Spreadsheet, audit, proof, print, and SSCC exports

Preview (0 rows)

0 rows loaded

Compare barcode pilot results by device

Local-only comparison CSV

Enter up to four tested devices or setups. The comparison stays on this device and holds any setup that misses one of the five displayed release targets.

Pilot release targets

First-scan success: ≥ 95%
Average scan time: ≤ 2 s
No-read rate: ≤ 2%
Duplicate warnings: ≤ 0
Offline sync: PASS

Tested devices and setups

Use one row per device, app, scanner, or barcode setup represented in the pilot.

Pilot row 1 Device or setup Symbology Scan attempts First-scan successes Average scan time (seconds) No-read exceptions Duplicate warnings Offline sync

Pilot row 2 Device or setup Symbology Scan attempts First-scan successes Average scan time (seconds) No-read exceptions Duplicate warnings Offline sync

Pilot row 3 Device or setup Symbology Scan attempts First-scan successes Average scan time (seconds) No-read exceptions Duplicate warnings Offline sync

Pilot row 4 Device or setup Symbology Scan attempts First-scan successes Average scan time (seconds) No-read exceptions Duplicate warnings Offline sync

Tested setups: 0
READY: 0
HOLD: 0
Incomplete: 0

Rollout decision

HOLD

Enter a tested setup or load the sample before releasing the barcode pilot.

Release gaps by setup

No represented setup misses a release target.

Per-setup release evidence

Active pilot rows will appear here.

Barcode pilot results and release decisions by setup
Device or setup	Symbology	First-scan success %	Average scan time (s)	No-read %	Duplicate warnings	Offline sync	Decision

What this checker looks for

The checker focuses on data problems that slow down barcode stock counts or create bad scans.

Missing SKUs or barcodes
Barcode-to-item or pack conflicts and GTIN check digit errors
No-read fallback, repair ticket, replacement-label, re-scan, print-readiness, and cycle handoff proof gaps
Product/location collisions and scan namespace overlap
Location-code spacing, separator, and zero-padding drift
Empty quantities or broken columns
Preserved batch, scope, counter, and sign-off fields
GS1 element-string, scanner-output, Digital Link, and SSCC readiness

How to fix issues

Fix the source list, export a fresh CSV, and run the check again before importing into Mobile Inventory.

Download the issue CSV for rows to fix
Copy the repair summary into the item-master or label ticket
Use owner, source field, priority, fallback proof, and verification columns for handoff
Keep damaged or missing labels on a manual-count route until replacement-label or supervisor proof is attached
File cycle handoff proof with bin-first scan, count attempt policy, reason-code prompt, pending-review owner, and release status before posting
Normalize location codes before bin-label printing or phone scanning
Use the 2D audit and SSCC packet before label generation
Keep one stable SKU and one barcode per item or package configuration
Use decoded AI row matches to catch stale lot, date, serial, count, or weight data
Leave quantity fields empty only when the count should start from zero

Next step

When the list is clean, use it as a CSV template or import it into Mobile Inventory for phone-based scanning.

Download a clean template
Count by phone
Export a variance report

FAQ

Is my CSV uploaded to a server?

No. This first version runs the check in the browser.

Which columns are required?

The checker expects columns such as SKU, Barcode, Description, Location, and Quantity. It accepts common column name variations and validates numeric GTIN-style barcodes when their length matches UPC, EAN, or GTIN formats.

Can I scan after the checker passes?

Yes. A clean barcode list is a good starting point for Mobile Inventory or another barcode count workflow.