How to Program NFC Price Tags for Retail: NDEF Encoding, Testing, and ESL Boundaries

Mar 19, 2026

Leave a message

Elly Huang
Elly Huang
Elly works on transparent display and kiosk configurations, mostly coordinating between store design teams and Legoyo's technical side. A lot of her projects have been in fashion retail and electronics showrooms, where the display has to fit into a c

A retailer can put an NFC tag on a shelf in minutes, but a dependable deployment requires more than a successful tap. The record must point to the correct product, the link must survive website changes, customers must be able to read the tag after it is mounted, and staff must know what to do when a tag is replaced. A second source of confusion is the phrase "NFC price tag": it can mean a passive NFC label that opens a web page, or an electronic shelf label (ESL) whose NFC function is only one part of a managed display system.

This guide explains how to program a passive retail NFC shelf tag with an NDEF URI record, confirm the result, release a batch without SKU mismatches, and plan for tag replacement. It also explains why the process is different from updating prices on an electronic shelf label system. If your objective is to change thousands of visible shelf prices centrally, start with the ESL architecture rather than assuming every display is programmed by tapping a phone.

 

 

First, identify which kind of "NFC price tag" you have

Device What the shopper sees What you program How information changes
Passive NFC sticker or shelf marker Printed product or price information, plus a tap point An NDEF record, commonly a URI The stored URI may stay fixed while the linked web destination changes
NFC-enabled electronic shelf label An electronic display showing price and other product content Only the documented NFC function, if exposed for commissioning or interaction Display content updates through the vendor's specified ESL management and communication path

These are not interchangeable. An ordinary passive NFC sticker cannot change its printed price. If it holds a link to a current online price, the web page can change without rewriting the physical tag-but the shelf still needs an accurate, separately maintained printed price. A managed ESL can change the price shown on its screen, but that does not prove its NFC memory is customer-writable, uses a generic NDEF record, or controls the display refresh.

Diagram comparing a passive NFC retail shelf tag with an electronic shelf label updated through an ESL management system.

 

 

Choose an NDEF record that supports the retail task

The NFC Forum's NDEF format is a common structure for NFC application data. For a tag meant to open product details on a shopper's phone, a URI record is usually the simplest starting point. The NFC Forum's URI Record Type Definition describes an efficient URI representation; it does not guarantee identical phone behavior under every operating system, setting, or app state.

For a retail pilot, write one deliberate record with one clear user action, unless the application specifically needs more. Multiple records can have valid uses, but they introduce interpretation and compatibility questions that a straightforward product-page tag may not need.

 

A concrete record and mapping example

Suppose a test shelf marker represents product SKU SKU-00427. Instead of storing the current selling price or a fragile campaign URL, a retailer could choose a stable address:

https://retailer.example/nfc/t/00427

This is an illustrative example, not an active retail URL. The tag stores an NDEF URI record containing the approved address. Separately, the retailer controls which current product or promotion page the address opens. The SKU, shelf position, tag identifier used by the project, and expected destination belong in a mapping register; they do not need to be embedded as a long plain-text description in the tag.

Field in the deployment register Illustrative entry Why it matters
Project tag ID TAG-00427 Stable operational reference for issuance and replacement
SKU / product reference SKU-00427 Connects the physical shelf marker with the correct product
Shelf location Aisle 03 / Bay 02 / Shelf B Allows an associate to find and audit the installed tag
Approved NDEF URI https://retailer.example/nfc/t/00427 Specifies what the writer must store
Expected destination Current product detail page Separates correct encoding from correct redirect configuration
Write/read-back status PASS or FAIL Records whether the stored payload was actually verified
Installed read result PASS or FAIL Records performance on the real shelf material
Protection state / revision Writable / protected / locked Prevents accidental rework decisions on irreversible tags

Important: a chip's hardware UID, a printed tag serial number, and an application-assigned tag ID are different concepts. The register should state which identifier your process reads and relies on. A UID by itself should not be treated as cryptographic proof that a tag or product is authentic; anti-cloning and authenticated interactions require a design built for that threat model.

 

 

Select the tag for the payload, mounting surface, and lifespan

The tag IC determines memory capacity, supported commands, protection options, and other capabilities. As a concrete family example, NXP lists the NTAG213, NTAG215, and NTAG216 as NFC Forum Type 2 Tag-compatible devices with 144, 504, and 888 bytes of user read/write memory respectively. These figures describe the referenced ICs, not a universal specification for all retail NFC tags. NDEF structure and record overhead also consume capacity, so verify that your final payload fits the exact tag and encoding configuration.

Do not choose purely by memory. A tag placed against metal shelving, close to liquid merchandise, behind a thick panel, or in an awkward approach position may read differently from the same tag held in a hand. Select the complete inlay, antenna, adhesive, and mounting arrangement for the fixture. If the shelf is metallic, use an appropriately designed on-metal assembly where required; attaching an ordinary inlay directly to metal can detune the antenna or reduce the usable read area.

Before purchasing a batch, check the intended phone and reader population, the minimum readable approach position, exposure to cleaning and wear, and the replacement method. Tag compatibility must be demonstrated on a representative installed sample, not inferred from the IC name alone.

 

 

Program one NFC shelf tag with a phone or reader/writer

A compatible phone application or dedicated NFC reader/writer can perform the encoding. The exact menu names depend on the app and platform. The following sequence is intentionally tool-neutral, so it works as a work instruction without promising one phone model's interface will be identical to another's.

  1. Prepare the source record. Confirm the project tag ID, SKU, shelf location, and approved URI in your register. Do not type a guessed product URL during the write session.
  2. Check the blank tag. Verify that it is the expected tag type, contains the required available memory, and is not already locked or protected in a way that prevents writing.
  3. Create an NDEF URI record. In the writer, choose the function for a URI or web address. Enter the approved URI exactly; avoid adding unrelated records unless the application requires them.
  4. Write the record. Position the phone or reader as directed by its manufacturer, hold the tag in the reading field through the write operation, and wait for the tool's completion response.
  5. Read back the actual tag. Move away from the write screen, read the tag again, inspect the record type and complete URI, and compare them with the source register. A success notification from the writer alone is not sufficient.
  6. Test on a second supported device. Open the tag on another representative phone or reader and confirm that the destination loads the correct product. Check the URL and redirect behavior rather than merely confirming that something opens.
  7. Mount the sample and test again. Repeat the read from the intended shopper approach after attaching the tag to the real shelf rail, label holder, or fixture.
  8. Approve the protection state only after verification. If locking is appropriate, apply it according to the exact IC documentation and then check that the approved read behavior remains intact. Keep a record of irreversible protection actions.

This is the pilot pattern. At scale, the process needs operator accountability, failure handling, reprint/replacement control, and a way to prevent a valid NDEF record from being installed against the wrong SKU.

Diagram showing how an NDEF URI is written to a retail NFC tag and independently read back for verification.

 

 

Release a batch without creating valid tags for the wrong products

The most expensive NFC mistake is not necessarily a failed write. It is a perfectly readable tag that directs shoppers to the wrong item. A second layer of validation must therefore compare the physical tag, mapped SKU, and installed position.

A controlled retail batch can use a simple sequence: prepare → issue tag ID → encode → read back → verify destination → assign shelf position → installed read test → release. Quarantine failures instead of reusing their IDs or overwriting the register informally. During rework, distinguish tags that were never written, tags carrying the wrong record, and tags that cannot be changed because of a locked state.

Failure observed Hold the batch? Corrective direction
The write tool reports success, but read-back differs from the approved URI Yes, for the affected tag Check writer settings and tag protection; rewrite only if permitted, then reverify
Correct URI opens the wrong product Yes Correct the destination mapping; retest the tag-to-item relationship
Tag reads on the bench but not after mounting Yes Inspect fixture material, antenna placement, shielding, and reader approach
Installed tag is mapped to another shelf/SKU Yes Correct placement and register before releasing the shelf position
Tag cannot be rewritten after a content mistake Yes Check irreversible lock state and replace the tag if required
URI works but the page is unavailable Investigate before release Check DNS, redirect, web hosting, and destination availability

Keep the project acceptance threshold explicit rather than assuming a fixed tag-per-hour productivity number. Manual encoding time depends on operators, reader ergonomics, memory operations, whether serialization is required, shelf access, and the degree of required audit evidence.

 

 

Why a stable redirect is useful-and what it does not solve

A direct product link can become stale when a retailer changes its website or campaign system. A stable, retailer-controlled short URI can make the physical tag more durable:

Physical NFC tag → fixed NDEF URI → retailer redirect or resolver → current product destination.

With this model, the link encoded on the tag does not change when the product's destination page moves; an authorized administrator updates the server-side mapping instead. The trade-off is operational: the redirect system, domain, and mappings become infrastructure that the retailer must monitor and maintain. If the resolver fails, every correctly encoded tag using that service can still fail for shoppers.

Test the behavior when a product is discontinued, renamed, moved, or temporarily unavailable. Decide whether the resolver should return a useful replacement product, an informative out-of-stock page, or a controlled "no longer available" state. A functioning HTTP redirect to the wrong product is still a failed retail experience.

 

 

Write protection is not the same as anti-counterfeiting

Leaving a public shelf tag writable can allow accidental or unauthorized record changes, depending on the tag and protection configuration. But immediately applying an irreversible lock is also risky: if the URI or mapping strategy is wrong, the tag may have to be physically replaced. NXP's NTAG21x documentation distinguishes writable memory, page locking, and configurable protection mechanisms. The exact result depends on how the IC is configured.

Decide in advance whether tags need to be reused, whether the URI is designed to remain stable, and who can approve a final lock. Lock only after the payload and installed read behavior are verified. For applications that need to authenticate product identity or resist cloning, evaluate an appropriate authenticated-tag and backend design; a standard NDEF URI record, an application tag ID, or a read-only bit alone does not establish authenticity.

 

 

For an NFC-enabled ESL, ask what the NFC function actually does

An electronic shelf label is an electronic display endpoint managed by a system. Some ESL models support NFC for identification, pairing, configuration, product interaction, or another documented function. Display updates usually follow the supplier's approved communication and software workflow, which can be separate from the NFC feature. Neither "has NFC" nor "supports a mobile app" tells you how a price reaches the screen.

For example, the KioskTagScreen site lists NFC read/write for a particular 5.8-inch electronic price tag. That field does not by itself establish NDEF support, how pairing works, customer write access, or any phone-to-screen price-update protocol. Confirm those behaviors from released model-level technical documentation before specifying them in a project.

If the goal is centrally managed pricing, ask the supplier to document how label-to-SKU binding works, how display updates are delivered, how failures are reported, which software and gateways are included, and what happens after a label or shelf location is changed. Those are ESL system decisions-not reasons to encode a new public NDEF URI into each tag whenever a price changes. For procurement context, see the ESL solution buyer's guide. For capacity and coverage, use the dedicated ESL gateway planning guide.

 

 

Acceptance checks before a retail shelf goes live

Check Evidence of acceptance
NDEF content The independently read record type and payload match the approved record
Item and shelf mapping The physical tag ID, SKU, and installed position match the controlled register
Destination The expected page opens on representative devices; redirect chain and item identity are correct
Installed RF behavior The tag can be read from intended user approach positions on the final shelf construction
Protection and rework The configured write/lock state matches the approved lifecycle, and the team can replace a failed tag
Site or campaign change A change in the website destination preserves correct behavior or triggers a documented exception
ESL, if used The electronic display is updated by the documented management path and its state is verified independently of an NFC tap

Keep a record of the failed conditions and what was corrected. The test is not complete because a phone detected an NFC chip; it is complete when the correct shopper action works at the correct shelf position and the operating team knows how to maintain it.

 

 

Troubleshooting: find the layer that failed

  • No NFC tag detected: compare with a known-good tag, check the reader state and position, and repeat after moving away from the metal fixture. Do not rewrite the NDEF record until RF detection is working.
  • Tag detected but wrong action: inspect the record type and payload. Check whether the writing tool created a text record or multiple records instead of the intended URI.
  • Correct URI, wrong product: inspect the project mapping and server-side redirect. Re-encoding may not fix an incorrect resolver configuration.
  • Correct URI, page does not load: check network connectivity, DNS, redirects, hosting, and application availability. The tag may be functioning normally.
  • Read fails only after installation: inspect the inlay's orientation, surrounding metal, label holder, and expected phone approach.
  • Tag cannot be rewritten: verify protection and lock state before treating it as defective.
  • ESL screen does not change after a tap: confirm what the model's NFC function is supposed to do. The price may be controlled by a separate ESL platform, not a direct NDEF write.

 

 

Choose the right workflow for the way content changes

Passive NFC tags are useful when a retailer wants a low-maintenance tap point to online information and can control the link destination. The strongest workflow is one in which the approved record, tag-to-SKU mapping, physical location, protection state, and replacement method are documented and verified. Managed electronic shelf labels solve a different operational problem: updating visible prices or promotional content from a central system.

The decision is therefore not "NFC or no NFC." It is whether the data behind a shelf marker changes, whether the physical marker itself needs rewriting, and whether the price shown to shoppers must change automatically. Keep those jobs separate, and use the inquiry channel to verify NFC behavior and software responsibilities for an exact ESL configuration instead of inferring them from a generic NFC feature label.

Send Inquiry