The moment a product leaves a factory, it begins to forget.

The material batch, the hands and machines that shaped it, the quality checks, and the reasoning behind its construction remain scattered across organizations. By the time the object reaches its owner, its history has been compressed into a box, a receipt, and a few symbols. Years later, even those may be gone.

This forgetting is ordinary, yet it limits almost every circular decision. We cannot repair what we cannot identify, confidently reuse what we cannot assess, or recover materials efficiently when composition is unknown.

Products do not need consciousness. They do need memory.

“A circular economy is not only a movement of materials. It is a movement of knowledge alongside materials.”

The information cliff after purchase

Before sale, a company may know a great deal about a product. It has specifications, bills of materials, supplier documents, test results, production dates, and quality records. At sale, only a small portion crosses the boundary to the owner.

The rest falls over an information cliff.

Some loss is reasonable: customers do not need an enterprise database, and some details are sensitive. But losing product knowledge creates costs later:

  • technicians spend time identifying parts;
  • resale buyers struggle to assess authenticity and condition;
  • refurbishers cannot price risk accurately;
  • recyclers receive anonymous mixtures;
  • owners replace items that might have been repairable;
  • brands lose contact with products they could support.

A product memory is a governed thread that preserves what later decisions may require.

What should a product remember?

Different products need different memories. A cotton shirt and an industrial motor do not have the same risks, lifetimes, or recovery paths. Still, a useful memory often has four chapters.

Chapter The question it answers Example
Origin What is this, and where did it begin? Model, serial, maker, production batch
Substance What is it made from? Fibers, alloys, chemistry, components
Experience What has happened to it? Use, service, repair, upgrade
Possibility What can happen next? Resale, refurbishment, disassembly, recovery

Origin helps establish identity. Substance makes the object legible. Experience describes changing condition. Possibility connects the past to the next best action.

The record should also remember uncertainty. If a supplier declaration covers a batch rather than an individual item, the passport should say so. If a repair used an unverified replacement component, that event can be recorded without pretending the original specification still applies.

Data callout: A truthful “unknown” is more useful than a precise-looking field with no defensible source.

Memory changes value

Two visually identical objects may have very different value because of what happened to them. One machine was serviced at every interval; another ran until failure. One bag is authentic and recently repaired; another has no verifiable origin. One battery retained favorable performance; another experienced conditions that narrowed its next use.

Today, that difference often lives in paper folders, proprietary service systems, or the memory of an owner. A portable product history can turn invisible care into visible value.

That has consequences for design. If maintenance can be recognized at resale, owners have a stronger reason to maintain. If verified refurbishment becomes legible, secondary markets can distinguish it from simple cosmetic cleaning. If recovered material quality is documented, it can move from anonymous waste toward a specified input.

Memory does not guarantee value, but it allows value to survive a transition.

Memory must belong to the product—not the platform

There is a danger in confusing a product memory with an app account. Platforms are temporary. People forget passwords, companies close services, and ownership changes.

A durable memory should remain connected to the item and use identifiers that can outlive a particular interface. Its essential data should be portable. Access should not depend entirely on the first owner remaining a customer of the original brand.

This does not mean all records are public. Ownership events can preserve privacy through consent, minimized personal data, and separation between the product’s history and a person’s identity. The object needs continuity; it does not need to become a tracking device.

The practical mechanics are described in How Digital Product Passports Work. The philosophical requirement is simpler: future access must be treated as part of present product quality.

Forgetting has been built into linear commerce

The classic linear model—make, sell, use, discard—does not require much memory. Once a sale is complete, responsibility and information can move away from the producer. The system is optimized for throughput.

Circular models reverse that assumption. Rental, repair, take-back, resale, remanufacturing, and material recovery all create return journeys. When products return, knowledge must return with them.

Consider a refurbisher receiving one hundred devices without reliable identities. Staff must inspect each one, infer configuration, search for compatible parts, and estimate risk. Now imagine the same devices arriving with model, component, repair, and diagnostic histories. Physical work still matters, but uncertainty falls.

Traceability therefore becomes a form of operational infrastructure, not merely communication. Why Traceability Is Becoming Infrastructure explores that transition.

The right to forget still matters

Persistent memory can create harmful surveillance if designed carelessly. A product history should not expose where an individual lives, when they use an object, or who they are. Product data and personal data are different domains, even when a service moment temporarily connects them.

Responsible design asks:

  1. Does this event need to be stored?
  2. Does it need personal identity?
  3. Who benefits from persistence?
  4. Who could be harmed by access?
  5. Can consent be withdrawn without breaking the product record?

Minimal data is often stronger data. A passport may need to know that an authorized repair occurred, not the customer’s name. It may need a condition score, not a continuous stream of usage telemetry.

Designing for the second question

Most product communication answers the first question: “Why should I buy this?”

A product memory answers the questions that follow:

  • How do I care for it?
  • Can it be repaired?
  • Is this replacement part compatible?
  • What happened before I owned it?
  • Is it safe for a second use?
  • Where should its materials go?

Those questions appear at different times, to different people. The memory must therefore be structured, permissioned, and capable of changing without losing its history.

Not every product needs an elaborate biography. Some need only a stable identity, material declaration, and recovery instruction. Others need item-level events across decades. The standard should be proportional usefulness.

The important shift is to stop treating information as packaging that disappears after purchase. Information is part of the product’s continuity. If objects are expected to circulate, their knowledge must circulate too.

In the traceable future, a product will not be considered complete merely because it can be sold. It will be complete when it can be understood—by the first owner, the next owner, the repairer, and the person responsible for giving its materials another beginning.