Informational only, not legal advice. Confirm all regulatory details against the official EU sources cited below and with your own legal and compliance teams before publication.

Most manufacturers already do traceability, whether or not they call it that. A recall forces you to find every affected unit; a quality event sends you hunting for the batch, the supplier, the process step. The problem is that this capability tends to be reactive and partial, re-stitched each time from legacy systems that were never designed to talk to one another.

The EU is about to make it mandatory, standardized, and machine-readable. Under the Ecodesign for Sustainable Products Regulation (ESPR), a growing list of products placed on the EU market must carry a Digital Product Passport (DPP): a machine-readable record, reached through a data carrier such as a QR code, that describes a product across its entire lifecycle, from origin, materials, environmental impact, compliance, and circularity to end of life. With it, traceability shifts from a reporting afterthought to a gate on the right to sell. Batteries set the clock: the battery passport is mandatory from February 2027.

A passport is required whether the product is made in Spain, the United States, China, Brazil, or anywhere else. If it sells into the single market, it needs a passport. And the reach extends to imports: through the central Registry, customs authorities can electronically verify that an imported product has a valid, registered passport.

As the broadest expression of this push toward traceability and sustainability, the DPP also sets the highest bar: a record for every item, defined by a common standard, kept accurate for the product's entire life, and served on demand. For a single EV battery pack, that means one passport that carries its cell supplier and origin, its carbon footprint, and a state-of-health record that stays current as the pack is used, repaired, and recycled. If today you can trace a product only when something goes wrong, the DPP asks you to trace it continuously and on demand.

What the regulation requires

The legal basis is Regulation (EU) 2024/1781, the ESPR, which hands the Commission the power to decide what data each product group must publish. Strip it down and a passport needs three things: a unique identifier; a data carrier, usually a QR code, that links to the passport rather than storing it; and a defined set of data points that stay accurate for as long as the product exists. The roll-out is staged, with batteries first under the EU Batteries Regulation (2023/1542) from February 2027, but it reaches much further. It covers physical goods across textiles, furniture, electronics, steel, aluminium, tyres, and beyond; it exempts software, services, and a few categories such as food and medicines; and it binds every producer selling into the single market, wherever they sit.

Why this is hard: it is a data problem

The DPP is, above all, a demand to build an operational data capability  and four properties make that demand hard to meet.

  • The architecture is decentralized by design. The Commission runs only a thin central layer, a Registry that indexes each product's identifier and metadata and holds the shared data models, while the passport data itself is stored and served by each economic operator. An operator may hand the work to a third party, but never the responsibility for it. Accountability cannot be outsourced.
  • The answers live several tiers up the chain. Material composition, recycled content, carbon footprint, sourcing evidence all come from suppliers you do not directly control. Answering the tier-1-to-tier-N question is a data-integration problem long before it is a compliance one.
  • Accuracy must last the product's life. A passport is not a launch-day PDF; for a battery, it is a live, per-unit record maintained through use, repair, second life, and recycling.
  • Access has to be tiered within a single dataset. Some fields are public; others open only to parties with a legitimate interest, such as repairers, recyclers, and authorities. And it is the operator, not the Commission, that decides who qualifies before releasing the restricted ones.

*In the Commission's own survey of 91 battery-industry organizations (https://single-market-economy.ec.europa.eu/events/eu-digital-product-passport-batteries-second-webinar-2026-07-07_en), data availability and quality ranked as the single biggest challenge (63%), with supplier data integration (51%), data collection (47%), and data quality (44%) close behind. QR codes came last, at 15%. The QR code is the easy part. The data behind it is the work.

How Databricks helps

A DPP is not a single workload. It is operational lookups, large-scale analytics, AI, and governed sharing over the same trusted data. Assembling that from separate databases, warehouses, app hosts, and model-serving endpoints is slow and brittle. You can build all of it on the Databricks Platform, as one governed backend for the operator side.

  • Lakebase — a managed operational store for sub-second passport lookups and supplier writes.
  • Unity Catalog — lineage, fine-grained access control, and the public-versus-restricted tiers the regulation requires.
  • Lakeflow Spark Declarative Pipelines, AI Functions, and Genie One — ingestion, compliance, and sustainability analytics, and AI-assisted enrichment across thousands of SKUs.
  • Databricks Apps — the consumer passport view and supplier portals.
  • OpenSharing — value-chain and cross-border exchange without copying data.

Why one platform, specifically for a DPP?

Because a passport is at once a public per-item lookup, a multi-tier analytics problem, and a governed-sharing problem over the same data. A serialized passport per unit is an operational workload at consumer scale, which Lakebase serves sub-second alongside the lakehouse. The data that fills it originates at the top of the supply chain, so Unity Catalog's lineage can answer a market-surveillance authority's question about where a given number came from. And because access is tiered by law, it is enforced once in Unity Catalog rather than re-implemented in a database or a warehouse tool, where versions inevitably drift apart. When a defect strikes a specific cell lot, that same lineage traces every affected pack in minutes. Fewer copies of the data mean fewer places for it to be wrong.

This complements the EU's central systems rather than replacing them. The Registry is a thin indexing layer: it holds each product's unique identifier, registration data, and high-level metadata. Where the applicable rules require it, operators register a passport there before placing the product on the market. The passport data itself lives on your backend. The Registry and its shared data models are the integration points, and Databricks provides the underlying data foundation the operator is responsible for.

To help teams move quickly, Databricks offers an open Digital Product Passport Solution Accelerator: a deployable reference architecture for the operator-side backend that ships a battery passport by default. It provides mine-to-pack traceability, tiered access, a consumer viewer, a supplier portal, and AI enrichment, all on synthetic data. You deploy it in your own workspace and adapt it to your own product groups.

One build, two payoffs: resilience and sustainability

The capability the DPP forces you to build is the very one that makes a supply chain resilient. A backend that can trace any item back to its raw materials, maintain a live record throughout its life, and share governed slices of that record does far more than pass a market-surveillance check: it enables recalls in hours and surfaces sourcing risks before they become headlines. The second payoff is equally concrete. Carbon footprint, recycled content, and repairability are precisely the metrics that sustainability teams struggle to assemble for ESG and CSRD reporting, figures too often estimated in spreadsheets disconnected from operations. Produced instead from governed, lineage-tracked data, the same source the regulator sees, sustainability reporting becomes a byproduct of running the business rather than a separate annual scramble.

What this does and doesn't do

No platform or accelerator can make you compliant. Only the economic operator achieves that, by meeting the regulation and validating its approach with regulators and its own legal team. What technology provides is the data capability the law assumes you already have: storing, serving, governing, and sharing passport data with unique identifiers, lifecycle accuracy, and tiered access. Data residency, EU registry integration, and adoption of the final data standard remain your responsibility.

The executive takeaway

Product traceability is no longer optional. It is mandated, dated, and global, mirroring what regulators already require across automotive, food, and minerals. Batteries are first, in February 2027, and for products in scope, a passport is a condition of selling into the EU. Miss it and you lose market access; treat it as a one-off compliance project and you will pay to rebuild it for the next product group. The smarter move is to decide the architecture once. Because the EU keeps the data with the operator, that decision sits with you, and it will outlast any single regulation. Build one foundation spanning operations, analytics, AI, and governed sharing, and the same investment that clears the deadline also delivers lasting supply-chain resilience and audit-ready sustainability reporting.

Sources

Explore the Databricks Digital Product Passport solution accelerator to see the backend end-to-end, then talk to your Databricks account team about your traceability data foundation. (Suggested format: button linking to the accelerator once published.)