The passport should disclose a bounded product record

As of 30 October 2026, the European Commission's textile passport page places adoption of the textile delegated act in Q4 2027 on an explicitly indicative timeline. It says exact information requirements will be defined through delegated acts and supporting technical specifications. That planned adoption is not a universal application deadline. A supplier should therefore distinguish preparing data from asserting compliance with a final textile schema.[S14]

The Commission describes the Ecodesign for Sustainable Products Regulation as framework legislation under which concrete product or horizontal rules are developed subsequently. Its implementation page describes working plans, impact assessments and consultation. Those stages explain why a useful data project can begin before every product-specific requirement is settled. They do not make a prototype's fields legally sufficient.[S15]

GFT recommends a policy register with separate entries for the framework, product-specific rulemaking, technical specifications and application conditions. Each entry should retain the official document, its status, the responsible reviewing role and the decision it affects. An entry without an established application condition should say that the condition remains to be confirmed. The register must not turn a consultation milestone into a shipment authorisation.

The proposed release process has distinct legal and evidential questions. The legal reviewer determines the applicable market and product obligations from current authoritative texts. The evidence reviewer determines whether the supplied records support the particular statement. A positive answer to either question cannot substitute for the other. This chapter is not investment, legal or tax advice. Clause-level legal analysis belongs to the companion legal paper and requires the relevant texts before any compliance claim is made.

A practical procurement brief should separate stable capabilities from changeable mappings. Stable capabilities include preserving evidence references, identifying the issuer, controlling disclosure and exporting the record. Changeable mappings include which fields a particular market requires, which vocabulary expresses them and which person must supply them. GFT recommends buying the ability to update those mappings under change control, with an auditable comparison of the old and new definitions.

Consider an illustrative buyer request for a passport described simply as compliant. The proposed response is a requirements clarification sheet within the project, not a compliance badge on the product. The sheet identifies product scope, intended market, applicable instrument, responsible operator and acceptance evidence. Until that mapping is approved, the interface should describe a voluntary product record. Commercial urgency does not resolve an unspecified legal test.

The Commission lists possible information categories including identification, composition, origin and use or repair information, subject to final requirements. Its sector overview separately describes rules on fibre names and composition labelling. GFT therefore recommends treating composition labelling, provenance evidence and future passport requirements as distinct review items. A composition statement does not establish where cotton grew, and an origin narrative should not displace the applicable composition review.[S14][S34]

A useful policy register also records what would trigger reconsideration: a revised requirement, a changed product category, a new destination market or an altered operator role. The proposed owner should assess the impact on existing records as well as future releases. Replacing the interface template without reviewing already issued claims would leave readers with inconsistent meanings under an apparently stable product identity.

GS1 Digital Link provides syntax for representing identification keys in web addresses, including batch and serial qualifiers. The resolver standard addresses discovery of related information and services through typed links. These standards help organise addressing and resolution. They do not by themselves establish that a physical garment carrying an address is the garment described at that address.[S12][S13]

GFT proposes treating carrier selection as an operating decision. The pilot should compare the intended label substrate, print process, attachment point and expected handling conditions. It should test whether people can find the identifier after ordinary use, whether the printed alternative remains readable and how replacement labels are authorised. No durability interval or scan-success result is assumed here; both need measurement under an agreed protocol.

The copied-code case should be demonstrated explicitly in the prototype. An illustrative legitimate batch record can be reached by a label attached to an unrelated item. The page can be technically available and the product record internally consistent while the attachment is wrong. GFT therefore proposes a reader message that explains what the code identifies, together with a discrepancy route for mismatched product descriptions. The message should avoid promising authentication from a successful scan.

The proposed operating controls include controlled label issue, reconciliation of replacement requests and retained links from retired labels to their replacements. A replacement should preserve the product identity where the physical identity has been established. It should not create an apparently new product merely to erase an unresolved mismatch. The responsible release role must decide whether a disputed attachment requires a warning, an identity investigation or suspension of the associated claim.

An illustrative counterfeit exercise should give the reviewer both a copied label and the original record, then ask what each proves. The expected conclusion is bounded: the label reveals a pointer, the record reveals the issuer's statements and the physical checks determine whether the attachment is credible. Designing the public interface around those separate questions prevents the familiar but unsupported inference that reachable information proves an authentic item.

GFT recommends an explicit carrier-to-record mapping with creation, replacement and retirement events. This is an interface requirement, not a replacement for the event exchange design in the preceding chapter. The mapping should reference the controlled product identity and retain the authorising decision for each change. A buyer receiving a record export should be able to distinguish a replaced carrier from an altered product claim without guessing from file names.

The reader also needs a route that does not require scanning. GFT proposes a printed identifier and a short route to a search form, with understandable error messages when the identifier is not found. The search result should show the product boundary before offering deeper evidence. A failure to resolve should remain a retrieval failure until investigated; it should not automatically accuse a supplier or certify the item as false.

Operational acceptance should include deliberately awkward conditions: partial print damage, a replaced label, the wrong batch suffix and an unavailable evidence link. The proposed review should record what the user saw and whether the next action remained clear. Passing only the pristine-label case would leave the design's central uncertainty untreated. The full adverse-case pilot remains the responsibility of the later pilot chapter, while this chapter defines the required disclosure behaviour.