RFID & NFC Smart Label Production Guide

Purpose and production context

Identify whether the job is UHF RAIN RFID, HF/NFC or a construction carrying both. Record the data owner, standard/version, required memory bank, serialization authority and read-back acceptance record. An SGTIN-96 request must include a valid GTIN, the licensed GS1 Company Prefix length, a numeric serial rule that fits 38 bits and the intended filter value. NFC work needs the exact NDEF record type, payload, language code where applicable and the inlay's usable NDEF capacity—not only total chip memory.

Do not let a label converter invent production identifiers. The artwork proof should show the human-readable GTIN or serial representation that will be reconciled with encoded data, but the encoded value requires its own approval field.

Definitions and distinctions

Use the SGTIN-96 EPC Encoder / Decoder to create a documented test vector. Encode one tag, read it with a separate device or printer verification command, then decode that read-back value rather than the source string. Compare GTIN, serial, filter and hexadecimal EPC. For NFC, use the NDEF Memory Estimator before writing a tag and then scan the physical tag on more than one intended device class.

A payload that technically fits can still be unsuitable: long redirect URLs may change, text encoding can consume more bytes than visible characters suggest, and locked tags cannot be corrected. Keep an approved golden tag and a plain-text record of the expected decoded fields.

Inputs, units and method

From the actual converted roll, measure the printed label repeat, inlay repeat and the chosen leading-edge reference to the inlay's specified chip or encode-zone position. Use several repeats rather than one. The Pitch Drift Checker converts a small measured pitch difference into cumulative offset and identifies the first label that leaves the entered alignment window.

Pitch drift is not the same as a constant phase error. A constant phase error may be corrected by registration or web phase; a pitch mismatch grows with every repeat and requires a material or converting correction. Record feed direction, unwind orientation, gap/mark reference and whether the inlay drawing measures antenna, chip or encode zone.

Worked production example

Printer families express RFID program position in millimetres, inches, dots or device-specific forward/backfeed coordinates. Use the Encode Position Converter to document neutral unit conversions and whole-dot rounding, then apply the printer manual's origin and sign convention. Do not copy a dot value between 203, 300 and 600 dpi devices.

Run the printer's RFID and media calibration on the exact label/inlay construction. An apparently correct print start does not prove the encoder antenna is aligned. If voids cluster at one position or every label fails, recheck calibration, supported inlay placement, read/write power and command syntax before increasing the production reserve.

Decision checklist for production allowance

Encode a representative pilot roll using the intended speed and retry policy. Separate first-pass success, successful retries and final void/reject tags. Enter those observed values in the Encoding Throughput Planner. Its output is an expected starting quantity and time, not a guarantee: intermittent RF interference, damaged inlays and stop/start handling can make a long run behave differently from a short trial.

Release enough unencoded material to cover expected loss plus the organization's normal statistical reserve. Keep face-print spoilage separate from RFID voids so purchasing and root-cause review can see which process consumed the allowance.

Common mistakes and cautions

• Approved data owner, schema/version, GTIN and serialization range recorded.
• Golden EPC or NDEF payload encoded, read back and independently decoded.
• Human-readable and machine-readable identity agree.
• Inlay type, chip, memory, web width, pitch, position and unwind direction match the job ticket.
• Printer resolution, media sensing, RFID calibration, program position and retry behavior documented.
• First-off labels pass print quality, encode/read-back and application/read-zone trials.
• Pilot yield and void count support the released material quantity.
• Final sample, data log and unused serial disposition are retained according to customer procedure.

Related workflow, sources and limitations

GS1's EPC Tag Data Standard controls SGTIN encodings and the 38-bit numeric serial limit used here. NFC Forum NDEF/Type 2 structures and manufacturer documentation control actual usable memory. Zebra, SATO, TSC and Avery Dennison documentation show that program position, pitch and retry behavior are printer-specific. These tools therefore calculate transparent data sizes and geometry but never select RF power, predict read range or certify a finished label. Sources: GS1 EPC Tag Data Standard, GS1 EPC Encoder/Decoder, Zebra inlay placement guidance, and SATO tag-offset guidance. Last reviewed: 2026-09-02.