English
简体中文
Русский
Español
ไทย
Tiếng Việt
Bahasa Melayu
Bahasa Indonesia
لالعربية
Deutsch
Batch Number Coding That Will Not Read: What to Check First On Line
Release time:
2026-09-20
Fixing batch number coding that fails to read: substrate contrast, code height and quiet zone, bad traceability data, and a compatible chip fault.
Summary: A batch code that will not read is rarely a dead coder, and swapping the machine out usually solves nothing at all. This walks through the checks worth doing first: substrate contrast, code height and quiet zone, bad traceability data, and an intermittent compatible chip.
A coder that will not read is rarely a dead coder. It prints, the operator sees a code, and the scanner disagrees. That gap between "looks fine to me" and a failed read is where most batch number trouble lives. Work through this order before booking a service visit.
Check Contrast Before Hardware
Print on the substrate the line actually runs, not a scrap of white carton from the bench. Substrate decides contrast more than any setting. Kraft board, coloured film and glossy laminate give three different read rates from identical settings. Ask one question first: did this code read last week on this exact product? If yes, nothing on the coder changed - the substrate did. That points at incoming material, not at ink.
Height, Ratio and Quiet Zone
The code must be tall enough for the scanner to resolve and short enough to fit the space you have. Squeeze a batch number into a two-millimetre band and the read rate drops fast. Then check the quiet zone. Packing a logo or a carton seam against the code causes most intermittent reads nobody can reproduce.
When the Data Itself Is Wrong
A surprising share of failures are not print quality. The code reads, the scanner accepts it, and the traceability system rejects the record because the format does not match the host. Two things go wrong. The date format flips when someone edits a template at shift change. Or the counter resets, so two batches in one week carry the same number. Both look like scanner faults. Neither is.
Compatible Chips and Intermittent Reads
On a coder running a compatible cartridge chip, a dropped code has one more suspect. If the controller reads identification data late or intermittently, the print still lands - but the timing shifts enough to affect how the code is laid down on a fast line. Separating this from your settings is simple. Fit a known-good chip from a batch that reads cleanly and run the same job. If the reads come back, the chip is the variable. Keep one reference chip bagged for this test.
What to Settle at Handover
Write the read rate on the handover sheet, not just the fact the line ran. A coder at ninety-eight percent and one at eighty-five percent look identical from the far end of the hall, yet both get reported as running. Record the substrate batch beside it. When a code stops reading two weeks later, that line tells you whether the material changed or the machine did.
For more on CIJ TIJ consumables and compatible chips, browse our industry insights.
Related products:
related news
E-mail address:
Hotline：
All referenced brand names including Linx, Imaje, Domino, VJ are used solely for illustrating product compatibility scope.
Topmark has no affiliation, authorization, partnership or official endorsement with any industrial printer manufacturers.
All products offered by Topmark are third-party compatible consumables, not genuine original OEM spare parts.
No trademark ownership is claimed for any trademarks mentioned herein.
