Skip to content
AMPHOZE

Circular economy

A product that comes back is a product someone designed to come back.

Circularity fails in the same place every time: an organisation builds the returns logistics and then discovers it cannot identify what came back, cannot tell what condition it is in, and cannot price it. The loop is a materials story on the slide and a data story in the building. We work on the second one.

The loop

Seven stages, and where technology attaches to each

Select a stage. Each one is only reachable because the previous stage emitted data the next one can act on — which is why a loop drawn without its enablers stays a diagram.

Fig. 01 — Product lifecycle loop

Design

Circularity is decided here or not at all. Whether a product can be opened, diagnosed, repaired, upgraded and separated at end of life is fixed by choices made before anything is manufactured — including the choice to give it an identity it carries for life.

  • Design-for-disassembly rules in CAD/PLM
  • Material and component data models
  • Simulation and digital twin
  • Passport schema defined at design time
  • Serialisation and identity scheme
Recycle feeds back into Design: composition and teardown findings are the most direct evidence available for the next revision, and the stage most often left unwired.

The data spine

Four layers, and each one is useless without the one above it

You cannot trace what has no identity, assess what has no history, or make a provenance claim that anyone will act on without all three. This is the part that has to exist before circularity is operable.

  1. 01

    Identity

    A stable, unique reference for the individual item — not the model, the item. Serialisation carried physically by QR, DataMatrix, RFID or NFC, and resolvable to a record for the item’s whole life, including after it changes owner.

  2. 02

    Traceability

    Where the item has been and what happened to it: production batch, supply chain, ownership transfers, service events, movements through reverse logistics. An event log against the identity, not a status field that overwrites its own history.

  3. 03

    Condition

    What state it is in now — from telemetry while in use, from inspection and imaging on return, and from the wear implied by its own usage history. This is what converts a returned object into a routable decision: repair, refurbish, resell or recover.

  4. 04

    Provenance

    What it is made of and where that came from, with enough integrity that a regulator, a buyer or a recycler will act on it. Materials, substances of concern, recycled content, and the attestations behind each claim.

Most enterprise systems model products at the SKU level, because that is what was needed to sell them. Circularity needs the individual unit: this pump, this laptop, this battery module, with its own history. Retrofitting per-item identity onto a product catalogue built for models is usually the largest piece of work in the programme, and the one nobody budgets for.

The layers also have to be readable by parties outside your company. A repair shop, a second-hand buyer, a customs authority and a recycler will each ask a different question of the same item, and none of them will have access to your ERP. That makes identifier schemes, data portability and scoped access architectural decisions taken early rather than integration details handled late.

Done properly, the spine pays for itself before any circular model launches: warranty claims resolve against real service history, recalls scope to the affected units instead of the affected model, and counterfeit parts become visible.

Digital product passports

The spine, made addressable from the object itself

A passport is what turns the data spine into something a stranger holding the product can query. It is arriving as regulation in several categories; it is more useful when it is not built to the compliance minimum.

  • It is an addressable record, not a document

    A passport is a resolvable identifier on the physical item that returns structured data about that individual unit. A PDF attached to a model number is not a passport; it cannot answer a question about the object in front of you.

  • It is append-only across owners

    Manufacture, sale, service, resale, refurbishment and recovery all write events. The item outlives any one company’s systems, so the record has to survive ownership changes — which makes identifier schemes, data portability and access control design decisions rather than details.

  • Access is scoped by role

    A consumer, a repair technician, a customs officer and a recycler need different fields from the same record, and some of those fields are commercially sensitive. Scoped access is what makes a manufacturer willing to publish anything at all.

  • Data quality is the whole product

    A passport populated by hand at the end of the line will be wrong within a quarter. The engineering work is in wiring it to the systems that already know — MES, PLM, ERP, service records, telemetry — so that the record is a by-product of operations rather than an additional job.

  • Regulation sets the floor, not the ceiling

    Requirements are arriving product category by product category, and the compliance-minimum reading of them produces a record that satisfies an auditor and nobody else. The same infrastructure, designed once with resale and refurbishment in mind, is what makes second-life business models operable.

Business models

Three models, and the software each one actually needs

Circular business models are usually presented as commercial choices. Each of them is, underneath, a specific set of systems that has to exist before the commercial model can run at all.

Product-as-a-service

The customer buys the outcome — hours of operation, units produced, availability — and the manufacturer keeps ownership of the asset.

Once the asset stays on your balance sheet, longevity stops being a threat to next year’s sales and becomes the thing that protects margin. Durability, repairability and efficiency all move from cost lines to profit drivers.

Hard part — Metering that survives disputes. If the customer can plausibly challenge the number on the invoice, the model stalls in finance long before it stalls in engineering.

Software it requires

  • Metering of the billable unit, at the device, trustworthy enough to invoice from
  • Contract and entitlement logic: tiers, minimums, overages, service credits
  • Usage-based billing with dispute-grade audit trails
  • Fleet management: where every unit is, who has it, what state it is in
  • Remote diagnostics and secure OTA update across a heterogeneous installed base
  • Availability commitments backed by predictive maintenance rather than optimism

Resale and refurbishment

Returned units are graded, restored to a defined standard and sold again — as a controlled channel rather than a leak into the grey market.

Value depends almost entirely on grading speed and accuracy. Under-grade and margin is given away; over-grade and it comes back as a return, plus the cost of the trust.

Hard part — Grading consistency across sites and shifts. Two facilities grading the same unit differently makes pricing unusable and destroys the channel’s credibility faster than any defect would.

Software it requires

  • Condition grading that draws on the unit’s own history rather than a visual check alone
  • Vision-assisted inspection with a documented, repeatable grade definition
  • Residual-value and dynamic pricing models per grade and product family
  • Reverse-logistics routing: which facility, which process, which queue
  • Component-level inventory for harvested parts
  • Second-life warranty logic and channel listing automation

Take-back programmes

The manufacturer brings its own products back at end of use, whether driven by regulation, by material recovery or by control of the second-hand channel.

Return rate is the whole model. A programme nobody uses is a compliance cost; a programme with a high return rate turns into a supply of graded input for the two models above.

Hard part — Friction at the point of return. Every additional step the customer has to take suppresses the return rate, and the return rate is the variable that decides whether the programme is an asset or an obligation.

Software it requires

  • Registration and identification of the returning unit, ideally from its passport
  • Incentive and credit issuance tied to condition rather than a flat rate
  • Collection logistics, consolidation and chain-of-custody records
  • Certified data erasure and its evidence, wherever the product held data
  • Recovery and compliance reporting per material stream
  • Feedback of teardown findings into the next design revision

Related

Where this becomes an engagement

Circularity is the top rung of the sustainability framework. The engagement itself — what we scope, what we build, what we hand over — is described under services.

Identity and serialisationTraceabilityCondition and gradingProduct passportsReverse logisticsUsage-based billing
Circular economy engagementsThe sustainability framework

Start with the spine

Before the returns programme, find out whether you can identify what comes back.

Tell us what your product is, what you know about each unit today, and where you want the loop to close. We will start with the gap between those three.

Start a ConversationRead our approach