What a business has to be before it can register anything

The short answer

Nothing obliges a textile business to put anything into the EU Digital Product Passport registry today. No product category that reaches this readership carries a live registration duty, and the instrument that built the registry sets no compliance deadline of its own. The registry itself is real and running: the implementing regulation establishing it was adopted on 16 July 2026, published in the Official Journal the following day and entered into force on 6 August 2026, with the portal operational since 20 July 2026.

If a business did want to register something, the first thing it would need is not product data. It is verified economic operator status. A legal entity reaches that with a qualified electronic seal or a qualified attestation of attributes, and until it holds one the registry will not accept a submission from it at all.

Two consequences follow and they pull in opposite directions. There is no reason to hurry, because the duty that would eventually make any of this compulsory for textiles arrives with a product act that has not been adopted, and when a duty starts is the one question this page will not answer in its own voice. There is also a clock, since the verification expires and a credential bought now will need renewing at least once before anything obliges you to use it.

The Commission has said publicly that the registry is operational. That statement is brief and accurate as far as it goes, and we record that we have not read it at its own address, because the address was not established by this build.

What the registry holds, and what it does not

The most common error in circulation is to describe the registry as a product database. It is not one. What gets registered is a record about a passport rather than the passport itself, and the difference decides who is holding your data and who a scan actually reaches.

A registration carries the product identifiers, the commodity codes for the goods, a reference to the service provider hosting the passport, the identity of the party doing the registering, a cryptographic hash of the version being registered, a persistent registration identifier the registry issues back and a link to the data the operator is hosting. The passport content stays where it already was. What an identifier has to be is a separate question, handed by the framework to internationally recognised standards without one being named, and it is answered under the identifier attributes.

Records are accepted at model, batch or item level, with a linking rule where more than one of those levels exists for the same goods. Which of the three a textile passport would attach to is not settled by anything adopted, and what level a passport attaches to works through the consequences of each answer.

The gate is who you are, not what you sell

The first mandatory thing the EU built into this system is operator identity, ahead of any product information. An economic operator has to become a verified economic operator before it can register anything at all, and verification runs on electronic identity instruments rather than on a form somebody fills in.

For a natural person that means an electronic identification means. For a legal entity, which is what almost every reader here is, it means a qualified electronic seal or a qualified attestation of attributes. Which economic operator you are in the first place is prior to all of this, and it is not always the company that assumes it is, so which role you occupy is the question to settle before any of this becomes a purchase.

The practical shape of this is a procurement task rather than a data task. A seal is bought from a qualified trust service provider, the same class of supervised commercial vendor that issues qualified certificates for electronic signatures, and it is issued against checks on the legal entity rather than against anything about the goods. It moves at the pace of company identity verification, which is not the pace of a software integration.

The credential expires, and that is the whole decision

Verification does not last indefinitely. It runs until the underlying electronic identity means expires and in no case longer than three years, after which the operator has to be verified again before it can keep registering.

Put that next to the other clock and the decision writes itself. A business that buys a seal now will pass through at least one re-verification before any textile obligation could reach it, because no adopted act creates that obligation, and whether anything has been dated at all is a question the status tracker answers row by row rather than one this page answers in a sentence. The renewal is not an administrative footnote. It is a recurring purchase from a commercial vendor, on a cycle the business has to remember, protecting a capability nobody currently requires it to have.

The registry keeps its side of this on fixed terms too. Registration data is deleted ten years after registration, and a proof of registration is retrievable for ninety days. Both are properties of the instrument rather than deadlines for anybody, and both are worth knowing before a vendor describes either as permanent.

The one cost nobody has published

There is exactly one thing on this page a business has to buy, and no figure for it.

Qualified electronic seals come from qualified trust service providers: commercial companies, supervised at Member State level and carried on national trusted lists. Pricing sits between that vendor and the buyer. We looked for a published figure for what a seal costs across the population of economic operators, at the Commission, at Member State supervisory bodies and in trade material, and we did not find one. That is a finding about the published record as we found it rather than a claim that no such figure exists anywhere, and how we handle a value we cannot establish sets out why the two are kept apart.

What is not a cost is worth stating in the same breath, because the two get conflated. Access to the semantic repository and to the registry's interfaces is free of charge, and the instrument states no registration fee. The credential is the cost. The registry is not.

What a third party can and cannot take off you

A vendor can register on your behalf. The instrument permits a third party to act for an economic operator, requires that third party to be a verified economic operator in its own right and leaves the operator fully responsible for what is registered.

So the honest reading of a vendor claiming it handles registry submission is that it handles the submission. It does not handle the responsibility, and nothing in the instrument moves that. The operator is also the controller of the data it submits, which is a second thing an outsourcing arrangement cannot quietly reassign. The instrument carries a duty at the moment of registration and a separate continuing duty thereafter, so a record that was accurate on the day it was accepted is not therefore a record that stays compliant on its own, and who stays responsible for a published field is where that lands in practice.

Five questions separate a vendor who has done this from one who has read about it:

• Are you a verified economic operator yourselves, and in which Member State?
• Is the registration made under your seal or under ours, and whose identity appears against the record?
• What happens to the registrations if we stop working with you?
• Who hosts the passport data the registry's link points at, and what happens to that link if the hosting stops?
• What do you do, and what do you need from us, when our verification comes up for renewal?

The fourth question has consequences well beyond the registry, and what happens when the link stops answering follows them through.

What registration is not, and the regulation says so itself

The registry runs automated checks on what is submitted to it. The regulation is unusually direct about what those checks establish, and it puts the point in its recitals rather than leaving anybody to infer it.

That is the strongest sentence available on this whole subject, and it is the regulator's rather than ours. A record that has passed those checks means a submission was well formed and its fields were populated. It means nothing about the fibre content being right, nothing about a claim being substantiated and nothing about the product complying with anything at all.

The framework the registry serves points the same way from a different direction: releasing goods is not deemed proof of compliance. Two instruments saying one thing, and it is the thing that most needs repeating inside a marketing team.

The practical rule that follows is short. No product should be described as registered or compliant on the strength of a registry record, and this estate describes no product, including any belonging to the businesses we work with, in either of those terms. If a supplier registering on your behalf uses that language about your goods, it is making a claim the regulation declines to make.

What to do now, which for most readers is nothing

For most people reading this the correct action is none, and knowing that is worth something. The alternative is buying a credential well ahead of any duty to use it and renewing it repeatedly to protect a capability nobody requires, which is exactly the behaviour a marketed registration deadline is designed to produce.

Four things are worth doing anyway, and none of them costs anything:

1. Establish which economic operator role your business occupies. That question is prior to the registry and it does not change when a product act arrives.
2. Decide which legal entity in your group would hold the seal, since verification attaches to an entity rather than to a brand or a website.
3. Put the renewal arithmetic in front of whoever would sign the purchase order, so that a three year ceiling is understood as recurring before anything is bought.
4. Keep the vendor questions above in the file you use when somebody offers to handle registry submission for you.

One thing is worth not doing. Do not let a registry deadline into a plan, because the instrument does not create one. The national layer is still being assembled underneath it. Member States have their own deadline for appointing national administrators, which is a duty on Member States rather than on any business and which is one reason a live registry can coexist with almost no mandatory users. That date sits on the status record, which is the one destination here that asserts a date on which a duty applies.

The first product category to carry a mandatory registration duty is not textiles, and its date belongs to that category and to no other. Anybody presenting it as a textile date is presenting a different sector's timetable as yours.

Sources

One instrument carries almost all of this page, and it was read at article level rather than through somebody's summary of it. No article number appears above, and that is deliberate: the internal numbering of the registry regulation has not yet been checked against the Official Journal PDF, so every provision is named here by what it does. When that check is done the numbers can be added without a sentence changing.

• Commission Implementing Regulation (EU) 2026/1778 establishing the Digital Product Passport registry
  CELEX 32026R1778In forceRelevant provisions reviewed

  Read at article level by one research programme in August 2026: the verification provisions, the registration provisions, the responsibility provisions, the retention and proof of registration provisions, the administrator designation provision and the recital on what automated checks establish. Two things it does not contain are load bearing above and were established by the same read: it sets no compliance deadline of its own, and it lays down no procedure for correcting, withdrawing or deactivating a registration. Article numbers are withheld pending a check of the instrument's internal numbering against the Official Journal PDF.

  View official source

• European Commission announcement that the Digital Product Passport registry is operational
  Institutional statementReached through a secondary reproduction, primary text not read

  Carries one proposition here, that the registry is operational. It is brief and accurate as far as it goes. Its address was not established by this build, so this row carries none and the sentence using it says the announcement was not read at its own source.

• Ecodesign for Sustainable Products Regulation (EU) 2024/1781, consolidated text
  CELEX 02024R1781-20240628In forceRelevant provisions reviewed

  The framework the registry serves. Used here for two propositions only: that the framework works by empowerment rather than by creating product duties itself, and that releasing goods is not deemed proof of compliance. Its passport articles are attributed differently by two independent reads of the same text, so no article of it is cited on this page either.

  View official source