The supplier confirms the label before it is sent
proposed
After the AI reads a document, the supplier could see the label that would go to the customer and confirm or correct it before it is sent. Today the supplier reads its label, read only, but confirms nothing, so a wrong reading reaches the customer’s review first. A confirmation step could leave the last look with the one who knows the data.
Where it came from
Out of scope in the brief — the supplier’s review and confirmation of labels before submitting, deferred by you to a PoC or MVP; and the dead end of the flow “A response with a missing value”.
An assurance level on every transaction
proposed
Each transaction could carry a level — self-declared by the supplier, evidenced by documents, or verified by a third party — so the customer reads not only a number but how far it can be trusted. Circulor’s profile describes four such levels, each building on the last, and attaches a status to a connection or a batch rather than to a single number.
Where it came from
Circulor’s four “Trust & Assurance” levels — self-declared, evidenced, verified, traceable.
A data-quality score beside measured / estimated
proposed
Beside measured or estimated, the label could show how much of a figure rests on the supplier’s own primary data, and a score for how good the data is. PACT records the share of primary data and three data-quality ratings from 1 (best) to 5 (worst), with worst-case values when a supplier cannot say. Watershed’s profile lists the origin of a supplier’s factors, but found no numeric data-quality score.
Where it came from
PACT’s primaryDataShare and dqi; the origin of a supplier’s factors in Watershed.
An export in PACT’s ProductFootprint shape
proposed
Beside CSV, the export could write a record in the shape of PACT’s ProductFootprint, so a PACT-conformant tool could read it. PACT is a standard with a network of conformant software; its profile counts 50+ listed solutions. The label carries no per-unit footprint today, so what maps across would have to be decided first.
Where it came from
The PACT data model and exchange rules.
The supplier’s document private until shared
proposed
Today the customer never sees the supplier’s original file. The document could instead stay private to the supplier and be shared with a chosen customer when the supplier decides to. Circulor’s profile says supplier documents “stay private until you choose to share them” and that the supplier controls who each is shared with.
Where it came from
Circulor — supplier documents “stay private until you choose to share them”; extends the rule that the customer never sees the file.
A replaced transaction kept as a version
proposed
Today a replacement withdraws the previous transaction and nothing of it is kept. A replaced transaction could stay as an earlier version, so the audit trail shows what was said before and what changed. PACT’s current rule is that a change to any part of a footprint results in a new footprint with a new id, the old one marked Deprecated.
Where it came from
PACT — a new id per change; the flow “Clarification” ends with the replaced transaction gone.
A supplier passes the request to its own supplier
proposed
In the demo the customer asks each of three suppliers directly. A supplier could instead pass the request on to its own supplier, and the chain would grow deeper than three. Circulor’s profile describes a map of facilities “across all tiers”, built from the buyer back toward the source.
Where it came from
Circulor — a supply-chain map “across all tiers”; the demo asks each supplier directly.
The label feeds the EU Battery Passport
proposed
The container’s label could feed the carbon-footprint part of the EU Battery Passport, so the data gathered along the chain is entered once. Circulor’s profile says its passports are created from templates built to ESPR and CEN/CENELEC standards and are “a subset” of the traceability data. The brief leaves the Digital Product Passport out of the label, so this would be a step beyond it.
Where it came from
Circulor — passports from ESPR templates; your STS Flow example lists the Digital Product Passport among its non-emission fields (out of the demo).
These are proposals for the product beyond the documentation, not promises: none of them is in the blueprint or on this site’s screens, and each could be dropped or changed.