A bottle leaves the filling line with a batch code in the ERP, a marketing description in the PIM and a bill of materials in the PLM. Three systems know it. None of them can tell a customer in a shop whether the one in their hand is genuine. The fix is not a new master database. A unique product identity acts as the join key, so each system keeps its role and the item itself becomes addressable by phone tap.
Enterprise systems were built around batches, SKUs and design versions. A product identity works at the level of one physical item. That gap creates friction, and the drivers are consistent across industries:
The aphorism that holds across all six: a record that cannot be addressed cannot be verified.
A product identity is a unique, cryptographically verifiable reference attached to one physical item, linked to the data that describes it.
It has three parts:
The identity is not a copy of the ERP record. It is the key that lets ERP, PIM and PLM answer questions about one specific item.
The distinction that matters: a product identity does not replace your systems of record. It gives them a common address, so that a question asked by a customer, a retailer or a regulator reaches the right system and returns one coherent answer.
The serialization logic behind this is covered in more depth in how unique product identities work at scale.
Do not migrate data. Assign each attribute to a single source of truth and expose it by reference. A workable split:
| Data type | System of record | Example attributes | Updates |
|---|---|---|---|
| Item and batch facts | ERP | Lot, production date, plant, ship-to, stock status | Event-driven |
| Commercial content | PIM | Name, description, images, care guidance, translations | On edit |
| Design and composition | PLM | Bill of materials, material specification, revision, compliance documents | On release |
| Item-level events | Identity platform | First tap, authentication result, ownership transfer, location of scans | Real time |
Item-level events are the one category that no existing system holds. They are new data, produced by the identity layer, and they flow back to the ERP and CRM rather than the other way round. The thinking behind this layer is explored in the product data layer most brands are missing.
The process runs in seven steps, from audit to feedback loop.
A step-by-step view of the hardware side is in the guide to implementing NFC product authentication.
The point of the integration is a response that no single system could produce alone.
Without a connected identity, a phone shows a generic brand homepage. The ERP, PIM and PLM stay invisible.
With one, the owner of a bottle of single-estate gin might read:
“Authentic. Batch 24-117, distilled and bottled at our Namur distillery on 14 March. Botanicals: juniper, coriander, bitter orange peel. Serve with tonic and a twist of orange.”
The authentication verdict comes from the chip. The batch comes from the ERP. The botanicals come from the PLM. The serving suggestion comes from the PIM. One tap, four systems, one answer.
The same record can then drive customer engagement and data collection, including Apple Wallet passes, ownership transfer and service reminders.
The tag should carry an identifier and a proof, not the data.
NTAG 424 DNA is the chip class for phone-tap authentication. It follows ISO/IEC 14443-A and NFC Forum Type 4, uses AES-128, and supports Secure Unique NFC (SUN) messaging. At every tap, the chip generates a fresh cryptographic signature appended to the URL. The server verifies it. A copied URL fails, because the signature is different each time.
The analogy is a door that issues a new one-time code every time someone approaches it. A photocopied key is useless, because the code it shows is already spent.
Storing product descriptions on the chip would be slow, hard to update and impossible to translate. Keeping them in the connected systems means a PIM edit is live on the next tap, with no re-encoding.
ISO 15693 (for example ICODE DNA, Type 5) belongs to a different job. It is vicinity-class, suited to supply chain scanning in cartons and pallets, and not the standard for phone-tap authentication.
Both carriers can resolve to the same ERP, PIM and PLM data. They differ in what they can prove.
| Criterion | NFC (NTAG 424 DNA class) | Serialised QR |
|---|---|---|
| Item-level authentication | Cryptographic, dynamic signature per tap | Depends on the platform. A printed code can be photographed and copied |
| Consumer action | Tap, no app on iPhone XS/XR and later, native on Android with screen on | Open camera, scan |
| Visibility | Hidden in the product or closure | Visible, printed |
| Regulatory role | Trust layer | Visible carrier, GS1 Digital Link QR is emerging as the practical default for DPP |
| Unit cost | Published converter prices for NTAG 424 DNA-class labels cluster around $0.45 to 0.65 at five-figure volumes. On-metal adds 7 to 30%. 50k+ is quote-only (public catalogues, 2026) | Near-zero marginal print cost. The real cost is serialization and platform (industry sources, 2026) |
| Tamper evidence | Available with closure variants such as TagTamper | Limited |
The ESPR is carrier-neutral, but in practice the pairing is clear: NFC for trust, a visible carrier for compliance. Many products carry both, resolving to the same record.
Not every product needs a secured chip and a live integration.
Serialised QR is the sensible option when unit value is low, volumes are very high, no secondary market exists and the line cannot absorb tag application. A QR code resolving to PIM content can serve information and compliance needs at almost no marginal cost.
A standard non-secure NFC tag (NTAG213-class) lists around €0.19 to 0.23 at 1,000 to 10,000 units (public catalogues, 2026). It can open a product page. It cannot prove the item is genuine, because a standard tag can be cloned.
Integration depth should follow the same logic. If the only goal is a product page, a PIM export is enough. If the goal is authentication, grey market detection or ownership, the ERP link and event feedback are what make the identity useful. Cost detail is available in the analysis of what NFC product authentication costs.
The same architecture adapts to each vertical. The data that matters changes.
The DPP turns data mapping from a nice-to-have into an obligation. With the central registry live since 20 July 2026, a passport must reference structured data about composition, origin and handling, and that data already sits in the PLM and ERP.
Brands that have done the attribute map and chosen a GS1 Digital Link structure can produce a passport as a view of existing records. Brands that have not must do the audit under deadline. Batteries follow their own passport regime from 18 February 2027. France’s AGEC law, in force since 2020, already requires consumer product information that the PIM typically holds. Practical preparation is covered in how to prepare product data for a Digital Product Passport.
40+ brands · 12 years · €1.5B protected
Product identities work when existing systems keep their roles and share one key. The brands that map their data before they choose a tag spend the least time reworking later.
Link them through a shared identifier. The ERP supplies lot, date and plant when a serial is bound to a tag at the production line. The tag stores only a GS1 Digital Link and a cryptographic proof. At tap time, the platform resolves the serial and returns the ERP data by reference.
No. The PIM and PLM stay as systems of record. The identity platform reads from them through APIs or scheduled sync and assembles one response per tap. Replacing them would add risk without adding capability. The only new data is item-level events, such as authentication and ownership.
Use GTIN plus a unique serial number, expressed as a GS1 Digital Link. The GTIN identifies the reference and already exists in most PIMs. The serial identifies the single item. Together they form a key that every system and every carrier, NFC or QR, can resolve consistently.
The tag stores an identifier and generates a cryptographic proof, not product content. With NTAG 424 DNA, SUN messaging adds a fresh signature to every tap. Descriptions, images and composition stay in connected systems, so a change in the PIM appears at the next tap without re-encoding.
iPhone XS and XR and later read NFC tags in the background without an app. Android phones read tags natively when the screen is on. This covers most phones in active use, so consumers do not need to install anything to authenticate a product.
Yes, with the right tag. Standard tags detune on metal, so on-metal tags with a ferrite layer are used, at a premium of 7 to 30% over standard labels (public catalogues, 2026). Glass and liquids affect range and need testing in the final packaging before launch.
They serve different roles. The ESPR is carrier-neutral, but GS1 Digital Link QR is emerging as the practical visible carrier for compliance. NFC adds the trust layer, with cryptographic authentication that a printed code cannot give. Many brands use both, pointing to the same record.
It depends on data quality and the number of attributes, not on the chip. The attribute audit and mapping usually set the pace, so they should start first. Tag selection and read testing can run in parallel, and no timeline should be assumed before the audit is done.
Talk to our team