Versatile Trace: Why a Traceability Record Is Not the Same as an Identity

Imagine a carton of fruit arriving at a wholesale market at six in the morning. It carries a label, a batch number, a consignment record — one identity, cleanly documented. An hour later the carton is open, empty, and flattened. Twenty consumer packs have left the building in five different directions, each one now carrying a label of its own. Somewhere between the loading bay and the shelf, the product stopped being the thing that was documented and became twenty things that were not. This is the moment identity continuity can quietly fail, and it is the moment Versatile Trace was built for.

The Word "Traceability" Hides the Actual Problem

The industry treats traceability as a recording problem. Capture enough events at enough nodes, the reasoning goes, and the chain will be complete. So systems are measured by how much they log: scans per node, records per batch, integrations per warehouse. But a log is not a chain. A log is a pile of observations about things, and it is only as useful as the certainty that each observation refers to the same thing as the one before it.

That certainty is not a recording problem. It is an identity problem. And identity in a supply chain is unusually hard for one specific reason: the unit does not stay the same. A pallet becomes cartons. A carton becomes packs. A pack becomes a purchase. Each transformation is a place where identity can be re-declared rather than inherited — and a re-declared identity is just a claim wearing a record’s clothing.

Dual-ID Logic: Two Layers, One Identity

Versatile Trace addresses this with what IGSO calls QRFiD — a dual-ID logic that runs a QR layer and an RFID layer over the same product at two different scales. The wholesale unit — carton, tray, pallet — carries an RFID identity readable at gates, in bulk, without line of sight and without anyone stopping to point a scanner. The consumer unit carries a printed QR identity readable by any shopper with a phone. Neither layer is a copy of the other. They are two resolutions of the same object, and they are bound to each other.

The binding is the entire point. When a consumer scans the QR on a single pack, the system does not merely return what that pack claims about itself. It resolves the pack to its parent wholesale unit and cross-checks the two. Read from the other direction, a gate reading an RFID carton can enumerate the consumer units that came out of it. The relationship runs both ways, which means it can be tested from both ends — and a relationship that can be tested from both ends is considerably harder to fake than a label that can only be read.

Four Things That Turn a Trace Into an Identity

First, the identity must be issued, not asserted. A serial that a supplier prints for itself proves only that the supplier owns a printer. An identity that is issued under a standard and anchored to an institutional resolver can be checked against something outside the party that benefits from it.

Second, the identity must survive transformation. When bulk becomes retail, the new unit has to inherit from the old one rather than begin its own unrelated story. Inheritance is what makes a chain a chain.

Third, the identity must be readable by the people who actually handle the product — not only by the systems that manage it. An identity legible solely to an ERP is an internal record. An identity a market porter can read at a gate and a shopper can read at a shelf is infrastructure.

Fourth, the identity must be resolvable to evidence. Origin records, freshness checkpoints, safety verification, certification status — the identity is the address at which that evidence lives. Without the evidence, the identity is a number; without the identity, the evidence has nothing to attach to.

“A trace tells you what was recorded. An identity tells you what you are holding. Only one of those survives the moment a case is opened.”

Why This Is a Data Problem Before It Is a Hardware Problem

It is tempting to read QRFiD as a tagging strategy — QR here, RFID there, better coverage. That is the smallest part of it. The substantive work is making locally generated production information globally readable: a packhouse in one jurisdiction records in its own formats, conventions, and language, and that record has to remain meaningful to a buyer, a regulator, or a customs officer who has never seen that packhouse and never will.

This is why Versatile Trace is designed to sit alongside existing ERP, warehouse-management, and logistics systems rather than replace them. Asking a supply chain to abandon its operational systems in order to become traceable rarely fits operating reality. The realistic path is a backbone that reads what those systems already produce and gives it a shared structure and a shared identity — so the data becomes portable without the operations becoming disrupted.

The Test Case Is Failure, Not Success

The honest measure of a traceability system is not how it behaves when everything is correct. It is how fast it can answer a question nobody wanted to ask. A safety result comes back wrong for one batch. Which cartons contained it? Which consumer units left those cartons? Which of them reached a shelf, and which are still in a chill room where they can be stopped?

A system that only records events answers this slowly, by reconstruction, in a spreadsheet, under pressure. A system built on continuous identity answers it by walking a relationship that was already there before anyone knew it would be needed. The difference between those two situations becomes critical in agricultural products, where delay narrows the window to act. Recall speed is not a feature of traceability. It is the audit of whether the identity layer was real.

Where It Already Runs

This is not only a design document. In May 2026, traceable blueberries from Selen reached shelves at BigC carrying IGSO freshness certification, and a shopper in the aisle could scan a box and see its harvest time, freshness tier and certification records. That deployment proves the consumer-facing half of the argument: an identity that resolves to evidence a shopper can read. The wholesale-side layer described above is the part that has to hold when the unit changes — the harder half, and the reason this is a backbone rather than an interface.

Versatile Trace is the layer that carries that continuity. Live Cert governs whether a certificate is currently valid; Origin Plus decides what a consumer sees in the three seconds they give it. Neither is meaningful if the system cannot say, with confidence, that the thing being certified and the thing being displayed are the same thing being held. That is the backbone’s job, and it is invisible when it works.

The Arc, in One Line

Traceability records where a product has been. Identity establishes what it is. Everything else IGSO builds — certification, consumer display, market access — rests on getting the second one right first.

Frequently Asked Questions

What is the difference between traceability and Versatile Trace? Conventional traceability records events at supply chain nodes. Versatile Trace maintains a continuous identity for the product across those events — including when the unit changes, such as when a wholesale carton is broken down into consumer packs. Recording events without continuous identity produces a log rather than a verifiable chain.

What does QRFiD mean? QRFiD is IGSO's term for a dual-ID logic combining a QR layer at the consumer-unit level with an RFID layer at the wholesale-unit level, bound so that each can be resolved and cross-checked against the other.

Does adopting Versatile Trace require replacing existing systems? No. It is designed to integrate with existing ERP, warehouse-management, and logistics systems and to support multiple data formats and protocols, so that locally generated production data becomes globally readable without requiring operational systems to be replaced.

How does this help with recalls? Because the relationship between wholesale and consumer units is maintained continuously rather than reconstructed after the fact, an investigation can move in both directions — from an affected batch to the consumer units that came from it, and from a consumer unit back to its origin records.