The Product Graph: Why Individual Product Data Beats SKU Data
Key Takeaways
- SKU data captures what left your factory; a product graph captures what each individual unit did in the world across its entire lifetime.
- Industry average recall completion rates hover around 20–30% without unit-level data; manufacturers with product graphs regularly exceed 70%.
- A product graph enables precision aftermarket revenue, predictive support, and auditable circular economy claims — none of which are possible at SKU level.
- Serialisation and frictionless registration are the two foundational capabilities required to start building a product graph.
Your business intelligence team can tell you exactly how many units of Model X shipped last quarter. They can break it down by channel, region, and price point. They can layer in return rates, margin contribution, and attach rates for accessories. It looks like insight. It feels like control.
It isn't.
What they cannot tell you is what happened to unit number 4,812. Where it ended up. Who owns it. Whether it's been serviced. Whether it's sitting in a skip or circulating on eBay. Whether the person who bought it is furious or delighted. Whether the filter clogged in month three and they never called support — they just switched brands.
SKU data is a photograph of what left your factory. A product graph is a living record of what a product did in the world. The gap between those two things is where billions of dollars in service revenue, loyalty, and liability management quietly disappear.
What Is a Product Graph?
A product graph is the complete, connected data record for a single physical unit — not a model, not a batch, not a category. One unit. It captures every meaningful event and relationship across that product's entire lifetime, from manufacture to end-of-life.
Think of it as a graph in the computer science sense: nodes and edges. The product is the central node. Connected to it are events (manufacturing, shipment, sale, registration, scan, support ticket, parts order, warranty claim, resale), entities (retailers, owners, technicians, service centres), and states (in warranty, out of warranty, recalled, resold, decommissioned).
A mature product graph for a single power tool might contain:
- Manufacturing: assembled at Line 4, Plant C, batch QC-2241, serialised at 09:14 on 14 Jan
- Distribution: shipped to Screwfix DC Birmingham on 22 Jan, transferred to Screwfix Bristol on 3 Feb
- Point of sale: sold at Screwfix Bristol on 3 March, transaction ID captured via GS1 Digital Link scan
- Registration: registered by John, Birmingham B15, on 5 March, two days post-purchase
- Support: inbound query on 12 April — stuck filter; resolved via self-service guide, step 7
- Parts order: replacement filter F-449 ordered 13 April, delivered 15 April
- Secondary market: scanned at a car boot sale in Solihull on 8 September — ownership transfer flagged
- End of life: deposited at WEEE collection point, 14 February following year
That is one product. That is one product graph. And it tells you things no SKU report ever could.
The SKU Data Ceiling
SKU-level data was designed for a world where manufacturers had no post-sale visibility. It answered the only questions the business could ask: how many did we make, how many did we ship, how many came back?
Those questions still matter. But they represent the first five minutes of a product's ten-year life. The remaining nine years and eleven months — the period during which customers form lasting brand opinions, buy replacement parts, recommend or condemn your product to friends, and decide whether to buy from you again — are entirely invisible.
The consequences are predictable:
Recalls stay incomplete. Without knowing which specific units went where and who owns them now, manufacturers rely on press releases and retailer cooperation. Industry average recall completion rates hover around 20-30%. With unit-level ownership data, that number routinely exceeds 70%. The US Consumer Product Safety Commission (CPSC) has consistently cited poor owner identification as the primary barrier to effective recall completion in annual product safety reports.
Support is reactive and expensive. Without knowing a product's history, every support interaction starts from zero. The customer explains the problem; the agent asks which model; nobody knows it's the third call about this unit or that it's out of warranty. Average handle time and cost per case stay stubbornly high.
Aftermarket revenue is invisible. You know Filter F-449 sells well. You don't know that it sells best to owners of Unit Series 2200-2800, approximately 14 months post-purchase, in postcodes with hard water. That insight — available only at the unit level — is the difference between a generic parts catalogue and a targeted aftermarket revenue engine.
Circular economy claims are unverifiable. Sustainability reports say "X% of products are recyclable." Product graphs can say "X% of products were actually recycled, by whom, when, and where." That distinction is becoming legally significant under EU ESPR rules. The EU's Ecodesign for Sustainable Products Regulation explicitly requires manufacturers to provide verifiable end-of-life data, not just recyclability claims — a standard that only unit-level audit trails can satisfy.
SKU Data vs. Product Graph Data
| Dimension | SKU Data | Product Graph |
|---|---|---|
| Granularity | Model / batch | Individual unit |
| Ownership | Unknown post-sale | Named, dated, located |
| Support history | Aggregate ticket counts | Per-unit event timeline |
| Location | Last known warehouse | Current owner location |
| Resale / secondary market | Invisible | Detected via scan events |
| Recall targeting | Broadcast to all owners | Precision to affected units only |
| Parts demand forecasting | Category-level averages | Unit-age and usage-based signals |
| End-of-life status | Assumed from sales age | Verified via collection scan |
| Warranty validity | Date-based approximation | Owner-verified, unit-specific |
| Compliance evidence | Aggregate claims | Auditable per-unit proof |
The table is not hypothetical. Every row represents a real operational capability — and a real gap in what SKU-only manufacturers know today.
What a Product Graph Enables
Predictive Support
When support knows that unit 4,812 was registered 14 months ago in a hard-water postcode, has had a filter query before, and is now approaching its second recommended service interval, the support interaction transforms. Instead of reactive troubleshooting, you can push a proactive maintenance reminder before the problem surfaces. A major appliance manufacturer piloting this approach reduced inbound support contacts by 34% in the first year — not by deflecting queries, but by preventing the conditions that generate them.
Precision Recall
Product recalls are one of the highest-stakes events in manufactured goods. The conventional approach — announce, broadcast, wait — fails because there is no direct line to the specific owners of specific units. A product graph inverts this entirely. You know unit 4,812 is registered to John in Birmingham. You can contact John directly, confirm the affected serial range, and track completion unit by unit. The legal and reputational difference between a 25% completion rate and a 75% completion rate is not academic — it is the difference between manageable liability and systemic failure. We explore this in detail in our piece on warranty data as an undervalued asset for manufacturers.
Lifecycle Analytics
Aggregate failure data tells you a component fails. Unit-level data tells you it fails in units manufactured in a specific week, in specific climates, after a specific usage pattern. That is the signal that drives root cause analysis, supplier negotiations, and design improvements. One power tools manufacturer used unit-level scan and support data to identify that a bearing failure was concentrated in units assembled during a three-week period when a lubricant supplier had changed formulation. The fix cost £40,000. The potential recall, without that precision, would have cost £4 million.
Circular Economy Verification
The EU Digital Product Passport (ESPR) does not ask whether your product is theoretically recyclable. It requires you to demonstrate — with auditable evidence — what actually happened to it. A product graph provides exactly that: a chain of custody from manufacture to collection point, with verified events at each stage. Brands that build this infrastructure now are not just complying; they are building a competitive position that companies without serialised unit data cannot quickly replicate. See our overview of the product data manufacturers aren't collecting yet.
Aftermarket Revenue at Precision
Parts sales, extended warranties, and service contracts are most valuable when offered to the right owner at the right moment. A product graph makes this possible. It knows the unit's age, its usage signals (inferred from scan frequency and support contact), its owner's location, and the parts most commonly ordered at this lifecycle stage. The result is not a generic upsell email — it is a contextually relevant offer that converts because it is specific. We cover this revenue model in full in why a product experience platform should replace the CRM for manufacturers.
How to Build a Product Graph
The architecture is simpler than it sounds. It requires two foundational capabilities.
Serialisation means assigning a unique identifier to every unit — not just a model number, but a per-unit serial that is embedded in a scannable code (GS1 Digital Link QR is the current standard) at manufacture. This is the anchor point for everything else. Without a unit-level identifier, there is no graph — only aggregate data.
Registration is how you attach a human owner to that identifier. Frictionless warranty registration at unboxing — triggered by scanning the product code — is the most effective mechanism. Registration rates above 40% are achievable when the registration experience takes under 60 seconds and delivers immediate value (warranty confirmation, setup guide, parts finder). Every registered unit becomes a named node in your product graph from day one.
From those two foundations, every subsequent event — support contact, parts order, resale scan, service visit — can be attributed to a specific unit and appended to its graph. The data model grows richer with every interaction, compounding in value over the product's life.
Vendors operating in this space include Evrythng (now part of Digimarc), Registria, and Kezzler, each with different emphases on serialisation infrastructure, registration workflows, and analytics. BrandedMark is built specifically for manufacturers of durable goods who need all three layers — serialisation, registration, and lifecycle analytics — in a single platform with no-code experience design and built-in GS1 and EU DPP compliance.
Frequently Asked Questions
How is a product graph different from an IoT device twin?
A device twin, in the IoT sense, mirrors the real-time state of a connected device — sensor readings, firmware version, operational status. A product graph is broader and works for any physical product, connected or not. It captures the lifecycle story of a unit: who owns it, what support they've needed, what parts they've ordered, where it's circulating. Most durable goods are not IoT-connected, and will not be. The product graph gives manufacturers unit-level intelligence for all of them, via scan events and registration data rather than continuous telemetry.
What is a realistic registration rate, and does the graph have value if most units aren't registered?
Registration rates vary by category and registration experience design. Power tools and appliances typically achieve 25-45% with optimised in-box QR registration flows; categories with strong warranty incentive (tools with theft protection, appliances with extended warranty on registration) can reach 60%+. A product graph at 35% registration still gives you individual-level data on roughly one in three units in the field — enough for precision recall targeting, cohort analysis, and aftermarket segmentation that is materially more valuable than SKU aggregates. The graph grows denser over time as more touch points (support, parts, resale scans) append to existing records.
How does the product graph relate to EU Digital Product Passport requirements?
The EU Digital Product Passport under ESPR requires manufacturers to provide verifiable information about a product's materials, repairability, and end-of-life pathway — accessible via a scannable identifier on the product itself. A product graph is the data architecture that makes this possible at unit level. Manufacturers who build serialisation and lifecycle event tracking now are building the DPP compliance infrastructure simultaneously. The two requirements are not separate projects — they share the same foundation.
The Shift That Is Already Happening
The manufacturers gaining ground in aftermarket revenue, recall management, and customer loyalty are not doing anything structurally different from their competitors. They are not spending more on advertising or hiring larger service teams. They are building product graphs — quietly, unit by unit — and compounding the advantage with every product that ships.
SKU data will always have a place in manufacturing operations. But it describes what left your factory. The product graph describes what your product did in the world, who it belonged to, what they needed from it, and what it is worth to them today.
That is not a reporting upgrade. That is a fundamentally different relationship between a manufacturer and the things they make.
BrandedMark gives every product a unique identity, a registered owner, and a full lifecycle record — from first scan to end of life. If you are ready to build your product graph, explore BrandedMark.