How to implement GRS/RCS chain of custody and Tier 2-3 mass balance in a textile PLM system

Scope of the tutorial — minimum existing PLM stack + Textile Exchange integration

The CSDDD (Corporate Sustainability Due Diligence Directive) establishes inescapable obligations for European companies with turnover above EUR 450M and more than 1,000 employees. However, the real structural impact falls on the rest of the value chain through the upstream cascade. If a company operates in Tier 1 (garment-making) or Tier 2/3 (weaving, spinning, chemical processing) and does not reach the CSDDD thresholds, it will receive these traceability requirements all the same. It is not a direct regulatory obligation; it is a contractual obligation imposed by the corporate client, without which the company will be excluded from the pool of authorised suppliers.

To market a product with sustainability claims based on recycling, the Textile Exchange standards require strict validation. The Global Recycled Standard (GRS v4) and the Recycled Claim Standard (RCS v4) require a Scope Certificate per production facility, a Transaction Certificate for each change of ownership of the material and an algorithmic mass balance when the Tier 3 chemical reactor simultaneously introduces virgin and recycled raw material. Accrediting recycled content requires an uninterrupted documentary chain between the source waste and the marketed product. This operational tutorial systematically sets out, in four steps, how to integrate this multi-tier traceability model into an existing PLM (Product Lifecycle Management) system, without needing to rewrite the foundational architecture of the software.

Before intervening in the PLM system's database, it is imperative to delimit the technological boundaries of the project. This tutorial assumes a standard transactional PLM stack that already manages bills of materials (BOM), supplier databases (Vendor Management) and a basic ERP-integration module for the ingestion of purchase orders (PO). We are not going to build a financial ERP from scratch nor a primary environmental-data capture platform (LCA). The objective is to endow the existing PLM with a layer of documentary governance capable of processing, auditing and reconciling Textile Exchange certificates, automating the mass balance.

The Textile Exchange regulatory framework clearly distinguishes two standards of application. The system must support the business rules of both. According to the official documentation, the primary objective of RCS is to increase the use of recycled materials, focusing on chain of custody. On the other hand, GRS is multidimensional: it establishes requirements for independent third-party certification of recycled input + chain of custody + social and environmental practices + chemical restrictions. If the PLM validates an item under GRS, the system must not only calculate the minimum 20% recycled-content threshold, but also audit that the facilities in the supply chain comply with the chemical-toxicity limits and applicable labour regulations.

Step 1 — map the chain Tier 1 → Tier 4 — systematic ingestion of supplier Scope Certificates

The first operational step consists of topologically mapping the supply chain in the PLM, descending from assembly (Tier 1) to the origin of the raw material (Tier 4). The OECD defines the high-risk nodes or bottlenecks in the chain as «choke points», indicating that they include key transformation points with visibility and control over upstream production and trade circumstances. In the textile sector, these «choke points» are usually polymerisation reactors (synthetics) or extrusion and dyeing plants. The PLM must be able to model these nodes and associate a valid Scope Certificate with each one.

To start, require credentials from suppliers: if a brand wishes to begin sourcing certified recycled material, it must request from its suppliers the Scope Certificate (SC) of their certification. In the PLM system, it is not enough to associate the SC with the supplier at corporate level; it must be associated with the physical facility (Facility). A supplier may have three factories but only one certified under GRS.

Extend the PLM database with the following relational pseudocode schema:

```sql CREATE TABLE TextileExchange_ScopeCertificate ( sc_id VARCHAR(255) PRIMARY KEY, supplier_id VARCHAR(255) NOT NULL, facility_id VARCHAR(255) NOT NULL, standard_type ENUM('GRS', 'RCS') NOT NULL, certification_body VARCHAR(255) NOT NULL, valid_from DATE NOT NULL, valid_to DATE NOT NULL, certified_categories JSON, is_active BOOLEAN DEFAULT TRUE, FOREIGN KEY (supplier_id) REFERENCES Vendors(id), FOREIGN KEY (facility_id) REFERENCES Facilities(id) );

CREATE TABLE SC_MaterialSpecs ( id INT AUTO_INCREMENT PRIMARY KEY, sc_id VARCHAR(255) NOT NULL, material_composition VARCHAR(255) NOT NULL, recycled_content_percentage DECIMAL(5,2), FOREIGN KEY (sc_id) REFERENCES TextileExchange_ScopeCertificate(sc_id) ); ```

Deploy a daily cron job in the PLM that scans the `valid_to` column. When an SC is 30 days from its expiry, the system must trigger automated alerts to the purchasing manager and the supplier. If the SC expires, the PLM must apply a preventive block (Hard Stop) in the purchasing module, preventing the generation of new POs for the certified items associated with that facility.

It is vital to understand that the validity of the SC is a necessary but not sufficient condition. The SC demonstrates capacity, not execution. It demonstrates that the Tier 2 spinning mill has the machinery and the isolated processes to operate with recycled PET, but it does not prove that the specific lot purchased contains recycled PET. To guarantee the identity of the material in transit, the second level of traceability comes into play: the Transaction Certificate.

Step 2 — integrate Transaction Certificates into the PO flow

The fundamental rule of GRS/RCS traceability establishes that the identity of the material must be preserved at each change of custody: the certification ensures that the identity of the recycled material is maintained from the recycler to the final product. The Transaction Certificate (TC) is the passport of that lot of material. In the operational environment of the PLM, the TC functions as a digital twin of the delivery note (Advanced Shipping Notice, ASN).

The procedure is unequivocal: request Transaction Certificates from the certified suppliers to verify that certified product is being received. The TC lists the details of the shipment and includes whether the material is pre-consumer or post-consumer recycled. The PLM must intercept the TC before the lot of fabric or yarn is released by the Quality Control department towards the production lines.

Integrate the TC into the transactional flow of the PLM by creating a volume-reconciliation table. When the ERP issues a PO for 10,000 metres of recycled-cotton fabric, the PLM expects the receipt of a TC that supports exactly that volume (adjusted for commercial tolerances of ±3%).

Model the interception in the PLM with the following pseudocode:

```python function validate_inbound_transaction_certificate(purchase_order_id, tc_document): po = get_purchase_order(purchase_order_id) tc_data = parse_tc_metadata(tc_document)

# 1. Validate that the sending supplier matches if po.supplier_id != tc_data.seller_id: raise SecurityException("The TC sender does not match the PO supplier")

# 2. Validate active SC on the transaction date sc = get_active_scope_certificate(tc_data.seller_facility_id, tc_data.transaction_date) if not sc: raise ComplianceException("The supplier was operating without an active Scope Certificate on the shipping date")

# 3. Reconciliation of volumes and composition for line_item in po.items: tc_item = find_matching_tc_item(line_item.sku, tc_data.items) if not tc_item: flag_quarantine(line_item, "No TC coverage exists for this SKU") continue

if tc_item.net_weight < (line_item.received_weight * 0.97): flag_quarantine(line_item, "Volume deficit in the Transaction Certificate")

if tc_item.recycled_type not in ['PRE-CONSUMER', 'POST-CONSUMER']: flag_quarantine(line_item, "Recycled origin not valid under the GRS taxonomy")

return status.APPROVED ```

This block ensures that no material enters the plant without documentary coverage. In addition, the PLM must record whether the material is pre-consumer or post-consumer, since the standard requires transparency about the source. The definitions are strict and the PLM must enforce them. For example, pre-consumer material is considered to be material diverted from the waste stream during a manufacturing process, excluding the reuse of materials such as rework, regrind or scrap generated in a process and capable of being reclaimed within the same process that generated them. If a supplier attempts to pass off the scrap from its own production line (regrind) as certified pre-consumer recycled content, the TC issued by the external certification body will block this irregularity.

Step 3 — algorithmic mass balance in PLM — Tier 3 chemical reactor

The real algorithmic challenge arises when the facility itself, or that of the direct supplier (Tier 2/Tier 3), carries out mixing or continuous chemical-reaction operations where the physical separation of virgin and recycled raw materials is impossible. In these scenarios, the PLM must implement a mass-balance module. The objective of mass balance is to ensure mathematically that the quantity of final product marketed with recycled-content claims does not exceed the sum of the certified recycled material introduced into the system, less the losses of the production process.

To model this scenario, the PLM must adopt the methodological guidelines of life-cycle analysis (LCA), considering the process-loss variables: the Process Loss Rates represent the quantity of the intermediate input that is lost or consumed as part of the process (mass/mass basis). A loss rate of 20% indicates that for every 1 kg of input, there is only 0.8 kg of output. The PLM algorithm must apply this loss rate equitably or weighted across the inputs.

In addition, the PLM must classify the recycled-content ratio (R1). The European ecosystem defines R1 as the proportion of material in the production input that has been recycled from a previous system. The PLM cannot use market averages to certify GRS; it must use supply-chain-specific data.

Implement the mass-balance engine in the PLM with a debit-and-credit logic in a virtual material account. For each kilogram of recycled PET fibre covered by a TC that enters the facility, the credit account adds 1 kg. When the spinning mill produces a blended yarn (e.g. 50% virgin, 50% recycled), the output deducts credits from the account based on the BOM formulation and the historical loss.

```python function calculate_mass_balance_allocation(production_run_id): run = get_production_run(production_run_id) bom = get_bom_for_sku(run.output_sku)

# 1. Total the recycled raw-material inputs with valid TCs total_recycled_input_kg = sum_certified_inputs(run.raw_materials, type='RECYCLED')

# 2. Apply the machine/process-specific loss (Process Loss Rate) process_loss_rate = get_machine_loss_rate(run.machine_id) # e.g. 0.15 for 15% loss effective_recycled_yield = total_recycled_input_kg * (1 - process_loss_rate)

# 3. Calculate theoretical consumption per BOM for the manufactured output # If we manufacture 1000 kg of yarn at 30% recycled, we will consume 300 kg in theory theoretical_recycled_consumption = run.total_output_kg * bom.recycled_percentage

# 4. Mass-balance reconciliation if theoretical_recycled_consumption > effective_recycled_yield: discrepancy = theoretical_recycled_consumption - effective_recycled_yield raise MassBalanceDeficit( f"Mass-balance deficit: {discrepancy} kg of certified input missing" )

# 5. Debit the consumption from the virtual GRS inventory account debit_certified_inventory( run.facility_id, material_type='RECYCLED_PET', amount=theoretical_recycled_consumption, )

return status.COMPLIANT ```

This algorithm avoids the «double counting» of sustainability attributes and ensures that, when the facility's own Transaction Certificate is issued towards the client (the large brand subject to CSDDD), the volume transferred is supported cryptographically and arithmetically by its own production processes.

Step 4 — annual external audit + reporting — SC renewal + reporting to the eco-organisation

No textile chain-of-custody implementation makes sense if it does not withstand the friction of an independent external audit. The methodological design of GRS and RCS stipulates without exception that a professional third-party certification body audits each stage of the supply chain. The PLM does not replace the auditor (Certification Body), but it centralises the aggregation of evidence so that the annual renewal of the Scope Certificate goes from being a weeks-long forensic process to a structured data export.

Annually, the auditor will verify the volumetric reconciliation (Volume Reconciliation). The PLM must generate a «Volume Reconciliation» report that demonstrates at a glance that the physical inventories and the transactional records match. If the auditor detects a discrepancy between the inputs (supported by incoming TCs) and the outputs (supported by outgoing TCs), the facility's Scope Certificate will be revoked. The risk of losing certification directly implies the loss of commercial viability before clients obliged by CSDDD.

Additionally, the PLM must contemplate the treatment of the scrap generated during production. If the process generates pre-consumer scrap and the company wishes to reintroduce it into a later production cycle by reclaiming it as recycled content, the system must be able to model this loop without violating the circularity rules. There are strict algorithmic options for this. One of the accepted paths, based on impact allocation, dictates that the impacts of producing the input material that leads to the pre-consumer scrap must be allocated to the product system that generated that scrap; the scrap is claimed as pre-consumer recycled content. The PLM must trace this scrap internally as a new input SKU, issuing an internal TC (or equivalent traceability record accepted by the auditor) that validates the origin of the scrap.

The final exportable report from the PLM will not only serve the Textile Exchange certification body (e.g. Control Union, Ecocert, Intertek). This same set of aggregated data is exactly what is demanded by European regulations on Extended Producer Responsibility (EPR) and the imminent requirements of the Digital Product Passport (DPP). Demonstrating volumetrically the use of recycled polyester or cotton will allow, for example, application for reductions in eco-modulation fees before integrated management systems (e.g. regulations derived from waste and contaminated soils in Spain), reducing the company's operational tax cost.

Operationalising the chain of custody

The implementation of the GRS/RCS chain of custody with algorithmic mass balance in an existing PLM requires synchronisation between the purchasing, receipt, quality-control and production modules. The integration effort is significant when assumed internally, but the contractual pressure of the CSDDD cascade admits no operational excuses.

For textile brands that need to implement a GRS/RCS chain of custody + Tier 2-3 mass balance without rewriting their existing PLM: Supply Chain Visibility — the TraceWeave module to ingest Scope/Transaction Certificates + automate mass balance + annual renewal + reporting to the eco-organisation. → Discover Supply Chain Visibility