Paper, plastic or glass
Start with the complete item.
Check the available label area, curvature, contents and packaging layers. Confirm the adhesive and exposure requirements, then test reading after the label is applied.
RFIDAK / Item identification
Identify retail items, assets and cartons with an external UHF reader. Choose the finished inlay, mounting position and data workflow around the task your team needs to complete.

01 / Start at the read point
A bench read does not establish that a packed carton, dense shelf or moving item will be identified in your operating workflow.
Match the inlay and placement to the actual object.
Confirm region, antenna, settings and the available read window.
Map the observed EPC to the correct item and business event.
Confirm the installation country. Regional UHF bands and reader settings vary. Specify the country and required reader configuration, then confirm the selected inlay covers that deployment. A broad UHF label description is not a worldwide operating approval.
Set a measurable acceptance test. Provide the item count, orientation, density and movement. Record missed items, unintended reads and completion time separately. Agree the acceptable result before ordering a test batch.
Need a consumer phone tap? Built-in NFC cannot read this UHF family. An external UHF accessory needs compatible hardware and software. For a web-link tap with phone NFC, see custom NFC stickers →
02 / The finished label
An inlay is the chip-and-antenna assembly. The finished label adds the face material, adhesive and liner. Approve the construction that will actually be supplied.
Start with the complete item.
Check the available label area, curvature, contents and packaging layers. Confirm the adhesive and exposure requirements, then test reading after the label is applied.
Review a UHF on-metal construction.
The antenna and mounting design must suit the actual metal surface. Confirm the finished thickness, available space and orientation. NFC isolation layers and UHF on-metal designs serve different technologies.
Test placement at the intended fill level.
Contents, closures, adjacent items and stacking can change the result. Compare label positions on representative filled items, including the orientation and load density expected at the read point.
03 / Chip selection
These chip characteristics help define a requirement. They do not guarantee an installed read distance, a label configuration or retailer approval.
Swipe to compare chip memory and ordering checks.
| Chip / buying guide | EPC memory | User memory | Check before ordering |
|---|---|---|---|
| Impinj Monza R6 ↗ | Up to 96 bits | None | Confirm the EPC format fits. This chip has no Access or Kill password and is not killable; do not apply R6-P specifications. |
| Impinj M730 ↗ | 128 bits | None | Check the approved inlay and encoding. Access and Kill share a 32-bit password; approve the exact controls before production. |
| NXP UCODE 8 ↗ | 128 bits | None | NXP marks UCODE 8 / 8m No Longer Manufactured. Confirm traceable supply and a repeat-order plan; UCODE 8m has different memory. |
Fit the encoded identifier. EPC memory is specified in bits. Confirm the required scheme and encoded length with your system or program owner. None of these three parts has user memory for an additional application payload; keep the wider item record in the agreed system.
Confirm supply and substitutions. NXP marks UCODE 8 / 8m No Longer Manufactured. Confirm traceable stock, quantity and repeat supply in writing. A substitute chip or inlay needs renewed encoding and mounted-reader checks before approval.
04 / Print & encode
Printing on a roll and encoding its RFID chips are separate operations. Identify the owner of each step and the data passed between them.
You print or encode locally.
Approve printable stock, RFID inlay and the exact printer-encoder configuration on a sample roll.
Artwork prepared for your encoding line.
Confirm whether the visible barcode or serial must match the EPC, and which team controls that mapping.
Print and EPC prepared together.
Approve the data file, serial allocation, read-back report, rejection handling and supported lock settings.
Send the complete printer specification. Include model, installed UHF RFID option, supported chip and firmware or software requirements. Approve the inlay position, media calibration, liner, label pitch, roll core, outer diameter and winding on sample stock.
Keep EPC, TID and printed data distinct. Agree the encoding scheme, unique serial allocation and mapping file. Factory TID is separate from writable EPC. Approve read-back, duplicate and reject handling before applying any permanent lock or supported password.
For a retailer program, obtain its current item-category, finished-inlay, placement and encoding requirements. Request evidence naming the proposed inlay. A chip name, EPC format or general RFID standard alone does not establish program approval.
One order record
Keep the chip, inlay, label and data requirements together. Request documents for the exact article when environmental performance or a customer program makes them necessary.
Send your label requirements →Before a production order
The sample is the configuration your team will accept, not just a label that responds to a reader.
Ask about UHF samples →05 / Your project
Choose the application, surface and supply format. On the contact page, add your country, reader and printer models, EPC requirement, artwork, dimensions and quantity.
Your quote will confirm the chip and inlay, availability, construction, sample charges, encoding, unit pricing and delivery schedule.
Read the sample policy →Buyer questions
A phone's built-in NFC reader cannot read this UHF EPC Gen2 label family. Use a compatible external UHF handheld, fixed reader, sled or accessory with the required software and regional settings. If the requirement is a consumer phone tap to a website, evaluate an NFC label instead. Phone operating-system support for an external reader also requires confirmation.
There is no universal result for a chip or sticker name. The finished antenna, item material, contents, placement, reader, power settings, orientation, density and available reading time affect performance. Specify the actual task and test known quantities. Record expected items missed, unintended nearby items read and the time needed to complete the task separately.
Test the finished item before selecting the construction. Metal can require a dedicated UHF on-metal design; liquid contents, foil closures and placement can change reading performance. Compare suitable candidates at the intended fill level, orientation and reading point. An NFC ferrite-backed label is not a substitute for a UHF on-metal label, and a substrate name alone does not establish suitability.
Monza R6 provides up to 96 bits of EPC memory; M730 and UCODE 8 provide 128 bits. These three parts have no user memory. Select against the required EPC format and the finished inlay, then confirm the exact chip and data controls. Monza R6 does not support Access or Kill passwords. NXP marks UCODE 8 / 8m No Longer Manufactured, so confirm traceable availability and the repeat-supply plan before ordering.
Printing support and RFID encoding support are separate checks. Confirm the exact printer model, installed UHF RFID module, supported chip and protocol, firmware and software. Match the approved inlay position and media settings, plus label pitch, liner, core, roll diameter and winding. Test print quality, EPC writing and read-back on sample stock; a printer brand or series name is not enough.
Define the EPC scheme and bit length, identifier ownership, unique serial allocation and mapping to printed barcodes or numbers. Keep the factory-programmed TID separate from writable EPC data. Agree read-back checks, duplicate and reject handling, and any supported lock or password settings for the exact chip. Monza R6 is not killable; M730 shares a 32-bit Access and Kill password. Do not apply one chip's security settings to another or permanently lock before approval.
No. Obtain the current program requirements for the item category, finished inlay, encoding, placement and verification. A chip name or a general RFID standard is not proof that the supplied finished label meets a particular retailer program. Request the named inlay documentation and any applicable approval evidence, then confirm the sample and submission process with the program owner.
The standard tags-and-labels MOQ baseline is 1,000 pieces. The quotation confirms the selected chip and inlay, label construction, printing, encoding and quantities per design. Agree sample charges, freight and acceptance checks under the sample policy. Production schedule and transit are quoted separately for the approved order and destination; availability should be confirmed before repeat supply is committed.
May we use Google Analytics cookies to measure visits and inquiry actions? Your choice does not affect the contact form. Cookie details