Where is it used?

These are not client references. Typical scenarios the product passport solves: export batches, supplier chains, CBAM path, lot tracking, green claims and external verify.

Scenarios

Problem · what it does · evidence link

In every card the path record stays in Trace; Gate filings and optional Evidence Sealing are added when needed.

Export / origin and batch trail

Problem: Which plant and lot produced this batch is unclear.
What it does: Links lot, plant and shipment on one product path.
Evidence: CX339 path record · UUID/QR check · optional seal.

Supplier → buyer data chain

Problem: Scope 3 / PCF supplier declarations break in the chain.
What it does: Writes supplier steps with controlled path updates.
Evidence: CX339 end-to-end path · optional Gate PCF bridge.

Product path into CBAM

Problem: Plant / product / shipment links break in CBAM files.
What it does: Path stays in Trace; formal filing in SustaGate CBAM.
Evidence: Trace path · Gate CBAM backbone · Gate not required.

Food / agri / raw-material lots

Problem: Harvest, processing and shipment records stay scattered.
What it does: Builds the lot path in the passport with templates.
Evidence: Batch-level path record · optional Micro Ledger seal (Evidence Sealing live).

Production + logistics handoffs

Problem: Warehouse, bonded and customs handoffs are invisible.
What it does: Writes handoffs into a time-stamped product passport.
Evidence: Who, when, which step · an auditable transit record.

Green claim / anti-greenwashing

Problem: Product claims lack a traceable path and evidence link.
What it does: Creates lot and shipment records bound to the claim.
Evidence: Trace path · optional Gate · CX341 green-claim line.

Auditor / customer UUID-QR verify

Problem: Buyers or auditors cannot access the record independently.
What it does: Shows the same product path externally via UUID / QR.
Evidence: External check · this site has no L2 API · CX3Scan /l2-evidence (live).

Recall / affected batches

Problem: Which lots and shipments are affected stays unclear.
What it does: Walks the lot path to surface affected batches fast.
Evidence: Recall scope is read from the product passport.

Let’s talk through your scenario

Clarify the product passport and CX339 path record against your team’s use cases.