Today
- The supplier has one list. The factory has another. The stores have a third.
- The lists don’t match, so nobody can say for sure.
- Everything gets pulled, just in case.
Record-keeping infrastructure for your business
ioxTrace gives every product, shipment, machine and document your software handles one permanent ID and one history, shared with the companies you choose. Finding an affected batch takes minutes, not days. A dispute becomes a lookup. An audit needs no phone calls.
Everything in your business has a history. ioxTrace keeps it in one record. The people you choose can check it. No one can quietly change it.
A device maker
“Our AI agents need a login to every system we run. Every login is a risk.”
On ioxTrace they read one record, and none holds the keys to a system.
One unit, one weekA fashion brand
“Every piece we sell will need a product passport, and our suppliers still send spreadsheets.”
Each supplier adds its own step once, with its evidence. The passport page reads from that record, whoever builds the page.
One jacket, seven yearsA fabric mill
“Every customer asks us for the same certificates, and again each time one is renewed.”
Keep one record in your own account and decide who reads it. Renew a certificate once, and every customer you shared it with sees it.
From the supplier’s sideNot building it yourself? A software provider can build on ioxTrace for you. Ask for your own account, and your records stay yours whoever builds the application. Or send us your scenario.
A database shows how things are today. An audit log lists what changed. ioxTrace does both, and adds an ID that works across companies, proof that nothing was edited, and sharing you control. Your application keeps the screens, the workflows and the decisions.
Standard ways inA REST API, a Python SDK and MCP tools for AI agents.
Built to be checkedReceipts and exports that the people you allow can check on their own.
No migrationKeep your database. Store the ioxTrace ID next to your own.
One example
If a supplier keeps part of the chain private, the answer says so. A recall never looks complete when it is not.
Here the record was an ingredient. It could as easily be a machine, a shipment or a certificate.
Pick a story. Each has four small cases to solve, using nothing but the record.
Identify
Your move
Your move
Fingerprint when stored:
Fingerprint now:
Your move
The stories, names and figures here are made up to show the product.
Bring your own scenario. We run it the same way.Book a demo
A regulator asks them. So does a customer, a partner, and anyone checking what an AI agent did.
One ID that stays the same in every system and every company.
Answered by Identify→Every change is kept, so you can see it as it was on any past day.
Answered by Remember→Every entry names who made it, whether a person or an AI agent.
Answered by Prove→Every document is sealed when it is stored. Edit it later, and it shows.
Answered by Prove→Identify, Remember and Prove answer the four questions. Share decides who else may ask. Everything else stays in your application.
One permanent ID per item.
So two companies never argue about which item they mean.
Every change is kept.
So “what did we know in March?” has one answer.
Anyone you allow can check it.
So nobody has to take your word for it.
Only what you allow.
So each partner gets what they need and nothing else.
Picture a company that designs, makes and sells motion-control devices. Its AI agents work in support, quality, production, purchasing and sales. Its systems write to ioxTrace once, so every agent reads one record and none holds the keys to a system.
5 agents8 systems
40 connections, 40 sets of keys
5 agents8 systems
13 connections, one record
Support inbox
Customer email: “It stalls in the cold.”
Support agent
Reads: Order · Factory test · Firmware version
Likely cause: driver board lot D-118.
Kept as its conclusion, with the three records it read.
Quality agent
Reads: Every unit built with lot D-118 · Test results · Support’s conclusion
212 units carry this lot. 38 went to cold regions.
Production agent
Reads: Quality’s finding · Line 2 schedule
Proposes holding 60 units on line 2.
Production lead approves, 10:20
Purchasing agent
Reads: Supplier certificate, sealed
The certificate rates the board to 0 °C. Our specification says −10 °C.
Sales agent
Reads: Orders · Dealers · Shipments
Proposes replacement boards for 38 customers.
Head of support approves, 08:35
Chief executive
“Why did we replace 38 units?”
The record answers in one view: who said what, based on what, and when.
Stays in your application: the agent, its tools, its prompts and its memory. This story is made up to show the product.
The same four jobs, applied to different problems.
A contractor maintains the lifts in an office tower. When the contract changes hands, the service history usually doesn’t.
A complete history at handover, and a clear answer when a failure is disputed.
Stays in your application: work orders, scheduling, service levels and technician assignment.
A fashion brand’s products are made by a network of mills and factories, then repaired, resold and recycled. Each step lives in a different system.
Supplier claims you can stand behind, and items that keep their authenticity through repair and resale.
Stays in your application: catalogue, merchandising, storefront and the product page itself.
A supplier reports a contaminated ingredient. The retailer has to find every batch, product and store it reached.
A recall scoped to the batches that matter, with the evidence to back the decision.
Stays in your application: the recall decision, customer notices and regulator reporting.
A shipment passes between a shipper, two carriers and a warehouse. When something arrives damaged, everyone has a different story.
Clear responsibility at every step, and claims settled on the record.
Stays in your application: routing, pricing, contracts and claims handling.
An equipment maker sells a machine that will be serviced by dealers, change owners and run for twenty years.
A service history any owner or dealer can trust, and fewer warranty arguments.
Stays in your application: service scheduling, parts ordering and warranty policy.
A lab issues test results that buyers, banks and insurers rely on. Today they phone the lab to check that a certificate is real.
Results trusted on sight, and far fewer verification calls.
Stays in your application: the testing process, how results are withdrawn and the verifier’s screen.
A property claim arrives with photos, an expert report and a repair quote. Months later, the other side challenges the evidence.
Decisions you can defend, with a clear trail of who saw and said what.
Stays in your application: claim workflow, assessment and payout decisions.
Picture a fashion brand that makes 12,000 pieces of one jacket. Each piece needs a Digital Product Passport that still answers in seven years, to shoppers, authorities, repairers and recyclers. The passport page is the part people see. ioxTrace keeps the record under it.
Padded jacket
ioxTrace IDJ4C7W-2MX9E2
Sewn in at the factory3
One jacket, seven years
Before the sale
Each supplier adds its own step, once.
Fibre supplier, adds
Recycled polyester, lot R-2291, with its certificate.
Mill, adds
Woven and dyed. The chemical test report is sealed.
Factory, adds
Cut and sewn: 12,000 pieces, one ID each.
On sale
You publish. Others check.
You, the brand, adds
Publish 12,000 passports from the record in one step.
Authority, reads
Asks what “recycled” rests on. Reads the certificate, sealed on the day it arrived.
Shopper, reads
Scans the label in the shop. Reads fibre, care and where it was made.
Years 1 to 7
The record keeps growing.
Repair partner , adds
Replaces the zip and adds the repair.
Resale partner , adds
Checks the piece and its repairs, then adds the resale.
Recycler , reads
Reads fibres and trims, and sorts the jacket for recycling.
An example of what each reader is granted.
| Shopper | Authority | Repairer | Reseller | Recycler | |
|---|---|---|---|---|---|
| Fibre and care | Yes | Yes | Yes | Yes | Yes |
| Where it was made | Yes | Yes | No | Yes | No |
| Parts and trims | No | Yes | Yes | No | Yes |
| Repairs and resale | Yes | No | Yes | Yes | No |
| Certificates and test reports | No | Yes | No | No | No |
| Suppliers at every tier | No | Yes | No | No | No |
You see everything a supplier writes on your record, with their name on it. You see their own records and documents only when they share them, and you are told when an answer is partial. Each supplier sees only its own step. You set each grant, and you can change it when the rules change.
Who builds the passport page? Your own team or your passport provider. Either way it reads from ioxTrace. Stays with you: design, sourcing, your shop and the page itself. This story is made up to show the product.
From the supplier’s side
An example of what each customer is granted, and what it then sees.
Customers cannot see each other. A hidden record answers like one that does not exist.
Written per customer: a step you add to a customer’s own product. It carries your name. They can dispute it, but not edit it. This example is made up to show the product.
ioxTrace is infrastructure. You build the application on top.
Not building it yourself? A software provider can build on ioxTrace for you. Ask for your own account, and your records stay yours whoever builds the application. Or send us your scenario.
269 checks. All passed.
Each check is a step a real team would take: trace a batch to its source, catch an edited certificate, stop an agent approving itself. Each run plays out a whole scenario on ioxTrace and checks every step on the way. Also validated for personal finance, industrial assets and digital goods.
Anything you need to keep track of: a product, a machine, a shipment, a batch, a certificate. ioxTrace gives each one an ID and a history.
Teams that build software used by more than one company: traceability, inspection, compliance, asset and AI-agent applications. You build the application. ioxTrace keeps the record underneath.
Either. ioxTrace is infrastructure, so someone builds the application on top: your own developers or a provider. Hold your own account: your provider works with keys you issue, and you can change provider without moving your records.
No. There is no chain, no token and no consortium to join. You get a standard API and signed receipts that the people you allow can check.
No. It is the layer those services are built on. Passport, recall, inspection and asset applications all use the same building blocks.
No. You keep both. ioxTrace sits underneath and keeps the identity, the history and the proof. You store its ID next to your own data.
A database shows how things are today. An audit log lists what changed. ioxTrace does both and adds three things: an ID that works across companies, proof that nothing was edited, and sharing you control.
A warehouse copies data so you can analyse it. ioxTrace keeps what happened to each item: who recorded what, when, with the document sealed and the people allowed to see it. One is for reports. The other is for showing someone else what is on record.
Only the people you allow. Each company’s records are kept apart. You grant access by partner, by purpose and by field, and every view is logged.
Everything a supplier writes on your record, with their name on it. Their own records and documents only when they share them. When part of an answer is withheld, you are told it is partial.
Who recorded what, when, and that nothing has changed since. It does not decide whether a claim is true. That judgement, like your policies and decisions, stays with you.
Yes. An agent reads records for context and evidence, follows changes and submits actions for a person to approve. It sees only what you grant. The agent itself, its tools and its memory stay in your application.
Then each agent holds a key to each system, and what it read is hard to reconstruct later. With ioxTrace each agent has one identity and one place to read, sees only what you grant, and its reads and conclusions go on the record.
You can issue your first IDs within hours, then add history, links and proof over the following weeks. Your existing systems stay in place throughout.
Plans are sized by capacity: request rate, keys, team size, workspaces and evidence storage. We don’t charge per product or per scan. Send us your scenario and we size a plan with you.
Send us the question your current systems cannot answer. We run it on ioxTrace and walk you through the result, record by record.
Your request is in. We will write to to arrange a time.
Your request, on the recordID