5 Core Fields Fashion Brands Must Capture Now for EPCIS Traceability

!Decorative EPCIS traceability title card

In this guide, "EPCIS traceability" refers to Digital Product Passports (DPPs), the evidence-backed, machine-readable product records the EU is building into law. The immediate action for any fashion or ecommerce brand is simple: run a product-data audit now and lock in a stable identifier, ideally a GTIN. Start there. The European Commission's DPP hub becomes a reference, not a scramble.

TL;DR:

• Using GTIN as the product identifier helps ensure compatibility with retail systems and simplifies registration with the DPP registry.
• Prioritize capturing core data fields such as composition by weight, country of manufacture, and supplier identity to build a practical and compliant passport.
• Conduct a focused data audit, pilot a product line, and establish clear ownership and approval processes to develop a scalable DPP readiness plan.
• Publish passports via QR codes using resolvable URLs, hosting content either in-house or through a provider, with access tailored to different stakeholder groups.
• Guarantee evidence integrity by maintaining version logs, assigning data ownership, and ensuring human review of any AI-extracted information before publication.

• What Is a Digital Product Passport, and Why Does It Matter?
• Where Do DPPs Stand Legally Today, and What's the Timeline?
• What Core Data Should Apparel Brands Capture First?
• How Do You Build a Practical DPP Readiness Plan?
• How Do You Actually Publish a Passport?
• Should You Build In-House or Use a Platform Partner?
• What Should You Do This Quarter?
• What Technical Standards Govern DPP Data Exchange?
• What Privacy and Governance Rules Apply to Passport Data?
• What Does Successful Textile DPP Implementation Look Like?
• What Are the Biggest Pitfalls in DPP Deployment?
• What's Next for DPP and Product Traceability Technology?
• Author Perspective: Governance Is the Real Lever Here
• How DPP Grid Helps You Build Evidence-Backed Passports
• Sources
• FAQ

A DPP is a digital container for product data. It pairs a machine-readable data carrier, usually a QR code, with hosted content that answers what a product is made of, where it came from, and how to care for or recycle it. The Registry itself doesn't store your full passport content; it holds identifiers and registration metadata, while the substantive data lives on pages you or your service provider host, according to the European Commission.

Several groups will pull from that same record:

• Consumers checking materials, care, and repair options before or after a purchase
• Repairers and recyclers who need composition and disassembly data to process a garment correctly
• Market surveillance authorities verifying conformity claims
• Retailers and resale platforms confirming authenticity for a secondhand sale

The upside for brands runs past regulatory box-ticking. A published textile passport becomes the backbone for repair programs, take-back schemes, and resale verification, giving your product a documented life after the first sale, not just a compliance footnote.

The Ecodesign for Sustainable Products Regulation (ESPR) is the horizontal framework. It doesn't specify what a textile passport must contain; that job falls to delegated acts written product-group by product-group. Batteries went first. Textiles are named a priority group under the Commission's working plan, with delegated-act adoption targeted around 2027 and DPP use signaled for 2029 as an indicative schedule.

Here's what's actually operational versus what's still coming:

• Live now: Regulation 2026/1778 established the DPP Registry framework, and the Commission reported that a production Registry and test environment went live in July 2026.
• Not yet defined: the specific data fields textile brands must publish, which wait on the delegated act.
• The practical reality: Registry infrastructure exists before product-specific rules do.

Regulatory checkpoint: The Registry can validate semantic conformity and issue registration identifiers today, but that's an infrastructure milestone, not a green light to claim compliance for apparel. Treat readiness and certification as two separate things until the textile delegated act lands.

A European Parliament study mapping the textile DPP model757808_EN.pdf) lists 16 categories of useful information, from composition to transport to environmental impact. Trying to fill all sixteen at once is how projects stall. Prioritize instead.

1. Product identifier — a GTIN paired with your internal style code, so the record resolves cleanly through retail and registry systems alike.
2. Composition by weight — the fiber breakdown retailers already ask for on hangtags.
3. Country of manufacture — the single origin fact most compliance and customer-trust questions come back to.
4. Supplier identity — the economic operator behind the product, documented, not assumed.
5. Care and repair instructions — the fields that turn a passport into a service tool, not just a disclosure.

Behind each field sits evidence: lab test reports, supplier certificates, audit findings, transaction records. Decide your granularity deliberately. A style-level passport suits a core basics line; a batch record fits a dye lot with variable inputs; serialized, item-level records make sense for limited runs or anything reselling for real money.

Pro Tip: Capture these fields inside your PLM or PIM system the moment a product is authored, not months later during a compliance push. Retrofitting composition and origin data across a back catalog is far slower than building the habit into new-product setup from day one.

Waiting for the textile delegated act before touching your data is the single most expensive mistake a brand can make right now. The practical guidance from ESPR analysts is consistent: audit, choose an identifier, pilot, then govern.

1. Run a focused product-data audit. Pick one category, say outerwear, and map every field against what you can actually document today. The gaps you find are your work list.
2. Choose an identifier strategy. GTIN is the pragmatic default because it resolves through GS1 Digital Link and slots into retail systems you likely already touch.
3. Pilot one product line. Generate a passport, print QR codes, and test how it looks from both a consumer's phone and a wholesale buyer's system. Small pilots surface data problems a full rollout would multiply.
4. Set ownership and versioning rules. Decide who approves a supplier's certificate before it goes live, and how you track a revision when a supplier changes a formulation.

The operational note that matters most: centralize your evidence in one place, and put a human in the approval loop for anything AI helped extract. AI can pull a fiber percentage off a scanned certificate in seconds; it shouldn't be the last check before that number goes public.

Pro Tip: Treat your first pilot line as a stress test for your supplier relationships, not just your software. If a supplier can't produce a composition certificate in a week, that's the real bottleneck you'll hit at scale.

QR codes are the expected consumer-facing carrier, mostly because they need no app and work with a phone camera almost everyone already owns. NFC shows up on higher-value items where tap-to-scan feels more premium, but QR remains the pragmatic default for apparel at volume.

Identifier resolution matters as much as the carrier itself:

• GTIN plus GS1 Digital Link gives you a resolvable URL structure that both retail systems and consumer scans can follow to the same record.
• Registry registration confirms your identifiers and semantic structure meet the Registry's validation rules; it doesn't replace hosting your actual content.
• Hosting can sit on brand-owned passport pages or with a DPP service provider, and the tradeoff is control versus setup speed.
• Access models vary by audience: a public consumer view shows care and material basics, while authority-facing detail and machine-readable records for recyclers can sit behind more restricted or structured access.

Two paths lead to a working DPP program. The first is PIM/PLM-first: you build passport generation on top of systems you already run, which gives full control at the cost of engineering time you may not have spare. The second is a platform partner that handles hosting, evidence management, and registry onboarding, trading some control for speed.

Whichever path you pick, the feature checklist stays the same:

• Product import from Shopify, CSV, or API, so you're not retyping a catalog you already maintain
• Supplier-facing evidence upload, because certificates rarely originate inside your own team
• AI-assisted extraction paired with human approval, so a suggestion never quietly becomes a published fact
• Support for model, batch, and item-level records, matching the granularity decision from earlier
• QR and machine-readable publishing in one workflow
• Version history and audit logs, so a supplier update three months from now doesn't erase what you published today

Evidence workflows and version history aren't nice extras. When an authority or a retail partner asks where a composition figure came from, a timestamped approval trail is the difference between a five-minute answer and a week of digging through email threads. DPP Grid is built around exactly this checklist, and it's a fair yardstick to measure any option against, whether you use it or not.

Turn the plan above into owners and deadlines, or it stays a plan.

1. Data audit (Operations) — map every required field against what exists today for one product category.
2. Identifier selection (Product/Ops) — confirm GTIN coverage or assign new codes where gaps exist.
3. Pilot launch (Product + Ecommerce) — publish passports for one line and test consumer and buyer access.
4. Evidence gathering (Sourcing) — chase supplier certificates and lab reports before the pilot, not during it.
5. QR deployment (Operations) — print and apply codes to physical product or packaging.

Register with the central Registry once the applicable product schema for your category is published, not before. Registering early against a schema that doesn't exist yet just means redoing the work.

DPP data exchange leans on a stack of existing identification and data-carrier standards rather than one bespoke EU format. GTIN and GS1 Digital Link handle identifier resolution, turning a scanned code into a URL that points at your hosted passport content. That's the layer most brands interact with directly.

!EPCIS product data exchange standards flow

Underneath that, the Registry itself validates semantic conformity, meaning it checks that the structure and vocabulary of what you submit match an expected schema before issuing a registration identifier, per Registry implementation guidance. This is where the JRC's methodology work comes in: it's shaping how data granularity and stakeholder needs get formalized into those schemas, and industry groups have already pushed back on overly complex structures, asking for phased rollouts instead of a single hard cutover, according to sector coverage of the JRC framework.

For brands integrating passport data into existing systems, the practical work sits in mapping your PIM or ERP fields to whatever schema the eventual textile delegated act specifies, then exposing that data through an API your passport provider or in-house system can query at scan time. Partners building tracking and event APIs, such as Shurq's tracking API, illustrate the kind of structured data exchange this layer increasingly resembles, even outside the DPP context specifically.

None of this requires custom protocol work from a fashion brand. It requires clean, structured product data that maps cleanly onto whatever standard the schema eventually specifies, which is exactly why the audit-first approach from earlier in this guide pays off before the technical requirements even solidify.

Passport content splits into two very different categories, and governance needs to treat them differently. Product-level facts, composition, origin, care instructions, carry no personal data and can sit fully public. Ownership records, resale history, and repair logs tied to an individual owner are a different matter entirely, and they deserve the same handling discipline you'd apply to any customer record.

Access control should mirror the audience split covered earlier: consumers get a public view of material and care basics, while conformity documentation for market surveillance authorities and detailed process data for recyclers can sit behind more restricted or structured access rather than fully open publication.

Version integrity matters just as much as access control. A passport that gets silently edited after publication, with no record of what changed or when, undermines the entire point of an evidence-backed record. Every update, whether it's a supplier submitting a revised certificate or a brand correcting a country-of-origin field, needs a timestamp and an approval trail. That audit log is what turns a passport from a marketing page into something an authority or resale platform can actually trust.

Practically, this means assigning clear internal ownership for who can approve a change to published data, keeping supplier-submitted evidence separate from brand-approved final records until review happens, and never letting an AI-generated extraction go live without a person checking it against the source document first.

The clearest lesson from early textile DPP work isn't about software. It's about sequencing. Brands that treated composition, origin, and supplier data as fields to formalize inside their product systems before adding QR codes or serialization moved faster than brands that started with the consumer-facing passport page and worked backward.

The European Parliament's textile DPP research frames this as a lifecycle model: information gets captured at manufacturing, refined through the supply chain, and made available at the point of sale and beyond, through repair and eventual recycling. Brands that mapped their existing hangtag and retailer-required data, the composition and origin fields buyers already ask for, into a structured record found they'd already done most of the hard data-collection work. What remained was formatting and publishing it.

The granularity decision plays out differently by category too. A basics line with consistent inputs works fine at style level. A limited drop with variable dye lots or supplier changes benefits from batch-level records, since a single style-level passport would misrepresent some units. Premium or resale-heavy pieces justify item-level serialization, because authenticity and ownership transfer depend on a unique record per unit rather than a shared style description.

The common thread across categories that got this right: evidence lived in one governed system before the passport existed, not scattered across supplier email threads and shared drives. That's the operational discipline this guide keeps circling back to, because it's the part that determines whether a passport project takes months or years.

!What Does Successful Textile DPP Implementation Look Like? — overview diagram

The most common failure mode is treating a DPP as a one-time content project instead of an ongoing data process. A brand builds a beautiful passport page for one collection, then has no plan for what happens when a supplier changes, a certificate expires, or a new batch uses a different fiber blend. The passport goes stale within a season.

A second pitfall is chasing granularity you don't need. Serializing every SKU down to the individual unit sounds thorough, but for a basics line with stable inputs, it multiplies data-entry work without adding real value to the consumer or the authority reading it. Match the granularity to the product, as covered earlier, or the workload becomes self-defeating.

Third, and this one catches brands off guard: publishing AI-extracted data without human review. An AI tool can misread a percentage off a scanned certificate or misattribute a supplier location, and if that goes straight to a public passport, you've published an error under your own brand name. Human approval before publication isn't bureaucratic overhead; it's the single check that keeps a passport trustworthy.

Fourth, brands sometimes wait for the textile delegated act to start any work at all, then face a compressed timeline once it lands. The ESPR timeline guidance is explicit that early data-prep, identifier selection, and piloting avoid exactly this crunch. Waiting doesn't reduce work; it just compresses all of it into a shorter window later.

The fix for all four is the same governance habit: one system of record for evidence, clear ownership for approvals, and a granularity decision made deliberately rather than by default.

The Registry's production environment going live in 2026 is an infrastructure milestone, not a finished system. Expect the next phase of development to focus on the textile-specific schema itself, shaped by the JRC's data-requirement methodology and the pushback industry groups have already voiced about complexity and transition timing.

Integration is the other clear direction. As more product categories get their own delegated acts, brands selling across categories, apparel, footwear, accessories, will need passport systems that handle multiple schemas without duplicating data-entry effort for shared fields like supplier identity or country of manufacture. Platforms that support model, batch, and item-level records within one system, rather than requiring separate tools per granularity level, will have an edge here.

Resale and circularity features are likely to matter more, not less. A passport that supports ownership transfer and authenticity verification turns a compliance artifact into something that actively extends a product's commercial life through resale, repair tracking, and take-back programs. That's less a regulatory requirement than a business opportunity riding on the same underlying data infrastructure.

Expect data-carrier technology to diversify too, with NFC picking up ground on premium goods even as QR remains the practical default for mass-market apparel. None of this changes the core advice in this guide: the brands that treat product data as a governed asset now, rather than a compliance deliverable to assemble later, will adapt to each new schema and standard with far less disruption than those starting from scratch.

Most guidance frames DPPs as a sustainability initiative. That framing undersells what's actually required. A DPP program succeeds or fails on product-data governance: who owns a field, who approves a change, how evidence gets versioned. The capture-at-source principle, entering data once in your PLM or PIM at the moment of authoring, saves more time than any downstream tool ever will. Assign an owner to this now. Waiting for the textile delegated act to name your fields is waiting for permission you don't need.

— Vytautas

DPP Grid is the practical route to everything covered in this guide, without building passport infrastructure from scratch. It imports your catalog from Shopify, CSV, or API, collects supplier evidence directly instead of chasing email threads, and uses AI to extract fields like composition and origin, with a human review step before anything publishes.

!DDP Grid

The platform supports model, batch, and item-level records, so your basics line and your limited drop can each use the granularity that actually fits. Every passport publishes with a QR code and machine-readable data, and every edit keeps a version history, which matters the day a supplier certificate changes or an authority asks where a figure came from. Worth being clear about the limits: DPP Grid provides product-data infrastructure and readiness workflows, not legal certification, and using it doesn't itself make a product compliant. If you're ready to move past spreadsheets, the fashion brand guide to getting started walks through setting up your first pilot line.

• Digital Product Passport - European Commission
• ESPR DPP implementation status and Registry availability

In this context, it refers to Digital Product Passports: evidence-backed, machine-readable records covering a garment's materials, origin, supplier, and care instructions, published for consumers and authorities alike.

Not yet. ESPR is in force as a framework, but textile-specific data requirements wait on a delegated act, targeted around 2027, so brands should prepare data now rather than wait for a finished rule.

GTIN is the pragmatic default, since it resolves through GS1 Digital Link and already integrates with most retail and registry systems.

It depends on your engineering bandwidth. A platform like DPP Grid handles import, evidence capture, and publishing without custom development, while an in-house build offers more control at a higher time cost.

Match granularity to the product. Stable-input basics work at style level, variable dye lots suit batch-level records, and premium or resale-heavy pieces justify item-level serialization for authenticity tracking.

• Fashion Digital Product Passport: 2026 Guide
• Clothing Digital Product Passport: A 2026 Guide