Paper, plastic or glass
Start with the final packaging.
Confirm material, available label area, curvature, contents and exposure. Nearby liquid, metal closures and the phone position can affect the result. Test after attachment.
RFIDAK / Printed & encoded labels
Custom NFC stickers.
Plan the next tap.
Connect your product or packaging to a web page with a phone tap. Choose the NFC chip, print and mounting surface, then test the complete experience before ordering.
- Chip options
- NTAG213 / 215 / 216
- Technology
- 13.56 MHz · NFC Type 2
- Order baseline
- 1,000 pieces; confirm your configuration
01 / Start with the content
How much memory
does the tap need?
All three listed chips use NFC Forum Type 2. Compare the actual encoded message with the available user memory.
Swipe to compare all columns.
| Chip | User memory | When to consider it | Check before encoding |
|---|---|---|---|
| NTAG213 | 144 bytes | Start here for a compact web-link payload. | Check the actual encoded NDEF message, including overhead. |
| NTAG215 | 504 bytes | More space when the approved payload exceeds NTAG213 capacity. | Confirm the receiving phone or app supports the record format. |
| NTAG216 | 888 bytes | More space for a larger approved NDEF message. | Larger memory does not add encryption or guarantee app-free handling. |
Send the final content. A short web address can be more practical than storing the full contact or product record. Record type, encoding and overhead matter; do not choose a chip from a universal character limit.
Check the phone action. Supported web-link records can use built-in phone handling. Contact records or app-specific actions may need compatible software. More memory does not change those requirements.
02 / The label in its real setting
The mounting surface
is part of the specification.
An unmounted sample does not establish how the label will read or remain attached to the finished product.
Metal or foil
Request an on-metal NFC construction.
A suitable antenna and isolation layer, often ferrite, may be needed. Approve the added thickness and mounted reading performance. A UHF on-metal label will not serve a phone’s built-in NFC reader.
What goes on the
approved order?
Use one configuration record for the chip, construction and data. Ask for article-specific material or performance documents when your project requires them.
Send your label requirement →- Operating Frequency
- 13.56 MHz NFC / HF
- Chip & Protocol
- NTAG213 / 215 / 216: NFC Forum Type 2 and ISO/IEC 14443 Type A. Other chip families require a separate review
- User Memory
- NTAG213: 144 bytes; NTAG215: 504 bytes; NTAG216: 888 bytes. Allow for NDEF formatting overhead
- Size & Construction
- Approve finished size, shape, inlay position, face material, adhesive and thickness for the actual mounting surface
- Printing & Supply
- Blank, printed or printed and encoded. Specify individual labels, sheets or rolls and the intended printer or applicator
- Encoding & Identifiers
- Agree NDEF content, printed QR or serial mapping and read-back checks. Factory-programmed UID is separate from writable content
- MOQ
- 1,000 pieces standard labels baseline, with the selected chip, construction and quantities per design confirmed in the quote
- Production & Delivery
- Confirm sample terms, approved configuration, order quantity, destination and required arrival date in the quotation
03 / Print, data & ownership
Decide what arrives
ready to use.
Visible artwork and chip content are separate deliverables. Approve both before encoding a batch.
Blank
You add content or print locally.
Confirm label stock, printer feed and an encoder that supports the selected NFC chip.
Printed
Your artwork, ready for local encoding.
Approve size, artwork, print position and how your team will encode and verify the labels.
Printed & encoded
Artwork and NDEF content prepared together.
Approve the payload, per-label data map, read-back checks and the locking plan.
A web link keeps the
on-tag content compact.
A common configuration stores a web address in NDEF. The phone presents the supported action; the destination is maintained through your website.
- 01Phone reads label
Test the mounted tag.
- 02Web address is handled
Supported phone and NDEF record.
- 03User opens your page
Keep the destination working.
Plan changes before locking. Permanent lock bits cannot be reversed. A locked tag can still point to a web page or redirect that you maintain, but changing its stored address requires writable memory and the appropriate access.
Separate identity from content. Map printed QR codes, serials and NDEF payloads explicitly. The factory-programmed UID is a different field. Static links and ordinary password protection do not provide per-tap product authentication.
For a public phone-tap link, keep the required NDEF content publicly readable. If reading is password-restricted, agree a compatible app workflow and test it; do not assume standard background reading will work.
Before a production order
Approve one complete
tap experience.
A useful sample test covers the label, the phone and the destination together.
Ask about NFC samples →- Mount it where it will be used. Apply the proposed label to the final packaging or object. Include foil, liquid, curvature and any overlying material in the test.
- Test the complete phone action. Use the intended phones, cases and NFC settings. Check the notification, destination page or app action using the final encoded content.
- Check print, data and attachment. Read back the NDEF payload and compare the QR or serial mapping. Agree adhesion and exposure checks for the exact label construction.
- Approve the production record. Record chip, drawing, material, artwork, data map and acceptance criteria. Approve any permanent lock before it is applied.
04 / Your project
Bring the surface.
Bring the content.
Start with these three choices. On the contact page, add your target phones, chip if known, artwork, dimensions, quantity and delivery country.
The quote will confirm construction, sample charges, encoding, unit pricing and timing for your order.
Read the sample policy →Buyer questions
Phone support,
encoding and orders.
What is the difference between NTAG213, NTAG215 and NTAG216?
The listed user-memory capacities are 144, 504 and 888 bytes respectively. They share 13.56 MHz NFC Forum Type 2 operation. Select against the actual encoded NDEF message, including formatting overhead; a character-count rule is not a reliable substitute. More memory does not add cryptographic authentication.
Can customers read these NFC stickers without installing an app?
A supported NDEF web-link record can use built-in phone handling, but this is conditional. Apple documents background tag reading on iPhone XS and later, subject to device state and supported records; the user taps a notification to open the supported action. Android behavior depends on NFC hardware, settings, software and the record type. Test the intended phones and final encoded label. Contact records and app-specific actions may need compatible software.
Will an ordinary NFC sticker work on metal or foil packaging?
Do not assume it will. Metal can change antenna behavior. Request an NFC construction designed for the actual metal or foil surface, often using a ferrite layer, and approve samples after mounting. Confirm size, added thickness, curvature, nearby liquid, phone position and the required tap behavior. A UHF on-metal label is not a substitute for a phone-readable NFC label.
Can the destination website be changed after the sticker is locked?
If the NDEF memory remains writable, supported content can be rewritten with the necessary access. Permanent lock bits cannot be undone. When a locked tag stores a web address you control, you may change the page or redirect at that address without rewriting the tag, subject to your web setup. Define who maintains the address and approve the locking plan before encoding.
Can you print a QR code and encode a different link on every sticker?
Specify the per-label printed QR or serial number and the NDEF payload in an approved data file. Agree which fields must match, how duplicates and rejected labels are handled, and what read-back report is required. Factory-programmed UID is a separate identifier and should not be presented as a writable sequential number.
Are NTAG213, NTAG215 and NTAG216 stickers clone-proof?
No. A copied static web address is not authenticated merely because it came from an NFC sticker. The family provides features such as locking, a 32-bit password and an originality signature, but these are not equivalent to per-tap cryptographic authentication. For an authentication project, specify the security objective, chip, verification service and key-management responsibilities separately.
Can our label printer also encode these NFC stickers?
Printing capability does not establish NFC encoding support. Check the exact printer, installed RFID module, supported chip and protocol, software, inlay position and roll specification. A UHF RFID printer does not automatically encode this HF NFC family. Run the actual print-and-read workflow on sample stock.
What are the MOQ, sample terms and lead time?
The standard tags-and-labels MOQ baseline is 1,000 pieces. Confirm the selected chip, construction, artwork, encoding and quantities per design in the quote. Stock and custom samples follow the sample policy; agree sample charges and freight before shipment. Production timing and transit are quoted separately for the approved order and destination.