One QR code on every appliance: from EU obligation to service portal

At a glance

• Starting point: Every EU energy label needs a QR code pointing to the EPREL database, but a fixed, printed destination link can't be adjusted when products change, corrections happen, or manufacturing errors occur.
• Solution: We built a redirect platform that resolves the right destination live, on every scan, from the article number and production batch encoded in the QR code, depending on whether it's an end customer, a service technician or the warehouse scanning.
• Outcome: Running for more than five years, since extended, from the same data foundation, into a multilingual service portal covering more than 600 products.

The starting point

With the EU's energy label reform, every label got a QR code that has to lead to the product's entry in the EPREL database. Sounds like a minor detail, but it's a problem with long-term consequences: the code gets printed once and then sits on the appliance for years, while the world behind it keeps turning. Product versions change, registrations get corrected, new regulations bring new data fields, and manufacturing errors happen, a label ends up on the wrong appliance or carries the wrong code.

Print the destination URL straight onto the label, and you have no room to manoeuvre in any of these cases. The customer scans it and lands nowhere, and the only fix would be reprinting, in the worst case on appliances already out in retail. Add the scale: multiple brands, a continuous stream of data from the PIM, manufacturing in batches.

Our approach

We turned it around: the appliance doesn't carry the destination, it carries a key. Every QR code encodes the article number (EAN) and the production batch as a URL to our own redirect platform, and the platform decides where it leads, freshly, on every scan. That moves control over every code ever printed out of the print shop and into a system that can actually be maintained.

Before building anything, we analysed the common denominator: not every scan is the same scan. The same mechanism has to send the end customer to the EU data sheet, the service technician to the documentation, and the warehouse to batch verification. So we separated resolving the code from the destination itself, and built it as a chain of rules that delivers the right result for each context.

The solution

• A key instead of a fixed address. Every code carries the EAN and the production batch. The platform resolves it live: end customers land on the EU data sheet in EPREL, service technicians land in the brand's documentation, the warehouse lands in the internal batch view.
• A resolution chain with no dead ends. Five stages, from an exact batch match down to a brand-level fallback. If a scan finds no perfect record, the code leads to the next-best correct page instead of an error message.
• Repair without reprinting. Incorrectly printed or wrongly matched codes get redirected to the correct destination through an override. One entry in the system, instead of a recall or relabelling.
• Product data that grows with the regulation. Article data arrives through an automatic import from the manufacturer's PIM. New energy-label fields from new EU regulations get picked up by the system itself, through a naming convention; there are 33 fields by now, and the import logic has never had to be touched for any of them.
• Everyday control. A test mode shows the resolved destination plus diagnostics instead of redirecting, so codes can be checked without triggering false alarms. Import reconciliation flags missing or unexpected data automatically, and scan statistics count usage per article.

The turn

The compliance infrastructure turned into a service portal. Since late 2021, the same data foundation that feeds the EU redirects has also supplied a public, multilingual document portal: user manuals, spare-parts lists, EU data sheets, repair guides and exploded diagrams, six document types across more than 600 products, plus routes into each brand's own customer service and a separate entry point for trade businesses.

What's remarkable is everything this portal doesn't need. It holds almost no data of its own: articles and brands come live via API from the QR platform, and which products appear with which document types is controlled by the manufacturer through a single field in its PIM, with no second editorial interface at all. The documents themselves get served straight out of the file store via a naming convention, including language variants and cleanly named downloads. Getting a new manual into the portal means: drop in a correctly named file. No deployment, no admin screen, no duplicate data store.

The outcome

• Running for more than five years, with continuous development, from the first build stage in 2020 to the most recent additions in 2026.
• One data cycle instead of separate point solutions: from the PIM through the QR platform to EPREL, the service portal and service partners. Three user groups, one system, one source of truth.
• New EU regulatory fields with no development project needed, wrongly printed codes fixable with no recall.
• Over 600 products in the portal, six document types, multilingual, editorially controlled from the system the manufacturer maintains anyway.

What this story shows

The obligation was a redirect. What we built was the software missing between the existing systems: between the manufacturer's PIM, the EU's database, the brands' service partners, and the appliances out in the field. Because that middle layer was designed as a whole from the start, the service portal later cost no second data store, just a second consumer of the same data.

Product data, EAN logic, batches, imports: it's the same discipline we use to run shops and stock in e-commerce, applied here to regulated product communication.

Business applications like this are built at total10 as bespoke software alongside your existing systems, from the data model to operations.