Digital Product Passport DPP ESPR | show required data before checkout

About the Extension

18 February 2027 is already fixed. From that day every traction, light transport and industrial battery above 2 kWh needs a digital product passport, reachable through a QR code on the product. If you sell that stock, you face a job no ERP and no PLM system takes off you. The duty sits on the product page, and your shop is what renders it.

The problem

Article 32 of the Ecodesign Regulation names distributors explicitly, not only manufacturers. The passport has to be easily accessible to customers and potential customers, and distance selling is called out by name. A QR code that only appears on the delivered box does not satisfy that. Nor does a PDF in a download area: the passport is read years after the sale by repair shops, recyclers, customs and market surveillance. Without an account in your shop, long after the product left your range.

The solution

This plugin puts the passport in the two places where it belongs. On the product page you get a passport panel with the public mandatory data, visible before the sale. Behind it sits a permanent address of the form /dpp/uid that works without login or consent, answers in English, German and Dutch, and serves the same data as JSON on request. The QR code on the product points straight there.

What's in it for you

You meet the accessibility duty exactly where it arises. The passport panel goes into its own tab next to description and reviews, below the buy box, or below the product description, picked per sales channel with no template work.

You do not have to be a manufacturer. In distributor mode the plugin shows the passports your suppliers publish and checks at a fixed interval whether their addresses still answer. When a link dies, you see it in the compliance overview instead of hearing about it from a customer.

A new passport does not start empty. Whatever the shop already knows is filled in: name, model identifier, GTIN, manufacturer, product group, date placed on the market, product image. Whatever holds for your whole range — take-back page, recycling instructions, separate collection — you enter once per sales channel in the settings. Whatever belongs to the manufacturer you maintain once on the manufacturer. Of the 14 required fields in the shipped ESPR schema that leaves 5, and none at all once your ERP fills the free text fields that ship with the plugin.

Trade secrets stay protected. Every passport field carries one of six visibility levels: public, buyer, repairer, recycler, authority, confidential. Anyone wanting more than the public level identifies with an access token, a client certificate or their order number. Formulations and supplier pricing live in the passport without living on the open web.

Your passports are provably unchanged. Versions are appended, never overwritten, and each one is tied to its predecessor through a hash chain. You can sign them on top. At /dpp/uid/verify anybody checks this themselves, an inspector included, without asking you.

Print ready data carriers come out of the backend, not out of a design tool. QR code, Data Matrix, NFC payload and an A4 label sheet holding 14, 24 or 40 labels, plus a nameplate view with a layout editor per schema, exported as an image into the media library.

Your bulk product import stays fast. The plugin does no passport work while a product is written. A write event only fills a work queue that runs afterwards in batches, idempotent and resumable after an abort. Signing, rendering and registry calls happen there, not in the request.

How the plugin works

Everything starts with a schema. Two ship with the plugin: a generic ESPR schema with 51 fields in 8 sections, and the EU battery schema after Annex XIII with 83 fields in 10 sections. A schema editor creates your own or adapts the supplied ones, versioned, with file export.

A product then gets a passport for the model, for a batch or for the individual item. You fill the fields in the backend, through a CSV import with column mapping and a dry run, or straight from your ERP through the Admin API. Once the passport is ready you publish it. Turned out wrong? A published passport is withdrawn, not deleted, because it is the buyer's evidence.

The plugin adds ten pages to the administration: passport list, passport detail with version comparison and signature state, schema management, compliance overview, EU registry, data carrier, import and queue state, plus a tab on the product. Permissions split into three groups, because different people own them: passports, schemas, registry.

Typical use cases

The battery seller with a hard deadline. You sell e-bike batteries and storage units above 2 kWh. You set up the Annex XIII schema, import the manufacturer data as CSV, print the label sheet for the serial numbers and are ready before 18 February 2027.

The furniture maker with their own production. You issue the passports yourself, sign them and export the nameplate as an image into the media library, which ends up on the sticker. The workshop hunting a spare part in five years scans the code and gets the repair data.

The pure distributor. You manufacture nothing but sell goods that need a passport. You store your suppliers' passport addresses, the plugin checks them regularly and reports dead links before market surveillance does.

The headless frontend. Five Store API routes deliver passport, verification result, bundle lookup, product reference and data carrier. The data carrier arrives as JSON with SVG markup, so an image tag without an access key never becomes your problem.

Technical facts for your IT team

Shopware 6.7, PHP 8.2 or newer. Shopware fetches the QR code library via Composer during installation, so the shop must be allowed to run Composer. The plugin creates 11 tables of its own and changes no Shopware table at all. Product and order line item are extended through plugin tables, every foreign key stays on the plugin side.

Out of the box the plugin calls no external service. Two connections have their own switch in the configuration and sit at off: the submission to the EU product passport registry and the check of supplier passport addresses. Two more only come into being once you set them up yourself, an archive target for the export and an HSM as key source. Signing keys never land in the configuration, you store a pointer to an environment variable, a file or an HSM.

For your ERP the plugin ships a free text field set on product and manufacturer: manufacturer identifier, user manual, EU declaration of conformity, take-back page, recycling instructions, separate collection, expected lifetime, carbon footprint. A value on the article beats the one on its manufacturer, which beats the sales channel default. Which passport field takes which source is declared in the schema, so it changes without touching code.

The access log can be switched off, stores the IP address shortened or not at all, and clears itself after the retention you set. The passport page runs through the HTTP cache with a configurable lifetime and is invalidated when a passport changes. Everything is switchable per sales channel, and the switch at the top silences the plugin for a channel completely. On uninstall Shopware asks you whether the passport data stays or goes with the tables.

To be honest

The plugin carries and publishes your passport data, it does not produce it. Carbon footprint, material origin and supply chain figures come out of your PLM, ERP or LCA tool, and if nothing sits there, nothing sits in the passport. Registering as a verified economic operator with the EU registry stays an administrative one off with an identity check that no software takes over. Outside batteries no delegated act with a passport duty is in force yet, so the supplied schemas are solid templates rather than a promise. That is why they are built to be replaced. If you want to know how far your range is affected, install the plugin on a test system and create a passport for a real article.

Legal notice

We accept no liability for legal requirements. Please check the use of this plugin with a qualified legal advisor.