Maintenance
Part of Fashion supply chain traceability: claims, mapping, events, and evidence
A fashion supply chain traceability checklist built for real conditions
Fashion supply chain traceability checklist for scope, identifiers, sites, events, quantities, evidence, custody, permissions, exceptions, tests, and disclosure.
What to take away
- Approve a traceability claim only when product, event, quantity, and evidence records align.
- Keep company, facility, product, lot, material, and transaction identifiers separate.
- Treat gaps, substitutions, impossible yields, and expired documents as exceptions.
- Restrict sensitive data while preserving enough information for verification and remedy.
- Test recall, correction, and system portability before calling the process ready.
Use this checklist for one defined product, material claim, or risk decision. Mark each item Pass, Review, Stop, or Not applicable. Add the record, owner, date, and next action. A general supply-chain map should not receive a pass for a product-level claim. Object hierarchy and custody terms come from the traceability reference guide.
1. Question and scope
- Product model, revision, SKU, color, lot, and period are defined.
- Claim or decision is written in one testable sentence.
- Included materials, trims, packaging, tiers, processes, and countries are listed.
- Excluded stages are disclosed and justified.
- Chain-of-custody model is named.
- Required evidence and acceptance rules were set before review.
- Legal, customer, certification, and internal requirements are separated.
Stop: the team cannot identify the object or claim being traced.
2. Actor and site identity
- Legal entity and trading name have separate fields.
- Each production site has a stable identifier and address.
- Agents and intermediaries are recorded without replacing factories.
- Approved process scope is listed for each site.
- Subcontractors and homework arrangements are addressed.
- Active, inactive, suspended, and unverified statuses are controlled.
- Similar supplier names have been deduplicated.
3. Product and material identifiers
Codes work only when every party shares their meaning. UNECE's reference guide to textile and leather identifiers describes code lists and identification schemes as building blocks for standardized, machine-readable data exchange. Use current identifier-owner rules and preserve crosswalks when suppliers use their own codes.
- Product, SKU, lot, batch, roll, and serialized unit levels are distinguished.
- Bill-of-material revision is linked to the production order.
- Supplier codes map to controlled internal or recognized identifiers.
- IDs are unique, persistent, and not reassigned.
- Labels or tags are attached to the correct physical object.
- Split, merge, blend, rework, and substitution events retain parent-child links.
Review: a valid identifier resolves to the wrong granularity.
4. Event data
For every material movement or transformation, check:
- what object entered and left
- event type and process
- facility and responsible actor
- start, completion, shipment, and receipt dates as needed
- quantity, unit, conversion, and loss
- order, invoice, shipping, or receipt reference
- certificate, test, declaration, or inspection evidence
- system timestamp and submitting user
Stop: finished output appears before its input or at an unapproved site without a resolved explanation. Event capture that avoids this comes from Step 6 of the traceability build method.
5. Volume reconciliation
Volume reconciliation
- Opening eligible stock
- Verified eligible receipts
- Documented process loss
- Eligible output transferred
- Closing eligible stock
- Difference and explanation
- Units and conversion factors are controlled.
- Yield tolerances match the process and material.
- Claim volume does not exceed eligible entitlement.
- Duplicate invoices, certificates, and transaction numbers are flagged.
- Allocation period and site boundary match the custody rules.
- Waste, samples, seconds, and rework are included.
6. Document and record controls
- Document subject, issuer, issue date, validity, and scope are captured.
- Files link to the related event or object.
- Original and corrected versions remain in the audit history.
- Record retention matches law, contracts, claims, and dispute needs.
- Access, export, backup, and deletion rules are documented.
- Expiry and renewal alerts have owners.
For covered US textile records, 16 CFR 303.39 requires records that establish a traceable line of continuity from raw material through processing to finished product and specifies a three-year retention period. That narrow legal requirement should not be presented as a complete sustainability traceability standard or applied outside its scope without review.
7. Claim evidence
- Every public statement has a named subject and boundary.
- Fiber, origin, recycled, organic, biobased, labor, and environmental claims use separate evidence fields.
- Certificate scope matches the site, product, process, and dates.
- Transaction evidence links eligible input to the relevant order.
- Sampling and independent verification limits are stated.
- The customer-facing wording matches the custody model.
- Missing tiers and unverified fields are visible.
Stop: an accounting model is described as identity-preserved physical content. Product-facing wording then goes through the label approval checklist.
8. Data quality and exceptions
- Required fields reject blanks or invalid formats.
- Dates follow a single format and logical order.
- Units and country, process, and material codes use controlled values.
- Outliers enter an exception queue.
- Supplier corrections need a reason and approval.
- Repeated issues change supplier controls or risk rating.
- Unresolved gaps block only the affected claim or product scope, not unrelated records.
9. Privacy, security, and fairness
- Personal data collection has a defined need and lawful basis.
- Worker names and grievance details have strict access controls.
- Supplier prices and formulas are not exposed through public pages.
- Role permissions follow least-access principles.
- Data sharing, correction, and appeal terms are clear to suppliers.
- Smaller suppliers receive proportionate formats and support.
- Security incidents have response and notification procedures.
10. Operational tests
- One upstream batch can be traced to affected finished goods.
- One finished item can be traced back through the claimed tiers.
- A deliberate duplicate or impossible quantity triggers a flag.
- A false facility record can be corrected without erasing history.
- A withdrawn certificate stops affected claims.
- Records can be exported in a usable form.
- Backup restoration and vendor-exit plans are tested.
11. Disclosure and release
Disclosure and release
| Status | Meaning | Action |
|---|---|---|
| Pass | Scope, quantities, events, and evidence align | Approve dated claim |
| Review | Limited gap has an owner and no false public implication | Hold or qualify affected field |
| Stop | Identity, custody, volume, site, or evidence conflict | Do not publish claim |
| Not applicable | Reason is recorded | Retain decision |
Consumer information should state the product identifier, date, covered tiers, custody model, verification status, and important limits. An attractive map without these facts can be less informative than a short, precise statement. Buyers reading such disclosures can log them in the personal purchase checklist.
Common questions
Must every field have third-party verification?
No. Set assurance by risk, claim, legal duty, and consequence. Clearly distinguish verified, reviewed, supplier-declared, and unknown data.
Can one missing tier invalidate the whole system?
It invalidates claims that require that tier. Other supported fields may remain usable if the gap is disclosed and separated.
How should substitutions be handled?
Record the original and substitute material, approval, date, lot, supplier, reason, and all affected tests, labels, certificates, and claims.
What is the most important drill?
Run both directions: material batch to finished products and finished product back to claimed sources. Measure unresolved records and time.
When should the checklist reopen?
Reopen after changes to product, material, supplier, facility, process, custody model, claim, standard, software, law, or data-sharing arrangement.
