Plant-Based Fibres
Overview
Plant-based fibres constitute one of the most diverse and widely used categories of textile materials. This includes fibres such as cotton, flax, hemp, jute, ramie, kapok, abaca, and many others derived from agricultural crops. Each material has distinct cultivation practices, processing pathways, and regional variations.
This section provides generalized guidance for representing plant-derived fibre supply chains within the United Nations Transparency Protocol (UNTP). The examples focus primarily on commonly traded fibres such as cotton, flax, and hemp, but the same event structures and modeling principles are applicable across a broader range of plant-based inputs.
Because agricultural systems and processing methods vary greatly, this specification does not define an exhaustive model for all possible plant fibres. Instead, it establishes a flexible framework of event types and identifier relationships that can be extended as new use cases emerge. The structure described here—spanning from cultivation and harvest through to garment manufacturing—offers a foundation for interoperability and transparent data exchange between implementations.
Event Type Schemas
This guidance references specific UNTTP event type schemas that implement the UNTP Digital Traceability Event (DTE) profile for textiles. For authoritative technical details, schema definitions, and current versions, refer to the Traceability Events specification page.
The event types covered in this guidance include:
- Cotton Ginning Event - Primary processing of cotton
- Spinning Event - Transformation of fibre to yarn
- Weaving Event - Formation of woven fabric
- Knitting Event - Formation of knitted fabric
- Non-Woven Formation Event - Formation of non-woven fabric
- Dyeing Event - Dyeing and finishing operations
All event schemas follow the UNTP 0.6.0 specification. Schema files are available in the /schema/ directory and are documented in the Traceability Events specification.
This documentation will evolve over time as:
- Additional plant-based materials are incorporated through practical implementations;
- Event type definitions are refined through community feedback and pilot testing; and
- Formalization of specific event profiles occurs by consensus within the UNTP community.
The objective is to ensure that each new fibre type or processing pathway can be modeled using consistent event semantics and identifier principles, maintaining alignment with UNTP’s overarching design for decentralized and verifiable traceability.
By following these patterns, implementers can model diverse plant-based supply chains in a harmonized manner, enabling transparency, comparability, and progressive standardization as consensus builds across industry stakeholders.
Cultivation and Harvest
Description
The cultivation and harvest stage represents the first appearance of plant-based material (cotton, flax, hemp) in the traceability system. It marks when the material transitions from being part of the environment to an identifiable object within the supply chain.
Justification
This process initiates traceability for plant-based fibres and anchors all downstream provenance and certification claims. It records the point of origin for ESG and sustainability data such as farm identity, production practices, and certifications.
Recommended Pattern
| Element | Description |
|---|---|
| Primary Event Type | ObjectEvent |
| Business Step | commissioning or add |
| Disposition | active |
| Purpose | Record the introduction of harvested raw material into the traceable supply chain. |
| Identifier Scheme | Any identity scheme operator; may represent a farm, field, or plot depending on claim granularity. |
Inputs & Outputs
| Role | Entity | Description | Notes |
|---|---|---|---|
| Input(s) | — | No prior traceable input; the material is entering traceability. | Optionally reference a pre-harvest CropLot or Field entity if modeled. |
| Output(s) | Harvested Material Lot | Raw cotton, flax, or hemp output from harvest. | Identified by lot, field, or season identifier; includes date, quantity, and location data. |
Summary
In most implementations, harvest is modeled as an ObjectEvent of type add, as it signifies the point at which the material is recognized in the supply chain. This approach maintains compatibility with other UNTP domains (e.g., agriculture, food, fisheries), where similar "entry" events mark the creation of traceable goods.
Identifier granularity should match the evidence required for downstream claims:
- Farm-level ID — appropriate for generic origin claims.
- Field-level ID — supports verification of certified plots.
- Plot or Season-level ID — supports ESG metrics such as water use or soil management per growing cycle.
Metadata such as harvest date, quantity, and credential links (e.g., organic or regenerative certification) should accompany the event.
Primary Processing (Ginning / Scutching)
Description
Primary processing converts raw harvested material into usable fibre. For cotton, this is the ginning process that separates lint from seed; for flax and hemp, analogous steps include retting and scutching to extract fibres from stalks. This stage creates the first standardized fibre units (e.g., bales, fibre bundles) that enter commercial trade and supply chain movement.
Justification
This process defines a transformation from raw agricultural material to traceable fibre units — the first form suitable for textile manufacturing. Recording it enables accurate material balance, supports segregation of material types, and provides the reference point for all subsequent manufacturing and blending events.
Recommended Pattern
| Element | Description |
|---|---|
| Primary Event Type | TransformationEvent |
| Business Step | processing |
| Disposition | active |
| Purpose | Capture the transformation of harvested raw material into standardized fibre units for trade or transport. |
| Identifier Scheme | Any interoperable identity scheme; each output fibre unit (e.g., bale, bundle) receives its own identifier. |
| Event Schema | For cotton ginning, use the Cotton Ginning Event schema (unttp-cotton-ginning-dte.0.0.1.json) with processType: UNTTP_COTTON_GINNING. See the Traceability Events specification for the authoritative schema definition. |
Input and Outputs
| Role | Entity | Description | Notes |
|---|---|---|---|
| Input(s) | Harvested Material Lot | Raw seed cotton, flax straw, or hemp stalks entering processing. | May aggregate material from multiple farms or plots. |
| Output(s) | Fibre Units | Cotton lint bales, flax fibres, or hemp fibre bundles produced from the input lot(s). | Each output receives its own identifier (lot, bale, or fibre bundle ID). By-products (e.g., cottonseed) may also be declared as secondary outputs. |
Summary
Primary processing is modeled as a TransformationEvent, as it represents a clear conversion of material form — from harvested plant matter to traceable fibre units.
The granularity of output identification determines the level of traceability and claim precision available downstream:
- Batch-level identifiers permit origin-level claims (e.g., “made with cotton from verified farms”).
- Unit-level identifiers (e.g., per bale or fibre lot) enable more granular blending and content verification in spinning.
This event establishes the first linkage between agricultural sources and manufactured materials, forming a critical node in the textile transparency chain. Subsequent logistics and manufacturing events reference these fibre identifiers to maintain continuity of material origin throughout the supply network.
Aggregation and Shipping of Fibre Units
Description
After primary processing, fibre units such as cotton bales or flax bundles are graded, aggregated, and prepared for shipment to downstream processors (typically spinning mills).
This stage records the physical handover of traceable material between organizations and establishes continuity of custody within the traceability graph.
Justification
Aggregation and shipping events provide the connective tissue between transformation stages. They verify that each fibre unit maintains its identity as it moves through logistics networks and prevent breaks in traceability. These events ensure that downstream actors can retrieve a complete lineage for any fibre unit they receive, supporting both compliance and origin verification.
Recommended Pattern
| Element | Description |
|---|---|
| Primary Event Type | AggregationEvent and ObjectEvent |
| Business Step | packing, shipping, and receiving |
| Disposition | in_transit (during shipment), active (upon receipt) |
| Purpose | Document the grouping of individual fibre units for transport and the subsequent transfer between facilities. |
| Identifier Scheme | Any interoperable identity scheme; each fibre unit and aggregated package (e.g., pallet, container) receives an identifier. |
Inputs and Outputs
| Role | Entity | Description | Notes |
|---|---|---|---|
| Input(s) | Fibre Units | Cotton bales, flax or hemp bundles prepared for shipping. | Each identified from the preceding processing event. |
| Output(s) | Aggregated Package or Shipment | A collection of fibre units grouped under a single logistics or transport identifier. | The aggregation may represent a pallet, container, or shipping batch, and is later disaggregated at the destination. |
Summary
Aggregation and shipping are modeled through a combination of AggregationEvent and ObjectEvent pairs:
- The
AggregationEventrecords the grouping of fibre units into a shipment structure. - The
ObjectEvent(with bizStep of shipping and receiving) records transfer of custody between facilities.
These events together maintain the chain of custody and link traceable materials to logistics records. The level of identifier granularity — for example, per bale versus per shipment — defines how precisely downstream systems can attribute origin or sustainability claims.
High-resolution identification allows a spinning mill to trace individual bales back to their specific agricultural sources, while coarse-grained aggregation supports broader batch-level traceability for standard market transactions.
This stage completes the first inter-organizational linkage in the textile supply chain, ensuring that traceability is continuous from farm through to the manufacturing network.
Spinning (Fibre to Yarn)
Description
At the spinning stage, fibre units are transformed into yarn through carding, combing, and twisting processes. This is the first step where materials from multiple sources may be intentionally blended to achieve desired fibre properties. The resulting yarn lots form the foundation for fabric production and downstream textile formation.
Justification
Spinning represents a material transformation that introduces new identifiers and, potentially, material aggregation. Recording this process is essential to maintain traceability where multiple input fibres (e.g., from different farms or regions) are blended. It allows for accurate content attribution, supports origin traceability across mixed inputs, and ensures that any subsequent sustainability claims reflect the composition of the spun yarn.
Recommended Pattern
| Element | Description |
|---|---|
| Primary Event Type | TransformationEvent |
| Business Step | processing |
| Disposition | active |
| Purpose | Record the conversion of fibre units (e.g., bales, bundles) into yarn lots or cones. |
| Identifier Scheme | Any interoperable identity scheme; yarn lots, spools, or cones receive new identifiers representing outputs of the transformation. |
| Event Schema | Use the Spinning Event schema (unttp-spinning.0.0.1.json) with processType: UNTTP_SPINNING_EVENT. See the Traceability Events specification for the authoritative schema definition. |
Inputs and Outputs
| Role | Entity | Description | Notes |
|---|---|---|---|
| Input(s) | Fibre Units | Cotton bales, flax fibres, or hemp fibres serving as feedstock for spinning. | May include fibres from multiple origins; blending ratios can be recorded if relevant. |
| Output(s) | Yarn Lots | Spun yarn represented as lots, cones, or spools. | Each yarn lot receives a new identifier. Additional data such as blend composition, weight, and count may be included. |
Summary
Spinning is modeled as a TransformationEvent because it converts fibre into a distinct material form with new identifiers and properties.
This stage often combines multiple input sources — enabling the traceability graph to express many-to-one relationships, linking each yarn lot to its contributing fibre units.
Granularity in identification directly influences the precision of downstream claims:
- Per-lot identifiers support batch-level statements such as “contains 100% traceable cotton.”
- Per-cone identifiers support highly granular blending and automated composition tracking.
By documenting the spinning transformation, UNTP ensures that data consumers (e.g., brands or auditors) can trace the composition of any yarn lot back to verified fibre sources and, by extension, to the originating agricultural entities.
This event forms the foundation for fabric manufacturing traceability, carrying forward both origin and material integrity within the textile chain.
Fabric Formation (Weaving / Knitting)
Description
The fabric formation stage transforms yarn into woven or knitted fabric.
It marks the transition from intermediate textile input to finished material ready for finishing and garment production.
The process can involve multiple yarn types or colours, and may include preparatory steps such as warping, sizing, or circular knitting.
Justification
This stage represents a new material form — fabric — and introduces new identifiers for the rolls or bolts created.
Recording the transformation ensures that each fabric lot can be traced back to its source yarn lots (and thereby to fibre origin).
Capturing this stage maintains continuity across the manufacturing chain and provides a reference for calculating blend composition or verifying origin-linked claims.
Recommended Pattern
| Element | Description |
|---|---|
| Primary Event Type | TransformationEvent |
| Business Step | processing |
| Disposition | active |
| Purpose | Record the conversion of yarn lots into fabric rolls or batches. |
| Identifier Scheme | Any interoperable identity scheme; each roll, bolt, or batch of fabric receives a new identifier representing the output of transformation. |
| Event Schema | For weaving, use the Weaving Event schema (unttp-weaving-dte.0.0.1.json) with processType: UNTTP_WEAVING_EVENT. For knitting, use the Knitting Event schema (unttp-knitting-dte.0.0.1.json) with processType: UNTTP_KNITTING_EVENT. For non-woven formation, use the Non-Woven Formation Event schema (unttp-non-woven-formation-dte.0.0.1.json) with processType: UNTTP_NON_WOVEN_FORMATION. See the Traceability Events specification for authoritative schema definitions. |
Inputs and Outputs
| Role | Entity | Description | Notes |
|---|---|---|---|
| Input(s) | Yarn Lots | Spun yarn, potentially blended from multiple fibre origins. | Inputs may include multiple yarn identifiers or colours. |
| Output(s) | Fabric Rolls / Batches | Fabric produced by weaving or knitting. | Each roll or batch receives its own identifier; metadata may include fabric type, width, weight, or pattern. |
Summary
Fabric formation is modeled as a TransformationEvent because it changes the material structure and introduces a new traceable object type: fabric.
This stage consolidates information from the spinning stage and passes forward the traceable identifiers representing the fabric lots.
Granularity in output identification governs the scope of later claims:
- Batch-level identifiers enable declarations such as “fabric produced from traceable yarn lots.”
- Roll-level identifiers allow precise linkage to specific yarn inputs or processing lines.
By capturing this step, the traceability graph remains unbroken from fibre through to finished fabric, allowing downstream systems to verify origin, content composition, and process continuity at any point in the textile supply chain.
Dyeing and Finishing
Description
The dyeing and finishing stage involves processes that alter the appearance, performance, or handle of fabric.
Typical operations include dyeing, printing, bleaching, washing, and mechanical or chemical finishing (e.g., coating, calendaring).
This stage does not change the fabric’s identity as a textile object, but it does change its state and attributes relevant to quality and compliance.
Justification
Finishing processes are critical to transparency because they introduce chemicals and treatments with environmental and social implications.
Recording these steps as traceability events ensures continuity between raw material and final textile state and allows later linkage to facility-level environmental and chemical management data (recorded in Digital Facility Records).
Capturing finishing events also helps confirm that all material batches undergoing finishing remain traceable to their origins.
Recommended Pattern
| Element | Description |
|---|---|
| Primary Event Type | TransformationEvent |
| Business Step | processing |
| Disposition | active |
| Purpose | Record the transformation of fabric from an unfinished (“greige”) state to a finished or dyed state. |
| Identifier Scheme | Any interoperable identity scheme; may retain the existing fabric identifier or assign a new identifier to represent a new material state. |
| Event Schema | For dyeing operations, use the Dyeing Event schema (unttp-dyeing-dte.0.0.1.json) with processType: UNTTP_DYEING_EVENT. See the Traceability Events specification for the authoritative schema definition. |
Inputs and Outputs
| Role | Entity | Description | Notes |
|---|---|---|---|
| Input(s) | Fabric Rolls / Batches | Unfinished or greige fabric entering the finishing process. | May consist of one or multiple rolls. |
| Output(s) | Finished Fabric | Dyed, printed, or coated fabric produced from the input material. | May carry the same identifier (state update) or a new identifier representing a finished variant. |
Summary
Dyeing and finishing are modeled as TransformationEvents, as they represent a change in the material's characteristics and potentially its traceable identity.
This event type ensures that a fabric’s transformation from greige to finished form is formally recorded, maintaining the continuity of the material’s traceability path.
Whether a new identifier is assigned or the existing one is retained depends on the system’s approach to versioning:
- Same identifier (state update): Simpler for sequential process tracking within one facility.
- New identifier (output entity): Preferred when multiple finishing states or lots need distinct traceable identities.
Capturing this stage supports downstream verification that finishing processes were performed in facilities with appropriate environmental and chemical management credentials (linked through Digital Facility Records, not the event itself).
The granularity of recorded identifiers (e.g., per roll or batch) defines how precisely downstream systems can link final garments to specific finishing conditions and facilities.
Garment Manufacturing (Cut, Sew, Assemble)
Description
The garment manufacturing stage transforms textile materials into finished apparel or other textile products.
It typically includes cutting fabric, sewing components, attaching trims and labels, and final assembly into complete products.
At this stage, the final product identity is created, often for the first time bearing a consumer-facing identifier or item code.
Justification
This is a pivotal transformation in the textile lifecycle, where intermediate materials become end products.
It also represents the point at which different material streams may converge — for example, a cotton fabric combined with polyester thread, wool trim, or leather components.
Capturing this stage as a traceability event enables downstream users to reconstruct the full composition of a garment, link it to the origins of each input material, and maintain integrity of claims related to origin, composition, or sustainability.
Recommended Pattern
| Element | Description |
|---|---|
| Primary Event Type | TransformationEvent |
| Business Step | manufacturing |
| Disposition | active |
| Purpose | Record the assembly of multiple input materials into finished textile products such as garments. |
| Identifier Scheme | Any interoperable identity scheme; each finished product or product batch receives a new identifier, representing a discrete item or lot. |
Inputs and Outputs
| Role | Entity | Description | Notes |
|---|---|---|---|
| Input(s) | Fabric Rolls / Batches | Primary textile inputs from plant-based fibres. | May include multiple rolls or colours. |
| Input(s) | Additional Components | Non-plant-based inputs such as buttons, zippers, synthetic threads, elastics, or leather trims. | Each component may have its own traceability lineage and identifier. |
| Output(s) | Finished Product(s) | Garments or textile products ready for distribution. | Each output receives a new identifier; may represent an individual item or a production batch. |
Summary
Garment manufacturing is modeled as a TransformationEvent, as it combines multiple material inputs into a single new product identity.
This stage integrates different material classes — plant-based, animal-based, and synthetic — and thus forms the junction point for cross-material traceability within UNTP.
The event links each input identifier (fabric, trims, accessories) to a new product identifier, enabling downstream verification of:
- Origin composition: e.g., “contains cotton traced to identified farms and wool traced to certified flocks.”
- Claim granularity: the level of identifier resolution (per batch or per item) determines whether traceability applies to the collection, style, or individual product level.
By recording this event, the transparency graph now provides a complete trace from the agricultural sources of each material through to the final assembled garment.
Subsequent distribution and logistics events extend this traceability beyond manufacturing, allowing end-market actors (brands, regulators, or consumers) to resolve the origin, composition, and facility history of the finished item.
Summary
The table below summarises the events described above, and provides high level attributes associated with Digital Traceability Events. For authoritative technical specifications, schema definitions, and current versions, refer to the Traceability Events specification.
| Stage | Event Type | Business Step | Purpose | Inputs | Outputs | Identifier Granularity |
|---|---|---|---|---|---|---|
| Cultivation & Harvest | ObjectEvent | commissioning / add | Introduces harvested material into the traceable domain. Marks the start of the supply chain. | — (optionally CropLot / Field) | Harvested material lot (e.g., seed cotton, flax straw, hemp stalks). | Farm, field, or plot; may include season or batch attributes. |
| Primary Processing (Ginning / Scutching) | TransformationEvent | processing | Converts harvested material into standardized fibre units for trade or manufacturing. | Harvested material lots | Fibre units (bales, bundles) and by-products. | Bale, fibre bundle, or batch level. |
| Aggregation & Shipping of Fibre Units | AggregationEvent and ObjectEvent | packing, shipping, receiving | Groups fibre units for logistics and records transfer of custody between facilities. | Fibre units | Aggregated package or shipment batch. | Shipment, container, or pallet level; traceable to individual fibre identifiers. |
| Spinning (Fibre → Yarn) | TransformationEvent | processing | Converts fibres into yarn, often combining multiple sources. Enables content and origin attribution. | Fibre units (bales / bundles) | Yarn lots or cones. | Yarn lot or cone; granularity defines blending resolution. |
| Fabric Formation (Weaving / Knitting) | TransformationEvent | processing | Produces woven or knitted fabric from yarn inputs; introduces new identifiers for rolls or batches. | Yarn lots | Fabric rolls or batches. | Roll or batch level; may include type, width, or pattern metadata. |
| Dyeing & Finishing | TransformationEvent | processing | Records change in fabric state (e.g., dyeing, printing, coating) to maintain continuity and link to facility data. | Greige / unfinished fabric | Finished or dyed fabric. | Roll or batch level; same or new identifier depending on state versioning. |
| Garment Manufacturing (Cut, Sew, Assemble) | TransformationEvent | manufacturing | Assembles fabrics and components into finished products; junction point for plant-based, synthetic, or animal-based inputs. | Fabric lots, trims, accessories, other materials | Finished garments or textile products. | Product or batch level; determines claim precision at item, style, or lot scale. |
Identifier Relationships Across Plant-Based Fibre Stages
Traceability in UNTP depends on the consistent handling of identifiers as materials move and transform across the supply chain. Each event type either creates, derives, groups, or retains identifiers, forming the connective structure of the transparency graph.
The following table and diagram illustrate how identifiers evolve across typical stages in a plant-based fibre supply chain — from the creation of the first harvest identifier through to composite product identifiers at the garment stage.
This representation helps implementers understand how continuity is maintained without prescribing a specific identity scheme. It also clarifies where new identifiers are introduced (e.g., at transformation stages) and where existing identifiers persist or are grouped (e.g., during aggregation or logistics). Together, these views serve as a reference for designing interoperable identifier models that maintain linkage and provenance throughout the textile lifecycle.
| Stage | Identifier Relationship | Description | Implication for Traceability |
|---|---|---|---|
| Cultivation & Harvest | New Identifier Created | The harvested material receives its first traceable identifier (lot, field, or plot level). | Establishes the origin node in the traceability graph. Enables later claims of origin, farm identity, or production practice. |
| Primary Processing (Ginning / Scutching) | New Identifier Derived | Each fibre unit (e.g., bale, bundle) receives a new identifier, derived from one or more harvested material lots. | Creates the first many-to-one or one-to-many relationships in the chain. Traceability from fibre back to specific harvest lots is retained. |
| Aggregation & Shipping of Fibre Units | Existing Identifiers Grouped | Individual fibre identifiers are aggregated under a new package or shipment identifier. The original identifiers remain active. | Supports logistics-level traceability without altering the core material identifiers. Chain of custody continuity maintained through shipment and receipt events. |
| Spinning (Fibre → Yarn) | New Identifier Derived | Yarn lots or cones receive new identifiers that reference the fibre unit identifiers as inputs. | Enables mapping of blended inputs to output yarn, supporting compositional and content-claim traceability. |
| Fabric Formation (Weaving / Knitting) | New Identifier Derived | Each fabric roll or batch receives a new identifier derived from one or more yarn lot identifiers. | Maintains traceability between yarn and fabric; allows blend attribution or production-batch tracking. |
| Dyeing & Finishing | Identifier Retained or Versioned | Fabric identifier may remain the same (state update) or be versioned as a new identifier for finished fabric. | Choice depends on whether multiple finishing variants are tracked separately. Both preserve continuity of traceability. |
| Garment Manufacturing (Cut, Sew, Assemble) | New Identifier Created (Composite) | New identifiers are assigned to finished garments or product batches, referencing multiple input identifiers (fabric, trims, components). | Represents the convergence point of multiple material lineages. Enables cross-material traceability (plant, animal, synthetic). |