If your product data lives in Akeneo, you are closer to a compliant Digital Product Passport than most manufacturers. The attributes ESPR asks for (material composition, origin, care instructions, certifications) already sit in your PIM. What you need is a connector that maps them to the DPP format, validates them, and generates a QR code per product or per unit. That takes two to three weeks, not a development project.

This article explains how the Akeneo integration works in practice: what gets mapped, what runs automatically, where the gaps typically are, and what the whole thing costs.

Why Akeneo users start from pole position

The Ecodesign for Sustainable Products Regulation (Regulation (EU) 2024/1781) has been in force since July 2024. It becomes fully applicable on 19 July 2026, the same date the EU's central DPP registry goes live. From that point, product categories get pulled into DPP obligations step by step through delegated acts. The European Commission's ESPR working plan for 2025 to 2030 names textiles, furniture, tyres, iron and steel, and aluminium among the first categories.

The hard part of a DPP project is almost never the passport itself. It is collecting and structuring product data. A manufacturer who keeps product information in spreadsheets and ERP fragments first has to build a data foundation. An Akeneo user already has one:

• Attributes are structured and typed
• Variants and product models are cleanly separated
• Localizations exist per attribute
• The REST API exposes all of it

That is why the typical Akeneo-to-DPP project at dpp.cloud takes two to three weeks. The data work is already done. What remains is mapping, validation, and QR generation.

How the integration works

The connector sits between your Akeneo instance and dpp.cloud. Akeneo stays the single source of truth. Nobody re-enters data, and your team keeps working in Akeneo exactly as before.

Four steps run in the background:

1. Sync: Akeneo pushes product changes via webhook or the connector polls the REST API. New SKU, changed attribute, deleted product, all of it arrives automatically.
2. Mapping: A mapping file defines which Akeneo attribute feeds which DPP field. material becomes material composition, care_label becomes care instructions, country_of_origin becomes origin information.
3. Validation: The connector checks required fields, formats, and reachable links. Products with gaps get flagged so your team sees exactly what to fix.
4. QR generation: Each product (or each unit, more on that below) gets a QR code pointing to its passport. The code can be written back into an Akeneo attribute so your label workflow picks it up without extra steps.

What maps to what

A typical baseline mapping for a textile or furniture manufacturer looks like this:

In most projects, around 80 percent of the required fields already exist in Akeneo. The rest are new attributes you create once, usually for circular economy data. The Joint Research Centre's preparatory work on textiles lists 49 data points across four categories, and the gaps almost always sit in the same place: recyclability, repairability, and take-back information. Three to five new Akeneo attributes close them.

Product-level or serial-number level?

ESPR requires passports at different granularity depending on the category: model, batch, or item level. Most platforms stop at product level. dpp.cloud can create a passport per physical unit, because underneath every passport sits an individual digital identity.

Why bother? A per-unit passport records what happens to that specific unit: repairs, ownership changes, refurbishment. That is the difference between a static data sheet and infrastructure you can run warranty automation and second-life programs on. We covered the revenue side of this in how manufacturers turn QR scans into after-sales revenue.

If you only need model-level passports for compliance, that works too. You can switch granularity per category later without redoing the integration.

A real project timeline

This is the pattern from our Akeneo onboardings, including a European children's furniture and textiles brand with roughly 600 active SKUs:

1. Day 1: Kickoff. Which categories, which attributes, which granularity. Two to three hours.
2. Days 2 to 7: Data review in Akeneo. Completeness check, gap list, decision on new attributes.
3. Days 7 to 10: Mapping call. Your team and ours define the attribute mapping, including localization handling.
4. Days 10 to 14: Technical setup. API credentials, connector configuration, new attributes created.
5. Days 14 to 17: Pilot. One product end to end, from Akeneo attribute to scannable passport. Sign-off.
6. Day 17 onwards: Rollout across the catalog, QR codes into the label process.

The honest caveat: the technical integration is the fast part. Coordinating with your label printer and physically getting QR codes onto products takes longer than the software. Plan for that.

What it costs

dpp.cloud runs on flat annual pricing. Growth at 10,500 euros per year (5 seats), Professional at 17,500 euros per year (25 seats). The Akeneo connector, mapping setup, and API traffic are included. There are no per-SKU or per-sync fees, so the price does not drift as your catalog grows. Details are on our pricing page.

For comparison: a custom-built DPP integration typically lands between 30,000 and 50,000 euros in development cost before you have validated a single passport, and you maintain it yourself afterwards. We ran the full comparison in our DPP software buyer's guide.

When to start

The registry going live on 19 July 2026 does not mean every category needs a passport that day. Textiles, for example, will realistically become mandatory in late 2028 or 2029, about 18 months after the delegated act. The full schedule is in our DPP timeline.

The reason to start earlier is practical, not regulatory. Data gaps take months to close when suppliers are involved. Label cycles are long. And a passport that is live before the deadline is not a cost, it is a customer touchpoint you already own. The manufacturers we onboard now treat compliance as the entry ticket and build their after-sales channel on top.

Next step

If you run Akeneo and want to know what your specific setup needs, book a 30-minute strategy session. We look at your attribute structure together, name the gaps, and give you a concrete timeline and price. No slideware.

Book your strategy session