A bottle leaves a distillery, passes through an importer, a wholesaler and a retailer, and is opened at a dinner table in a city the brand has never sold in. The brand shipped it. It never learns what happened next. First-party product data closes that gap: information a brand collects directly from interactions with its own physical products, such as scans, authentication results, tamper status and ownership transfers. The product, not a retailer or a broker, becomes the source.
Marketing teams have spent years building first-party data: website visits, purchases, newsletter sign-ups, loyalty programmes. That work assumes the brand meets the customer. Many premium brands do not.
They sell through distributors, retailers and marketplaces. They know how many units shipped to a partner and very little after that. Several pressures make the gap more costly:
The counterfeit dimension alone is large. Counterfeit goods were estimated at USD 467 billion in 2021, up to 2.3% of global trade (OECD/EUIPO, Mapping Global Trade in Fakes 2025). Clothing, footwear and leather goods account for 62% of seized counterfeits (OECD/EUIPO, 2025).
The silent owner problem: The product reaches the customer even when the brand does not. Every owner holds a physical object that carries the brand’s name and, if equipped, a way to talk back.
First-party product data is information a brand collects through its own products, via a data carrier on each item, without relying on a retailer, platform or data broker.
It has two parts. The first is data about the item: where it was scanned, whether it is genuine, whether it has been opened. The second, collected only with consent, is data about the person interacting with it: registration, ownership, preferences.
The distinction that matters: A sell-out report from a retailer tells a brand what a partner chose to share. A verified scan tells the brand what happened to one specific item, reported by the item itself.
The source defines the category. The product is the channel, which lets brands that sell indirectly collect data they would otherwise buy, estimate or never see.
| Type | Collected by | Example | Who owns it |
|---|---|---|---|
| First-party product data | The brand, through the product | Bottle authenticated in Singapore; owner registered | The brand |
| First-party customer data | The brand, through its own channels | Website account, boutique purchase | The brand |
| Zero-party data | Volunteered by the customer | Stated preferences at registration | The brand, with consent |
| Second-party data | A partner, shared with the brand | Retailer sell-out report | The partner, under agreement |
| Third-party data | An aggregator or broker | Market panels, audience segments | The third party |
The two first-party types complement each other. Customer data starts from a person. Product data starts from an item and links to a person only when the owner agrees.
| Data | Example | Typical use |
|---|---|---|
| Scan location and time | Country or city, date of each scan | Diversion detection, market insight |
| Authentication result | Genuine, failed, replayed code | Counterfeit detection, enforcement evidence |
| Tamper status | Sealed or opened | Refill detection, first-open date |
| Scan pattern | First scan, repeat scans | Engagement and product use insight |
| Registration and ownership | Owner registered, ownership transferred | CRM, warranty, resale |
| Service and repair events | Authorised repair, inspection | After-sales, resale value, passports |
| Content engagement | Care guides, stories or offers viewed | Content optimisation, reorder journeys |
The first four are product data in the strictest sense and identify no one. The last three can involve personal data and need consent. City-level or country-level location is usually enough for diversion and market analysis, and far less sensitive than precise geolocation. The scan location signal alone often reveals markets a brand did not know it reached.
Collection is less a technology question than a design question. The product has to invite interaction, and the interaction has to be worth the owner’s time.
Step three sets the volume. Consumers rarely scan only to check authenticity. They scan when the product offers something they want. Experience design and data strategy are the same conversation, and customer engagement and data collection work best when designed together.
What the consumer sees after tapping a bottle might read: “Genuine bottle. First opened today. Register your ownership to activate your warranty and receive tasting notes.”
Data collected through a copyable code has a hidden flaw: counterfeit products produce scans too. If a fake carries a photocopied QR code, its scans look identical to genuine ones. Every report built on them, whether market insight, engagement or diversion maps, quietly includes the fakes.
The photocopied ticket problem: A printed QR code is a ticket anyone can photocopy. A cryptographic NFC tag is a ticket that is re-signed at every entry. The first records who showed a picture. The second records who held the original.
| Carrier | Can a fake produce a “genuine” data point? | Data quality |
|---|---|---|
| Printed or serialised QR code | Yes, a copy scans the same | Unverified |
| Copy-resistant print (ACM-secured barcode, Diamond Dust) | Hard to reproduce | Verified where a chip is not economic |
| Cryptographic NFC (NTAG 424 DNA class) | No: a new signed code on every tap, checked server-side | Verified; tamper status with the TagTamper variant |
The NTAG 424 DNA chip class follows ISO/IEC 14443-A and NFC Forum Type 4. It uses AES-128 and Secure Unique NFC (SUN) messaging: each tap produces a new cryptographic signature that the server validates. A replayed or cloned URL fails. Recent phones need no app: iPhone XS and XR and later read tags in the background, and Android reads natively with the screen on. Product authentication technology built on this chain gives every scan a verified status.
QR wins in several cases. It adds roughly zero marginal print cost, since the real cost is serialisation and platform (industry sources, 2026). It suits very high volumes, low unit values, products with no secondary market and lines where every cent counts. It needs no chip and no tag placement.
For Digital Product Passports, a visible carrier is the practical default. The ESPR (Regulation (EU) 2024/1781) is carrier-neutral, and GS1 Digital Link QR is emerging as the de facto choice. The sound framing is NFC for trust, visible carrier for compliance. Many brands will use both on the same item.
The trade-off is plain. QR gives reach at low cost. Cryptographic NFC gives data you can rely on.
Published converter prices for NTAG 424 DNA class labels cluster around USD 0.45 to 0.65 per unit at five-figure volumes (public catalogues, 2026). On-metal versions cost 7% to 30% more. Quantities of 50,000 and above are quote-only.
Standard non-secure NFC tags of the NTAG213 class list at around EUR 0.19 to 0.23 at 1,000 to 10,000 units (public catalogues, 2026). They are cheaper because they cannot prove authenticity. Anyone can copy them.
Physical constraints matter as much as price. Standard tags detune on metal, so closures, metal cases and tins need on-metal tags with a ferrite layer. Tag placement decides read reliability, and a well-designed integration reaches 99% reads.
The same mechanism serves different questions depending on the product.
For secondary markets, ownership certificates turn the record into proof that travels with the item.
It can be, if the two kinds of data stay separate from the start.
| Data | Examples | Handling |
|---|---|---|
| Product data | Scan time, country or city, authentication result, tamper status | Identifies no person; kept for the product’s life; shared with partners as needed |
| Personal data | Registration, ownership, contact details, preferences | Collected only with clear notice and consent (GDPR in Europe); owner identity never exposed to later owners or partners |
Clean provenance is the asset. The brand knows where each data point came from and on what terms.
One investment in identity and carriers produces evidence for several teams.
| Team | Uses the data to | Question it answers |
|---|---|---|
| Brand protection | Detect counterfeits, clones and refills | Where are fakes being scanned? |
| Supply chain and commercial | Detect diversion, understand sell-through | How much stock sold in its intended market? |
| Marketing and CRM | Build consented owner relationships | Which markets engage most after purchase? |
| Client services | Support warranty, service and resale | Who owns this item now? |
| Compliance | Serve Digital Product Passports by unit | Which data applies to this exact item? |
On compliance: the central EU DPP registry has been live since 20 July 2026 (European Commission). Textiles are indicatively the first product group, around 2027, with enforcement around 2028 to 2029. Brands that build the identity layer for commercial reasons meet those requirements as a by-product.
Start with one product line where the reason to scan is obvious and the data would change a decision.
Track five metrics: coverage (share of units with a working identity, target 99% or more), scan rate, registration rate, verified share and signals acted on. The first season usually surprises brands twice: by how many scans come from markets they do not sell into directly, and by how many owners register when the product offers something worth having.
40+ brands · 12 years · €1.5B protected
Products already reach every owner, whoever sold them. Brands that give each item a secure identity turn that reach into verified, consented data they own.
First-party product data is information a brand collects directly from interactions with its own physical products. It includes scans, authentication results, tamper status, registrations, ownership transfers and service events. A carrier such as NFC on each item delivers it, and the brand owns it without relying on retailers or brokers.
First-party customer data starts from a person interacting with a brand channel, such as a website account or boutique purchase. First-party product data starts from an item. It records what happens to a product anywhere in the world and links to a person only when the owner consents, for instance at registration.
Brands give each unit a unique identifier, usually a GTIN plus serial as a GS1 Digital Link, and attach a readable carrier such as NFC or a secure QR code. Each scan is recorded as an event on the item’s record. Consent is requested only for registration and ownership.
Yes, when product data and personal data are kept apart. Scan time, approximate location, authentication result and tamper status identify no one. Registration, ownership and contact details are personal data and need clear notice and consent. Owner identity should never be exposed to later owners or partners.
A copyable carrier lets counterfeits generate scans that look genuine, which contaminates every report built on them. Cryptographic NFC of the NTAG 424 DNA class signs a new code on every tap and validates it server-side, so only genuine items produce verified data points.
No. iPhone XS and XR and later read NFC tags in the background without an app, and Android phones read them natively with the screen on. A tap opens a web experience directly. Registration and ownership steps happen there, with consent requested at the moment of action.
Talk to our team