Monza R6-P + NTAG213 Dual-Frequency Tag, AZ-DF-S01: spec drawing (UHF + NFC, Monza R6-P + NTAG213)

AZ-DF-S01

Monza R6-P + NTAG213 Dual-Frequency Tag, AZ-DF-S01

One tag, two interfaces: Monza R6-P for UHF inventory and NTAG213 for NFC/HF interaction; validate both workflows on the intended devices.

Full dimensions for this design are available on request. Ask for the specification and samples before ordering. Request specifications

Validate samples first. Engineer reply within 24 h.

See the sample validation checklist

Specifications
SKU AZ-DF-S01
Frequency Dual: UHF 860–960 MHz + HF 13.56 MHz
Protocol EPC Gen2v2 (ISO/IEC 18000-63), RAIN RFID (UHF); ISO/IEC 14443-A, NFC Forum Type 2 (HF)
Chips (UHF + HF) Impinj Monza R6-P (UHF) + NXP NTAG213 (HF)
Antenna size On request
Format Inlay (dry / wet / label)
Typical applications Logistics & supply chain

Design and application notes

Monza R6-P + NTAG213 Dual-Frequency Tag, AZ-DF-S01 is a dual-frequency RFID tag that carries an Impinj Monza R6-P (UHF) and an NXP NTAG213 (HF/NFC) chip on a combined UHF dipole and HF coil antenna, providing UHF (860–960 MHz) and HF (13.56 MHz) interfaces. For supply-chain inventory and consumer interaction, check protocol support in the intended readers, phones, operating systems and applications, then validate both workflows on the actual item.

Two chips share one tag. The Impinj Monza R6-P handles UHF reads (selectable 128-bit EPC + 32-bit user memory or 96-bit EPC + 64-bit user memory, serialized TID), and the NXP NTAG213 handles NFC and HF interaction (144 bytes of user memory (NDEF), 7-byte UID; ISO/IEC 14443-A, NFC Forum Type 2). The two chips store data separately and require separate encoding and read-back checks. Validate with the intended UHF reader and a phone or HF reader and application that support the relevant protocol. For NDEF, check the complete message and expected action, and confirm that your backend maps both identifiers to the intended item record. Please note: Impinj marks Monza R6-P as not recommended for new designs; ask us about current alternatives.

Full dimensions for this design are available on request. We do not publish a read range for this design. Range depends on the reader, antenna, power and tagged material, so ask us for test data or samples for your setup.

It is typically used for carton, tote and pallet labels. The application pages below give chip and size recommendations for each industry.

Order it as a dry inlay for your own converting, a wet inlay with adhesive and liner, or a finished label, blank or printed, with data such as an NDEF URL encoded and locked. We ship samples first so you can validate on your own items and readers, then quote the format you tested.

Specification basis and validation

Vendor documents describe the chip, not finished-tag read range.

Confirm catalog dimensions against the final tag construction. Reference read ranges require sample testing on your item with your reader setup.

Order in the format you need

Confirm the construction and encoding during sampling, then quote the configuration you validated.

  • Dry inlay

    Chip and antenna on a PET carrier without adhesive, for your own converting, hang tags or lamination.

  • Wet inlay

    The same inlay with pressure-sensitive adhesive on a liner, applied like a NFC sticker.

  • Label

    Paper or synthetic face stock over the inlay, blank or printed, with data encoded and locked.

  • Custom

    Other label sizes, face stocks, adhesives, printing, encoding and roll formats on request.

What should the sample pass before a bulk order?

Agree the actual use conditions and pass criteria before selecting samples. The catalogue supports shortlisting; confirm finished-tag performance and delivery configuration in writing and through sample validation.

  1. Test UHF and NFC workflows separately

    Fix the UHF reader and antenna settings and test the intended read zone on real items. Separately record target phones, OS and applications; read back the complete NFC content and verify the expected action.

  2. Confirm the backend mapping of both identities

    Read back the UHF and HF chips separately and reconcile them with the item, printed ID and backend record. The two chips are read and written independently; the business system must confirm their mapping. Approve access and irreversible lock scopes separately.

  3. Record the approved construction and delivery configuration

    Record the SKU, sample revision, lot, device settings, results and approver. Confirm final dimensions, materials, printing, encoding, quantity and delivery requirements, and agree which configuration changes require another trial.

Use the test record to save actual conditions and results. English and Chinese worksheets are provided; the agreed reviewer determines acceptance.

Download test record

How ordering works

  1. 01

    Specify

    Share surface, read distance, chip preference and volume. We shortlist tags that fit.

  2. 02

    Sample

    Receive sample tags of the shortlisted designs to try in your own setup.

  3. 03

    Validate

    Test on your items, readers and printers. We adjust chip, size or format if needed.

  4. 04

    Produce & ship

    Volume production with 100% inline electrical test, then export shipping.

Frequently asked questions

Can I order the AZ-DF-S01 as a wet inlay or a printed label?

Yes. The same chip and antenna are available as a dry inlay (no adhesive), a wet inlay (adhesive on a liner) or a label with paper or synthetic face stock, blank or printed. Data encoding and locking and custom label sizes are quoted on request; see custom tags.

How are the two chips on the AZ-DF-S01 read?

Validate Impinj Monza R6-P with the intended UHF reader and NXP NTAG213 with a phone or reader and application that support its HF protocol. Check the target phone, OS and application; for NDEF, read back the complete message and verify the expected action. The two chips hold separate data and need separate encoding and read-back checks. Confirm that the backend maps both identifiers to the same item record. A static URL alone does not prove product authenticity.

How do I get samples and a quote for the AZ-DF-S01?

Use the quote button on this page or request samples. Tell us the item, surface, read distance and annual volume; an engineer replies within 24 hours with a recommendation and a sample plan.

Talk to an RFID engineer

Not sure which tag fits your project?

Send the surface, read distance and volume. An engineer replies within 24 hours with a recommendation and a sample plan.

Email us: sales@antenza.com

Quick quote

Monza R6-P + NTAG213 Dual-Frequency Tag, AZ-DF-S01

AZ-DF-S01

Tell us the quantity and where the tag goes. We reply within 24 hours.

For a quote, share the item, surface material, UHF reader, target phone or NFC reader, quantity, and printing or encoding needs.

An engineer replies within 24 hours.

By sending this form you agree to our privacy policy. We use your details to answer and follow up on this inquiry.

Cloudflare Turnstile checks submissions to prevent spam.

Email us Get a quote