Millie Summary:
- The EU Digital Product Passport registry went live in July 2026, passports for certain batteries become mandatory in February 2027, and iron and steel, textiles, aluminum, tires, and furniture follow on a published schedule.
- U.S. manufacturers that sell into Europe will be asked for product-level data on materials, origin, repairability, and environmental performance that most already hold somewhere and few can assemble on demand.
- The companies that respond well will treat the passport as a digital thread and data integration program, starting with an honest inventory of where product data lives today.
Many U.S. manufacturers will soon be asked, under the EU’s Digital Product Passport rules, for information they already own and still cannot produce on demand. The alloy composition of a steel bracket, the supplier lot behind a battery module, the recycled content of an aluminum housing, the repair history of an industrial pump: somewhere in the enterprise, each of these facts has been recorded. The trouble is where. It sits in a plant historian in Ohio, a supplier certificate attached to an email from 2023, a quality system that was never integrated with the ERP, and a spreadsheet maintained by the one engineer who knows how its columns map to part numbers. When a European distributor or a market surveillance authority asks for that information in a structured, machine-readable format tied to a specific product, the answer depends on whether someone can stitch those fragments together before the deadline.
That is where the risk sits. A request that should take minutes becomes a cross-functional exercise, with engineering, quality, procurement, and IT each pulling from its own system and making judgment calls about which record is current. An inaccurate product record submitted to a regulator creates more exposure than a late one. Meanwhile, the cost of all this effort rarely shows up as a line item, which is why leadership teams tend to underestimate it until a shipment is questioned or a contract renewal stalls.
What the Digital Product Passport Actually Requires
Think of the Digital Product Passport as an online record that travels with a physical product. Each product carries a QR code or similar tag, and scanning it pulls up information about that specific item, such as what it is made of, where its materials came from, how to repair it, and how to recycle it at the end of its life. The manufacturer is responsible for creating and maintaining that record, while the EU runs a central registry that gives every passport a unique ID so it can be found and verified. Not everyone who scans the code sees the same thing. A shopper might see care and sustainability details, while a customs or regulatory official sees the data needed to confirm the product meets EU rules. The goal, according to the European Commission, is to keep products in use longer and make EU product rules easier to enforce.
The legal foundation is the Ecodesign for Sustainable Products Regulation (ESPR), which has been in force since July 18, 2024. ESPR replaced an earlier directive that applied only to energy-related products, and it now reaches virtually all physical goods sold in the EU, with narrow exceptions such as food and medicinal products. The regulation is a central part of the Commission’s Circular Economy Action Plan, adopted in March 2020, which set out to make sustainable products the norm across the single market.
The rollout is phased, and the early dates are no longer hypothetical. According to the Commission’s indicative timeline, the passport registry became operational on July 20, 2026. Passports become mandatory for certain batteries, including electric vehicles, light transport, and industrial batteries, on February 18, 2027. Product-specific rules for iron and steel, construction products, textiles, aluminum, tires, furniture, mattresses, and energy-related products follow between late 2026 and 2029. Once each product rule is adopted, companies receive a transition period of at least 18 months. Separate EU laws covering toys, packaging, detergents, and critical raw materials also carry passport provisions.
For U.S. businesses, the important detail is that the obligation follows the product into the market, regardless of where it was made. The Commission notes that the registry identifier for imported products can be checked at customs. Exposure also travels through supply chains. A U.S. supplier of castings, wire harnesses, or battery components may never ship directly to Europe, yet its OEM buyers will need its data to complete their own passports and will push those requirements upstream through contracts and supplier scorecards. Medical device and life sciences manufacturers are not named in the first wave, but many already manage unique device identification and lot traceability for U.S. regulators, and the capabilities the passport demands are an extension of the same discipline.
The Real Problem Is Fragmentation
Most of the conversation about the passport has been framed as a compliance question, which leads companies to hand it to the wrong team. Compliance functions interpret regulations well, yet they are rarely equipped to reconcile part masters across four systems or to establish which supplier lot ended up in which serial number. Walk through what a passport would require for one product, and the information usually exists. What is missing is a reliable way to connect it.
Consider a mid-sized U.S. maker of industrial pumps that sells through a distributor in Germany. The distributor asks for the material composition and recycled content of a pump housing. Engineering holds the as-designed bill of materials in the PLM system, while the ERP holds the as-purchased version, with supplier part numbers that do not always match. Mill certificates for the castings sit as PDFs in the quality management system, and recycled content is known only to the foundry, which reports it inconsistently. The MES knows which castings went into which assemblies, but its records use work order numbers that no other system references. Somewhere in operations, a spreadsheet bridges the gaps. Each of these systems works well for the job it was bought for, and none was designed to answer a question about a single physical unit that cuts across all of them. Answering the distributor once is an inconvenience. Answering it for thousands of SKUs, in a standardized digital format that stays accurate as products are repaired and refurbished, is an architecture problem.
The Missing Digital Thread
The term digital thread gets used loosely, so it is worth being precise. A digital thread is the connected record that links a finished unit to the raw materials, suppliers, process conditions, inspections, and field events that shaped it, using identifiers that every system recognizes. With a working thread, a manufacturer can trace backward from a serial number to the lots and suppliers inside it, and forward from a supplier lot to every unit it touched and every market those units reached. Product genealogy is the technical core of that capability, and a Digital Product Passport is essentially a regulated, externally visible view of it.
The quickest way to test whether a thread exists is to imagine a supplier calling to report a nonconforming batch of resin. How long would it take to identify every affected unit, where each one shipped, and which are still in the warehouse? Some regulators have already set the pace. The FDA’s food traceability rule requires covered companies to hand over traceability records within 24 hours of a request, with enforcement starting in July 2028. In many manufacturing plants, the same question can take days, assembled by people working through production records and shipping logs by hand. That gap has consequences well beyond regulation, from recalls scoped wider than necessary to root cause investigations that end in educated guesses.
Sustainability and service data show the same pattern. Many manufacturers calculate emissions at the corporate or plant level and allocate them across products, an approach that does not hold up when a buyer or regulator asks about a specific product. Repair history, meanwhile, often sits in a service platform that never feeds back to engineering. Together these disconnects mean the company cannot tell a complete, verifiable story about any single product it makes.
Where IoT Fits In
Over the past decade, many manufacturers invested heavily in connected factories, instrumenting equipment and standing up industrial IoT platforms to stream machine data into historians and cloud storage. Most of those programs were justified by equipment effectiveness and predictive maintenance, and many delivered on that promise. What they rarely delivered was traceability. Sensor data is typically stored by asset and timestamp. It records that furnace four held a certain temperature profile between 2:10 p.m. and 3:40 p.m. on a Tuesday afternoon. It does not record which parts were inside the furnace or which material lot they came from.
Collecting data and making it usable for product records are separate achievements. To become part of a product’s digital record, machine data needs context: a join between the time-series stream and the production order, the work-in-process location, and the genealogy that says which serial numbers were at that station at that moment. That contextualization layer is the piece most IoT programs skipped, because the original use cases did not need it. A maintenance model cares about vibration on a spindle. A product record cares about what that spindle was cutting.
Once the context is in place, IoT data becomes some of the most valuable evidence a manufacturer has. Heat treatment profiles can demonstrate that a safety-critical part was processed within specification. Energy consumption measured per batch gives product-level carbon figures a far more defensible basis than plant-wide estimates. Manufacturers that already have sensor infrastructure are closer to passport readiness than they may realize, provided they make contextualization and product identity the next phase of that investment.
Why This Is Bigger Than Europe
It would be easy to read the passport as a European idiosyncrasy and plan to deal with it only for the product lines that ship there. That would miss the larger signal. The passport is the most concrete expression so far of a direction that manufacturing has been moving in for years, toward products that carry a verifiable account of where they came from and how they were made. The Commission’s own rationale makes the logic clear: its ESPR overview notes that more than 80% of a product’s lifecycle environmental impact is determined at the design stage, which is why regulators now want data that follows the product from design through end of life. The Commission is also preparing a Circular Economy Act, due for adoption in 2026, aimed at building a single market for secondary raw materials, which will raise the value of knowing exactly what materials a product contains.
The same pressure is arriving from other directions. In automotive, Drive Sustainability, a partnership of more than 20 vehicle manufacturers including Ford and Toyota, reports over 127,000 supplier sustainability assessments completed, and responsible sourcing of raw materials is one of the areas those assessments cover. Sustainability reporting is moving from corporate averages toward product and supplier specifics. A manufacturer that can answer these questions from a governed data foundation answers each of them faster and more credibly than one that rebuilds the answer manually every time.
What Manufacturing Leaders Should Do Now
Start small and concrete. Pick one product family that ships to Europe, or that a European-facing OEM buys from you, and trace a single finished unit end to end, documenting every system it touches and every point where someone has to decide which record is correct. Tools can shorten this work considerably. Microsoft Purview, Microsoft’s data governance platform, can connect to common ERP systems, databases, and data warehouses to build a catalog of what data exists and how it moves between systems. For the unstructured material every plant accumulates, such as supplier certificates and inspection reports, AI document processing can extract composition and origin data that would otherwise require someone to open each file. MILL5 can run this discovery as a focused engagement, producing a working map of where one product’s data actually lives and which gaps matter most.
Next, stress-test product genealogy. Run a mock request with a deadline, such as a simulated supplier recall or a passport request from a distributor, and measure how long the answer takes and how much the team trusts it. Most manufacturers discover that the answer depends on two or three people who know how to join records by hand. Microsoft Fabric changes that by bringing ERP, MES, QMS, and PLM records into a single copy of data in OneLake, where lot-to-serial relationships can be modeled once and used by anyone with access. A Power BI report built on that model lets a quality engineer trace a nonconforming lot forward to every affected unit and shipment without a multi-day manual search. MILL5 builds these genealogy models in Fabric, starting with the product family from the first step so the value is visible before the program scales.
Governance comes next, and it becomes practical once the data is visible. Map the business processes where product data is created and changed, from engineering change and supplier onboarding through production and field service, and assign an accountable owner to each. Agree on one definition of part, lot, serial, and supplier across systems, and write data obligations into supplier agreements so that recycled content and origin information arrive in a usable form. Microsoft Purview supports this work by tracing lineage from source system to report and by running data quality rules that flag a missing lot number or a mismatched supplier ID before it reaches a passport. MILL5 helps clients stand up Purview alongside the governance model itself, because a catalog without agreed definitions and owners tends to go stale quickly.
The final step is architectural. Point-to-point integrations between ERP, MES, QMS, and PLM tend to multiply until no one can maintain them. A more durable design is a governed data layer organized around product identity, where operational systems publish their records once and every downstream use draws from the same source. In a Microsoft environment, OneLake serves as that layer. Azure IoT Operations collects machine data at the plant edge, and Fabric Real-Time Intelligence joins those sensor streams to production orders so that a furnace temperature profile is tied to the parts that were inside it. With that foundation in place, AI becomes far more useful. Models built with Azure AI services can predict quality escapes or assemble a draft passport record from verified data, and Copilot in Fabric lets engineers and analysts ask questions of product data in plain language. MILL5 works across both ends of this architecture, from IoT and connected systems on the plant floor to data and AI in the cloud. Building this foundation is a multi-year effort for most organizations, which is precisely why it needs to start before the product rule for your category is published.
The Cost of Waiting
The 18-month transition period that follows each product rule sounds generous. For a company that already has clean master data, consistent identifiers, and a functioning digital thread, it probably is. For everyone else, it is shorter than the time it typically takes to rationalize part masters across plants, bring suppliers into a structured data exchange, contextualize years of sensor data, and stand up the governance that keeps all of it accurate. Those are foundational programs, and foundational programs do not compress well under deadline pressure. Manufacturers that wait until the rule for their category is published may find they are starting a multi-year effort with a fraction of that time available, while competitors who started earlier are already answering their buyers’ questions.
The passport will eventually reach most physical products sold into Europe, and the data expectations behind it are spreading well beyond Europe’s borders. The manufacturers that come through this well will be the ones that started treating connected product data as a strategic asset before anyone required it of them.
Many manufacturers already possess the information regulators, customers, and partners are asking for. The challenge is connecting it. If your organization is evaluating product traceability, digital thread initiatives, IoT modernization, data governance, Microsoft Fabric, or enterprise data architecture, contact MILL5 to discuss how to prepare for the next generation of manufacturing transparency requirements.
