Label Data Validator
Send CIS your warehouse label data file before it goes to print. We run 16+ automated checks for duplicates, typos, blanks, sequence gaps, and formatting problems that lead to reprints.
In business since 2013 | Labels | Die-cut foam for packaging and tool organization | Warehouse rack labels and signage
Check your label data before it goes to print
Before your warehouse labels and signage go to print, CIS checks the label data file behind them. A CIS label specialist reviews the file with you so problems are fixed before production, not after the labels are on the racks.
A pre-print data check CIS offers its warehouse labeling and signage customers.
How the pre-print check works
Send your file
Send CIS the .xlsx, .xls or .csv file you plan to print from.
CIS checks the data
CIS runs 16+ automated checks on your file.
A specialist calls you
A CIS label specialist calls you to go over the pre-print check.
Send your label data file to CIS
Tell us who you are and attach the Excel or CSV file you plan to send for printing. A CIS label specialist will call you to set up your pre-print check.
Need these printed? See printed FNSKU and UPC label rolls.
CIS ran Zion Solutions Group's label data through the CIS Label Data Validator, caught errors before print, and saved them about $15,000 in reprints.
16+ automated checks
The checks CIS runs on your file, built from the problems CIS sees most often in warehouse label data files.
Blank or missing data
Empty cells in barcode, human-readable, arrow, aisle, level, location, and location type columns.
Duplicate barcodes
The same barcode on more than one label in a sheet (and across totem levels).
Near-duplicate barcodes
Barcodes one character apart where a letter changed, a common typo pattern. Runs at any file size.
Barcode characters and symbology
Characters that the detected symbology cannot encode, missing Code 39 asterisks or % start characters, and mixed letter case.
Extra spaces
Leading or trailing spaces, doubled spaces, and tabs inside barcode or human-readable cells.
Hidden or special characters
Non-printable or non-ASCII characters that can corrupt a scan.
Barcode vs human-readable
The printed text should match the barcode, or match it once dashes and dots are removed.
Arrow values
Arrow cells must use a known value such as U, D, L, R, N or Up, Down, Left, Right, None.
Arrow direction consistency
Mixed arrows inside one aisle and level, where a small minority points the other way.
Location sequence gaps
Missing location or bay numbers inside an aisle's numbered range.
Location type consistency
Location types that are rare within a level, which often means a typo or a formula error.
Level count consistency
Levels in an aisle with a different label count than the rest.
Skipped levels
An aisle that uses levels A, B, and D but not C, or 1, 2, and 4 but not 3.
Barcode structure cross-check
Learns how barcodes are built from the other columns (for example AISLE-BAY-LEVEL-POS) and flags rows that break the pattern.
Totem consistency
All barcodes on one totem row should point at the same aisle and bay.
Barcode length and print fit
Estimated printed barcode width at the chosen bar width, compared with the label width.
Color values
Color columns with values that are not hex codes or color names.
Arrow and color by level
Labels whose arrow or color breaks the pattern the rest of that level follows, and files where every arrow is identical.
Check digits and check strings
WMS check string columns should hold a fixed number of digits on every row.
Placeholder barcodes (pending)
Barcode cells that hold a location code or a placeholder word instead of a real barcode. Reported as pending, not as errors.
Pattern breaks and outliers
Aisles with unusual label counts, values with an unusual length, and text mixed into number columns.
Cross-sheet duplicates
Barcodes that appear on more than one sheet. Same-type sheets are errors; rack plus totem overlap is noted.
Aisle sign match
Aisles in the label data that have no aisle sign, and signs for aisles that are not in the data.
Original vs updated sheets
When a file has an original and an updated sheet: additions, removals, and changed records.
Label count and file profile
Labels per sheet, totem label math, optional expected-count comparison, and sheets the profiler could not read.
What happens to your file
Your file goes to the CIS label team and is used to prepare your pre-print check. A CIS label specialist calls you to go over what the checks found.
Want to check a file yourself first? Read how to check warehouse label data before printing.
Label Data Validator FAQs
Send us your label data file for a pre-print check. Same-day quote: 770-561-5285.
