When an RFID printer prints VOID across a label, it has tried to write the chip and could not verify the result. An RFID label void or encoding failure usually traces to one of six layers: calibration, programming position, media, RF power, the data being written, or the printer’s own reader module. Each leaves a different pattern, so read it first and fix one layer at a time.
What a VOID label is telling you
On Zebra printers the ^RS command governs what happens next: the failed label is ejected with VOID printed across it, and the same data is tried on the next label, up to a set count (1–10, default 3). If the error persists, the printer drops the format and carries on, pauses, or enters error mode, as configured.
A single VOID followed by a good label is the system working as designed. A run of voids is a pattern. Zebra printers keep valid and void label counters, shown on the printer configuration label and resettable from the RFID menu: note them before changing anything, as your baseline.
Read the pattern before touching settings
| What you see | Likely layer | First check |
|---|---|---|
| Every label voids | Calibration, or media the encoder cannot use | Media calibration, then tag calibration; confirm the roll is passive UHF Gen2 |
| Printer stops at the inlay, not the gap | Media calibration | Label length was calibrated to the inlay; recalibrate to the gap |
| Intermittent voids across a roll | Placement, pitch or power | Inlay position and pitch against the printer’s spec; re-run tag calibration |
| One roll voids, other rolls are fine | Media | Read the voided labels on a desktop reader; swap in a known-good roll |
| Voids began after a software, firmware or media change | Settings overridden or stale | Compare the label software’s RFID settings with the printer’s; recalibrate |
| ”Cannot communicate with reader”, or RFID settings missing | Printer’s reader module | Power off, wait at least 10 seconds, power on |
Most of these causes and fixes come from Zebra’s RFID issues table.
Calibrate in the right order
Zebra’s RFID Programming Guide 3 separates media calibration, which learns label length and the gap, from RFID tag calibration, which finds the programming position, the antenna element and the read/write power. Run them in this order:
- Load the roll and run media calibration.
- Close the printhead and feed one label.
- Run RFID tag calibration with the neighbouring transponders left on the liner, so the printer finds settings that do not encode them too.
- Print a short test run and read the valid and void counters.
- Adjust position or power by hand only if calibration does not give a clean result.
Re-run tag calibration every time the RFID media changes. A printer that stops at the inlay has skipped or botched step 1.
This is not Zebra-only: TSC’s T800 desktop RFID printers feed three labels during calibration to set encoding position and power. TSC’s Printronix calibration notes add that a dead or weak tag near the decision point stops calibration until you restart it elsewhere on the roll.
Programming position, and the software that overrides it
The programming position is where along the label the printer stops to write, and it is the setting tag calibration finds. On Zebra Link-OS printers, ^RS sets it as a forward feed (F0 upwards) or a backfeed (B0–B30), with F0, the leading edge, as the default. Two behaviours catch people out:
- A position sent in a label format stays in force until a new one is sent or tag calibration runs, so last month’s format can leave the wrong position behind.
- RFID settings sent by label-design software override the printer’s own, so the next print job can undo a clean calibration.
Pick one source of truth: either calibration owns position and power and the label format leaves them out, or the software sets them deliberately for each roll. Then use the printer’s RFID test, which reads and writes without moving the media, to confirm the encoder sees the tag before printing a batch.
Media the encoder cannot work with
Check the media type first. EPC Class 1 Gen 2 (ISO/IEC 18000-63, also marketed as RAIN RFID) is a passive UHF standard, so an HF 13.56 MHz or NFC inlay will never encode on a UHF module. Zebra, for one, states that Gen 2 is the only tag type its current RFID printers support.
Zebra’s placement guidelines define inlay centre and inlay position, each typically to ±3 mm, and inlay pitch. Transponders placed too close together let the printer couple to more than one; Zebra’s minimum pitch for the Link-OS printers in its guide is 16 mm. These are Zebra’s figures, not universal ones. Zebra ties low yields, meaning too many voids per roll, to labels outside that specification.
Keep artwork clear of the chip too: Zebra warns that print quality can suffer when printing directly over the transponder, especially in the area around the chip, so design the label around the chip location.
Zebra advises testing a small batch before buying in quantity, and so do we. Identium designs and manufactures UHF RFID inlays and labels; for shipping cases, see our UHF RFID carton labels. Name the printer model in your enquiry so pitch and offset are specified against it.
Write power: too little and too much both fail
Tag calibration sets read and write power, and both directions fail. Zebra’s write-power reference explains that too little power can leave the tag unable to be programmed, while too much can cause communication errors or program the wrong tag. Turning power to maximum trades a visible fault for a hidden one, because the data may land on a neighbouring tag.
Many UHF chip datasheets list write sensitivity separately from read sensitivity, and where they do, the write figure is usually the weaker one: the chip needs more power to write than to answer. So a tag slightly off position can respond to a read and fail the write at the same field strength. Our guide to tag sensitivity on a datasheet explains those figures, and the Gen2 standard has a tag error code for this case: insufficient power.
Print speed is not among the void causes in Zebra’s RFID Programming Guide 3 or its ZT411 troubleshooting table. If you suspect it, change speed alone and compare void counts on the same roll.
When the data is the problem
EPC length. The PC word in EPC memory carries length bits that tell the tag how many 16-bit words of EPC to report. Under GS1’s EPC UHF Gen2 air interface standard (section 6.3.2.1.2.2 in version 2.0.1), an encoder that changes the EPC length must write new length bits for the tag to report it, and a write of an unsupported length is not executed. On a Zebra, the ^RF command writes 96 bits from EPC bit address 20h by default; only its memory bank A mode, on the ZD500R, ZT400 and ZT600, sizes the write to the data and updates the PC bits. If your EPC is not 96 bits, confirm how your printer handles it; a chip that cannot take the requested length returns memory overrun.
Locked banks. A locked Gen2 EPC bank accepts a write only after the encoder presents the correct access password; a permalocked bank accepts none. Both stay readable, which is why a recycled or pre-encoded label can read normally and still void every time. Look for the Gen2 error memory locked (listed in the standard’s error-code annex) or, on a Zebra, GEN2 MEMORY LOCKED. LOCK ERROR is a different fault: the printer could not change the tag’s lock bits.
The error-code table in Zebra’s RFID Programming Guide 3 also lists NO TAG FOUND, WRITE FAILED, PROTOCOL BAD EPC and GEN2 MEMORY BAD PC. Decide the lock policy before encoding: our UHF chip and memory guide covers the banks.
Reader-module and comms faults
The encoder is a reader module with its own start-up, and Zebra’s troubleshooting table lists these faults:
- Printer cannot communicate with the RFID reader: power off, wait 10 seconds, power on.
- RFID parameters missing from setup: the printer was power-cycled too quickly for the reader to initialise; wait at least 10 seconds.
- Outdated firmware: printer or reader firmware is on Zebra’s list of causes.
- RF interference: a nearby fixed reader can disrupt encoding, so move the printer and keep the media door closed while programming.
Region matters too. On a Zebra, the error-code table in its RFID Programming Guide 3 includes COUNTRY CODE ERROR, and the codes available depend on the printer’s configured region. In India, select the printer’s India country code: the licence-exempt band is 865–868 MHz under G.S.R. 853(E) of 2021, and an India setting shown as 865–867 MHz is a tuning within that allocation. Watch for a unit configured for the US 902–928 MHz band.
Printer or inlay? A quick isolation test
- Read three voided labels and three good ones on a desktop UHF reader, away from metal.
- A voided label answering with a blank, all-zeros or factory-pattern EPC was never encoded, or the write failed. Read its TID bank: a response usually confirms the chip is healthy, so look at position, power, locks or data.
- A voided label that does not answer at all, even against the reader’s antenna, is dead or damaged. Check the roll and the handling for physical damage to the inlay.
- Load a known-good roll on the same printer. If it encodes cleanly, the suspect roll is at fault; if it voids too, look at the printer and its settings.
- Re-run tag calibration on the suspect roll at a different point. Zebra notes that consistent encoding failures may point to the tags, the label formats or the transponder placement.
Once labels have left the printer and the trouble appears on site, our field troubleshooting guide takes over.
On the iT4R and industrial printers
The method above carries across brands; menu names and command syntax are what change.
The iT4R desktop RFID printer (current production model IT4RL) encodes passive UHF EPC Gen2 labels only, including on-metal label stock up to 1 mm thick; it does not encode HF 13.56 MHz cards, NFC tags or LF livestock tags. Its free Labelsoft software can print each tag’s EPC and TID on the label face, so a voided label can be checked against a desktop reader. Ask us for the iT4R calibration procedure rather than applying Zebra or TSC menus to it.
For industrial volumes, Identium supplies Zebra, TSC and Honeywell printers; see our RFID printer range. For buying, see the RFID printer buyer’s guide and the India RFID Store’s printer price guide.
What to send us when a roll keeps voiding
- Printer model and firmware version
- Label-design software name and version, and whether it sends RFID settings
- EPC length and scheme, and your lock policy
- Inlay type, label size, roll specification and pitch
- Valid and void counter readings, before and after calibration
- Three voided labels and three good ones from the same roll
With that, we can tell you which layer you are most likely stuck in. If the answer is a different inlay or label, custom tag orders typically turn around in 5–10 days. Contact our team with the details.
Further reading on Identium One
- SGTIN-96 encoding explained bit by bit — what the printer is actually writing to the EPC bank.
- Gen2 EPC memory bank and PC word — why an EPC-length mismatch makes a write fail.