Skip to main content
Symolem
Back to all articles
Textile DPP Data Requirements: Essential Checklist

Textile DPP Data Requirements: Essential Checklist

October 6, 2026 18 min read

What data goes in a textile digital product passport, and which fields are actually required? The answer isn’t a fixed checklist yet. As of October 2026, the European Commission has not adopted the textile-specific delegated act; the Joint Research Centre’s May 2026 preparatory study proposed 49 data points, but proposals aren’t binding requirements. Treating every suggested field as law creates confusion. Treating none as a preparation priority creates a different risk.

Supplier records are often fragmented across products, facilities and value-chain tiers. A fibre claim may sit in a brand’s product file, a spinning mill’s records in India and dyeing data with a Turkish supplier, with no clear link between the claim and its evidence. An estimate, a supplier declaration and a verified test report aren’t interchangeable.

This article sets out the textile data categories to assess, from product identity and material composition to traceability, chemicals, environmental information and circularity. It also explains how to label each field’s legal status, evidence basis, owner and access level, so your team can distinguish current obligations from proposed fields and practical preparation choices. The result is a prioritised route from scattered supplier records to governed product data.

Key Takeaways

  • Separate ESPR framework provisions from textile-specific obligations established by applicable measures; don’t label potential data points as legal requirements without that basis.
  • Map what data goes in a textile digital product passport by grouping fields across product identity, materials, production, use and end-of-life.
  • Assess each field’s source, evidence, accountable owner, update trigger and intended audience to expose gaps and control access.
  • Build a prioritised data map around a defined product scope and record each field’s status, evidence and ownership.
  • Use an ESPR readiness diagnostic to structure compliance records, verify supporting evidence and assign a Verification ID for use with a chosen DPP provider or retail onboarding system.

What data goes in a textile Digital Product Passport under the ESPR framework?

A Digital Product Passport (DPP) is structured product information linked to a product through a data carrier, such as a QR code, that enables the information to be accessed. The carrier provides a route to the data; it doesn’t prove that the data is complete, accurate or legally compliant. A QR code pointing to a platform is not evidence that a fibre composition claim is verified or that the applicable legal requirements have been met.

The key distinction is between the ESPR framework and the product-specific rules that determine a category’s required data. The framework establishes the basis for product passports, including product identification, information access and interoperable data. Applicable product measures set out which information fields must be supplied, who can access them and when the requirements apply.

For textile teams asking what data goes in a textile digital product passport, the answer must be tied to the relevant product category and current legal measures. A data-point map should make that distinction visible instead of treating every proposed or commonly used field as mandatory.

To see a broader explanation of how Digital Product Passports are being developed, watch this video:

What does the ESPR framework establish for product passports?

The framework is not a universal textile data template. It sets the architecture within which product-specific rules can require a passport, identify the information to include and define access arrangements. Interoperability matters because product data must be structured for exchange and retrieval across relevant systems, not trapped in disconnected files or presented only as unstructured documents. The applicable measure determines the binding field-level obligations for the product concerned.

Is there one definitive textile DPP data list in 2026?

No single list should be treated as universally binding for every textile product. As of October 2026, no textile-specific ESPR delegated act has been adopted, so proposed fields and industry protocols must not be represented as enacted textile obligations. Applicability depends on the current legal measures for the product category and their effective dates. Check those measures before making a compliance claim.

Classify each proposed field using four labels:

  • Adopted requirement: expressly required by an applicable legal measure for the product and market in scope.
  • Proposed measure: included in preparatory work or a draft, but not yet an adopted obligation.
  • Operationally useful: helps substantiate a claim, manage supplier records or prepare implementation, without being presented as legally required.
  • Not yet determined: the applicable rules have not settled whether, how or at what level the field must be reported.

A candidate data field is not a confirmed legal obligation unless an adopted measure makes it applicable to the product in scope. For example, a brand may find facility information useful for connecting a garment to its production stages, while the specific legal requirement and reporting granularity remain subject to the applicable textile measure. Keep the source and status beside the field, and revisit both as rules develop. That prevents a practical preparation choice from being mislabelled as law, while preserving a clear record of what is still unresolved.

Which textile DPP data categories should brands assess first?

Start with the product and work outwards. A useful textile data map distinguishes information that describes the product itself from records held by suppliers, production facilities, the brand or a particular batch. That separation helps teams identify what can be reliably linked to a product and where evidence is missing, without assuming every candidate field is a legal requirement.

For each category, assess relevance against the product scope and applicable measures before assigning a mandatory status. The European Commission identifies textiles as a priority area in its overview of ESPR and Digital Product Passports, but that does not make every commonly discussed textile field universally required.

What product identity and composition information may be relevant?

Assess product identifiers, product category, model or style references, and batch details where available. Then map fibre composition and materials or components at a level your source records support. A bill of materials may describe the garment’s fibre mix, while a supplier declaration or test report may substantiate a specific material attribute. Record which source supports each value rather than merging unlike evidence.

Substances-of-concern information may also be relevant, but applicability depends on the product and applicable requirements. Don’t infer a legal duty from a field appearing in an industry template. Identify the relevant rule and product scope, then record what evidence supports the information.

Which supply-chain and product-life data categories should teams assess?

Map supplier and production-stage records where they support provenance or an applicable requirement. For example, a spinning mill in India may hold fibre or yarn records, a dyeing house in Turkey may hold process documentation, and a CMT factory in Portugal may hold assembly and production records. Keep facility identity, supplier identity and batch-specific evidence distinct; one supplier record shouldn’t automatically be treated as proof for every product or production run.

Assess product-life information as separate candidate categories, not as one broad “circularity” field. Care instructions, repair or reuse guidance, and end-of-life information each have different sources and purposes. Some may be useful for product communication or future implementation planning, but their presence in a data map alone doesn’t establish a legal obligation.

  • Product level: identity, category, composition and product-specific characteristics.
  • Supplier or facility level: source and production-stage records tied to the relevant site or organisation.
  • Batch level: evidence that applies to a defined production run rather than every version of a product.
  • Brand level: records or claims controlled by the brand, with their own source and substantiation.

Environmental impact and recycled-content values need the same discipline. Treat them as evidence-backed values with a defined source and scope, not as unqualified marketing statements; an estimate, supplier declaration and verified report are not interchangeable. For a broader view of how these categories fit into implementation planning, consult the textile DPP implementation framework. The practical priority is to map potential data points now, preserve their provenance and avoid labelling them mandatory until the applicable measure supports that conclusion.

How should textile DPP data status, evidence, and access be assessed?

A textile data field is not ready for use merely because it has been entered in a system. Teams need to know its legal status, source, supporting evidence, accountable owner, update trigger and intended audience. These dimensions should be assessed together, so a required field with weak evidence is visible as a gap, not mistaken for compliance.

Traceability connects a product value to the supplier, facility, batch or record it came from. Verification asks a different question: does the evidence support the value being reported? A traceable claim can still be inaccurate, outdated or based on an estimate.

How can teams assess whether textile DPP data is reliable?

Record the source system, supplier or facility, collection date, method and supporting document for each material claim. Then label the value as verified, estimated, missing or conflicting; don’t collapse these states into a single “complete” field. If supplier documents disagree, preserve the discrepancy and assign an owner to resolve it rather than selecting a value without a documented basis.

Data provenance is the recorded history of a value, including its source, collection method and supporting evidence; it lets teams assess whether a product-level claim is traceable and substantiated.

Use a data-point map to keep the assessment operational. The entries below are examples of how to structure that register, not a declaration that each field is legally required for every textile product.

FieldStatusSource recordOwnerEvidenceAccess
Fibre compositionConfirm against applicable measureBill of materials or supplier recordProduct complianceSupporting supplier documentationAs required by applicable rules
Production facilityAssess scope and legal basisSupplier or sourcing systemSourcingFacility record linked to product or batchRole-based, subject to legal rules
Recycled-content claimCandidate field; verify applicabilityMaterial or transaction recordsMaterials teamEvidence supporting the stated valueShare according to audience and rules
Care informationAssess applicable requirementProduct specificationProduct developmentApproved care dataConsumer-facing where appropriate

Which textile DPP information should be public or restricted?

Access is a separate decision from legal status. A field may be legally required without being intended for unrestricted public viewing; conversely, a brand may choose to publish useful product information that isn’t a specific legal requirement. Assess commercial sensitivity, the intended audience and applicable rules independently for each field.

Role-based access can help distinguish information intended for consumers from records shared with supply-chain actors or authorities, but it’s an implementation choice that must operate within applicable legal requirements. Map who needs each record and why, then document the access decision and its owner. For related Digital Product Passport data governance and security considerations, include permissions and evidence controls in the same implementation plan.

•	what data goes in a textile digital product passport

How can a fashion brand build a defensible textile DPP data map?

A defensible data map starts with a defined boundary. Specify the product group, intended market, regulatory assumptions and a representative product before collecting fields; otherwise, teams risk combining records that apply to different products, production runs or legal contexts. Record assumptions explicitly, including what remains uncertain, and revisit them when the applicable measures or product scope change.

Then build a data-point map that connects each data point to its definition, legal status, source, owner, evidence, access decision and current gap. This is a governance tool, not just an inventory. It shows whether a field is supported by existing records, needs supplier follow-up or requires a decision about scope.

What should a textile DPP data-point map record?

Give every field a plain-language definition, format, unit where relevant and applicable product scope. Record its legal status, source system or supplier, accountable owner, collection method and review trigger, such as a specification change or updated supplier evidence. Add a gap status and a named remediation action. If the value is unknown, record it as unknown; never fill the gap with an assumed figure.

  • Field definition: what the value describes, its expected format and the products it covers.
  • Governance: legal status, accountable owner, source, evidence location and access decision.
  • Control: collection method, review trigger, gap status and next action.

How should teams organise supplier evidence across value chains?

Map each field to the party best placed to substantiate it. A supplier may hold a process record, while the brand owns the product specification and approves the final claim. Before requesting information across tiers, align field definitions, units, permitted formats and the product or batch identifiers needed to connect the response to the right item.

Trace existing records first. Search product lifecycle, sourcing, quality and compliance systems, then identify supplier documentation already held before issuing new requests. This reduces duplicate requests and exposes whether the weakness is missing evidence, inconsistent formats, unclear ownership or an absent link between the record and the product. The DPP implementation challenges can help teams account for data collection and governance risks.

Prioritise gaps by regulatory relevance, evidence weakness, dependencies and remediation effort. A field tied to an applicable requirement and supported only by an unsubstantiated claim deserves different treatment from a useful operational field with a clear source. Resolve dependencies early: if a product value relies on a supplier record, establish who can provide it and how it will be linked before treating the product record as complete.

This approach turns the question of what data goes in a textile digital product passport into a managed work plan: scope the product, map existing records, assign owners, and track gaps without disguising uncertainty as evidence. Structure and prioritise your textile DPP data map with Symolem’s ESPR readiness support.

How does Symolem support textile DPP data readiness?

Data readiness is a governance and evidence problem, not a software-only task. An ESPR readiness diagnostic helps scope the products and markets under review, establish the regulatory assumptions, and assess which records already exist across brand systems and suppliers. It then identifies where potential data points lack evidence, ownership is unclear, or the connection between a product and its supporting records is incomplete.

The operational question, what data goes in a textile digital product passport, is only one part of readiness. Teams also need to know which fields apply, what evidence supports each value, who maintains it and what happens when it changes. That assessment turns fragmented inputs into prioritised implementation work rather than a flat list of unverified data points.

When is specialist textile DPP data mapping useful?

Specialist support is useful when product information is spread across supplier records, internal systems and inconsistent material documentation. A diagnostic can map the field to its source, accountable owner and evidence status, then expose dependencies that need resolving before a record can be relied upon. This is particularly valuable where one product draws information from several value-chain tiers. The ESPR readiness diagnostic provides a starting point for structuring that assessment.

For example, a brand may have a product specification but still need to connect a material claim to supplier documentation and the relevant production record. Symolem supports the assessment and structuring of those compliance records, including the identification of missing evidence and unclear responsibilities. The result is a clearer basis for deciding what to retrieve, verify or govern next.

What should brands and retailers do next?

Brands can begin with representative products, identify the systems and supplier records that may support their fields, and assign an evidence owner to each gap. Retailers and marketplaces can assess third-party brand evidence before purchase orders are signed, so missing or weak substantiation is visible before a buying decision. Both need a clear distinction between a complete data field and a claim supported by appropriate evidence.

Symolem verifies and structures product compliance records and assigns a Verification ID. That ID can feed a chosen DPP provider or retail onboarding system; Symolem does not build or issue consumer passports. The value is in establishing a traceable, evidence-led record and a prioritised route to address gaps, not in treating a digital interface as proof of compliance.

For Retailers & Marketplaces: Screen third-party brand compliance before signing the PO. Explore Symolem-ID or run a free product scan.

For Fashion Brands: Need to retrieve missing Tier 1-3 supplier evidence or substantiate social accounting for retail stockists? Take the 5-minute Free Assessment or Book an Advisory Consultation.

Make your next step a governed data decision

The value of asking what data goes in a textile digital product passport lies in what your organisation does next: assign responsibility, protect the integrity of product claims and build a repeatable process for maintaining records as products and suppliers change. Don’t wait for every detail to be settled before establishing ownership and resolving evidence gaps. A clear governance structure gives teams a controlled way to adapt as applicable requirements develop.

Strengthen your textile DPP readiness with Symolem, through structured field mapping, evidence review and implementation prioritisation.

For Retailers & Marketplaces: Screen third-party brand compliance before signing the PO. Explore Symolem-ID or run a free product scan.

For Fashion Brands: Need to retrieve missing Tier 1-3 supplier evidence or substantiate social accounting for retail stockists? Take the 5-minute Free Assessment or Book an Advisory Consultation.

Build the evidence discipline now, and your teams will be better placed to respond with clarity as requirements take shape.

Frequently Asked Questions

What data goes in a textile Digital Product Passport?

The applicable data depends on the product category and legal measures in scope. A brand might organise records around product identification, fibre and component details, production references, care information and end-of-life guidance, then establish which fields apply to the specific product. The answer to what data goes in a textile digital product passport should therefore be recorded against a defined product and market, not copied wholesale from another brand’s template.

Is there a mandatory textile DPP data list in 2026?

As of October 2026, there isn’t one adopted textile-specific list that applies universally to all textile products. The product-specific ESPR delegated act for textiles has not been adopted, so potential data points in preparatory work shouldn’t be labelled binding requirements. Before making a compliance claim, document the product category, market and applicable legal measure, then check the measure’s requirements and application date against the product’s actual scope.

Can a QR code alone make a textile product passport compliant?

No. A QR code can act as a data carrier, but it doesn’t establish that the linked information is accurate, complete, current or accessible to the right audience. Test the full pathway: scan the code, confirm it resolves to the intended product record, check that permitted users can retrieve relevant information, and confirm that the underlying values have supporting records. A functioning link is a technical check, not evidence of legal compliance.

How should brands verify textile DPP data?

Check each value against its original record and confirm that the document applies to the relevant product, material or production period. For example, a fibre declaration should identify what product or input it covers, who supplied it and when it was collected. Record unresolved conflicts rather than choosing the most convenient figure. Set review triggers for changes to specifications, suppliers or supporting documents, so outdated evidence doesn’t continue to support a live claim.

Which textile DPP data should be public?

There is no safe assumption that every passport field should be publicly visible. Decide access field by field, considering applicable legal rules, the intended audience and commercial sensitivity. Consumer-facing product information may need different handling from detailed supplier records used by business partners or authorities. Keep an access rationale with the data-point map, and ensure that confidentiality choices don’t restrict information that an applicable rule requires to be available.

Should textile DPP data be recorded at product, batch, or item level?

The required level depends on the applicable product rules, and the textile-specific granularity decision remains unsettled in the information available for 2026. Operationally, brands should first identify whether an existing record describes a style, a production run or a single item. For instance, a batch test report shouldn’t be attached to every product version unless its scope genuinely covers them. Keep the level explicit so later requirements can be mapped accurately.

How can a brand distinguish required DPP fields from recommended data?

For each field, record the legal source and the provision that makes it applicable to the product and market. If the field appears only in a draft, study, industry protocol or internal template, label it accordingly rather than calling it mandatory. Recommended operational data can still be valuable for substantiating claims or coordinating suppliers. Keep that value, but separate its business purpose from its legal status and schedule review when rules change.

Article infographic

Frequently Asked Questions

The framework is not a universal textile data template. It sets the architecture within which product-specific rules can require a passport, identify the information to include and define access arrangements. Interoperability matters because product data must be structured for exchange and retrieval across relevant systems, not trapped in disconnected files or presented only as unstructured documents. The applicable measure determines the binding field-level obligations for the product concerned.

No single list should be treated as universally binding for every textile product. As of October 2026, no textile-specific ESPR delegated act has been adopted, so proposed fields and industry protocols must not be represented as enacted textile obligations. Applicability depends on the current legal measures for the product category and their effective dates. Check those measures before making a compliance claim. Classify each proposed field using four labels: A candidate data field is not a confirmed legal obligation unless an adopted measure makes it applicable to the product in scope. For example, a brand may find facility information useful for connecting a garment to its production stages, while the specific legal requirement and reporting granularity remain subject to the applicable textile measure. Keep the source and status beside the field, and revisit both as rules develop. That prevents a practical preparation choice from being mislabelled as law, while preserving a clear record of what is still unresolved. Start with the product and work outwards. A useful textile data map distinguishes information that describes the product itself from records held by suppliers, production facilities, the brand or a particular batch. That separation helps teams identify what can be reliably linked to a product and where evidence is missing, without assuming every candidate field is a legal requirement. For each category, assess relevance against the product scope and applicable measures before assigning a mandatory status. The European Commission identifies textiles as a priority area in its overview of ESPR and Digital Product Passports, but that does not make every commonly discussed textile field universally required.

Assess product identifiers, product category, model or style references, and batch details where available. Then map fibre composition and materials or components at a level your source records support. A bill of materials may describe the garment’s fibre mix, while a supplier declaration or test report may substantiate a specific material attribute. Record which source supports each value rather than merging unlike evidence. Substances-of-concern information may also be relevant, but applicability depends on the product and applicable requirements. Don’t infer a legal duty from a field appearing in an industry template. Identify the relevant rule and product scope, then record what evidence supports the information.

Map supplier and production-stage records where they support provenance or an applicable requirement. For example, a spinning mill in India may hold fibre or yarn records, a dyeing house in Turkey may hold process documentation, and a CMT factory in Portugal may hold assembly and production records. Keep facility identity, supplier identity and batch-specific evidence distinct; one supplier record shouldn’t automatically be treated as proof for every product or production run. Assess product-life information as separate candidate categories, not as one broad “circularity” field. Care instructions, repair or reuse guidance, and end-of-life information each have different sources and purposes. Some may be useful for product communication or future implementation planning, but their presence in a data map alone doesn’t establish a legal obligation. Environmental impact and recycled-content values need the same discipline. Treat them as evidence-backed values with a defined source and scope, not as unqualified marketing statements; an estimate, supplier declaration and verified report are not interchangeable. For a broader view of how these categories fit into implementation planning, consult the textile DPP implementation framework. The practical priority is to map potential data points now, preserve their provenance and avoid labelling them mandatory until the applicable measure supports that conclusion. A textile data field is not ready for use merely because it has been entered in a system. Teams need to know its legal status, source, supporting evidence, accountable owner, update trigger and intended audience. These dimensions should be assessed together, so a required field with weak evidence is visible as a gap, not mistaken for compliance. Traceability connects a product value to the supplier, facility, batch or record it came from. Verification asks a different question: does the evidence support the value being reported? A traceable claim can still be inaccurate, outdated or based on an estimate.

Record the source system, supplier or facility, collection date, method and supporting document for each material claim. Then label the value as verified, estimated, missing or conflicting; don’t collapse these states into a single “complete” field. If supplier documents disagree, preserve the discrepancy and assign an owner to resolve it rather than selecting a value without a documented basis. Data provenance is the recorded history of a value, including its source, collection method and supporting evidence; it lets teams assess whether a product-level claim is traceable and substantiated. Use a data-point map to keep the assessment operational. The entries below are examples of how to structure that register, not a declaration that each field is legally required for every textile product.

Access is a separate decision from legal status. A field may be legally required without being intended for unrestricted public viewing; conversely, a brand may choose to publish useful product information that isn’t a specific legal requirement. Assess commercial sensitivity, the intended audience and applicable rules independently for each field. Role-based access can help distinguish information intended for consumers from records shared with supply-chain actors or authorities, but it’s an implementation choice that must operate within applicable legal requirements. Map who needs each record and why, then document the access decision and its owner. For related Digital Product Passport data governance and security considerations, include permissions and evidence controls in the same implementation plan. A defensible data map starts with a defined boundary. Specify the product group, intended market, regulatory assumptions and a representative product before collecting fields; otherwise, teams risk combining records that apply to different products, production runs or legal contexts. Record assumptions explicitly, including what remains uncertain, and revisit them when the applicable measures or product scope change. Then build a data-point map that connects each data point to its definition, legal status, source, owner, evidence, access decision and current gap. This is a governance tool, not just an inventory. It shows whether a field is supported by existing records, needs supplier follow-up or requires a decision about scope.

Give every field a plain-language definition, format, unit where relevant and applicable product scope. Record its legal status, source system or supplier, accountable owner, collection method and review trigger, such as a specification change or updated supplier evidence. Add a gap status and a named remediation action. If the value is unknown, record it as unknown; never fill the gap with an assumed figure.

Map each field to the party best placed to substantiate it. A supplier may hold a process record, while the brand owns the product specification and approves the final claim. Before requesting information across tiers, align field definitions, units, permitted formats and the product or batch identifiers needed to connect the response to the right item. Trace existing records first. Search product lifecycle, sourcing, quality and compliance systems, then identify supplier documentation already held before issuing new requests. This reduces duplicate requests and exposes whether the weakness is missing evidence, inconsistent formats, unclear ownership or an absent link between the record and the product. The DPP implementation challenges can help teams account for data collection and governance risks. Prioritise gaps by regulatory relevance, evidence weakness, dependencies and remediation effort. A field tied to an applicable requirement and supported only by an unsubstantiated claim deserves different treatment from a useful operational field with a clear source. Resolve dependencies early: if a product value relies on a supplier record, establish who can provide it and how it will be linked before treating the product record as complete. This approach turns the question of what data goes in a textile digital product passport into a managed work plan: scope the product, map existing records, assign owners, and track gaps without disguising uncertainty as evidence. Structure and prioritise your textile DPP data map with Symolem’s ESPR readiness support. Data readiness is a governance and evidence problem, not a software-only task. An ESPR readiness diagnostic helps scope the products and markets under review, establish the regulatory assumptions, and assess which records already exist across brand systems and suppliers. It then identifies where potential data points lack evidence, ownership is unclear, or the connection between a product and its supporting records is incomplete. The operational question, what data goes in a textile digital product passport, is only one part of readiness. Teams also need to know which fields apply, what evidence supports each value, who maintains it and what happens when it changes. That assessment turns fragmented inputs into prioritised implementation work rather than a flat list of unverified data points.

Specialist support is useful when product information is spread across supplier records, internal systems and inconsistent material documentation. A diagnostic can map the field to its source, accountable owner and evidence status, then expose dependencies that need resolving before a record can be relied upon. This is particularly valuable where one product draws information from several value-chain tiers. The ESPR readiness diagnostic provides a starting point for structuring that assessment. For example, a brand may have a product specification but still need to connect a material claim to supplier documentation and the relevant production record. Symolem supports the assessment and structuring of those compliance records, including the identification of missing evidence and unclear responsibilities. The result is a clearer basis for deciding what to retrieve, verify or govern next.

Brands can begin with representative products, identify the systems and supplier records that may support their fields, and assign an evidence owner to each gap. Retailers and marketplaces can assess third-party brand evidence before purchase orders are signed, so missing or weak substantiation is visible before a buying decision. Both need a clear distinction between a complete data field and a claim supported by appropriate evidence. Symolem verifies and structures product compliance records and assigns a Verification ID. That ID can feed a chosen DPP provider or retail onboarding system; Symolem does not build or issue consumer passports. The value is in establishing a traceable, evidence-led record and a prioritised route to address gaps, not in treating a digital interface as proof of compliance. For Retailers & Marketplaces: Screen third-party brand compliance before signing the PO. Explore Symolem-ID or run a free product scan. For Fashion Brands: Need to retrieve missing Tier 1–3 supplier evidence or substantiate social accounting for retail stockists? Take the 5-minute Free Assessment or Book an Advisory Consultation. The value of asking what data goes in a textile digital product passport lies in what your organisation does next: assign responsibility, protect the integrity of product claims and build a repeatable process for maintaining records as products and suppliers change. Don’t wait for every detail to be settled before establishing ownership and resolving evidence gaps. A clear governance structure gives teams a controlled way to adapt as applicable requirements develop. Strengthen your textile DPP readiness with Symolem, through structured field mapping, evidence review and implementation prioritisation. For Retailers & Marketplaces: Screen third-party brand compliance before signing the PO. Explore Symolem-ID or run a free product scan. For Fashion Brands: Need to retrieve missing Tier 1–3 supplier evidence or substantiate social accounting for retail stockists? Take the 5-minute Free Assessment or Book an Advisory Consultation. Build the evidence discipline now, and your teams will be better placed to respond with clarity as requirements take shape.

The applicable data depends on the product category and legal measures in scope. A brand might organise records around product identification, fibre and component details, production references, care information and end-of-life guidance, then establish which fields apply to the specific product. The answer to what data goes in a textile digital product passport should therefore be recorded against a defined product and market, not copied wholesale from another brand’s template.

As of October 2026, there isn’t one adopted textile-specific list that applies universally to all textile products. The product-specific ESPR delegated act for textiles has not been adopted, so potential data points in preparatory work shouldn’t be labelled binding requirements. Before making a compliance claim, document the product category, market and applicable legal measure, then check the measure’s requirements and application date against the product’s actual scope.

No. A QR code can act as a data carrier, but it doesn’t establish that the linked information is accurate, complete, current or accessible to the right audience. Test the full pathway: scan the code, confirm it resolves to the intended product record, check that permitted users can retrieve relevant information, and confirm that the underlying values have supporting records. A functioning link is a technical check, not evidence of legal compliance.

Check each value against its original record and confirm that the document applies to the relevant product, material or production period. For example, a fibre declaration should identify what product or input it covers, who supplied it and when it was collected. Record unresolved conflicts rather than choosing the most convenient figure. Set review triggers for changes to specifications, suppliers or supporting documents, so outdated evidence doesn’t continue to support a live claim.

There is no safe assumption that every passport field should be publicly visible. Decide access field by field, considering applicable legal rules, the intended audience and commercial sensitivity. Consumer-facing product information may need different handling from detailed supplier records used by business partners or authorities. Keep an access rationale with the data-point map, and ensure that confidentiality choices don’t restrict information that an applicable rule requires to be available.

The required level depends on the applicable product rules, and the textile-specific granularity decision remains unsettled in the information available for 2026. Operationally, brands should first identify whether an existing record describes a style, a production run or a single item. For instance, a batch test report shouldn’t be attached to every product version unless its scope genuinely covers them. Keep the level explicit so later requirements can be mapped accurately.

For each field, record the legal source and the provision that makes it applicable to the product and market. If the field appears only in a draft, study, industry protocol or internal template, label it accordingly rather than calling it mandatory. Recommended operational data can still be valuable for substantiating claims or coordinating suppliers. Keep that value, but separate its business purpose from its legal status and schedule review when rules change.

Talk to a consultant

Have a question about how this applies to your brand?

Ask Lavinia Fernandes directly. Tell us your products and markets and you get a straight answer on what applies and what to do first.