Note: the regulation is still evolving, and so are these data requirements.

The ESPR delegated act for textiles has not been adopted yet, so the final passport data set and the required granularity (model, batch or item) are not fixed.

Everything marked Expected (ESPR) is our current best reading, not a final legal requirement. We will update this article once the delegated act is published.

(1) Goal

Centralise product, material and value-chain data per product, so you can publish a passport today and extend it once the delegated act defines the final data set.

(2) Kick-start minimum: what IT needs to deliver first

Product master: name, product code, product type, finished good vs. component (plus colour and size if the passport sits below style level)
Main material composition per product (fibre and %)
Main (T1) supplier per product, with a contact email. Suppliers are onboarded in Retraced, not via the API.

Everything else is either collected from your suppliers inside Retraced or can be added later.

(3) Features needed

#	Feature	Role	Why it is needed
1	Product Library (Style → Variant → SKU)	Core	The product the passport describes. Holds identifiers and product attributes.
2	Material Composition	Core	Fibre composition and recycled content, a core passport attribute.
3	Network (supplier master data)	Core	The suppliers that products and maps are linked to.
4	Product Mapping	Core	Supplier-declared value chain per product: tiers, facility processes, countries.
5	Digital Product Passport	Core	Publishes the passport from the data above.
6	Certified Materials Management (CMM)	Important	Transaction certificate evidence for recycled or certified material claims.
7	Order Tracing	Supporting	Verifies the declared chain against real POs and collects style-level documents (test reports, care and recyclability information).
8	BOM (components and trims)	Supporting	Component-level structure for trims, linings and packaging.
9	Supply Chain Mapping	Supporting	Network context and supplier onboarding.
10	Questionnaires	Supporting	Facility data (e.g. energy, water) if LCA data turns out to be required.
11	LCA Enablement	Depends on delegated act	Environmental footprint, if ESPR requires it.

(4) Data points per feature

1. Product Library

Endpoint: POST /api/v2/styles/

Data point	Requirement	Public API v2 field	Note
Product name	Mandatory ⚙️	`name`
Product code (ERP / PLM / PIM ID)	Mandatory ⚙️	`codes[]` (codeId + codeValue)	At least one, e.g. ERP_ID, PLM_ID.
Product type	Mandatory ⚙️ (top-level style only)	`styleTypeId`	Retraced taxonomy (GET /api/v2/style-types/) or your own code via constant mappings.
Finished good vs. component	Mandatory ⚙️ (top-level style only)	`isComponent`
Your own product ID	Recommended	`externalId`	Unique across all product levels; can be used instead of the Retraced ID in later calls.
Main supplier (T1)	Mandatory	`mainSupplier`	Needed to send the Product Mapping request. Retraced company ID or your internal company code.
Colour (variant)	Mandatory if the passport is at variant level	`parentId` (style) + `color`
Size (SKU)	Mandatory if the passport is at SKU level	`parentId` (variant) + `dimension`
GTIN / EAN	Expected (ESPR)	`codes[]` (EAN_GTIN_13, UPC_GTIN_12)	Likely basis for the unique product identifier and data carrier.
Product weight	Expected (ESPR)	`weight {value, unit}`	Also an LCA input.
Recyclability information	Expected (ESPR)	`ecoFootPrint`: recyclabilityRate, recyclabilityCanBeSorted, recyclabilityAbsenceDisruptor, recyclabilityCanCollectAtScale, recyclabilityIndustrialScale
Substances of concern	Expected (ESPR)	`ecoFootPrint.hazardousMaterials[]` (idx, name, percentage)	If you send the list, idx, name and percentage are required ⚙️ for each substance.
Claim intentions (e.g. GRS, GOTS)	Mandatory if claims are shown on the passport	`claimIntentions[]`	Links the product to CMM evidence.
Brand	Optional	`brands[]`	Create the values first via POST /api/v2/style-properties/.
Season, collection, department	Optional	`seasons[]`, `collections[]`, `departments[]`	Same as brand.
Other suppliers, vendors	Optional	`suppliers[]`, `vendors[]`
Images	Optional	`imagesFileIds[]`	Upload via POST /api/v2/files/ first.
Description, gender	Optional	`description`, `gender`
Other attributes	Optional	`customProperties`	For attributes without a dedicated field.

2. Material Composition

Endpoints: POST /api/v2/material-headers/, POST /api/v2/material-lines/

Data point	Requirement	Public API v2 field	Note
Composition header name (e.g. Shell fabric)	Mandatory ⚙️	`name`
Product the header belongs to	Mandatory ⚙️	`link.styleId`
Main composition flag	Mandatory ⚙️	`link.isMainMaterial`
Fibre / raw material	Mandatory ⚙️	`rawMaterialId`	From the Retraced raw material catalogue. Mapping your ERP fibre names to it is a typical IT task.
Percentage	Mandatory ⚙️	`percentage`	The lines per header should add up to 100.
Header and product reference on each line	Mandatory ⚙️	`materialHeaderId`, `styleId`
Recycled vs. virgin	Expected (ESPR)	via the catalogue raw material (e.g. recycled polyester)	Needed for recycled content.
Fibre country of origin	Optional	`countriesOfOrigin[]`	Often supplier-provided via Product Mapping.
Fibre weight	Optional	`weights` + `weightUnit`
Blend hierarchy	Optional	`parentId`, `level`, `position`	For blended yarns.
Your own IDs	Recommended	`externalId`

3. Network (supplier master data)

Companies are read-only in the Public API (GET /api/v2/companies/).

Suppliers are onboarded in Retraced (network import, data migration or invitation) and then referenced from products and orders by Retraced company ID or your internal company code.

Data point	Requirement	Public API v2 field	Note
Supplier legal name	Mandatory	— (not in Public API)
Country	Mandatory	—
Address (street, city)	Mandatory	—
Facility process(es) (e.g. Sewing, Weaving)	Mandatory	—	Valid IDs: GET /api/v2/facility-processes/.
Contact person and email	Mandatory	—	Needed to invite the supplier.
Internal company code	Recommended	—	Lets IT reference suppliers by its own code in the API.
Identifiers: OS Hub ID, GLN, DUNS, VAT ID, commercial register number, HIGG ID	Recommended	—	Improve matching to existing profiles and avoid duplicates.
Certificates, audits	Optional	— (readable via GET)	Can be collected via questionnaires.

4. Product Mapping

Not in the Public API. Requests are created in Retraced from products already in the Product Library.

Data point	Requirement	Public API v2 field	Note
Products to map	Mandatory	— (products via POST /api/v2/styles/)
T1 supplier and its facility process	Mandatory	— (mainSupplier on the style helps)
Instructions (expected mapping depth, components to include)	Recommended	—	Communicate the expected mapping depth per request.
Upstream suppliers per tier, their processes and countries	Supplier-provided		No IT data needed.
Components used	Supplier-provided
Resulting supply chain	—	readable via `GET /api/v2/supply-chains/{id}`

5. Digital Product Passport

Data point	Requirement	Public API v2 field	Note
Product with code and composition	Mandatory	from features 1 and 2
Supply chain attached to the product	Mandatory	— (from Product Mapping or Order Tracing)
Public page activation	Mandatory	`isStoryActive` (styles)	Requires a supply chain to be attached.
Passport level (style, variant, SKU, batch)	Mandatory decision		Style → Variant → SKU → Batch is supported. Serialised item-level passports are not available yet.
Unique identifier / data carrier	Expected (ESPR)	see GTIN above
Care, repair and end-of-life information	Expected (ESPR)		Exact format to be confirmed once the delegated act is final.
Environmental footprint	Expected (ESPR)		Only if confirmed; see LCA Enablement.

6. Certified Materials Management (CMM)

Orders come in via the Order Hub (POST /api/v2/orders/); transaction certificate matching happens in Retraced.

Data point	Requirement	Public API v2 field	Note
Order number	Mandatory ⚙️	`orderNumber`	Unique per company and order type.
Buyer	Mandatory ⚙️	`buyerCompanyId`
Supplier	Mandatory ⚙️	`supplierCompanyId`
Order lines: product, quantity, unit	Mandatory ⚙️ (per line, if lines are sent)	`lines[]`: styleId, quantity, unit	Lines are optional on the order itself but needed for CMM.
Claim intention on the product	Mandatory	`claimIntentions[]` (styles)	Defines what needs to be evidenced.
Line weight in kg	Recommended	`lines[].secondaryQuantity` + `secondaryUnit` = KILOGRAM	Makes reconciliation against transaction certificate quantities easier.
Your own order / line IDs	Recommended	`externalId`, `lines[].externalId`, `lines[].orderLineNumber`
Order date, shipment reference	Optional	`orderDate`, `shipmentReference`
Transaction certificate	Supplier-provided	—

7. Order Tracing

Orders are created via the Order Hub (POST /api/v2/orders/) and sent to tracing under an attachment template.

Data point	Requirement	Public API v2 field	Note
Order number	Mandatory ⚙️	`orderNumber`
Buyer	Mandatory ⚙️	`buyerCompanyId`
Supplier (T1)	Mandatory ⚙️	`supplierCompanyId`
Order lines: product, quantity, unit	Mandatory ⚙️ (per line, if lines are sent)	`lines[]`: styleId, quantity, unit	Needed for tracing.
Facility process of buyer / supplier	Recommended	`buyerFacilityProcess`, `supplierFacilityProcess`	IDs from GET /api/v2/facility-processes/ or your own codes.
Required document set	Optional	`tracingAttachmentTemplateId`	Falls back to the company default if not set. For DPP: test reports, care and recyclability documents.
Order and delivery dates	Optional	`orderDate`, `agreedDeliveryDate`, `expectedDeliveryDate`, `deliveryDate`
Tags, order sub-type	Optional	`tags`, `orderSubType`	Orders have no season field in the Public API; use tags instead.
Shipment reference	Optional	`shipmentReference`
Receiver, vendor, factory	Optional	`receiverCompanyId`, `vendorCompanyId`, `factory`
Responsible persons	Optional	`internalResponsiblePersons[]`
Your own order / line IDs	Recommended	`externalId`, `lines[].externalId`
Upstream orders, documents, transformations	Supplier-provided	—

8. BOM (components and trims)

Endpoints: POST /api/v2/bom-headers/, POST /api/v2/bom-lines/

Data point	Requirement	Public API v2 field	Note
Component as its own product	Mandatory (for BOM)	style with `isComponent = true`
BOM header name	Mandatory ⚙️	`name`
Product the BOM belongs to	Mandatory ⚙️	`link.styleId`
Main BOM flag	Optional	`link.isMainBom`
BOM header on each line	Mandatory ⚙️	`bomHeaderId`
Parent product	Mandatory ⚙️	`entity.styleId`
Component	Mandatory ⚙️	`component.styleId`
Quantity and unit	Optional	`quantity`, `quantityUnit`
Weight	Optional	`weight`, `weightUnit`
Country of origin	Optional	`countryOfOrigin`
Placement (e.g. Collar)	Optional	`placementId`	Via POST /api/v2/bom-placements/.
Main component flag	Optional	`isMainComponent`

9. Supply Chain Mapping

Not in the Public API. Same inputs as Network (feature 3). Suppliers disclose their own suppliers and facility processes in Retraced.

10. Questionnaires

Not in the Public API. No IT data needed beyond the Network contacts. The content (facility energy, water, waste, ESG practices) is defined in the questionnaire template and answered by suppliers.

11. LCA Enablement

Reuses weight, composition and process countries from features 1, 2 and 4.

Data requirements: Digital Product Passport (DPP)