Impinj Monza vs NXP UCODE for UHF Tags

Start with the identifier and the workflow

Write down what the reader must obtain from the tag during normal operation. If your database holds the asset details, the tag may only need the identifier used to retrieve that record. If the process requires information stored directly on the tag, specify that information, its format, how it changes, and who is allowed to write it.

The GS1 EPC Tag Data Standard specifies EPC representations and associated tag data. Use the appropriate encoding scheme when the application requires GS1 identifiers. Do not equate a memory capacity with an identifier format: the chosen format and the finished tag's available configuration must agree.

Make the requirement concrete before requesting a chip option. Supply an example record, the expected encoded result, and the reader operation that consumes it. Ask the integrator to check available space and processing behavior. This is more useful than requesting extra chip memory without explaining what will be stored there.

Verified memory options in the checked models

The following values come from the linked manufacturer product pages and comparison tables, checked on October 1, 2026. A configurable value is deliberately shown as configurable. An unconfirmed value is not converted into a claimed absence of memory.

Verified memory options in the checked models

Exact IC	EPC memory	User memory	TID confirmed in checked material
Monza R6	96 bits	None	Not confirmed here
Monza R6-P	96 or 128 bits	64 or 32 bits, configuration dependent	Not confirmed here
Monza 4QT	128 bits	512 bits	Not confirmed here
Impinj M730	128 bits	None	Not confirmed here
UCODE 7	Up to 128 bits	None	96 bits
UCODE 7m	Up to 128 bits	32 bits	96 bits
UCODE 8	128 bits	None	96 bits
UCODE 9	96 bits	Not confirmed here	96 bits

Impinj's sources are the Monza R6 series, Monza 4 series, and M700 series pages. NXP's sources are UCODE 7/7m, UCODE 8/8m, and UCODE 9. Confirm the ordered tag's exact configuration; a family page can describe options absent from the selected model.

For a tag with configurable EPC and user memory, ask the supplier to document the delivered configuration and usable capacity. Specify whether encoding, locking, and password handling are included. Keep a representative encoded sample with the acceptance record so a later batch can be checked against the same requirement.

Treat chip features as specific requirements

Impinj lists Access/Kill and short-range mode for R6-P, and QT technology among the features of Monza 4QT. Its M730 comparison entry lists a shared Access/Kill password. These descriptions are not interchangeable security specifications. Consult the corresponding Impinj product documents and test the commands actually used by the application.

If a feature matters, describe the expected behavior in the request rather than writing secure chip. Identify the reader software, the command sequence, how credentials are managed, and what a successful or failed operation should look like. Have the integrator confirm support before approving the tag. A feature appearing in marketing material does not show that your existing software invokes it correctly.

Separate identification from writing during acceptance testing. The application might identify a tag reliably yet fail to complete a required update under the same process conditions. Design a test for each operation and record its result separately. Include recovery behavior for interrupted writes and the expected response to a locked tag.

Include lifecycle in a new design decision

The checked Impinj R6 material says R6 is in the end-of-life process and R6-P is not recommended for new designs. NXP's checked UCODE 7/7m and UCODE 8/8m pages show No Longer Manufactured; its UCODE 9 page shows Active. These are dated manufacturer statements, not a promise about a tag supplier's stock.

For an existing deployment, a legacy chip can be relevant to matching previously validated tags. Ask the supplier about inventory, lot traceability, replacement options, and the intended ordering horizon. For a new deployment, request a supported proposal instead of copying an old model's chip choice into a fresh specification.

Document substitutions before they happen. Require the exact proposed IC and the revised tag specification, then assess memory, encoding, command support, and asset-level performance. An equivalent label on a quotation should not remove the need to review those requirements. Keep the accepted revision with the purchase specification.

Compare complete tags under one test plan

Shortlist finished tags that satisfy the required memory and supply conditions. Use the same assets, mounting method, region setting, reader, antenna, software, and movement for the comparison. Define the pass condition in operational terms so the preferred sample reflects the job rather than a loosely described maximum-distance demonstration.

For textiles, compare attached samples through the intended processing sequence and checkpoints. For metal assets, compare them mounted on the intended metal surface with the specified adhesive or fastener. Inspect attachment as well as the data read. The sample read test guide helps make the setup repeatable.

Keep individual sample identities and chip options in the results. If the supplier changes the chip and antenna together, evaluate the revised finished tag as a new candidate. You cannot attribute any difference entirely to the IC when more than one design element changed. Ask for a clear revision history rather than inferring it from the external shape.

Questions to put in the sample request

• Which exact chip and configuration will be delivered?
• Which identifier format and user-data operation have been checked?
• Which reader commands and firmware are required?
• What lifecycle and substitution policy apply to the proposed option?
• What finished-tag band and mounting method were tested?
• Can representative encoded samples be supplied with traceable model revisions?

Use the answers to compare textile laundry tags or FR4 on-metal tags, then request samples for a documented trial. Include encoding and acceptance work when reviewing laundry tag pricing; the chip name alone is an incomplete buying specification.

When this does not apply

This comparison covers selected passive UHF ICs in the verified catalogue data. It does not compare HF, NFC, active devices, every Monza or UCODE generation, or finished-tag certification. It also provides no claim that one listed IC guarantees a particular read distance, wash life, or resistance to chemicals.

If the memory requirement is already satisfied and the problem is missed reads, start with the installed read-zone checks. A chip replacement should follow evidence from that investigation and a sample trial. If a required memory field remains unconfirmed, obtain the exact manufacturer and supplier documentation before ordering rather than filling the gap with an assumed value.