The EU Digital Product Passport Is an Export, Not a Rebuild

2027 is the first sell-date when EU textiles must ship with a Digital Product Passport, and the mandate is specific in field terms: composition by percentage, chemicals and test data, country and process steps, recycled content and certificates, care and repairability, and a unique identifier resolvable via a QR or digital link. Treat that as your engineering spec. The fastest brands will not rebuild for it. They will export it from the same structured garment record they already use to brief factories and power their sales channels. Compliance as use means one machine-readable record that serves the regulator and the AI agent from one source.

The 2027 Export: Build Once, Ship Twice

The Digital Product Passport is a schema and an audit trail with a QR at the edge. It rewards brands that run a connected pre-production workflow where material facts are captured in fields, versioned, and signed. If the garment record is already machine-readable, the passport is a filtered export. If the record lives in scattered PDFs, emails, and supplier PDFs, the passport becomes a rebuild project with manual data entry, vendor chases, and late-season rework.

There is a second reason to build once. The market is saturated with AI image generators and campaign tools. They are interchangeable and they produce pixels. A pixel is not machine-readable. An AI shopping agent that stands between the shopper and your catalog cannot verify fibre content from a render, cannot map the product into the right meaning space, and cannot cite it to the user. The F* Word is not an image generator. It is the validation and orchestration layer that produces the structured garment record: the asset plus the machine placement data plus the machine recommendation data that makes an agent confident enough to surface the product.

The operating point from The F* Word team's book, The Machine-Readable Brand, is simple: mandates accumulate between 2026 and 2030 and none of them phases out. If you solve the passport as a one-off sustainability project, you add permanent overhead. If you treat it as the first export of a single record, every new mandate becomes another export template, not another scramble. That is the compliance stack strategy the book outlines, and it starts in pre-production, not in a PDF afterthought.

One validated garment record exporting to a Digital Product Passport, feeds and AI retrieval

The Popular Framing Is Wrong: This Is Not a Sustainability Project

The passport is not a narrative about your footprint. It is structured-data regulation with a deadline. Sustainability language often centers on story, targets, and initiatives. The passport asks for verifiable, referenceable, machine-parsable facts tied to a unique product identifier. If you house those facts in a living record that your sourcing team already maintains, compliance is maintenance. If you try to retrofit them from CSR decks and campaign copy, compliance is rework.

Where the framing goes off course:

It gets staffed to the sustainability desk. Most passport fields sit with product development and sourcing. Chemical tests, BOM percentages, origin routing, and construction notes live in tech packs and supplier declarations. The sourcing desk owns the facts and the fabric codes.
It starts after design lock. By then, fabric substitutions and trim changes have already shifted composition and sometimes country-of-origin math. The passport wants the final truth. If you do not capture changes as they happen, you end up reconciling contradictions at the tail end.
It treats images as evidence. Photos and renders are marketing assets. They do not carry the claims an agent or a regulator will read. The data of record must live as fields with proofs.

If you want a simple cost model, consider this illustrative math: 1 hour per style to reconcile composition sources, 2 hours to obtain and attach chemical and recycled-content documents, 30 minutes to assign and test a QR, and 30 minutes to proof the page. On a 2,000-style year, a rebuild costs 8,000 to 10,000 hours before exceptions. An export from a verified record reduces that to minutes per style for final checks.

Side-by-Side: Passport Fields vs Your Current Record

caption

Passport requirement	Where it lives today	Verification needed	Effort with one record	Effort without	Also used by AI agents
Material composition by percentage	Tech pack BOM, supplier BOM spreadsheet	Final BOM roll-up, version history, fabric codes	Auto-roll from BOM, lock at PP sample sign-off	Manual reconcile across PDFs and emails	Fiber tags, comfort and care inference, attribute precision
Restricted substances and chemical test data	Supplier declarations, lab test reports	Valid lab certificate, date, lot linkage	Attach report to material lot in record	Chase suppliers, re-request, re-sample	Safety claims, regional eligibility, filter confidence
Origin and processing steps	POs, packing lists, vendor matrix, route plans	Facility IDs, country codes, process timestamps	Pull from supplier master and PO lineage	Rebuild chain from emails and invoices	Shipping time estimates, duty rules, local recommendations
Recycled content and certification	Supplier certificate PDFs, trim specs	Certificate number, scope, expiry, batch mapping	Map cert to material lot and BOM percent	Manual match, risk of mismatch or expiry	Eco-attribute labeling, agent explainability
Care, durability, and repairability	Care label spec in tech pack, construction notes	Standards reference, stitch and seam specs	Export care codes and link construction notes	Rewrite from copy, risk of inconsistency	Post-purchase prompts, size and use suitability
Unique identifier and QR resolution	GTIN/UPC in merchandising system, assorted QR vendors	Persistent URL, redirect governance, item-to-QR map	Generate from canonical ID and route by locale	Late-season sticker work and mislinks	Product page fetch, agent citation, recall routing
Packaging materials and recyclability	Packing spec, vendor manual	Material codes, weights, supplier attestations	Include packaging line items in BOM	Contact DC and vendors, estimate by weight	Fulfillment impact, total footprint estimation
Repair parts and access to instructions	Service SOPs, ad-hoc PDFs, brand site pages	Spare part SKUs, instruction URL, language coverage	Publish repairables and link to SKU-map	New content build, translation rushes	Agent post-purchase support, returns reduction

Side-by-Side: Passport Fields vs Your Current Record: supporting image for eu digital product passport fashion

What Production-Ready Actually Requires

Production-ready means your garment has a canonical record with schema, identifiers, evidence, and exports. It is not another dashboard. It is a set of primitives the whole company reuses.

Schema and IDs. Decide the garment as the primary entity. Assign a stable product ID that survives season and locale variants. Pair it with a GTIN where needed and a QR that resolves to a persistent URL. Store every field the passport asks for in that record, with data types and units.
Supplier and material lineage. Connect material records to suppliers, facilities, and lots. Each attachment is an object: test report, certificate, invoice, or time stamp. The record should show which lot was used in which style and at what percent. That is how you pass an audit and also answer an agent when it asks for proof.
Version control and sign-offs. Lock composition and care at PP sample approval or fit confirmation. Keep a change log that shows who changed which field and when. Emit a machine-verifiable signature or at least a checksum for the export.
Serialization and QR routing. Generate QR codes from your IDs. Point them to a stable resolver domain you control. Route by locale to show the correct language and regulation block without changing the code.
Exports, not copy-paste. Produce the EU Digital Product Passport as a data export. Also produce an AI agent feed that includes the same facts, plus merchandising attributes like style intent and use context.

This is where The F* Word sits in your stack. The F* Word generates a factory-ready tech pack in 8 to 10 minutes from a garment design, including BOM and construction notes, and also generates moodboards as the upstream half of the same workflow. It is not a PLM, not a 3D sim, and not an image generator. It is the validation and orchestration layer that turns the creative intent into a verified record that you can export to factories, regulators, and agents. See the pre-production flow described at thefword.ai/pre-production-workflow-software-fashion and how creative direction connects at thefword.ai/creative-direction-workflow-fashion-brands.

Bridge back to the agent point. The market is full of AI tools that output beautiful imagery. That category is commoditized and does not move the passport or the agent needle. Agents read fields, units, provenance, and care. When your record holds those fields and you export them, you win both the compliance check and the recommendation slot. The F* Word's role is to make that record production-grade, auditable, and exportable.

A Decision Framework for VP Product, Design, and Merch

For workflow buyers and sourcing leaders:

Make ownership explicit. Assign the product record to the VP Product Development or Director Sourcing. Sustainability advises. Legal reviews. IT provisions access. The owner signs off on the export.
Adopt export-first architecture. Keep PLM where it is if it works. Put an orchestration layer on top that reads design inputs, writes the BOM and construction notes, and validates supplier attachments. This is how you avoid PLM surgery and still get a machine-readable record. The F* Word operates as that layer.
Supplier operating model. Maintain a clean supplier master with facility IDs and country codes. Standardize how test reports and certificates are submitted. Time-box submissions to PP sample stage. Tie late submissions to change control.
Governance and cadence. Ship a monthly passport export dry run by category starting now. Publish exceptions. By 2026, move to weekly runs tied to buys.

For in-house designers and creative directors:

Design in structured intent. Moodboards and references should map to material families, construction methods, and functional attributes so the record can infer test plans and care. The F* Word generates moodboards and then produces the tech pack in 8 to 10 minutes, which means your choices carry through to BOM and factory-ready notes without a second translation.
Accept constraints early. If a recycled nylon option lacks valid certification for Q3, picking it in concept costs more later. Work with sourcing on viable libraries and let the record show proofs as you design.

For merchandisers:

Attach commercialization context. Add region, channel, size run, and pricing bands to the same record so the agent feed can reason about availability and fit. This avoids separate spreadsheets that drift.
Use the same identifier. Your SKU strategy should map to the canonical product ID so the QR, the passport, and the PDP stay in lockstep.

If you want a shorthand, use the Export vs Rebuild test. If a field cannot be produced without emailing a supplier or opening a PDF, you are on a rebuild path. If the field exists as a value with a change log, you are on an export path. Shift fields one by one into export status before 2026 and you de-risk the cutover.

Getting Started: A 2026 Readiness Sequence

Use this four-step sequence. It is sequenced to minimize lift and concentrate ownership with the sourcing desk, not the sustainability desk.

Define the record and assign IDs. Pick the garment record schema. Include composition, chemicals, origin steps, recycled content, care, repairability, packaging, and the unique identifier. Map every field to a current source. Assign the product ID and pick the QR resolver pattern. Document the sign-off points.
Connect creative to the BOM. Put The F* Word in front of your design team so the system generates moodboards and then a factory-ready tech pack in 8 to 10 minutes from each design, including BOM and construction notes. This moves composition and care into structured fields early and avoids later reconciliation. It also aligns with your merchandising launch plan. Reference workflow coordination at thefword.ai/ai-fashion-merchandising-launch-workflow.
Operationalize supplier evidence. Standardize how labs and vendors submit test reports and certificates. Attach them to material lots inside the record. Add expiry checks. Require facility IDs and country codes for each process step on POs. Set due dates at PP sample or T&A milestones so the passport does not trail shipping.
Ship exports and practice. Produce a DPP test export and an AI agent feed in parallel. Render the QR and test resolution in two locales. Run a mock audit. Have merchandising and legal review the public view. Fix gaps. Repeat monthly until the exception rate is under 5 percent.

This is a sourcing-led program. The fields live with BOMs, vendors, and labs. Sustainability and brand comms benefit, but they do not hold the keys. When you treat the passport as an export, the team that already manages the record leads the work, and the company gains a reliable feed for agents at the same time.

One last planning note. The compliance stack will get denser from 2026 to 2030. None of it phases out. Use the stack logic from The Machine-Readable Brand page to plot your exports by mandate and region. The same record can output DPP for the EU, a safety and care card for another region, and a full-fact agent feed for global catalogs. That is how you convert compliance into distribution.

Frequently Asked Questions

What counts as the unique product identifier for the passport in fashion?

You need a persistent ID that links a physical unit to its digital record. Most brands pair an internal product ID with a GTIN and expose a QR that resolves to a stable URL. The key is persistence and governance so the URL and the fields behind it do not rot across seasons and locales.

How should we handle legacy seasons and carryovers?

Start with carryovers and core programs because the BOM and supplier sets are stable. Backfill fields that the passport expects and attach proofs where they exist. For deep legacy, create a cutline by risk and value, then treat anything below the line as a basic page with minimal claims while you rebuild upstream processes for new seasons.

Do we need a new PLM or 3D system to comply?

No. You need a verified, exportable garment record. Keep PLM if it serves you and add an orchestration layer that validates fields, captures proofs, and emits the passport. The F* Word is that layer. It is not a PLM, not a 3D sim, and not an image generator, and it produces a factory-ready tech pack in 8 to 10 minutes from a design, including BOM and construction notes.

Who should own the program day to day?

Assign ownership to the VP Product Development or Director Sourcing, with legal and sustainability as stakeholders. The data lives in BOMs, supplier attestations, and POs, so sourcing has the levers to make it accurate. Set a weekly cross-functional review to clear exceptions and lock exports on cadence.

Start free at thefword.ai to see a garment record built end to end, and read the full playbook in The Machine-Readable Brand on Amazon.