FousEPREL
Turn your EPREL registrations into an API
Read your product models, EPREL registration numbers, statuses and file upload reports from the EPREL Compliance System with one API call each. Or have a workflow check your models every Monday and email you the ones not yet PUBLISHED.
Works with your own EPREL account. Fous is an independent product.
What you can build on EPREL
Get registered models
Build thisReads the product models of one product group in the Compliance System, with each model's status, energy class and placing on the market dates.
- Takes
- Product group, status (optional), trademark (optional)
- Returns
- Model identifier, trademark, EPREL registration number, status, energy class, on-market start date, on-market end date, blocked
Check file upload reports
Build thisReads the upload history of ZIP file uploads, with each upload's result, its report status and the operations that failed.
- Takes
- Uploaded since (optional)
- Returns
- Upload date, result, report status, operations, failed operations with model identifier and status
Get a model's label and information sheet
Build thisOpens one model by its EPREL registration number and downloads its energy label and its Product Information Sheet in the languages you pick.
- Takes
- EPREL registration number, languages
- Returns
- Model identifier, label PDF, product information sheet PDF per language, QR code
Set a model's on-market end date
Build thisOpens a published model, enters the date the last unit is placed on the market and saves the change with the reason of change you give.
- Takes
- EPREL registration number, on-market end date, reason of change
- Returns
- Model identifier, EPREL registration number, status, on-market end date
Automate EPREL with a workflow
A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.
Models not yet published, every product group
Build this- Starts
- Every Monday at 7:00
- Step 1
- For each product group you name, get the registered models.
- Step 2
- Keep the models in INCOMPLETE or COMPLETE status.
- Step 3
- Email you the list, one section per product group, with model identifier, trademark and registration number.
Failed file uploads, posted to your team
Build this- Starts
- Every 30 minutes
- Step 1
- Check the file upload reports since yesterday.
- Step 2
- Keep the uploads that were not there on the last run and did not end in SUCCESS.
- Step 3
- Post each one, with its report status and failed operations, to your team's webhook.
Newly published models, handed to your product system
Build this- Starts
- Every day at 18:00
- Step 1
- For each product group, get the models in PUBLISHED status.
- Step 2
- Keep the models that were not there on the last run, and stop when there are none.
- Step 3
- Post model identifier, registration number, energy class and on-market start date to your webhook.
You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.
Once built, one call from your code
Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get registered models” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "energy-label.ec.europa.eu/get_registered_models",
"input": {
"product_group": "Dishwashers",
"status": "PUBLISHED",
"trademark": "Northwind"
}
}'
{
"status": "completed",
"data": {
"product_group": "Dishwashers",
"models": [
{
"model_identifier": "NW-DW45-B2",
"trademark": "Northwind",
"registration_number": "1934027",
"status": "PUBLISHED",
"energy_class": "B",
"on_market_start_date": "2026-03-02",
"on_market_end_date": null,
"blocked": false
}
],
"count": 1
}
}
An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.
EPREL’s own options
The Commission offers suppliers three ways to register models: the web forms of the EPREL Compliance System, ZIP file uploads of XML, and system-to-system delivery over eDelivery from your own Access Point. A public API serves published product data, and the Commission suggests it for online stores. Your own models also export to a CSV file.
| Option | What it covers | What it takes |
|---|---|---|
| Public API | Published product data, which the Commission suggests for online stores. | Its syntax is documented in the EPREL wiki, which needs an EU Login. |
| ZIP file upload | Creates and updates many models at once from a registration-data.xml file and its attachments, with a report per upload. | A verified supplier organisation. At most 200 MB and 1000 operations per ZIP. |
| System-to-system (eDelivery) | Sends the same ZIP payload from your system to the EPREL Access Point and returns a transmission report on the same channel. | Your own Access Point and the EPREL S2S Identification form sent to the EPREL helpdesk. |
| The Compliance System by hand | Register, edit and publish models, generate labels, information sheets and QR codes, and export all models to CSV. | An EU Login and a verified supplier organisation. |
Read on November 12, 2026: EPREL user manual for suppliers, What do suppliers need to know?, EPREL registration quick guide.
Signing in to EPREL
EPREL signs you in with EU Login, the Commission's authentication service, using the email address your Supplier Admin invited, and the session ends after a few minutes of inactivity. Each person has a role: Supplier Admin, Supplier User or Supplier Reader. With Fous you sign in once through EU Login with your own account: the login is sealed with AES-256, and an expired session is signed back in.
Worth knowing
- Verification comes first
- Since 22 October 2024 your supplier organisation must be verified before you can register or edit any model. Since 22 April 2025 a national trade register code is the only accepted identity type.
- Every change needs a reason
- After publication you can change anything except the Model Identifier and Trademark, and each change needs a reason of change such as CORRECT_TYPO. A changed label or fiche is republished within 24 hours.
- Reported issues reach the authorities
- The public can report a model with REPORT THIS MODEL. If an issue stays open for 30 days without action from you, an email goes to the market surveillance authorities of your country.
- Uploads are processed, then reported
- A ZIP needs registration-data.xml at its root and holds at most 1000 operations. Each upload gets a report status such as PROCESSED_WITH_WARNINGS, and each operation its own status.
More in Government: Southern, Eastern and Nordic Europe, EU
- Telemaco
- EUDR Information System
- Road Transport Posting Declaration Portal
- EU Funding & Tenders Portal
- Cégkapu
- UETS
- e-Zamówienia
- Mercell
- NEN
- Plataforma de Contratación del Sector Público
- Prozorro
- TRACES NT
- e-ΕΦΚΑ
- PUE ZUS
- Segurança Social Direta
- SGK İşveren Sistemi
- Sociálna poisťovňa e-Služby
- Dijital Vergi Dairesi
- myAADE
- Portal das Finanças
- e-Beyanname
Other industries: Urssaf compte employeur, webDEALER, Simplifile, Wide Area Workflow, Cal eProcure, INTIME.
Frequently asked questions
Yes, a public API for published product data, which the Commission suggests for online stores. For registering your own models EPREL offers ZIP file uploads of XML and system-to-system delivery over eDelivery from your own Access Point, and your models export to a CSV file.
Yes, with a ZIP file upload in the Compliance System. The ZIP holds a registration-data.xml file and the attachments, up to 200 MB and 1000 operations, and each upload gets a report with a status per operation.
In the model's page in the Compliance System. The generated label downloads as a ZIP with PDF, PNG and SVG files, and the Product Information Sheet as one PDF for one language or a ZIP of PDFs for several.
Supplier Admins and Supplier Users. A Supplier Reader can only view. Only Supplier Admins create trademarks and contacts, and they invite the other Supplier Admins, Supplier Users and Supplier Readers.
No. Fous is an independent product. You use it with your own EPREL account, and a method reads and does only what that account can.
Put EPREL behind an API call
Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nexte-ZamówieniaMercellNENUrssaf compte employeurHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of EPREL (European Commission (DG ENER)). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.