Synton measures how much of a named, dated, cited dataset your products already carry, and separates the half that is law in force from the half that is still expected. It will not tell you that you are compliant, because on this subject nobody honestly can yet.
Read from the primary texts: the ESPR consolidated text (CELEX 02024R1781-20240628), Regulation (EU) 2023/1542 and Implementing Regulation (EU) 2026/1778. Last reviewed 20 August 2026. Every figure on this page is dated so you can see how old it is.
18 Feb 2027The only Digital Product Passport date in force today, and only for the batteries the Regulation puts in scope.
2 bandsLaw in force and expected-but-not-yet-law are scored apart, never averaged into one figure.
3 tiersPublic, legitimate interest, authority. Restricted data is withheld, and the withholding is shown to the reader.
0Compliance scores. We report data coverage against a cited dataset, and we name the article beside it.
What the product actually does
A number is only as good as the text behind it
7 decisions separate a passport readiness report from a compliance score. Each one can be checked against the instrument it names.
Every data point names its source
A field is on your list because an instrument in force names it, or because the preparatory work names it consistently and we say which. Each point carries the regulation, the article and the reason it is there, so you can check the reading against the text instead of trusting a number. The alternative, an unsourced field list turned into a percentage, is what most passport tooling ships.
Regulation and article on every pointPosition last reviewed 20 August 2026
Law in force is never blended with what is expected
A point is marked specified when an instrument in force names it, and candidate when it is expected in a delegated act that has not been adopted. The two are scored as separate bands with separate denominators. A single average across both would imply a certainty that does not exist, hide the one obligation that is real, and manufacture urgency around several that are not.
Two bands, two denominatorsNo blended figure anywhere
Our own gaps are reported as ours
When a dataset asks for something we have nowhere to store, that point is reported as uncapturable, excluded from your denominators and listed on its own. Counting our missing columns as your missing data would flatter us at your expense; listed separately, the same fact is our roadmap. The battery dataset reports none of these today, and the two that remain are expected textile points.
Three states: present, missing, uncapturableOur gaps never score against you
Access tiers are real, and withholding is disclosed
ESPR Article 10 requires a passport to differentiate what each audience may read, and the battery dataset splits along the same three audiences: anyone who scans the carrier, people with a legitimate interest such as repairers, remanufacturers and recyclers, and authorities. A passport that serves every field to every scanner is not a more generous passport, it is your supply chain published. Restricted points are stripped before the page is built, and the viewer is told how many were withheld and under which tier, so a redacted passport does not read as an incomplete one. A tier comes from an authenticated decision and can never be claimed in a query string.
The code points at a GS1 Digital Link over your own GTIN, not at an identifier we minted. ESPR Articles 11 and 12 require a persistent identifier free of vendor lock-in, and Article 77(6) of the Batteries Regulation requires the code on a battery to reach a unique, permanent address serving that battery's passport, which a product page that breaks on your next replatform does not satisfy. A lot or serial number narrows the answer to that unit and never widens back to the model. GS1 Digital Link is the carrier form the Commission's preparatory work points at: a strong candidate, not a legal designation, and we label it that way.
ESPR Art. 11 to 12Batteries Regulation Art. 77(6)
Battery scope is asked, never assumed
The battery passport covers LMT batteries, electric vehicle batteries, and rechargeable industrial batteries above 2 kWh. It does not cover a portable cell, and it does not cover an SLI starter battery. The word "batteries" alone cannot separate a 60 kWh traction pack from a hearing aid cell, so the scope check has three answers and the third one matters most: undetermined, meaning tell us which kind this is. Showing every battery seller a February 2027 date would be the easy, confident, wrong answer, and a false deadline on a regulated subject costs a supplier programme nobody needed.
Regulation (EU) 2023/1542 Art. 77(1)Three verdicts, including undetermined
We prepare the registry record. We do not submit it.
ESPR Article 13 has the Commission setting up a digital registry by 19 July 2026, and Implementing Regulation (EU) 2026/1778 lays down how it operates. We build the registration record its Articles 8 and 9 describe, validate it, and tell you exactly what is still missing. We do not post it: we hold no credentials for the interface and have not read its request schema. The registration identifier is minted by the Commission, so ours stays empty until the registry returns one. A value we generated there would be a forged regulatory reference.
Impl. Reg. (EU) 2026/1778 Arts. 8 to 9Prepared, never submitted
The position, stated plainly
Where the law stands today
3 situations, and only 1 of them has a date. Anything offering you a fourth is quoting an expectation as though it were a rule.
Batteries in scope
Regulation (EU) 2023/1542, Article 77 and Annex XIII
Status
Adopted. The dataset is named in the Annex.
Applies from18 February 2027
LMT batteries, electric vehicle batteries, and rechargeable industrial batteries above 2 kWh. Portable cells and SLI starter batteries sit outside it. This is the one product group with an obligation a merchant can miss, and we treat it accordingly.
Textiles and footwear
Regulation (EU) 2024/1781 (ESPR), Chapter III
Status
Framework in force. The textiles delegated act is not adopted.
Applies fromNo date in law
Until that act exists, the mandatory field list, the product granularity, the access rights split and the transition period are all legally undetermined. We carry the expected fields so you can collect them early, and every one of them is labelled expected rather than required. Any textile deadline you have been quoted is a prediction about when the act will land, not a rule.
Every other product group
Regulation (EU) 2024/1781 (ESPR), Chapter III
Status
No product specific delegated act.
Applies fromNo date in law
You get the framework level only: the persistent unique identifier, the responsible economic operator and the carrier any passport will need. Collecting those early carries no regret. Not holding them today breaks no rule, and we will not pretend otherwise to sell you a project.
The horizontal standards, the CEN and CENELEC JTC 24 series covering identifiers, data carriers, access rights and interoperability, were still in progress at our last review. Interoperability details will move, which is why the position above carries a date. The framework itself sits in Regulation (EU) 2024/1781, Chapter III, Articles 9 to 15.
Why we will not hand you a number that says compliant
A passport claim is a regulated statement. Telling a merchant they are compliant with a rule nobody has written yet is the most damaging thing this product could do, so it is designed out rather than reviewed for.
That is not caution for its own sake. A compliance percentage built from an unsourced field list is worse than no number at all: it is precise, it is confident, and it is about nothing. It sends people to buy supplier data they do not need, and it goes quiet on the one dataset that is adopted and does have a date.
No invented datesA dataset that is not adopted carries no obligation date anywhere in the product. That rule is enforced in code and pinned by a test, not left to a copy review.
No blended scoreLaw in force and expected-but-not-yet-law are separate bands with separate denominators, so neither can flatter the other.
No claimed tierAccess comes from an authenticated decision. A tier asserted in a request parameter is an assertion by a stranger, and nothing here parses one.
No invented field listA product group gets a dataset when there is a text to cite. Adding a plausible looking list for electronics or furniture is the exact regression this replaced.
No fabricated identifierRegistration identifiers come from the Commission. Ours stays empty until the registry returns one.
Limits
What this does not do
Anyone can list what a product does. This is the part you can hold us to, and the part a compliance score will not print.
It is not a conformity assessment
Coverage measures how much of a named dataset you hold. It does not replace the conformity procedures the Regulation requires, and it does not judge whether a document you hold is adequate. Presence is scored; adequacy is not.
It does not submit anything to a regulator
We prepare the registration record and stop. Preparation is all it is, and the record itself says so.
It does not give textiles a deadline
Because there is not one. The delegated act was not adopted at our last review, so the honest answer to "when do I need this" for a textile product is that nobody knows yet.
It does not invent per unit data
State of health is measured per battery and it decays, so an undated reading is a number of unknown age presented as current. A reading with no date scores as missing, and you keep the value you typed.
It is not legal advice
We cite the instrument and the article so your own counsel can check the reading rather than take our word for it. That is what the citations are for.
Start from what you actually hold
Connect a store, pick a product group, and read the coverage split into law in force and expected, with the article printed beside every line.