This is the on-ramp for anyone evaluating the platform who wants more depth than the product pages. Conceptual, not a code reference — for the API surface, see API Reference.
From workspace provisioning to a consumer scanning a QR code — here's how everything fits together.
An organisation gets a TierraTrace workspace — a scoped environment with its own members, product registry, and API keys. Provisioning is handled by the identity layer (see TierraTrace Auth).
Map your product hierarchy — categories, attributes, certifications, and the data fields each passport must carry. Schemas are validated against the EU ESPR data model and can be customised per product line.
Use TierraTrace Connect to wire in your ERP (SAP, Oracle, Dynamics), MES, or supplier portals. Events flow in via webhooks, REST, or direct connector — each one anchored to the Hyperledger Fabric ledger.
Once your schema is live and events are flowing, TierraTrace issues a Digital Product Passport for each product or batch. Every passport gets a QR code, a unique identifier, and a cryptographic signature.
Consumers, regulators, and partners scan the QR code. TierraTrace Verify runs the eight-stage pipeline and returns a signed, human-readable result — no app, no account required.
Each module is a distinct capability — they're designed to work together as a single traceability flow, not as standalone tools.
Traceability, passport, verification, and carbon aren't four separate stories — they're one. A supply chain event feeds Traceability. Traceability informs the Passport. The Passport is what Verify checks. Carbon accounting runs alongside every leg of that journey. The result is a single, verifiable source of truth for each product — from raw material to end-of-life.
Need more detail? The platform PRDs that this documentation is based on live in the engineering repo. If you're an enterprise evaluating the platform, the EU DPP Whitepaper and CBAM Playbook are the best starting points for understanding scope and compliance coverage.
