Back

Digital Product Identity

How to Connect Existing ERP, PIM and PLM Data to Product Identities

Thomas


03 Nov 2026

connection abstract

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.

Why is it hard to connect ERP, PIM and PLM data to individual products?

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:

  • Granularity mismatch. ERP tracks lots and stock movements. PIM describes a reference. PLM manages a design revision. None of them natively holds “this unit, serial 004812”.
  • Three owners, three vocabularies. Operations, marketing and R&D each define attributes their own way, and the same material or origin may be written three ways.
  • No shared key. Without GTIN plus serial, records can only be matched through fragile free-text fields.
  • Latency. A tap happens in real time. Many back-office exports run overnight.
  • Regulatory pressure. The central EU Digital Product Passport registry has been live since 20 July 2026 (European Commission), under ESPR, Regulation (EU) 2024/1781. Data scattered across systems must be assembled on demand.
  • Counterfeits and diversion. Fakes represented USD 467 billion, up to 2.3% of global trade in 2021 (OECD/EUIPO, Mapping Global Trade in Fakes 2025). Authentication needs item-level truth, not batch-level assumptions.

The aphorism that holds across all six: a record that cannot be addressed cannot be verified.

What is a product identity?

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:

  1. An identifier. Typically a GS1 Digital Link made of a GTIN plus a serial number.
  2. A carrier. An NFC tag, a UHF tag or a Secure QR code physically bound to the item.
  3. A registry record. The entry that connects the identifier to production, ownership and event data.

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.

Which system should own which data?

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.

How do you connect ERP, PIM and PLM data to a product identity?

The process runs in seven steps, from audit to feedback loop.

  1. Audit the attributes. List what each system holds and which attributes a tap, a retailer or a regulator will need. Drop anything nobody will read.
  2. Fix the key. Use the GTIN from the PIM as the product reference. Add a serial number issued at production. Express both as a GS1 Digital Link URL.
  3. Map the attributes. For every field, record the source system, the owner, the format and the update trigger. This map is the contract between teams.
  4. Issue serials at the line. The identity platform generates or receives serials and binds each one to a tag or code at encoding time. The ERP production order supplies lot, date and plant at that moment.
  5. Expose data through APIs or scheduled sync. The platform pulls commercial content from the PIM and composition data from the PLM, caching what must load in under a second. Master data stays where it is.
  6. Resolve at tap time. The phone reads the tag, the platform verifies the authentication, then assembles the response from cached PIM, PLM and ERP data and returns it in the consumer’s language.
  7. Return events to the business. Authentication results, first activation and ownership transfers go back to the ERP, CRM or BI tools, so supply chain and brand protection teams work from item-level facts.

A step-by-step view of the hardware side is in the guide to implementing NFC product authentication.

What does the consumer see after a tap?

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.

Should the NFC tag carry the data or only point to it?

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.

NFC or serialised QR as the carrier

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.

When is a simpler setup the right choice?

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.

How does the integration differ by product category?

The same architecture adapts to each vertical. The data that matters changes.

  • Wine and spirits. ERP lot and bottling data, PLM or recipe composition, closure-integrated tags that break on opening. Liquid and glass affect read range, so tag placement needs testing.
  • Luxury watches. Serial and reference from the ERP, movement and case specification from the PLM, warranty and ownership transfer on top. Metal cases need on-metal tags with a ferrite layer, because standard tags detune on metal.
  • Cosmetics and fragrance. Batch and expiry from the ERP, ingredient lists from the PLM or regulatory systems, usage guidance from the PIM. Packaging laminates and foils call for read tests.
  • Leather goods and fashion. Material origin and workshop from the PLM, care content from the PIM. Textiles and apparel are the first expected delegated act under the ESPR, indicatively 2027 and enforceable around 2028 to 2029, since application starts at least 18 months after each act.
  • Cigars. Batch, vitola and ageing data from the ERP, with tags on bands or boxes.
  • Furniture. Material and repair information from the PLM, ownership and warranty records tied to the item over a long life.
  • Premium audio. Firmware, model and serial data from the ERP and PLM, with registration and support through the tap.

How does the Digital Product Passport change the integration work?

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.

FAQs

How do you link ERP data to an NFC tag?

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.

Do you need to replace your PIM or PLM to create product identities?

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.

What identifier should connect product data across systems?

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.

Does the NFC tag store product information?

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.

Which phones can read NFC product tags?

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.

Can NFC tags work on metal or glass products?

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.

Is NFC or QR better for a Digital Product Passport?

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.

How long does an ERP, PIM and PLM integration take?

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

Blog

Discover more articles

All our articles