This collection helps your IT and data team run a data availability and API readiness check before you start with Retraced. There is one article per use case, and each answers two questions:
Which Retraced features does this use case need? Each feature is marked Core, Important or Supporting.
For each feature, which data points are required and which are optional?
The data points refer to Retraced Public API v2 fields, so your IT team can map them against your ERP, PLM or PIM. The feature selection is based on our experience implementing these use cases with brands.
(1) How to read the requirement column
Label | Meaning |
Mandatory ⚙️ | Required by the Retraced Public API v2. A request without it is rejected. |
Mandatory | Not enforced by the API (or not part of the API), but the use case does not work without it. |
Recommended | Not blocking, but strongly improves results, for example matching, evidence quality or reconciliation. |
Expected (regulation) | Likely to be required once the regulation or delegated act is final. Collect it if available. Not final. |
Optional | Nice to have. |
Supplier-provided | Not needed from your IT team. Collected from your suppliers inside Retraced. |
(2) What the Public API v2 covers
Your IT team can write the following through the Public API v2: products (styles, variants, SKUs), style properties (brands, seasons, collections, departments), material compositions, BOMs, orders (Order Hub, including sending orders to tracing via an attachment template) and files.
Companies, certificates, audits, CAPA, supply chains and facility processes are read-only in the API.
Everything else (supplier onboarding, Product Mapping, Supply Chain Mapping, Certified Materials Management, Questionnaires, Entity Screening, Risk Management) is set up in the Retraced platform or provided by your suppliers.
In the use case articles, these rows show "— (not in Public API)".
(3) Tip for IT: use your own IDs
Every object you write through the API accepts an optional externalId (your own ID). Wherever the API expects a Retraced ID, you can then use your own ID instead. Companies, product types and facility processes can also be referenced by your own codes via /api/v2/constant-mappings or internal company codes.
(4) Use cases
Digital Product Passport (DPP): ESPR readiness
UFLPA: US forced labour prevention
EUFLR: EU Forced Labour Regulation