Under the Uyghur Forced Labor Prevention Act (UFLPA), goods made wholly or partly in Xinjiang, or by entities on the UFLPA Entity List, are presumed to be made with forced labour. To rebut that presumption, the importer must document the supply chain down to raw material, tied to the actual shipment. In textiles, cotton is the main high-risk input, so the evidence is order-level: real purchase orders and the documents that tie each shipment to its production chain.

(1) Goal

For US-bound products, show the full chain down to raw material per purchase order, with supporting documents at each tier, and screen every party against restricted-party and forced-labour risk lists.

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

Supplier master for T1: legal name, country, address, facility process, contact email (onboarded in Retraced, not via the API)
Purchase orders for US-bound products: order number, buyer, supplier, order lines (product, quantity, unit)
Product master with main material composition, so cotton-containing products can be prioritised

(3) Features needed

#	Feature	Role	Why it is needed
1	Network (supplier master data)	Core	Every party in the chain; the basis for screening and mapping.
2	Supply Chain Mapping	Core	Extends visibility beyond T1 to the subcontractors where forced-labour risk usually sits.
3	Order Tracing	Core	Verifies actual production per purchase order. Order-level documents are what is used to rebut the presumption.
4	Entity Screening	Core	Flags suppliers and subcontractors matching restricted-party or forced-labour lists.
5	Product Library + Material Composition	Important	Identifies which products contain high-risk fibres and need full raw-material traceability.
6	Questionnaires	Supporting	Facility-level information: legal, labour conditions, recruitment practices, audits.
7	Risk Management	Supporting	Scores suppliers on labour-related factors to prioritise follow-up.
8	Product Mapping	Supporting	Declared chain per product, useful before purchase orders exist.

(4) Data points per feature

1. Network (supplier master data)

Companies are read-only in the Public API (GET /api/v2/companies/). Suppliers are onboarded in Retraced and then referenced by Retraced company ID or your internal company code.

Data point	Requirement	Note
Supplier legal name	Mandatory	As registered; this matters for screening.
Country	Mandatory
Full address (street, city)	Mandatory	Region-level location (e.g. Xinjiang) is a key risk signal.
Facility process(es)	Mandatory	e.g. Ginning, Spinning, Weaving, Sewing. Valid IDs: GET /api/v2/facility-processes/.
Contact person and email	Mandatory	Needed to invite suppliers into mapping, tracing and questionnaires.
Internal company code	Recommended	Lets IT reference suppliers by its own code on orders.
Identifiers: DUNS, VAT ID, commercial register number, OS Hub ID, GLN	Recommended	Improve screening match accuracy and avoid duplicates.
Certificates, audits	Optional	Readable via GET. Can be collected via questionnaires.

2. Supply Chain Mapping

Not in the Public API.

Data point	Requirement	Note
T1 supplier list with contact emails	Mandatory	From Network. This alone is enough to start a mapping.
Known lower-tier suppliers (e.g. nominated mills, spinners)	Optional	Speeds up the mapping if you already know them.
Upstream suppliers and their processes	Supplier-provided	Suppliers disclose their own suppliers in Retraced.

3. 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`	Unique per company and order type.
Buyer	Mandatory ⚙️	`buyerCompanyId`
Supplier (T1)	Mandatory ⚙️	`supplierCompanyId`	Retraced company ID or your internal company code.
Order lines: product, quantity, unit	Mandatory ⚙️ (per line, if lines are sent)	`lines[]`: styleId, quantity, unit	Needed for tracing. The product must carry its composition (feature 5).
Facility process of buyer / supplier	Recommended	`buyerFacilityProcess`, `supplierFacilityProcess`	IDs from GET /api/v2/facility-processes/ or your own codes.
Required document set	Recommended	`tracingAttachmentTemplateId`	Falls back to the company default if not set. For UFLPA, use a template with commercial invoice, packing list, transport documents, production records and raw-material purchase records per tier.
Shipment reference	Recommended	`shipmentReference`	Ties the trace to the US import entry.
Line weight in kg	Recommended	`lines[].secondaryQuantity` + `secondaryUnit` = KILOGRAM	Supports quantity plausibility checks across tiers.
Order, shipping and delivery dates	Recommended	`orderDate`, `expectedShippingDate`, `shippingDate`, `agreedDeliveryDate`, `actualDeliveryDate`	Supports timeline plausibility checks.
Your own order / line IDs	Recommended	`externalId`, `lines[].externalId`, `lines[].orderLineNumber`
Receiver, vendor, factory	Optional	`receiverCompanyId`, `vendorCompanyId`, `factory`	Useful where an agent or trading company sits between you and the factory.
Tags	Optional	`tags`	e.g. tag US-bound orders.
Counterparty order reference	Optional	`counterpartyOrderNumberRef`
Responsible persons	Optional	`internalResponsiblePersons[]`
Upstream orders, documents, transformations	Supplier-provided	—

4. Entity Screening

Not in the Public API. Uses Network data.

Data point	Requirement	Note
Legal name, country, address	Mandatory	From Network.
Registration identifiers	Recommended	Fewer false positives and false negatives.
Lower-tier parties	Supplier-provided	Become screenable once discovered via mapping or tracing.

5. Product Library + Material Composition

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

Data point	Requirement	Public API v2 field	Note
Product name	Mandatory ⚙️	`name`
Product code	Mandatory ⚙️	`codes[]` (codeId + codeValue)
Product type	Mandatory ⚙️ (top-level style only)	`styleTypeId`
Finished good vs. component	Mandatory ⚙️ (top-level style only)	`isComponent`
Your own product ID	Recommended	`externalId`	Can then be used as styleId on order lines.
Composition header (name, product, main flag)	Mandatory ⚙️	`name`, `link.styleId`, `link.isMainMaterial`
Fibre and percentage	Mandatory ⚙️	`rawMaterialId`, `percentage` (+ materialHeaderId, styleId)	Identifies cotton-containing products.
Fibre country of origin	Optional	`countriesOfOrigin[]`	Usually supplier-provided and evidenced via tracing.
Main supplier	Optional	`mainSupplier`

6. Questionnaires

Not in the Public API. No IT data needed beyond the Network contacts. The content (legal information, labour conditions, recruitment practices, audits) is defined in the questionnaire template.

7. Risk Management