What Is Product Lifecycle Management? The Modern Definition
Key Takeaways
- Traditional PLM software (Siemens Teamcenter, PTC Windchill, Arena) covers design through manufacture but goes dark at shipment — leaving 90% of a product's actual life untracked
- ERP, CRM, and field service systems fill parts of the post-sale gap but none connects a specific physical product to its current owner, state, and full service history
- A Product Operating System extends PLM with persistent digital identity per unit, enabling ownership registration, warranty tracking, aftermarket commerce, and EU DPP compliance across the full lifecycle
- The EU Digital Product Passport mandate (ESPR, from 2027) requires lifecycle data — ownership, service events, disposal — that traditional PLM systems do not capture
92% of manufacturers don't know who owns their products.
A company can spend three years and £40 million bringing a new appliance to market — precision-engineered, rigorously tested, beautifully packaged — and the moment it ships to a distributor, that company loses track of it entirely. No owner. No location. No service history. No idea whether it's still working, sitting in a warehouse, or being used in a country they never intended to sell into.
That number — 92% — comes from industry research on durable goods manufacturers published by the Manufacturing Leadership Council. It's not a niche problem. It's the default state of manufacturing.
Product Lifecycle Management software was supposed to solve this. It hasn't. And understanding why requires taking a hard look at what PLM actually covers, and what it has always ignored.
The Problem: PLM Stops at the Factory Gate
Ask any product manager or engineer what PLM means, and you'll get a broadly consistent answer: it's the system that manages a product from concept through design, engineering, prototyping, manufacturing, and launch.
That answer is correct. It's also only half the story.
The major PLM platforms — Siemens Teamcenter, PTC Windchill, Arena Solutions, Aras — are extraordinarily capable within their domain. They manage CAD data, bill of materials, change orders, compliance documentation, supplier collaboration, and manufacturing handoffs. For the product development phase, they are the record of truth.
But every one of those systems goes dark at the moment of shipment.
Once a finished product leaves the factory, PLM has nothing more to say about it. There's no concept of an owner. No field for where the product is installed. No mechanism to track a service event, record a repair, log a firmware update, or note that the product changed hands when a building was sold.
From a PLM perspective, a product that shipped in 2019 and a product that shipped yesterday are indistinguishable. Both are "released." What happened next is simply not the system's concern.
What Product Lifecycle Actually Means
The word "lifecycle" implies the full arc of a product's existence. In practice, a physical product moves through something like this:
Design → Engineering → Prototyping → Compliance → Manufacturing → Quality → Distribution → Retail → Purchase → Unboxing → Setup → Registration → Use → Maintenance → Service → Repair → Resale → End of Life → Recycling
Traditional PLM covers roughly the first seven stages. Everything from "Purchase" onwards — the stages that represent the actual life of the product in the real world — receives no systematic attention from PLM at all.
Consider the timescales involved. A product might take 18 months to design and manufacture. It might then be in active use for 10 to 15 years. The post-purchase phase isn't a footnote. It is 90% of a product's life. It receives approximately 0% of PLM's attention.
Where the other systems are supposed to fill the gap
Manufacturers know this gap exists. They've tried to paper over it with adjacent software categories:
- ERP tracks inventory and transactions, but at a product-type level. It knows you have 400 units of SKU-7842 in a warehouse. It doesn't know that serial number 7842-00391 was sold to a residential customer in Manchester and has been running continuously for three years.
- CRM tracks customer relationships. But it tracks customers, not products. It knows a customer called Sarah Davies bought an appliance in March. It doesn't know which specific unit she bought, what firmware version it's running, or whether it's the one that was recalled last autumn.
- Field Service Management software tracks service tickets and engineer dispatch. But it only activates when something goes wrong, and it depends on customers voluntarily calling in. It has no visibility into the 95% of products that never generate a support ticket.
None of these systems connects the specific physical product to its current owner, its current state, and its full history. That connection simply doesn't exist in the standard manufacturing technology stack.
Why This Matters More Than It Used To
The gap between traditional PLM and the real world has always existed. For most of manufacturing history, it was accepted as an inconvenient fact. You built and sold a product. What happened next was someone else's problem.
Three forces have made that position untenable.
First, the EU Digital Product Passport. Under the European Sustainability Products Regulation (ESPR) — adopted by the European Parliament in 2024 — manufacturers selling into the EU will be required to maintain and share detailed product data across the entire lifecycle — including materials, repairability, carbon footprint, and end-of-life handling. That data must follow the physical product through its whole life, not just to the factory gate. ESPR applies from 2027 onwards and will cover a sweeping range of product categories. See our full breakdown of what the Digital Product Passport means for manufacturers.
Second, the direct relationship imperative. Selling through retail channels means the retailer owns the customer relationship. Amazon, Argos, and Currys know far more about your end customers than you do. As the economics of aftermarket revenue — spare parts, service contracts, accessories, upgrades — become increasingly important, manufacturers who can't reach their customers directly are at a structural disadvantage.
Third, rising customer expectations. Consumers now expect the same connected experience from physical products that they get from software. The product should know who owns it. It should provide contextual help. It should remember its service history. It should make reordering consumables frictionless. Products that can't do these things look and feel outdated.
The Modern Model: A Product Operating System
The response to all three pressures is the same: give every product a persistent digital identity.
Not a generic product type identity. A specific, individual identity — tied to that serial number, that unit, that owner.
When a product has a persistent digital identity, everything changes. The identity becomes a thread that connects every stage of the product's life, from manufacture through to recycling. Every event in that product's life — registration, service, firmware update, ownership transfer, end-of-life — attaches to that identity and becomes part of a permanent, accessible record.
This is what a Product Operating System does. It's the infrastructure layer that PLM has always been missing.
A product with a digital identity can:
- Register its owner at unboxing, the moment the QR code is scanned
- Surface its manual in the correct language for the buyer's location — the same shift from paper to digital instructions that is transforming post-purchase support
- Track its warranty against the actual purchase date, not a default assumption
- Connect to support with full product context already loaded
- Sell spare parts directly, knowing exactly which parts fit that model
- Transfer ownership when the product is resold or relocated, updating all associated records
- Publish its environmental data for DPP compliance and sustainability reporting
None of this requires the product to be "smart" in the IoT sense. It doesn't need a wireless connection or an embedded processor. It needs one thing: a durable, unique identifier — a QR code or NFC tag — that links the physical object to its digital record.
For a deeper look at the fundamentals, see why every product needs a digital identity.
What This Looks Like in Practice
Abstract frameworks are easy to agree with. Here's what a Product Operating System looks like in concrete terms.
A thermostat that knows its installer
A heating engineer fits a new thermostat at a residential property. Before leaving the job, they scan the QR code on the unit. The scan registers the product at that address, logs the installer's certification details, captures the installation date, and activates the manufacturer's two-year warranty. When the homeowner subsequently scans the same code, they're presented with their user manual, a guided setup walkthrough, and a direct channel to manufacturer support — all pre-populated with the correct product details. No form-filling. No digging out the serial number from the back of the unit.
A pressure washer whose rental history follows it
A tool hire company runs a fleet of commercial pressure washers across 12 depot locations. Each unit carries a unique digital identity. When a machine is rented out, the scan logs the customer, start date, and depot. When it's returned, the system records run-time hours. When it goes in for service, the technician logs the work against that specific unit. When the machine is eventually sold into the second-hand market, the buyer can scan the code and see the full service history — every rental cycle, every maintenance event, every part replaced. The second owner inherits the same trust and transparency the first owner had.
An oven whose service record transfers with the house
A family sells their home. The kitchen includes an integrated oven purchased four years ago. Under a Product OS model, the seller transfers the product registration to the buyer as part of the conveyancing process — a 30-second QR scan. The new homeowner inherits the remaining warranty, the full service history, the original manual, and direct access to manufacturer support. The manufacturer, meanwhile, has updated the ownership record and now has a relationship with a new customer — without spending a penny on acquisition.
An air purifier that orders its own filter
A premium air purifier tracks filter usage through a combination of runtime hours and air quality data. As the filter approaches the end of its service life, the product identity system surfaces a replacement prompt the next time the owner scans the unit's code. One tap orders the correct filter for that specific model — sourced directly from the manufacturer, not via Amazon. The manufacturer captures the aftermarket revenue. The customer gets the right part, first time, without having to identify the model number themselves.
The Business Case
Connecting a product to its owner across its entire lifecycle isn't just philosophically correct. The financial case is substantial.
Direct customer relationships. When a manufacturer captures first-party data at registration, they break the retailer's monopoly on customer knowledge. They can communicate directly, personalise service, and build the kind of relationship that drives repeat purchase.
Aftermarket revenue. Spare parts, consumables, accessories, extended warranties, and service contracts are significantly more profitable than the original product sale. Manufacturers with direct customer connections capture a far larger share of this revenue than those who sell blind through retail channels.
Reduced support costs. Self-service product experiences — manuals, troubleshooting guides, setup videos — deflect a substantial proportion of inbound support contacts. When a customer can get the answer from a product scan in 30 seconds, they don't call the support line.
Regulatory compliance. The EU Digital Product Passport will require manufacturers to maintain and share product data across the lifecycle. Manufacturers who have built product identity infrastructure will satisfy this requirement as a byproduct of their normal operations. Those who haven't will face a significant compliance project.
Sustainability differentiation. Circular economy credentials are increasingly important to both consumers and enterprise buyers. A product with a traceable service history is more repairable, more resaleable, and more recyclable than one that isn't. That's a real differentiation story, not just a CSR footnote.
How to Start
The PLM gap is real, but closing it doesn't require a multi-year transformation programme.
Start with product identity. Assign a unique QR code or NFC tag to every product at manufacture. Print it on the label, emboss it on the chassis, embed it in the packaging — whatever is durable and scannable. This is the foundation layer. Everything else is built on top of it.
Add registration. Build a simple post-purchase registration flow, triggered by scanning the code. Capture the owner's name, contact details, and purchase date. This alone transforms your customer visibility position.
Layer on support and self-service. Attach the manual, setup guide, and FAQ to the product identity. Now every scan is a self-service support interaction — resolving queries, including error codes and fault diagnosis, before they become support tickets.
Connect commerce. Link spare parts, accessories, and consumables to the product identity. When a customer scans their product, show them what's compatible. Direct aftermarket revenue starts here.
Extend through the lifecycle. Add ownership transfer, service history logging, warranty management, and DPP compliance as capabilities. Each layer adds value — to the customer, to your service operation, and to your regulatory position.
This is the architecture of a Product Operating System. It's not a single software purchase — it's a new way of thinking about what a product is after it leaves your factory. For a practical starting point, the connected packaging checklist walks through how to launch a product with a digital identity from day one.
BrandedMark is the operating system for physical products. Every product gets a digital identity, a lifecycle, and an ongoing relationship with its owner. Join the waitlist →
Frequently Asked Questions
What is Product Lifecycle Management (PLM)?
Product Lifecycle Management is the discipline of managing a product's information, processes, and systems from initial concept through design, engineering, manufacturing, and launch. PLM software platforms centralise product data — CAD files, bills of materials, compliance documents, change histories — and enable collaboration across product development teams and supply chain partners.
What's the difference between PLM, ERP, and CRM?
PLM manages product development data. ERP manages business operations — finance, inventory, procurement, and logistics — at the product-type level. CRM manages customer relationships and sales pipelines. None of these systems tracks the relationship between a specific physical product and its current owner after the point of sale. That gap is what a Product Operating System is designed to fill.
What is a Product Operating System?
A Product Operating System is the infrastructure layer that gives every individual physical product a persistent digital identity, and connects that identity to its owner, its service history, its documentation, and its commercial lifecycle. It extends the traditional PLM view — which ends at manufacture — through ownership, use, maintenance, resale, and recycling.
What is the EU Digital Product Passport and how does PLM relate to it?
The EU Digital Product Passport (DPP), introduced under the European Sustainability Products Regulation (ESPR), requires manufacturers selling into the EU to maintain and share standardised product data across the full lifecycle — including materials, repairability, carbon footprint, and end-of-life instructions. Traditional PLM captures much of the manufacturing-phase data required, but DPP compliance also demands lifecycle data — ownership, service events, and disposal — that PLM systems don't track. Manufacturers will need product identity infrastructure to bridge that gap.
How do QR codes enable modern product lifecycle management?
A serialised QR code — unique to an individual unit, not just a product type — acts as the physical link between a product and its digital record. When scanned at any point in the product's life, it can surface the correct documentation, register an ownership change, log a service event, or connect the owner to direct support. Because QR codes require no special hardware on the product itself, they're cost-effective to deploy across large product volumes and long supply chains. Combined with a Product OS platform, each scan becomes an event in the product's permanent lifecycle record.