Repère

← All guides

What to keep for an audit of a supplier's REP registration

Published

An auditor asks how you know what the REP register showed for a supplier. The answer they can accept is narrower and more precise than most supplier files hold. Here is what it looks like, and how to keep it.

What an auditor is actually asking for

An auditor reviewing your supplier controls is not asking you to vouch for the supplier. They are asking what you checked, against which source, and when: a dated statement of what the ADEME register said about this producer, in a form they can trace back to the register itself.

The source is a good one to point at. The register rests on article L. 541-10-13 of the environment code, and ADEME publishes it as open data under the Licence Ouverte, so anybody can go where you went. What they cannot do is go back in time, which is why the date on your record carries as much weight as its content.

So the useful record has a fixed shape: the identifier you searched by, the stream, what the register showed, the dataset it came from and the date of that dataset. A record that says less leaves the auditor to reconstruct the rest, and one that says more, a conclusion about the supplier, adds the part they will discount.

A screenshot versus a dated record

The usual exhibit is a screenshot of the ADEME portal. It shows that somebody, at some point, saw a page. It carries no provenance: nothing in the image ties it to the version of the dataset it was drawn from, and the date in the corner is whatever the computer clock said, or whatever an image editor makes it say.

It also points at something that no longer exists. The page is built from the register as it stood that day; tomorrow the same search returns tomorrow's register, and if the registration has been withdrawn in between, the row is not there at all. An auditor who tries to reproduce the screenshot cannot, and an exhibit nobody can reproduce has to be taken on trust.

A dated record is the opposite on each count. It names the source dataset and the snapshot it was read from, and quotes the row as the register published it, identifier, stream code and immatriculation, instead of a picture of a page. Kept beside the snapshot it came from, it can be checked against that snapshot long after the live page has changed.

Evidence is per stream

Registration is per stream: a producer registers once for each product family it is concerned by and holds one identifiant unique for each. A single line in a supplier file reading "registered with ADEME" therefore establishes nothing in particular, because it does not say for what.

The record has to name the stream you are buying in. A supplier registered for household packaging and absent from electrical equipment is a common shape, and a line recording only the first tells the auditor nothing about the second. Store the stream code exactly as the register returns it, not a label of your own, so each line can be matched back to its source row.

Identity needs the same care. Registration is also per establishment, so one SIREN can hold several immatriculations, and SIREN 384560942 had three on 11 October 2026. ADEME also reissues IDUs, so key your records on the stream and the immatriculation together rather than on the IDU alone, and keep the IDU the register showed on each date beside them.

The withdrawal case

Evidence matters most on the day a registration ends. ADEME publishes two datasets: producers currently registered, which held 308,665 rows on 11 October 2026, and producers no longer in conformity, which held 108,230 that day. A withdrawal moves a row from the first to the second; it is not a status switched off in place.

In the second dataset the row carries two fields the first never has: date_fin_conformite, the end date, and motif_desattribution, the motive. Those are what make a withdrawal citable, an event with a date and a stated reason for one producer and one stream, and they are what an alert should quote. A registration that simply disappears with no row in the second dataset is a different case, and filing it as a withdrawal states something the register never said.

Read the motive as a list, not a single value. The field is not a clean enumeration: values combine, so one row can read AUTRE || SIGNAL, and anything comparing it to one expected string will misfile that row. Quote it as the register published it, and do not turn it into a conclusion about the supplier.

Keeping the trail

Because the live register only ever shows today, the trail has to be kept as it happens. The workable form is an append-only archive: each dated snapshot is written once and never edited, so a record made in March reads exactly as it did in March when the auditor asks about it in November.

Keep it for as long as your own obligations can be examined, not for as long as the supplier relationship lasts: a question about a supplier you dropped long ago is still a question about what you knew at the time. Note too that the trail resolves to a day, not an hour, because ADEME publishes the register daily and a change can only be seen from one snapshot to the next.

Be plain in the file about what the trail is. Repère reports what the register stated on a date, citing the source and the snapshot; it never certifies compliance, and no record it produces says whether a supplier meets its obligations. That restraint is what makes the record usable: the auditor gets the source's own words and the date, and draws the conclusion that is theirs to draw.

Figures quoted in this guide were read from ADEME's published datasets on the date above. The register changes every day, so treat them as a dated observation rather than a current count.

Other guides

Put a date on the answer

Query the register by SIRET or SIREN and keep what it said, with the day it said it. No credit card to start.