Skip to content

October 2026

FSMA 204 Traceability: What US Importers Need

If you import food products into the United States, you have probably seen FSMA 204 mentioned in supplier contracts or compliance checklists. It is part of the FDA’s Food Safety Modernization Act, designed to improve the ability to trace potentially contaminated food quickly and remove it from the market.

When do you need to comply?

Final rule: November 2022 (21 CFR Part 1, Subpart S), with the original compliance date of 20 January 2026. The FDA later extended the deadline to 2028 - see our FSMA 204 compliance date timeline Do not treat the extension as a pause: large grocers and retailers are already writing FSMA 204 traceability data requirements into supplier contracts, so for practical purposes the commercial market is enforcing now.

What does the rule actually require?

FSMA 204 (21 CFR Part 1, Subpart S) applies to foods on the FDA Food Traceability List - leafy greens, melons, tomatoes, fresh-cut produce, fresh herbs, cheeses, nut butters and certain ready-to-eat foods, among others. It adds a standardised, structured data set on top of the food-safety records you already keep.

The rule centres on three building blocks:

  • Traceability Lot Code (TLC) - a unique identifier for the lot, assigned where the food is first packaged or processed and recorded at every Critical Tracking Event (CTE) as the product moves one step back and one step forward through the supply chain.
  • Key Data Elements (KDEs) - the data captured at each CTE: the TLC, the product description, the location where the food was grown or raised, the harvest or processing date and, where applicable, the first processor details.
  • A traceability plan - the written document describing how you assign TLCs, which KDEs you record at each CTE and how records are maintained and produced on request.

In practice, you must be able to provide this information to the FDA within 24 hours of an official request.

Why the 24‑hour window matters

Before FSMA 204, the FDA could request records under existing authorities, but the new rule formalises a fast-response requirement. If you cannot produce the required traceability records within 24 hours, the FDA can regard it as a failure to maintain required records - a violation that can lead to penalties and, for imported food, heightens the risk that shipments face scrutiny or refusal at entry.

How Sustalium can help

Sustalium’s platform includes a FSMA 204 module that lets you:

  • Build a traceability plan step‑by‑step, with prompts for each data element the rule requires.
  • Upload supporting documents – harvest records, shipping documents, supplier certificates – and attach them to the relevant lot.
  • Generate a printable plan that you can post in your facility and keep as part of your compliance records (the rule requires records to be kept for two years).
  • Export the data in a structured format that can be shared with trading partners or uploaded to FDA portals if needed.

Because the platform stores data in a structured layer, you can also create the same traceability record for multiple SKUs or language versions without re‑entering the same information.

Typical mistakes we see

  • Confusing FSMA 204 with the older Section 204 requirements – they run in parallel; you need both if your product falls under the original rule.
  • Using generic lot numbers that don't tie back to a specific growing location or processing date – the rule expects enough detail to trace the food one step forward and one step back in the supply chain.
  • Not updating the traceability plan when you change suppliers or switch packaging materials – any change that affects traceability should be reflected in the plan.
  • Keeping records only in spreadsheets that cannot be produced within 24 hours – consider a system that can export the data quickly if the FDA asks.

First steps for importers

  1. Check whether your food product is on the FDA's Food Traceability List. If it is, FSMA 204 applies.
  2. Map your current supply‑chain data to the rule's building blocks: TLC, KDEs at each CTE, and the traceability plan.
  3. Identify gaps – what do you already capture, and what is missing?
  4. Choose a system – many companies use a combination of ERP, spreadsheet and dedicated traceability software. Sustalium's FSMA 204 module is built for SMEs that need a simpler alternative to enterprise‑grade solutions.
  5. Write and validate your traceability plan – run a tabletop exercise where you pretend the FDA calls and you have 24 hours to produce the records.
  6. Archive the plan and make it part of your routine QA documentation.

Quick checklist

  • Product on the FDA Food Traceability List?
  • Traceability lot code (TLC) scheme in place
  • Product description matches the label
  • KDEs captured at every Critical Tracking Event (growing/harvest location, date, first processor)
  • One-step-back / one-step-forward links documented
  • Traceability plan written and current
  • Records retained for 2 years
  • 24‑hour production test completed

Further reading

  • FDA – "New Era of Smarter Food Safety" traceability page
  • FDA – Final rule on Traceability Requirements for Certain Foods (2022)
  • Industry guide – "Implementing FSMA 204 for Importers" (sessions hosted by food‑safety consultants)

Key takeaways

FSMA 204 applies to foods on the FDA Food Traceability List. You must assign traceability lot codes, capture key data elements at each Critical Tracking Event, keep a written traceability plan, and produce records within 24 hours of an FDA request. The federal compliance date is July 2028, but major retailers are already demanding the data - the practical deadline is now. Sustalium FSMA 204 module walks you through each data element, generates a printable plan and QR code, and keeps your records in a searchable archive.

General Certificate of Conformity: What SMEs Need

A General Certificate of Conformity (GCC) is a certificate that declares a product complies with the applicable consumer product safety rules of the U.S. Consumer Product Safety Commission (CPSC). For children's products the same style of certificate is issued as a Children's Product Certificate (CPC). It is not issued by a third party: the manufacturer or importer issues it themselves, based on testing performed by a CPSC-accepted laboratory where third-party testing is required.

When is a GCC required?

CPSC rules require a certificate any time a regulated consumer product is imported or sold in the US:

  • Children's products (toys, child care articles, infant furniture) require a Children's Product Certificate (CPC) and must be tested by a CPSC-accepted third-party laboratory.
  • Non-children's consumer products subject to a CPSC rule (for example, bicycle helmets, cigarette lighters, residential pool covers) require a General Certificate of Conformity (GCC) - some of these rules mandate third-party testing, others allow a reasonable testing program.

Outside the U.S., many other regions have equivalent documents. The EU uses the Declaration of Conformity (DoC) as part of the CE marking framework; other countries have their own versions. The underlying principle is the same: the party placing the product on the market asserts that it meets the relevant requirements.

What the GCC must contain

If you are required to issue a GCC, it must include, at minimum, the following elements:

  1. Product identification – name, model number, identifying characteristics (batch number, serial number where applicable).
  2. Manufacturer or importer information – name, address, contact details. If the manufacturer is outside the region, the importer of record is listed.
  3. Applicable safety rule or regulation – the specific statute, code or standard the product is claimed to comply with (e.g., "ASTM F963 – Standard Consumer Safety Specification for Toy Safety").
  4. Conformity statement – an explicit declaration that the product complies with the referenced rule. Wording such as "This product conforms to the requirements of 16 CFR Part 1500" or "This toy complies with ASTM F963‑21."
  5. Identification of the responsible person – name, title and signature of the individual who assumes responsibility for the statement.
  6. Date of issue – when the certificate was issued.
  7. Testing information – name of the testing laboratory, test report number, date of testing, and the specific tests performed that demonstrate compliance.

Quick tip: The CPSC publishes model templates for the GCC and CPC on its website. Using a template ensures you include all required fields and the correct regulatory citations.

How the GCC differs from a Declaration of Conformity (DoC)

Aspect General Certificate of Conformity (U.S. CPSC) Declaration of Conformity (EU CE marking)
Primary region United States European Union
Typical products Non-children's products subject to CPSC rules (children's products use the CPC) Machinery, electrical equipment, toys, medical devices, etc.
Legal basis Specific consumer‑product safety rules (16 CFR) Harmonised directives & regulations (e.g., Machinery Directive, RoHS)
Third-party involvement Certificate is self-issued; children's products must be third-party tested at a CPSC-accepted lab before certification May require notified-body assessment for high-risk categories; DoC is always issued by the manufacturer
Retention Keep for 5 years (records requirement under 16 CFR Part 1110) Keep for 10 years after the product is placed on the market
Marking Often paired with a children's product certificate (CPC) mark on the product Must be CE‑marked if other CE directives also apply

Common reasons a GCC is challenged or rejected

  • Missing the specific regulation citation – "Our product is safe" is not sufficient; you must reference the exact rule (e.g., 16 CFR Part 1500, ASTM F963‑21).
  • Using an outdated test report – safety standards are revised. A test report from 2018 may not satisfy a 2024 requirement.
  • Omitting the testing laboratory information – the GCC must name the lab that performed the verification; a blank field or "internal testing" without documentation is a red flag.
  • Referring to a generic standard – "ISO 9001" is a quality‑management standard, not a product‑safety standard. Do not list it as the basis for a GCC unless the specific safety rule references it.
  • Issuing the GCC before testing is complete – the GCC should only be issued after the product has been tested and the results confirm compliance.

How Sustalium simplifies GCC / DoC management

Sustalium’s platform does not replace the legal requirement, but it centralises the data you need to issue a compliant GCC or DoC:

  • Regulation mapping – you select your product type, and the platform lists the applicable safety rules or harmonised standards. For each, you record the current status (not applicable, in progress, compliant).
  • Test‑report library – you can upload the test lab report, note the report number, date and the specific tests performed. The platform indexes this information so you can retrieve it when drafting a GCC or DoC.
  • Conformity‑statement generator – based on the regulation you have selected and the test data on file, the platform can produce a draft conformity statement with the correct citation format.
  • Hash‑verified public page – similar to the DPP and DoC workflow, the platform can generate a public page with a QR code that links to the declaration. Buyers or regulators can scan the code and see the conformity statement, test‑report reference and issue date – all without requesting a PDF by email.
  • Retention tracking – the platform records the issue date and tracks the 10‑year (EU) or 3‑year (U.S.) retention period, sending a reminder when the document is approaching the renewal date.

Step-by-step: drafting a CPC for a children's product

  1. Identify the applicable CPSC safety rule – determine which children's product safety rule covers your item (e.g., 16 CFR Part 1500 for general safety, or a specific rule such as 16 CFR Part 1222 for infant bouncers).
  2. Complete the required testing – have a CPSC-accepted laboratory perform the tests specified in the rule. Obtain the official test report.
  3. Upload the test report to Sustalium – include the report number, date and the specific tests performed.
  4. Enter the product identification – name, model number, batch/serial range.
  5. Generate the CPC – the platform produces a draft with:
  6. Product identification.
  7. Manufacturer/importer details.
  8. Exact regulation citation (e.g., "16 CFR Part 1222").
  9. Conformity statement referencing the test report.
  10. Responsible person name and signature.
  11. Issue date.
  12. Review and issue – verify that all fields are correct, sign the document (digital or physical), and distribute it with the product. Keep a copy in your compliance archive for the required retention period.
  13. Attach the QR code (optional) – if you want buyers or regulators to verify the GCC instantly, generate a public page and QR code via the platform; the code links to the stored test‑report reference and conformity statement.

Checklist: GCC readiness

  • Applicable safety rule identified and cited exactly (e.g., 16 CFR Part 1222).
  • Product tested by an accredited lab; test report obtained.
  • Test report uploaded and indexed (report number, date, tests performed).
  • Product identification recorded (name, model, batch range).
  • Manufacturer/importer details entered.
  • Conformity statement generated with correct regulation reference.
  • Responsible person named and signature added.
  • Issue date recorded.
  • Document retained for required period (5 years under 16 CFR Part 1110, 10 years EU).
  • (Optional) QR code / public page generated for instant verification.

Quick use case: new infant bouncer

A company launches an infant bouncer sold in the U.S. The applicable rule is 16 CFR Part 1222 (Infant Bouncers). The company:

  1. Labs test the bouncer for fall‑risk, restraint‑system strength and label clarity.
  2. Uploads the test report to Sustalium (report #CL2026‑B1, dated 2026‑03‑15, tests: fall distance, harness strength, label legibility).
  3. Enters the product name ("Peaceful Nap Infant Bouncer"), model number, and manufacturer details.
  4. Clicks "Generate CPC" – the platform produces a document that reads: "This infant bouncer conforms to the requirements of 16 CFR Part 1222, based on test report #CL2026‑B1."
  5. Prints the GCC and attaches it to the product packaging. Also generates a QR code; retailers can scan it to see the test‑report reference and compliance statement instantly.
  6. Keeps the CPC and test report in the compliance archive for 5 years (16 CFR Part 1110), with a reminder set before the retention period ends.

Further resources

  • CPSC – "General Certificate of Conformity" template and guidance page.
  • CPSC – "Children's Product Certification" page (explains the CPC requirement that often accompanies the GCC).
  • EU Commission – "Declaration of Conformity" guidance (for CE‑marked products).
  • Sustalium help centre – "Regulation mapping and DoC generation" walkthrough.

Key takeaways

A GCC (or a CPC for children's products) is a self-issued certificate that a product meets the applicable CPSC safety rules. Cite the exact regulation (e.g., 16 CFR Part 1222), reference a CPSC-accepted laboratory test report, and retain the document for 5 years under 16 CFR Part 1110. A QR‑linked public page can give buyers instant verification without emailing PDFs.

GPSR Art. 22: Four Blocks Every Listing Needs

If you sell physical products on an online marketplace in the European Union, you have probably heard that the General Product Safety Regulation (GPSR) introduces new requirements that apply from 13 December 2024. One of the most concrete obligations is that online marketplaces must display four specific information blocks on every product listing that involves an EU‑based seller or a product intended for the EU market.

Why GPSR Art. 22 matters for marketplace sellers

The regulation puts the onus on the marketplace operator to ensure that certain safety‑related information is visible to the buyer before purchase. The goal is to reduce the time it takes for authorities or buyers to get the data they need – for example, when a product is flagged as unsafe and a rapid recall is required.

The four blocks are not optional; if any of them is missing, the marketplace can face enforcement action. The blocks are:

The four required blocks

1. Manufacturer identification

The name and address of the manufacturer established in the EU. If the manufacturer is outside the EU, the name and address of the EU‑based authorised representative must be shown instead.

2. EU Responsible Person

For products where the manufacturer is outside the EU, the marketplace must display the name and contact details of the EU‑based responsible person. This is the person whom authorities can reach if they need to act quickly on a safety concern.

3. Product identifier

A clear way to identify the specific product. This can be: * A GTIN (Global Trade Item Number), * A batch number, * A lot number, * Or another identifier accepted by the relevant national authority.

The identifier must be readable and – where applicable – linked to the product's label.

4. Safety‑warning information

A short description of the risks associated with the product and any mandatory warnings. The content must be proportionate to the product type – for a child's toy it might include age‑grading and choke‑hazard warnings; for an electronic device it might cover installation or electrical‑safety notes.

The regulation does not prescribe the exact wording for every product, but the information must be accurate, visible and readily understandable by the average consumer.

How marketplace operators are expected to comply

The regulation states that the marketplace must display these blocks "in a clear and legible manner". In practice, many operators:

  • Add the blocks to the product‑page template – so they appear on every listing automatically.
  • Use the data supplied by the seller – the seller provides the manufacturer details, responsible‑person info and product identifier through a dedicated onboarding form.
  • Validate the data – some operators run a quick check that all four fields are filled in before the listing goes live.
  • Make the blocks editable by the seller – so the seller can keep the information up to date if, for example, they change their authorised representative.

What happens if a block is missing?

If a marketplace operator does not display one or more of the four blocks, national market‑surveillance authorities can:

  • Issue a formal warning.
  • Require the marketplace to remove the non‑compliant listing.
  • Impose administrative fines – the amount varies by member state but can be substantial for repeated violations.
  • In serious cases – where there is a demonstrable risk to consumers – the authority can order a product recall or a temporary sales ban.

How Sustalium helps sellers and marketplaces

Sustalium’s platform was built with GPSR compliance in mind. If you use the platform, you can:

  • Enter your company details once – the manufacturer name, EU address and authorised‑representative information are stored in your profile.
  • Add product identifiers – GTIN, batch number or lot number are captured at the product‑level and can be reused across multiple marketplaces.
  • Generate safety‑warning text – the platform prompts you for the key risk‑categories relevant to your product type (child safety, electrical, chemical, etc.) and creates a draft warning that you can edit.
  • Produce a GPSR‑compliant listing block – with one click, you can export the four required pieces of information in the format expected by major marketplace APIs (eBay, Etsy, Bol.com, etc.).
  • Keep the data current – if you change your authorised representative or product identifier, a single update propagates to all connected marketplaces.

Checklist for sellers

  • Manufacturer EU name and address (or authorised representative) on file
  • EU Responsible Person name and contact details recorded
  • Product identifier (GTIN, batch or lot number) entered for each SKU
  • Safety‑warning text drafted and approved for your product category
  • Listed on marketplace with all four blocks visibly displayed
  • Periodic review – update any of the four items when changes occur

Further information

  • European Commission – "General Product Safety Regulation (GPSR) – What you need to know" portal
  • Your national market‑surveillance authority – contact details and guidance specific to your country
  • Sustalium GPSR help centre – template library and marketplace‑integration guides

Key takeaways

GPSR Art. 22 requires four information blocks on every EU marketplace listing: manufacturer identification, EU Responsible Person, product identifier, and safety‑warning information. Non-compliance can lead to warnings, fines, listing removal, or product recalls. Sustalium streamlines the compliance process by centralising seller data and enabling one‑click generation of the required blocks for all major marketplaces.

REACH and RoHS compliance for small manufacturers

If you make or import chemical substances, mixtures or electrical equipment into the European Economic Area, you have probably encountered REACH and RoHS. They are the two biggest regulatory frameworks for chemical and electrical safety in the EU, and both affect SMEs – even though the paperwork can look designed for large enterprises.

What REACH actually requires

REACH (Registration, Evaluation, Authorisation and Restriction of Chemicals) entered into force in 2007. Its core idea is that industry must manage the risks from the substances they use and tell ECHA (the European Chemicals Agency) what is on the market.

If you are a small manufacturer or importer, REACH applies to you if:

  • You manufacture or import one tonne or more of a substance per year across all your EU applications. This is the "tonnage trigger".
  • You use a substance covered by an authorisation or restriction.
  • You need to register a substance with ECHA unless an exemption applies.

For many SMEs, the tonnage trigger is the sticking point. If you import a chemical blend or a raw material in quantities above 1 t/year, you (or your downstream user) must register it. The registration includes:

  • A technical dossier describing the substance’s properties and uses.
  • A chemical safety assessment if the substance is classified as toxic or hazardous.
  • A registration fee paid to ECHA.

What RoHS restricts

Restriction of Hazardous Substances (RoHS) was adopted in 2003 and restricts the use of specific hazardous materials in electrical and electronic equipment placed on the EU market. The restricted substances are:

  • Lead (Pb) – 0.1 % threshold by weight in homogeneous materials
  • Mercury (Hg) – 0.1 % threshold
  • Cadmium (Cd) – 0.01 % threshold (more stringent than the others)
  • Hexavalent chromium (Cr(VI))
  • Polybrominated biphenyls (PBB)
  • Polybrominated diphenyl ethers (PBDE)`
  • Certain phthalates (DEHP, BBP, DBP, DIBP) - added by RoHS 3 (EU 2015/863), 0.1 % threshold each

RoHS applies to complete products as well as components and sub-assemblies. If you sell a circuit board, a power supply or a finished device with electronic functions in the EU, you must ensure those restricted substances are below the thresholds. A Declaration of Conformity is issued, and the product must be CE-marked - RoHS is part of the CE marking framework.

Where SMEs typically stumble

  • Underestimating the tonnage trigger – many importers think REACH only applies to large volume players. If you are above 1 t/year across all your EU uses, you have registration obligations.
  • Assuming RoHS only matters for big brands – any product with electrical functions, even a small gadget or a power supply, must comply if sold in the EU.
  • Confusing REACH and RoHS – they are separate. RoHS restricts certain substances in EEE; REACH manages chemical risks across all industries. A product can be subject to both.
  • Not keeping updated declarations – substance lists change, new restrictions are added, and your supplier’s compliance status may change over time.

How Sustalium simplifies the process

Sustalium’s platform includes structured modules for both frameworks:

  • REACH module – you enter the substances you use (or import), their tonnage, and the platform flags whether you have registration obligations. It tracks registration deadlines and can generate the technical dossier fields you need for ECHA submission.
  • RoHS module – you select the electrical product category, and the platform checks each restricted substance against your material declarations. It generates a RoHS-compliant Declaration of Conformity and flags any materials that exceed the thresholds.
  • Data reuse – if you already entered substance information for a REACH registration, the same data can be referenced when creating a RoHS declaration for a product that contains those substances. You do not re‑enter the same information twice.
  • Multi‑language support – both the REACH dossier and RoHS DoC can be generated in the languages you sell into, without re‑typing the technical details.

Quick compliance checklist for SMEs

REACH - [ ] Calculate your total annual import volume per substance across all EU uses - [ ] If ≥ 1 t/year, determine if you need to register or if a downstream user/importer registration covers you - [ ] Keep records of substance safety data sheets (SDS), usage volumes and any exemptions claimed - [ ] Set a calendar reminder to review registrations annually

RoHS - [ ] Identify which of your products contain electrical or electronic functions - [ ] Verify that restricted substances are below the 0.1 % (or 0.01 % for Cd) threshold in homogeneous materials - [ ] Maintain material certificates from your suppliers (declare the material composition) - [ ] Issue a RoHS Declaration of Conformity and CE‑mark the product if required - [ ] Review material declarations whenever you change a supplier or change a component

Getting started without a compliance team

  1. Map your supply chain – know where your raw materials come from and whether they are chemical substances or electronic components.
  2. Check the tonnage – add up your imports per substance; if you are near the 1 t trigger, err on the side of registration.
  3. Ask your suppliers – request REACH registration status and RoHS declarations for the materials you purchase.
  4. Use a data platform – Sustalium can centralise the information you already collect from SDS and supplier certificates, so you are not starting from a blank sheet each time you need a declaration.

Further resources

  • ECHA – "How to register" guidance and webinars for SMEs
  • EU Commission – "RoHS FAQ" page for manufacturers and importers
  • Sustalium help centre – REACH and RoHS module walkthroughs and template library

Key takeaways

If your SME imports or manufactures ≥1 t/year of a substance across the EU, REACH registration is likely required. For electrical products, verify that restricted substances stay below the RoHS thresholds (0.1 % for most, 0.01 % for cadmium). Centralise supplier certificates and use a data platform to reuse data across both frameworks.

RoHS Compliance Software: Automate Declarations

The EU RoHS Directive (2011/65/EU) restricts ten hazardous substances in electrical and electronic equipment. If you manufacture, import, or distribute electronics in the EU, you must collect compliance declarations from your supply chain — for every component, every batch, every supplier. Managing this manually across hundreds of components breaks down fast.

RoHS compliance software automates supplier data collection, substance screening, declaration generation, and certificate lifecycle management — replacing spreadsheets with a single auditable platform.

The RoHS Compliance Challenge

An electronics product might contain 50-500 components from 10-30 suppliers. Each component needs a RoHS declaration. If one supplier's declaration expires or one component exceeds a threshold, the entire product becomes non-compliant.

The Component-Level Problem

Problem Business Impact
Component-level data collection 50-500 declarations per product, each requiring supplier follow-up
Expired certificates Products shipped with outdated declarations = regulatory risk
No cross-referencing REACH and RoHS share similar data — re-collected separately
Retailer audits Days of manual document gathering per request

Why Manual Processes Fail

  • Component-level data collection: 50-500 declarations per product, each requiring supplier follow-up
  • Expired certificates: Products shipped with outdated declarations = regulatory risk
  • No cross-referencing: REACH and RoHS share similar data — re-collected separately
  • Retailer audits: Days of manual document gathering per request

What RoHS Compliance Software Automates

1. Supplier Declaration Portal
  • Self-service onboarding for component suppliers
  • Pre-filled forms per material category
  • Automated reminders (day 3, 7, 14)
  • Document upload (test reports, certificates, MSDS)
  • Response rates: 85%+ within 2 weeks
2. Substance Screening
  • Auto-screen declarations against current RoHS thresholds
  • Flag near-threshold substances (e.g., lead at 850 ppm = warning)
  • Cross-reference with REACH SVHC for combined chemical compliance
  • Risk scoring for incomplete or implausible data
3. Declaration Generation
  • Per-component RoHS declarations
  • Product-level consolidated declarations
  • Declaration of Conformity (DoC) generation
  • Machine-readable formats for retailer systems
  • QR codes for in-box compliance documentation
4. Certificate Lifecycle
  • Expiry tracking with automated renewal requests
  • Version history per supplier submission
  • Audit trail for regulatory inspections
  • Bulk updates when RoHS list changes

Top RoHS Compliance Software Platforms (2026)

1. Sustalium — Best for Multi-Regulation Electronics Compliance

Sustalium provides RoHS compliance alongside REACH, ESPR, GPSR, and EUDR in a single platform — ideal for electronics manufacturers who also need broader regulatory coverage.

Key Features:

Feature Sustalium
RoHS declaration framework Per-component and product-level structured framework
Substance threshold screening Against all 10 restricted substances
REACH / RoHS combined screening Single supplier declaration covers both
Supplier portal Self-service declarations + automated reminders
Certificate management Expiry tracking, renewal workflows, verification
Declaration of Conformity Structured declaration framework with QR-coded public page
Sector-specific frameworks Electronics, automotive, medical, industrial
Bulk CSV import Onboard 500+ components in 10 minutes
Pricing €10 per document per month

Best for: Electronics manufacturers and importers who need RoHS alongside REACH and other EU regulations.

2. GreenSoft — Electronics-Focused Compliance

GreenSoft specialises in material declarations for electronics OEMs.

  • Full BOM (Bill of Materials) substance screening
  • IPC-1752 / IEC 62474 material declaration formats
  • REACH + RoHS + SCIP database integration
  • Pricing: Custom (typically €3K-15K/year)

Best for: Large electronics OEMs with complex BOMs.

3. Toxnot — Chemical Data Management

Toxnot (by 3E) provides chemical inventory and hazard assessment.

  • Full substance inventory management
  • SDS authoring
  • MRSL / ZDHC screening
  • Pricing: Custom (typically €5K-20K/year)

Best for: Chemical manufacturers and formulators.

4. Assent Compliance — Supply Chain Data Management

Assent offers broader supply chain compliance for electronics and automotive.

  • Full material declaration management
  • RoHS / REACH / Conflict Minerals / PFAS
  • Supplier engagement platform
  • Pricing: Custom (typically €10K-50K/year)

Best for: Enterprise companies with dedicated compliance teams.

Feature Comparison

Feature Sustalium GreenSoft Toxnot Assent
RoHS declarations ✅ ✅ ✅ ✅
REACH declarations ✅ ✅ ✅ ✅
Supplier portal ✅ ❌ ✅ ✅
Certificate expiry tracking ✅ ✅ ✅ ✅
DoC generation ✅ ❌ ❌ ❌
QR code compliance docs ✅ ❌ ❌ ❌
Multi-regulation (ESPR, GPSR, EUDR) ✅ ❌ ❌ ❌
Pay-as-you-go pricing ✅ (€10/doc/month) ❌ ❌ ❌
Starting price €10/month ~€3K/year ~€5K/year ~€10K/year

Feature Comparison

Feature Sustalium GreenSoft Toxnot Assent
RoHS declarations ✅ ✅ ✅ ✅
REACH declarations ✅ ✅ ✅ ✅
Supplier portal ✅ ❌ ✅ ✅
Certificate expiry tracking ✅ ✅ ✅ ✅
DoC generation ✅ ❌ ❌ ❌
QR code compliance docs ✅ ❌ ❌ ❌
Multi-regulation (ESPR, GPSR, EUDR) ✅ ❌ ❌ ❌
Pay-as-you-go pricing ✅ (€10/doc/month) ❌ ❌ ❌
Starting price €10/month ~€3K/year ~€5K/year ~€10K/year

Implementation Timeline

Week 1: Setup

  • Create account and configure company profile
  • Import component catalogue (CSV upload)
  • Select electronics framework

Week 2: Supplier Onboarding

  • Invite component suppliers to portal
  • Suppliers submit RoHS declarations
  • Upload existing test reports and certificates

Week 3: Screening

  • Run substance threshold screening
  • Flag near-threshold components
  • Cross-reference with REACH SVHC for combined compliance

Week 4: Go Live

  • Generate product-level RoHS declarations
  • Create Declarations of Conformity
  • Share documents with retailers / distributors

Frequently Asked Questions

What's the difference between RoHS and REACH?

RoHS restricts specific substances in electrical and electronic equipment. REACH covers all chemical substances in all products. If your product has electronics, you need both. Sustalium handles both with a single supplier declaration.

How often do I need to update RoHS declarations?

At minimum annually, plus whenever the restricted substances list changes or you switch component suppliers.

Do I need a RoHS declaration for every component?

Yes — and that's why software is essential. A single product can have 50-500 components, each requiring its own supplier declaration. Software automates collection and consolidation.

Can one software platform handle RoHS and REACH together?

Yes. Sustalium maps supplier chemical data to both regulations simultaneously — one supplier submission fulfills both RoHS and REACH requirements.

Last updated: June 23, 2026

RoHS vs REACH: Supplier Compliance Requirements

Quick answer

RoHS restricts hazardous substances in electrical and electronic equipment; REACH governs the chemicals used anywhere in a product through registration and SVHC declarations. Suppliers need a RoHS compliance statement per product plus REACH SVHC declarations when a candidate list substance exceeds 0.1% by weight. Understanding the difference between RoHS and REACH is essential for any company placing electrical or electronic equipment on the European market. While both regulations deal with hazardous substances, they serve different purposes, cover different product ranges, and have different compliance requirements. This practical comparison focuses on the supplier requirements that matter most for SMEs and manufacturers.

RoHS vs REACH at a glance

Aspect RoHS REACH
Primary focus Restriction of specific hazardous substances in electrical and electronic equipment Registration, evaluation, authorisation and restriction of chemical substances
Product scope Electrical and electronic equipment (EEE) All chemical substances in all products
Key substances Lead, mercury, cadmium, hexavalent chromium, PBB, PBDE, DEHP, BBP, DBP, DIBP Thousands of substances, including SVHC (Substances of Very High Concern)
Compliance mechanism Supplier declarations, DoC, CE marking Registration with ECHA, technical dossiers, safety assessments
Thresholds Concentration limits (e.g., 0.1% for most substances) Registration threshold (1 tonne/year across all EU uses)
Testing Threshold screening of restricted substances Chemical safety assessment, technical dossier
Retention Keep for the life of the product plus 3 years (CPSC recommendation) Keep for 10 years after the product is placed on the market

RoHS supplier requirements

What RoHS requires from suppliers

If you manufacture or import electrical and electronic equipment (EEE) into the EU, your suppliers must provide evidence that restricted substances are below the threshold limits. The key supplier requirements are:

  • Material declarations: Suppliers must declare the presence and concentration of the 10 restricted substances in their materials/components.
  • Test reports: Laboratory test reports demonstrating that the substance concentrations are below the RoHS thresholds.
  • Declaration of Conformity: A statement asserting that the component or product complies with RoHS requirements.
  • Up-to-date information: Supplier declarations must be current; substance restrictions can change, and new substances may be added.

RoHS threshold limits (by substance)

Substance Maximum concentration
Lead (Pb) 0.1% (1000 ppm)
Mercury (Hg) 0.1% (1000 ppm)
Cadmium (Cd) 0.01% (100 ppm)
Hexavalent chromium (Cr(VI)) 0.1% (1000 ppm)
PBB (polybrominated biphenyls) 0.1% (1000 ppm)
PBDE (polybrominated diphenyl ethers) 0.1% (1000 ppm)
DEHP (phthalate) 0.1% (1000 ppm)
BBP (phthalate) 0.1% (1000 ppm)
DBP (phthalate) 0.1% (1000 ppm)
DIBP (phthalate) 0.1% (1000 ppm)

RoHS declaration framework

A RoHS declaration typically includes:

  • Product identification (name, model, batch number)
  • Supplier identification (name, contact details)
  • Statement of compliance with RoHS
  • List of restricted substances and their concentrations
  • Test report references
  • Signature of the responsible person
  • Issue date

REACH supplier requirements

What REACH requires from suppliers

REACH applies to all chemical substances, not just those in EEE. Key supplier requirements include:

  • Registration: If you import or manufacture 1 tonne or more of a substance per year across all EU applications, you must register it with ECHA.
  • Substance information: Suppliers must provide the name, CAS number, classification, and safety information for each substance.
  • Technical dossier: A dossier describing the substance's properties and uses, prepared by the registrant.
  • Safety data sheets (SDS): Must be available for all substances imported or manufactured above 1 tonne/year.
  • Downstream user obligations: Companies using chemicals must inform downstream users of any risks and appropriate risk management measures.

REACH declaration framework

A REACH declaration or registration typically includes:

  • Substance identity (name, CAS number, EC number)
  • Registration status (registered, exempt, in progress)
  • Tonnage range (1-10, 10-100, 100-1000, 1000+ tonnes/year)
  • Classification and labelling information
  • Safety assessment summary (for carcinogenic, mutagenic or toxic to reproduction substances)
  • Contact information for the registrant

How Sustalium handles both regulations simultaneously

Sustalium maps supplier chemical data to both RoHS and REACH requirements with a single supplier submission. The key features include:

  • Unified supplier portal: One submission covers both RoHS threshold screening and REACH registration status.
  • Automatic cross-referencing: Substance data is automatically checked against both RoHS thresholds and REACH registration requirements.
  • Dual declaration generation: One submission generates both a RoHS Declaration of Conformity and REACH registration information.
  • Tonnage tracking: The platform tracks whether your substance usage crosses the 1-tonne/year REACH registration threshold.
  • Hazard communication: Both RoHS threshold warnings and REACH SVHC flags are displayed alongside each other.

Practical scenario: electronics manufacturer

An electronics manufacturer importing components from 20 different suppliers:

  • Without Sustalium: Each supplier submits separate RoHS declarations and REACH information. The manufacturer must reconcile 40+ documents, check for conflicts, and maintain separate records for each regulation.

  • With Sustalium: Each supplier submits one chemical data package. Sustalium automatically:

  • Screens against RoHS thresholds (are any restricted substances above the limits?)
  • Checks REACH registration status (is the substance registered? above 1 tonne/year?)
  • Generates both a RoHS DoC and REACH registration summary from the same data
  • Flags any substance that requires attention under either regulation
  • Maintains a single audit trail for both regulations

Practical scenario: fashion brand importing textiles

A fashion brand importing textile products:

  • Without Sustalium: Must manage REACH for chemical substances in dyes and finishes, plus any RoHS requirements for embedded electronics (e.g., wearable technology).

  • With Sustalium: The platform identifies which substances in the textile product fall under REACH, screens for RoHS if the product contains any electronic components, and generates the appropriate declarations for both regulations from a single data entry.

Key takeaways

  • RoHS is focused on 10 specific hazardous substances in EEE, with concentration thresholds and supplier declarations.
  • REACH covers all chemical substances, with a 1-tonne/year registration threshold and comprehensive dossiers.
  • A product can be subject to both regulations – especially electronics that contain both electrical components and chemical substances.
  • Sustalium simplifies compliance by unifying supplier data, automating threshold screening for both regulations, and generating the appropriate declarations from a single submission.

Key takeaways (TL;DR)

Aspect RoHS REACH
Substances 10 specific restricted substances Thousands of substances, including SVHC
Threshold Concentration limits (0.1%/0.01%) 1 tonne/year registration threshold
Supplier action Submit declarations, test reports Register with ECHA, provide SDS, technical dossier
Sustalium One submission covers both regulations Unified data, automatic screening, dual declarations

Deep dive: For the complete requirements, deadlines and the fields reviewers check, open the Sustalium compliance page for REACH & RoHS declarations.

Last updated: June 23, 2026

How to share verifiable compliance proof with buyers

When you sell compliance‑regulated products – whether it is a CE‑marked device, a DPP‑registered product, or an FSMA‑204‑tracked food item – buyers often need proof that your product meets the required standards. The way you present that proof can influence a purchasing decision, a customs clearance or an audit result.

Why the format of proof matters

Buyers, auditors and customs officers see many documents. A PDF attachment emailed on request is easy to ignore or lose. A public, verifiable page with a QR code that can be scanned in seconds carries more weight. The difference is not just convenience – it is about trust and speed.

If a buyer is evaluating multiple suppliers, the one that can instantly demonstrate compliance with a simple scan has a competitive advantage. If an auditor is checking a sample shipment, being able to produce a hash‑verified declaration on the spot avoids delays.

What "verifiable" means in practice

Verifiable proof means the recipient can confirm the document's authenticity and content without having to call you or exchange emails. In the Sustalium approach, this works through:

  • A public URL – each product or asset gets its own page on the Sustalium platform. The page is indexed and can be accessed by anyone with the link.
  • A QR code – printed on product packaging, shipment labels or sales collaterals. Scanning the code opens the same public page in a browser.
  • Hashcode verification – every generated document (Declaration of Conformity, DPP, traceability plan) receives a unique hash. The recipient can run a quick check (via the platform or a dedicated tool) to confirm the hash matches the document you describe. If the hash does not match, the document has been altered.
  • Multi‑language support – the same public page can display the declaration in the buyer's language, while the underlying data remains unchanged.

Common proof formats buyers ask for

Format Typical use case Verifiability
PDF attached to email Informal supplier evaluation Low – recipient must trust the sender
Signed PDF with digital signature Formal tenders or audits Medium – signature can be verified, but requires software
Public URL with QR code Sales portals, trade shows, packaging High – anyone can scan and view
DPP public page with hashcode Electrical goods, toys, packaging High – hash confirms document integrity
FSMA 204 traceability plan (exportable) Food importers, customs High – structured data, 24‑hour availability

How Sustalium enables verifiable proof

If you use the platform, sharing compliance proof becomes a one‑click activity:

  • Generate a public page – each asset, product or framework output gets its own URL. The page shows the key compliance declarations, a summary of the data you entered, and any applicable certificates.
  • Create a QR code – with one click, you can download a QR‑PNG that links to the public page. Print it on your packaging, labels or sales sheets.
  • Share the hashcode – the platform displays a unique hash for each generated document. You can include this hash in your sales material; the buyer can run the same hash‑check on their end to confirm the document has not been altered.
  • Switch languages – the public page can be viewed in the buyer's language without generating a new document. The underlying data stays the same.
  • Archive and retrieve – every generated document is stored for the required retention period (10 years for DoC, 5 years for CBAM records, etc.) and can be re‑issued at any time if the buyer requests an updated version.

Step‑by‑step: sharing a CE‑derived proof

  1. Enter your product data in Sustalium (materials, standards applied, test results).
  2. Generate the Declaration of Conformity – the platform produces a PDF and a public page.
  3. Download the QR code – print it on your product label or shipment document.
  4. Share the page link – include the URL in your sales portal, email signature or product catalogue.
  5. Include the hashcode – if the buyer wants extra assurance, share the hash; they can verify it against the platform output.
  6. Update if needed – if you change a material or apply a new standard, regenerate the page and QR code; the old hash becomes invalid, ensuring only current proof is circulating.

Step‑by‑step: sharing FSMA 204 traceability proof

  1. Complete your traceability plan in Sustalium (lot numbers, growing location, processing date, first processor).
  2. Export the plan – the platform produces a structured file (CSV/JSON) ready for customs submission.
  3. Generate a QR code – link to the plan's public summary page.
  4. Attach to shipment docs – include the QR code on the commercial invoice or packing list.
  5. Tell the buyer – "Scan the code to see the 24‑hour traceability record for this lot."
  6. If customs asks – you can produce the full plan within 24 hours from the platform archive.

Checklist: what makes proof "verifiable"

  • Publicly accessible – the recipient does not need a login or your permission to view it.
  • Current – the document reflects the latest material and standard versions.
  • Hash‑protected – a unique identifier that detects any post‑generation changes.
  • Language‑ready – displayed in the buyer's language without re‑creating the document.
  • Retention‑compliant – kept for the legally required period (10 years for DoC, 5 for CBAM, etc.).
  • Easy to share – QR code or short URL that fits on packaging or sales material.

Quick use case: exhibition booth

At a trade show, you have a booth with product samples. Instead of handing out PDFs that the visitor might never open:

  1. Print a small QR code on your booth signage.
  2. The QR code links to the product's Sustalium public page.
  3. The page shows "CE marked, RoHS compliant, 80+ frameworks supported".
  4. The visitor scans, sees the proof instantly, and can save the page link.
  5. Later, the visitor's procurement team can reference the same page during vendor evaluation.

Further resources

  • Sustalium help centre – "Creating and sharing public compliance pages" guide
  • European Commission – "CE marking: How to use the declaration of conformity" booklet
  • FDA – "New Era of Smarter Food Safety" traceability tools guide

Key takeaways

Verifiable proof – a public URL with QR code and hashcode – is now expected by buyers and auditors. It builds trust faster than email attachments and speeds up customs or due‑diligence checks. Sustalium's one‑click public page and hash verification makes this accessible for any SME.

SMETA and Sedex audit evidence – what you need to know

Quick answer

SMETA audit evidence is the documented proof behind a Sedex-appraised SMETA 4-Pillar or 2-Pillar audit: labour rights, health and safety, environmental and business-ethics records. You assemble wage records, working-hours data, safety documentation and corrective action plans, and share them through the Sedex platform so buyers see a single audited profile. If you source from or supply to companies that operate in global supply chains, you have probably encountered SMETA audit reports or Sedex platform registrations. They are the most widely used frameworks for ethical and compliance risk assessment in supply chains, especially in retail, textiles and manufactured goods.

What SMETA actually is

SMETA (Sedex Members Ethical Trade Audit) is a standardised audit methodology produced by Sedex, a not‑for‑profit membership organisation. It is not a certification – it is an audit report that captures what was found at a specific site at a specific point in time.

There are four pillars in a typical SMETA audit:

  1. Labour standards – working hours, wages, freedom of association, no child or forced labour.
  2. Health and safety – workplace conditions, fire safety, personal protective equipment, accident reporting.
  3. Environment – waste management, energy use, water consumption, emissions.
  4. Business ethics – bribery, corruption, legal compliance, contract compliance.

An audit is conducted by an approved SMETA audit company. The auditor visits the site, interviews workers, reviews documents and takes photos. The result is a report that contains findings (pass/fail or observation), corrective‑action requests and a summary of the site's ethical‑trade performance.

What Sedex platform membership adds

Sedex is the online database where companies store and share supply‑chain data. Membership gives you:

  • A secure place to keep audit reports, membership certificates and related documents.
  • The ability to share selected data with trading partners (suppliers, customers, NGO).
  • Self‑assessment questionnaires that can be filled in between formal audits.
  • Industry‑specific tools – for example, the Food Protocol or the Chemical Programme add‑ons.

Many companies use Sedex as their central supply‑chain ethics hub. A site that has a current SMETA audit uploaded to Sedex is often viewed as "lower risk" by buyers who do not want to commission their own audit.

Why the audit report matters for your business

If you are a supplier, having a current SMETA report uploaded to Sedex can:

  • Shorten the questionnaire cycle – many buyers will accept a recent SMETA report in lieu of their own long audit questionnaire.
  • Demonstrate transparency – it shows you have had an independent third party look at your working conditions and environmental practices.
  • Identify gaps – the corrective‑action section tells you exactly what needs to be fixed, and by when.
  • Track progress over time – if you commission a SMETA audit annually, you can see whether your corrective actions are resolving the original findings.

If you are a buyer, a supplier's SMETA report helps you:

  • Reduce duplication – you do not need to send your own auditor to the same site.
  • Set baseline expectations – the report tells you the minimum standards the supplier is meeting.
  • Prioritise improvement – the corrective‑action requests tell you where to focus your supplier‑development efforts.

Common pitfalls we see

  • Assuming SMETA is a "certification" – it is not. It is a snapshot audit. A site can have a good SMETA report one year and drift significantly the next if no corrective actions are taken.
  • Only looking at the summary score – the real value is in the detailed findings and corrective‑action requests. A high overall score can mask specific serious issues (e.g., forced labour or severe health‑safety deficiencies).
  • Keeping the report in a personal folder – if the only copy of the SMETA report is in the procurement manager's email inbox, the rest of the organisation cannot access it when needed. Uploading to Sedex or a shared compliance repository fixes this.
  • Not updating the report – regulations and customer expectations change. A SMETA audit that is three years old may not reflect current expectations (especially around climate‑related environmental criteria or newer worker‑wellbeing topics).

How Sustalium simplifies SMETA‑related workflows

Sustalium's platform does not replace a SMETA audit, but it streamlines the data‑management side that usually follows an audit:

  • Audit‑findings tracker – you can import the findings from a SMETA report (or any third‑party audit) into Sustalium. Each finding is recorded as an item with a due date, responsible owner and status (open, in progress, resolved). This turns a static PDF into an actionable task list.
  • Corrective‑action documentation – you can attach evidence (photos, policy updates, training records) to each corrective‑action item. Over time, you build a digital trail that shows auditors or buyers what you have done to address the original findings.
  • Supplier‑certificate library – SMETA audit reports, Sedex membership certificates and any related third‑party validations are stored centrally and indexed. You can retrieve the correct report in seconds when a buyer requests it.
  • Linking audit data to product outputs – if you use Sustalium to generate DPPs, public compliance pages or traceability plans, the audit‑findings data can be referenced. For example, a public page can note "SMETA‑audited factory – working‑hours compliance verified 2025".
  • Progress reporting – you can generate a simple internal report that shows, for each SMETA pillar, how many findings were open at the last audit, how many have been resolved, and what the next review date is. This can be shared with buyers or internal stakeholders without attaching PDFs.

Step‑by‑step: turning a SMETA report into action

  1. Receive the SMETA report (PDF) from your audit company.
  2. Upload the report to Sustalium (or your chosen compliance repository).
  3. Import the findings – for each finding, enter: description, severity, responsible person, due date, and current status.
  4. Assign corrective actions – for every "open" finding, create a concrete task (e.g., "Update break‑room policy to include 48‑hour maximum weekly working hours – due 2026‑02‑15 – owner: HR manager").
  5. Attach evidence – upload the new policy document, training attendance sheets, or photos of the improved workspace.
  6. Mark as resolved – when the task is complete, change the status to "resolved" and add a brief note. The audit report now has a live "what we did" section.
  7. Upload the updated status to Sedex – if your organisation is a Sedex member, you can upload the revised findings or a summary of resolved items to your Sedex profile, so trading partners see the progress.

Checklist: SMETA‑ready supplier

  • Current SMETA audit report uploaded to Sedex (or available on request)
  • Key findings and corrective‑action requests documented in a task‑tracking system
  • Evidence attached to each corrective action (policy updates, photos, training records)
  • Report reviewed annually; next audit scheduled
  • Corrective actions tracked for completion (open/closed dates visible)
  • Summary of progress shared with key trading partners when requested

Further resources

  • Sedex – "How SMETA works" page and list of approved audit companies
  • Sedex – Food Protocol and Chemical Programme guidance (if your sector applies)
  • Sustalium help centre – "Importing audit findings" walkthrough and template library

Key takeaways

A SMETA audit is a snapshot, not a certification. The real value is in the findings and corrective‑action tracker. Importing those findings into a task‑tracking system turns a static PDF into a live compliance process that buyers can audit without re‑commissioning your site.

Textile compliance software for fashion brands 2026

Fashion brands face a growing landscape of regulatory requirements – from REACH and GRS to OEKO-TEX and country-specific mandates. Managing compliance across global supply chains is complex, and many brands struggle with scattered data, inconsistent supplier responses, and the inability to provide verifiable proof to buyers and regulators.

Why textile compliance software matters

Fashion brands typically source from 50–200+ suppliers across different countries, each providing different sets of compliance data. Without a centralized system, brands often:

  • Scattered data: Supplier certificates, REACH declarations, and test reports live in email inboxes and shared folders – impossible to retrieve when a buyer or regulator asks.
  • Inconsistent standards: Different suppliers provide different subsets of compliance data, making it impossible to compare or aggregate.
  • No public proof: Brands cannot easily provide verifiable compliance proof to buyers, hurting sales and sustainability claims.
  • Regulatory risk: Missing or outdated compliance data can lead to fines, import blocks, or reputational damage.

Textile compliance software centralizes all compliance data in one platform, automates supplier reminders, and generates verifiable public proof with a single click.

Key features to look for

Feature Why it matters for fashion brands Red flag
Supplier-certificate library – a centralized place to store REACH declarations, OEKO-TEX certificates, and other compliance documents you receive from suppliers. You already receive these from suppliers; the software should index them, not make you re‑type them. "No document storage" – you will end up in the same email‑folder situation you started with.
Chemical-compliance check – the software flags restricted substances (e.g., azo dyes, phthalates, heavy metals) based on the materials you entered and marks whether REACH compliance can be claimed. You want to avoid costly product recalls or buyer rejections due to hidden restricted substances. "No chemical screening" – you will still be manually checking substance lists.
Public compliance pages – each compliance artefact gets a public URL with a QR code that buyers can scan. Buyers and investors increasingly expect instant, verifiable proof. "PDF only – email us for the document" is a red flag.
Multi‑language support – the same data can generate compliance pages in the languages you sell into (DE, FR, ES, EN). You sell in multiple European markets. "Each language requires a separate product entry" defeats the purpose of a data layer.
Hash‑verified declarations – every generated declaration receives a unique hash. Buyers or auditors can run a verification check to confirm the document has not been altered after generation. Audit and buyer confidence require document integrity. "No hash verification" – documents can be altered after generation without detection.
Pay‑as‑you‑go pricing – subscriptions under €200/year or one‑off fees for core features. Compliance spend should not consume a significant part of the operating budget. "Custom quote required" – if you have to ask for a price, it is likely too expensive for an SMB.
Email / chat support – not just a ticket system with a 48‑hour SLA. When you are stuck on a regulation, you want an answer the same day. "Only web‑form support" – too slow for time‑sensitive compliance questions.

How Sustalium supports textile compliance

Sustalium’s platform is built for fashion brands and textile SMEs, so you can start small and add depth as you grow:

  • REACH and GRS management – you input the substances your textiles use (dyes, finishes, trims), and the platform flags restricted substances based on REACH and the Global Recycled Standard (GRS). You can record the status for each substance: not applicable, in progress, or compliant.
  • OEKO‑TEX integration – you can record OEKO‑TEX certification status for each product, and the platform will generate the appropriate compliance statements.
  • Supplier-certificate library – you can upload the REACH declarations, OEKO‑TEX certificates, and other compliance documents you receive from suppliers. The platform indexes them so you can retrieve them in minutes rather than hunting through email folders.
  • Public compliance pages – each compliance artefact gets a public URL with a QR code. You can share this link in buyer communications, on your website, or in your sustainability report. The page displays the key compliance declarations in plain language, and the recipient can verify the hash if they wish.
  • Multi‑language support – the public page can be viewed in the language of the buyer or market you are targeting, without re‑creating the document. The underlying data remains a single source of truth.
  • Hashcode verification – every generated declaration receives a unique hash. Buyers or auditors can run a verification check to confirm the document has not been altered after generation.
  • Five‑year archive – all compliance data, generated pages and hash records are stored centrally and retained for the required period, with search functionality if a regulator or buyer requests historical data.

Step‑by‑step: setting up textile compliance in Sustalium

  1. Input your product profiles – product name, style/sku, collection, basic description.
  2. Enter material composition – for each fibre type, enter the weight percentage (e.g., 70% organic cotton, 25% recycled polyester, 5% elastane). The platform validates that the total equals 100%.
  3. Add supplier certificates – upload REACH declarations, OEKO‑TEX certificates, and other compliance documents you receive from suppliers. Tag them by product for easy retrieval.
  4. Run the chemical‑compliance check – the platform flags any restricted substances (e.g., azo dyes, phthalates, heavy metals) based on the materials you entered and marks whether REACH/GRS compliance can be claimed.
  5. Generate public compliance pages – with one click, the platform produces public pages with QR codes for your key products. Share this link in buyer communications, on your website, or in your sustainability report.
  6. Update when anything changes – if you switch to a different dyehouse or a different certified recycled‑polyester source, edit the material composition once; the public pages and QR codes update automatically.

Common textile compliance pitfalls

  • Ignoring the fibre‑percentage rule – the total must always equal 100%. If you list "cotton 70%" and "polyester 40%" without noting the overlap, the data is invalid.
  • Omitting the manufacturing location – the compliance data should include at least the final assembly country.
  • Assuming the software replaces the care label – compliance data is a data layer; care‑label information (washing temperature, ironing) should still be on the physical label, but can be referenced from the compliance page.
  • Not updating the compliance data when you change suppliers – if you switch to a new dyehouse or a different certified recycled‑polyester source, the compliance data changes; the public pages must be regenerated to stay accurate.

Checklist: is your textile compliance ready?

  • Material composition entered with total = 100 %
  • Manufacturing locations recorded
  • REACH and/or GRS status recorded for each product
  • Supplier certificates uploaded and indexed
  • Public compliance pages generated and QR codes printed on products
  • Page content reviewed for accuracy (matches actual product)
  • Hashcode displayed on the page or in the product documentation
  • Plan for updates when materials or suppliers change

Real‑world use case: mid‑size fashion brand

A brand with 30 SKUs womenswear uses Sustalium to:

  • Enter the fibre composition for each SKU once (e.g., "80% Tencel lyocell, 20% silk").
  • Generate a public compliance page for each SKU; the QR code appears on the online product page and the physical hangtag.
  • When a wholesale buyer asks for sustainability proof, the brand sends the QR code link instead of a PDF. The buyer scans it, sees the material breakdown and REACH compliance status, and can verify the hash if desired.
  • When the brand switches to a lower‑impact dyehouse for the next season, they edit the chemical‑usage data in Sustalium; the public pages update automatically, and the old hash becomes invalid (ensuring only current data is circulating).

Further resources

  • OEKO‑TEX – "Standard 100" and "Made in Green" certification guides
  • GRS – Global Recycled Standard requirements and documentation guide
  • Sustalium help centre – "Textile compliance setup guide" (step‑by‑step with screenshots)

Key takeaways

Textile compliance software should offer supplier‑certificate management, chemical‑compliance checking, public‑facing compliance pages with QR codes, multi‑language support, and hash‑verified declarations at a pay‑as‑you‑go price point. Sustalium provides all of these features, built specifically for the fashion and textile industry.

Key takeaways (TL;DR)

  • Centralised data – one platform for REACH, GRS, OEKO‑TEX and other compliance documents.
  • Public proof – QR‑coded compliance pages that buyers and auditors can verify instantly.
  • Hazard screening – automatic flagging of restricted substances based on REACH and GRS.
  • Pay‑as‑you‑go pricing – under €200/year for SME‑focused compliance software.