Catch invalid barcodes on every row before you export or print
For ops teams tired of reprint runs — GS1 check digits, GTIN lengths, and GS1-128 AI structure verified per row with inline error messages. Fix data in place, export only valid labels.
The per-row validation engine checks every barcode in your import before you export or print — GS1 check digits, GTIN lengths, GS1-128 AI structure, and symbology-specific rules. Invalid rows highlight inline with a plain-language reason so you fix the source data instead of discovering errors at the scanner. Valid and invalid counts update live as you edit. Download an invalid-rows workbook to correct your spreadsheet offline, then re-import. Validation runs entirely in your browser: Zebralines never uploads your catalog to validate it on a remote server.
One bad row in a thousand means a full reprint — unless you catch it first
Spreadsheet imports carry transposed digits, wrong GTIN lengths, and missing check digits that only surface when a retailer scanner beeps reject.
Desktop tools validate on export — after you have already committed to a print run of 500 labels.
GS1-128 payloads with missing FNC1 separators pass visual inspection but fail at the warehouse portal.
Ops teams waste hours reconciling which SKUs in a batch were wrong instead of fixing the source file before print.
Zebralines validates every row as you import and edit — inline, local, and specific about what to fix.
Inline errors with plain-language reasons on every row
Invalid rows highlight in the bulk preview and invalid-rows panel with the exact failure: wrong check digit, GTIN too short, unsupported character, or GS1-128 AI structure error. Edit values in place and watch the row turn valid in real time. No cryptic error codes — messages written for operators, not GS1 specification authors.
GS1 check-digit and GTIN length verification
EAN-13, UPC-A, and GTIN-family symbologies get automatic check-digit computation and verification via the GS1 Luhn algorithm. Enter 12 digits and Zebralines adds the check digit; enter 13 and it verifies the last digit matches. GTIN length rules enforce retailer-compatible symbol sizes before export.
Export valid labels and download invalid rows separately
Export and print include only valid rows — invalid entries are excluded automatically from PNG, PDF, ZIP, and print queues. Download an invalid-rows Excel workbook listing every failure with the original column data so you can fix the source spreadsheet offline and re-import. Valid row count updates live in the export panel.
Three steps. No jargon.
Import your spreadsheet
Drop a CSV or Excel file in bulk mode. Zebralines maps columns and begins per-row validation immediately as rows load.
Review inline errors
Open the invalid-rows panel to see failures grouped by reason. Edit values in the grid or fix your source file and re-import.
Export only valid labels
When valid row count matches your target, export PNG, SVG, PDF, ZIP, or send to print — invalid rows stay out of the output.
Built for teams like yours
Quality assurance lead
Gate every production label run behind per-row validation. Download the invalid-rows report for suppliers who sent bad GTIN data.
Marketplace seller
Import 2,000 SKUs from a supplier spreadsheet and fix check-digit errors before printing FBA labels — not after Amazon rejects the shipment.
Logistics coordinator
Validate GS1-128 AI strings in a pallet-label CSV before the dock prints. Catch missing FNC1 separators before they halt receiving.
Works well with this
Common questions
GS1 check digits, GTIN lengths, symbology-specific character rules, and GS1-128 Application Identifier structure on supported plans. Errors show inline per row.
Catch invalid barcodes on every row before you export or print
Per-row validation runs locally. Zero catalog upload.