Your labels print perfectly — but the tags don't encode, a handheld reads nothing, and every failed label comes out stamped VOID. That's the most reported RFID printing problem in the industry, and it has a short list of root causes. This guide walks through them, gives you a pre-flight checklist that prevents most mass failures, and maps the JNXRFID print–encode–verify workflow that keeps bad labels off your line.
Root Causes
VOID is not a defect — it's the printer quarantining a label it could not encode or verify, so a blank tag never silently ships to your line. The failure modes below are documented in public RFID-industry support resources and in day-to-day field service; they apply across RFID printer brands because the underlying process is the same: the printer must find the chip, write to the right memory, and read the data back.
The most common cause, and the one behind most “it worked yesterday” mass failures: nobody re-ran RFID calibration after changing the label roll. Different smart-label rolls place the inlay at a different offset and pitch. If the encoder is aiming where the chip used to be, every label fails. The same symptom appears when the tag position offset in the driver doesn't match the media spec.
RFID chips have separate memory banks (EPC, User, TID), and not every tag has a User bank. Writing to a bank the tag doesn't have — or pushing more data than the tag's capacity (e.g., 26 characters into a 96-bit / 24-hex-character EPC) — fails the write and prints VOID. Check the inlay's spec sheet before you lock your encoding scheme.
Tags that were previously locked, or come from a converter with tamper/lock settings enabled, will reject writes. If the TID reads but the EPC won't take, suspect a locked bank or wrong password rather than a hardware fault.
Many “my printer prints but doesn't encode” tickets end at the driver: the label template sends print-only content, or the EPC length in the driver (96-bit vs 128-bit) doesn't match the data scheme (e.g., SGTIN-96). The printer obediently prints — and writes nothing.
Sources: public RFID printer support documentation and field-service write-ups across major printer vendors. Figures are industry-published, not JNXRFID measurements.
Prevention
Run this after every media change and before every production run — it prevents the large majority of mass VOID incidents:
Lock driver settings behind an admin profile so operators can't accidentally switch the template to print-only — cause #4 is entirely preventable.
Model Selection
| Model | Frequency | Form Factor | Best Fit |
|---|---|---|---|
| JD240TR | UHF | Desktop | Retail backroom / office encoding stations, low-to-mid volume |
| JD240THR | HF/NFC | Desktop | Authentication and HF programs with desk-side encoding |
| T430R | UHF | Entry industrial | First RFID printer for cost-conscious teams stepping up from barcode |
| JT240TR | UHF | Industrial | Item-level source tagging and high-volume encoding programs |
| JT240THR | HF/NFC | Industrial | Volume brand authentication (ISO 15693 & 14443A) |
Every JNXRFID RFID printer ships with free LabelSoft label design software — no subscription tiers. JNXRFID printers use their own RFID encoding modules and are positioned as a compatible-workflow alternative to offerings from vendors such as Zebra® (for example the ZD621R) — not as Zebra products.
Close the Loop
VOID handling is only half the quality story. The other half is catching bad labels before they leave the print room:
Lay out the label in LabelSoft with the EPC or HF data structure your program requires — scheme and data length matched to the tag spec from day one.
One pass, one unique identity per label. Verify-after-write flags failures; VOIDed labels are re-printed, not stocked.
Spot-check or 100% verify on a JRE-series desktop reader — powered by the genuine Zebra RE40 module and compatible with Zebra 123RFID Desktop — so teams already in the Zebra toolchain integrate without relearning.
Verified tags flow into portals, handhelds, or checkout stations. One vendor across the print–encode–verify chain.
Typical first-pass encode yields on a controlled bench exceed 99.5%. We'll help you set up the calibration SOP and verification bench during your evaluation — that's where most RFID printing programs actually succeed or fail.
FAQ
VOID is the printer's way of quarantining a label it could not encode or verify. The three most common root causes are: (1) the encoder cannot detect the inlay — usually because RFID calibration was not re-run after a media change or the tag position offset is wrong; (2) the data is being written to a memory bank the tag does not have, or exceeds the tag's memory capacity; (3) the EPC bank is locked or an access password is blocking the write. These failure modes are documented in public support resources from major RFID printer vendors, and they apply across RFID printer brands.
Yes — this is the single most common cause of sudden mass encode failures. Different smart-label rolls can place the inlay at a different position and pitch, so the encoder must re-learn where the chip sits. Best practice: after every roll change, run media calibration, then RFID calibration, then print the printer's built-in RFID test label. Lock driver settings (EPC length, encode+print mode, region) behind an admin profile so operators cannot change them.
Add a verification step after printing. Enable verify-after-write on the printer so failed encodes are flagged and reprinted automatically, then spot-check or 100%-verify a sample of encoded labels on a desktop reader. JNXRFID JRE-series desktop readers are powered by the genuine Zebra RE40 module and work with Zebra 123RFID Desktop software, so a JNXRFID printer + JNXRFID reader verification bench drops into an existing Zebra-toolchain process. JNXRFID is an independent company and is not affiliated with or endorsed by Zebra Technologies.
JNXRFID industrial RFID printers support challenging media programs — including on-metal tag workflows and thick media — and we validate tag print-and-encode performance before shipment for pilot projects. Tell us the tag, chip, and inlay you plan to use, and we'll confirm fit on an evaluation unit first. Note that on-metal tags need on-metal-rated inlays; ordinary inlays placed on metal will detune and become unreadable regardless of printer.
We'll confirm printer and media fit — and validate print-and-encode performance on your actual tags before you commit. Evaluation units ship within 1–2 weeks.
Contact JNXRFID