How to Build Textile Lot Traceability: From Approved Sample to Roll, Test Report & Transaction Certificate
Share
Textile lot traceability works when every physical unit and every document can be linked through stable identifiers—from the approved specification and sample to production lots, individual rolls, test specimens, packing records and the final shipment. A folder of unrelated certificates is not a traceability system. Buyers need an evidence chain that can answer: which material was used, where it was processed, which rolls were shipped, which sample was tested and which claim document applies to that transaction?
This guide gives bedding and home-textile buyers a practical record structure. It also separates ordinary production traceability from certified chain-of-custody evidence: the two can support each other, but they are not interchangeable.
What is the minimum traceable unit for fabric procurement?
Start with a clearly defined production lot and keep roll-level identifiers inside it. A product SKU identifies a commercial style; a specification revision identifies the approved requirements; a lot identifies a production grouping; and a roll ID identifies one physical unit. None of those should be substituted for another.
The buyer and Nantong Oulai should agree what events create a new lot—for example, a change in yarn lot, dye or print batch, finishing run, machine setting, specification revision or approved material input. The rule should match the project rather than being invented after a problem appears.
Which records should connect from sample to shipment?
| Stage | Identifier to preserve | Minimum linkage | Buyer evidence |
|---|---|---|---|
| RFQ and order | Product code, PO and specification revision | Commercial terms to the exact approved technical file | PO, signed specification and change log |
| Approval sample | Lab dip, strike-off or golden-sample ID | Sample to revision, colour/pattern and approval date | Approval record and retained counterpart |
| Material input | Yarn/fibre/material lot | Input lot to supplier document and production lot | Input record; claim documents when applicable |
| Production | Greige, dye/print and finishing batch | Process batch to machine/date/settings and operator record | Lot genealogy or batch summary |
| Fabric rolls | Unique roll ID | Roll to production lot, measured length, width, weight and inspection result | Roll list and inspection map |
| Testing | Sealed sample ID and report number | Specimen to selected roll(s), lot, sampling date and method | Sampling record and complete report |
| Packing and shipment | Package/pallet and shipment ID | Packed roll IDs to packing list, invoice and shipment | Final packing list and shipping documents |
| Certified claim, if ordered | Scope and transaction-document references | Certified entity and claimed input to the relevant sale/shipment | Applicable scope and transaction evidence |
How should approved samples and specification revisions be controlled?
Give every approved sample a unique ID and link it to the current specification revision, product code, colour or pattern, approval date and approver. Retain a protected counterpart where practical. If any critical field changes, issue a revision and record whether a new sample or new testing is required.
This is broader than keeping a “golden sample.” Our sample-to-bulk change-control guide explains sample governance; traceability adds the downstream links from that approved state to actual rolls and shipment records.
How should roll IDs connect to inspection and laboratory testing?
A roll list should identify the lot, roll number, measured quantity and relevant inspection data. When a laboratory sample is cut, record the source roll, position or sampling basis, date, sampler and seal or sample ID. The laboratory report should repeat enough of that identity to prevent a result from being detached from the material it represents.
ISO/IEC 17025:2017 sets requirements for competent, impartial and consistent laboratory operation, but laboratory accreditation does not determine whether the tested sample represents every roll in a shipment. The procurement plan must define sampling and applicability. Use our textile test-report verification checklist to review laboratory scope, sample identity, method and result; use the pre-shipment roll-inspection guide for physical inspection records.
Is a scope certificate proof that a specific order is certified?
No. A scope certificate shows that an organization and listed activities or product categories fall within a certification scope for a stated period. It does not, by itself, prove that every product, lot or delivery from that organization is certified.
Textile Exchange describes its Content Claim Standard as a chain-of-custody framework that uses scope and transaction certificates to create an independently verified audit trail. For an OCS or related content claim, buyers should check current scope and eligibility, then obtain the transaction or other supporting documentation required for the specific claimed order.
The merchant-provided portfolio illustrates this distinction:
- Jiangsu Jingyiyang Textile Co., Ltd. holds IDFL-issued GOTS Version 7.0 Scope Certificate SC-029367-0, GOTS License GOTS-25372, issued 4 August 2026 and valid to 3 August 2027. Its scope includes greige yarns and listed trading/warehousing activities. The certificate itself explicitly does not prove that delivered goods are GOTS certified; order evidence requires the applicable valid Transaction Certificate.
- Qingdao Hengtai Huasheng Supply chain Co., LTD holds GOTS and OCS scope certificates valid to 30 December 2026. The OCS certificate carries TE-ID TE-00328197 and includes OCS 100 and OCS Blended categories. These documents are scope evidence, not automatic proof for every delivered lot.
Therefore, neither FAB-0141 Heavyweight Brushed Cotton Jacquard nor FAB-0701 Polyester–Lyocell Blend Sheet Fabric should be described as GOTS- or OCS-certified unless the exact product/order eligibility and required transaction evidence are verified.
How is a test report different from certification evidence?
A test report supports results for the identified sample under the reported methods and conditions. It is not automatically a product certificate, supply-chain certificate or guarantee for future production.
For example, SGS Test Report SL42604345449801TX dated 24 August 2026 identifies a white woven cotton sample submitted for Nantong Oulai Trading Co., Ltd. Its reported results apply only to that tested sample. Without an explicit, documented link, the report must not be generalized to FAB-0141, FAB-0701, another lot or a future order. Traceability is the mechanism that establishes—and limits—that link.
How can live catalog examples be mapped into a traceability plan?
Brushed cotton jacquard
The live FAB-0141 listing states 100% cotton, jacquard construction, a brushed heavyweight surface and winter-bedding applications. A useful lot record should link yarn/material input, jacquard production, brushing/finishing batch, approved surface sample, roll IDs and any dimensional-change, appearance or thermal-testing samples. If a certification claim is ordered, its chain-of-custody documents must point to the same material flow.
Polyester–lyocell blend sheet fabric
The live FAB-0701 listing identifies a polyester–lyocell blend, but does not publish exact percentages. Before labelling or bulk approval, buyers should freeze the agreed blend ratio and connect the approved composition document, yarn/input lots, print or dye batch, finishing batch, roll list and test specimens. A change in blend, print, colour or technical specification should trigger a documented revision and an agreed reapproval decision.
What should buyers request in a traceability pack?
- PO, product code and signed specification revision
- Approved sample or lab-dip/strike-off identifiers
- Lot-definition rule and production-lot number
- Input material and process-batch references
- Complete roll list with unique roll IDs and quantities
- Inspection records linked to rolls or lots
- Sampling record connecting test specimens to source material
- Full laboratory reports, not cropped result pages
- Packing list mapping rolls to packages and shipment
- Change log, concession and corrective-action records where relevant
- For certified claims: verified scope status plus applicable transaction/supporting evidence
- Retention period, file owner and access method
GS1’s Global Traceability Standard offers a cross-industry model for designing traceability systems around consistent identification and traceability events. A textile buyer does not need to adopt a particular barcode system to apply the core discipline: identify the object, record the event and preserve the links.
Frequently asked questions
Is a SKU the same as a lot number?
No. A SKU identifies a product style or commercial item; a lot number identifies a production grouping. Multiple lots may share one SKU.
Can one test report cover every roll?
Only if the sampling plan, lot definition and contractual acceptance rule support that conclusion. The report itself proves only what was tested and reported.
Is a scope certificate enough for a GOTS or OCS shipment claim?
No. Verify the certified entity’s current scope and product eligibility, then obtain the applicable transaction or supporting documentation for the claimed order.
Must a textile supplier use GS1 barcodes?
Not necessarily. The essential requirement is stable, unique identification and preserved links. The parties can agree labels, digital records or standards-based identifiers appropriate to the supply chain.
How long should traceability records be retained?
Set a contract-specific period that considers legal, customer, certification, warranty and complaint needs. Record ownership and retrieval responsibility should be explicit.
Authoritative Sources
- GS1 Global Traceability Standard
- ISO/IEC 17025:2017 — General requirements for the competence of testing and calibration laboratories
- Textile Exchange — Content Claim Standard
- Textile Exchange — How organic cotton certification works
- Global Standards — GOTS: how the system works
- GOTS Version 7.0 — official standard document