Open a web page
A label can carry a link to a product page, instructions or a campaign. Check the actual encoded link against the available memory; a short destination may not need the largest chip.
BULK NFC TAG BUYING GUIDE
When you buy NFC tags in bulk, the chip is only one part of the purchase. The finished tag also has to fit your product, work with the intended phone or reader, and carry the data your application needs.
DO RFID TAG supplies NFC label and tag options for business projects. Use this guide to compare NTAG213, NTAG215 and NTAG216, choose a suitable format, and turn a sample that works into a consistent bulk order.
A label can carry a link to a product page, instructions or a campaign. Check the actual encoded link against the available memory; a short destination may not need the largest chip.
Each item may need a different destination or identifier. Plan how the tag record connects to your database and how any printed code refers to the same item.
Follow the chip, protocol and data format required by the application. A tag that opens a website on a phone is not automatically suitable for an access-control or payment system.
A low unit price is useful only if it covers the product and preparation your project needs. Compare like-for-like configurations before deciding which quotation offers better value.
| Compare | Why the difference matters |
|---|---|
| Chip and finished construction | Chip type, antenna outline, face material, adhesive and any on-metal layer can change the product being quoted. |
| Printing and data preparation | Blank stock, custom artwork, one common record and variable records involve different preparation and checking. |
| Quantity and presentation | Use the same requested quantity and agree whether the tags are delivered as rolls, sheets or individual pieces. Presentation needs to suit the next operation. |
| Setup, packing and transport | Separate any one-time setup cost from the unit price. Compare the stated packing, delivery terms and freight scope as well. |
DO RFID TAG can discuss a quotation for the selected configuration and quantity. MOQ, current availability, production time and delivery terms should be stated for that quotation; a generic chip name is not a fixed-price or stock commitment.
These NXP chips operate at 13.56 MHz and follow NFC Forum Type 2 and ISO/IEC 14443 Type A. Start with the application requirement and the message to be encoded, then choose a finished tag built around the appropriate chip.
| Chip | User read/write memory | Selection point | Existing label information |
|---|---|---|---|
| NTAG213 | 144 bytes | A starting point for short web links and compact records, when accepted by the application. Test the actual message before selecting it. | 25 mm blank NTAG213 roll labels |
| NTAG215 | 504 bytes | More user memory, or a project that specifically requires NTAG215. Use the required chip rather than assuming a larger number is interchangeable. | NTAG215 sticker information |
| NTAG216 | 888 bytes | A larger record or a specification calling for NTAG216. More memory does not establish stronger product authentication or longer reading distance. | NTAG216 label information |
Memory figures describe the user read/write area, not an equal number of URL characters. NDEF formatting, configuration and record overhead affect the payload that can be stored. Source: NXP NTAG213/215/216 data sheet.
Memory is not the whole product. NTAG213 does not mean one fixed label diameter, and NTAG216 does not guarantee a longer read range. Antenna design, the reader field, mounting conditions and the finished construction all matter.
A chip name does not tell you how the product will be attached, handled or printed. Decide where the tag will go before comparing quantities and unit prices.
For packaging, documents and other surfaces that accept an adhesive label. Compare the outline, adhesive, face material and whether the label is supplied blank or printed.
For projects that need a card to be carried, handed out or repeatedly handled. Choose an NFC card with the chip required by the application, rather than selecting any RFID card by appearance.
For limited installation space or an embedded design. Compare the actual product dimensions, mounting surface and reading position against your device or enclosure.
Metal surfaces need a tag construction intended for that mounting condition. A larger memory chip does not solve detuning caused by metal. Check the chosen product in its final position with the intended phone or reader.
Specify what should be written to each tag as part of the order. Blank delivery, the same destination on every tag and a different record for every item are different jobs.
| Data choice | Useful when | Check on the sample |
|---|---|---|
| Blank | Your own team will write the data using its existing equipment. | The selected chip, writer and software can create the required record. |
| One shared destination | All labels should open the same landing page or instructions. | The encoded destination opens correctly on the intended devices. |
| A different record per item | Each item needs its own destination or database reference. | Each tag resolves to the intended item, and any printed identifier or QR code matches the same record. |
For a traceability project, the tag can point to a larger record maintained by your system. You do not have to store the full production and shipping history inside the tag’s memory.
If the label also needs artwork, a tap instruction or variable printing, explore our custom printed NFC stickers. For writing and testing background, use the NFC programming guide.
Test the real URL or data record, including the intended formatting. A sample containing a different short test link does not prove that a larger final record will fit.
Attach it to the intended surface or place it in the enclosure. Test the phones or readers that will actually be used, including the expected tapping position.
Where each item has its own identifier, check that the printed text, QR code and NFC destination refer to the same item. Review the chosen artwork and label outline as well.
Record the chip, construction, artwork and data requirements used for approval. Agree how the supplied batch will be identified and what checks are required before deployment.
For authentication, access or payment projects: confirm the system’s chip and security requirements first. NTAG21x password controls and originality signatures have specific roles; an ordinary static URL or UID is not a complete dynamic product-authentication service. For a different security-focused product direction, see the NTAG424 DNA label and discuss the required verification system.
Not simply because it has more memory. Compare the actual antenna, tag construction and reader setup. Test both products in the final mounting position rather than choosing from a fixed distance assigned to the chip name.
NTAG21x user memory can be written again when its access settings allow it and the relevant area has not been permanently locked. Decide how the tags will be used and maintained before applying write protection.
Discuss blank delivery, one shared record or variable encoding for the selected product. If your team will print or encode the tags, check compatibility with its printing process, writer and software on samples.
FROM SELECTION TO A BULK ORDER
You can begin with the product, where the tag will go and what should happen when it is read. If you already have a chip requirement, artwork or encoded message, share it; if not, we can discuss suitable tag options with you.

Au is an RFID and NFC manufacturer based in Shenzhen, China, with over 10 years of experience.