Chapter 3 — full chapter
Chapter 3 — full chapter
3.7 Material Sustainability Analyzer by FashionKIC
Every material decision is a trade-off made with incomplete information: the recycled option may save water but use more energy; the bio-based fibre may beat cotton on carbon but lose on durability; the cheaper blend may be the one your factory cannot actually source. The FashionKIC Material Sustainability Analyzer is designed to support the preliminary environmental assessment and comparison of fashion and textile materials and recommend more sustainable alternatives, while remaining transparent about data quality and methodological limitations (Finnveden et al., 2009).
The Material Sustainability Analyzer database was built and enriched using data from the following sources:
- Textile Exchange – Life Cycle Inventory (LCI) Library: environmental/LCA data for textile materials.
- FashionMatImpact (Hugging Face): additional material and environmental impact data used to expand the material database.
- Sustainable Fashion: Eco-Friendly Trends (Kaggle): used mainly for additional material information and enrichment, including eco-scores, country of origin, and certifications.
We then processed, cleaned, merged, and standardized these data into the internal material database used by the Material Sustainability Analyzer.
Data sources:
Textile Exchange LCI Library
FashionMatImpact dataset
Sustainable Fashion: Eco-Friendly Trends dataset
The analyzer is a screening and comparison aid, not a substitute for a product-specific life-cycle assessment. Users should record data year, geography, system boundaries and uncertainty, verify supplier-specific information where possible, and avoid presenting a relative score as an absolute environmental claim (Finnveden et al., 2009).
A practical workflow starts by defining the product function and the properties that cannot be compromised. Compare only materials that can meet those requirements, use the same units and system boundaries, and separate measured supplier data from proxy values. Review both the total score and the indicators that drive it; an average can hide a serious burden or a weak result for durability. Sensitivity testing helps show whether the recommendation remains stable when uncertain inputs change.
Results should be communicated as conditional evidence, not as a universal ranking. Save the dataset version, access date, assumptions and any manual adjustments with the project file. Before using a result in a public claim, confirm it with product-specific evidence and applicable verification requirements. The tool is most useful when it narrows options, reveals data gaps and prompts a better supplier conversation; final approval still requires technical performance, cost, availability and circular-recovery checks (Finnveden et al., 2009; Niinimäki et al., 2020).