Do battery raw material suppliers need passport data?

Usually, no. In most cases, a raw material supplier does not create or publish the battery passport itself. That legal duty is more likely to sit with the battery manufacturer or, in some cases, the importer or other economic operator that places the battery on the EU market.

But that is not the same as saying upstream suppliers are unaffected. If your customers need passport content, they will come to you for the raw material, sourcing, due diligence, traceability and carbon data that sits upstream in the chain. So when people ask whether battery raw material suppliers need to provide passport data, the practical answer is often yes, even where the formal obligation to issue the passport belongs to someone else.

The battery passport is intended to make a battery more transparent across its life cycle. At a basic level, it is a digital record linked to an individual battery or battery model, designed to support compliance, traceability, sustainability claims, market surveillance and, over time, reuse, repurposing and recycling.

Under the EU Battery Regulation, the passport is part of a wider compliance structure for certain batteries placed on the EU market. It is not only about a label or a QR code. It is about making defined information accessible to the right parties, in a consistent form, so that manufacturers, importers, authorities, customers and downstream operators can identify what the battery is, where key inputs came from, and how the battery performs against regulatory requirements.

That creates an immediate upstream data need. A battery manufacturer cannot produce a credible passport from finished product specifications alone. It needs information from the supply chain, including data on constituent materials, origin, recycled content where relevant, due diligence controls and carbon-related inputs. Some of that information exists at cell level or pack level, but some of it starts much earlier, with processors, refiners and raw material suppliers.

This is why the question matters. A supplier of lithium chemicals, nickel products, cobalt intermediates, graphite materials or other battery inputs may never upload the final passport, but the passport framework still reaches back into its records. If we supply a material that ends up in an industrial battery, an EV battery or an LMT battery within scope, our customer may need us to substantiate data that appears later in the passport or supports declarations behind it.

The purpose is not only traceability for its own sake. The Regulation also links battery compliance to due diligence and sustainability topics. That means upstream information is often needed to support more than one requirement at the same time. A customer may ask for one dataset because it feeds the passport, another because it supports due diligence policy implementation, and another because it is needed for a carbon footprint declaration or technical documentation.

If you want a clearer view of the likely data fields involved, our guide to what data a battery passport needs is a useful starting point.

The key distinction is between the company that must place compliant batteries on the market and the upstream supplier that provides materials or components into that chain.

In the EU, the legal duty is generally carried by the relevant economic operator responsible for the battery placed on the market. In practice, that is often the manufacturer established in the EU, or the importer if the manufacturer is outside the EU and the importer is the operator placing the product on the Union market. Depending on the supply model, an authorised representative may handle some tasks, but the underlying compliance burden does not simply disappear.

For battery passports specifically, the party responsible is normally the one placing the in-scope battery on the market under its name or trademark, or importing it into the EU. That operator is the one most likely to have to ensure the passport exists, contains the required information, is kept up to date where required, and is available to the relevant users and authorities.

A raw material supplier is usually further upstream. If we sell mined, processed or refined material to a cathode producer, precursor producer, active material producer or cell manufacturer, we are not normally the operator issuing the final battery passport. The same is often true for suppliers of chemical feedstocks, metal salts, foils and certain other battery inputs.

That said, there are cases where the position changes. If a business moves downstream and supplies a finished battery, or imports one into the EU, it may become the responsible economic operator for that product. The label "raw material supplier" is not decisive on its own. What matters is the role the company plays in the actual placing on the market.

The UK position is different in one important respect. The battery passport regime discussed here is driven by EU law. The UK has its own product regulation framework after Brexit, and UK businesses exporting batteries or battery-containing products into the EU still need to meet EU requirements for those sales. So a UK raw material supplier may not face a standalone domestic UK battery passport duty for UK-only transactions, but it can still face very real customer demands when supplying into EU-bound chains. We cover that point in more detail in battery passport rules UK exporters need before EU sales.

Even where we do not issue the passport ourselves, there are several common situations where we may still need to provide passport-related data.

The first is the most obvious. Our direct customer asks for it as part of its own compliance process. If we supply a material used in an in-scope battery, the customer may need upstream evidence to complete required passport fields, maintain technical documentation, answer an auditor, or satisfy a notified body or market surveillance authority. In that case, the request may come through a supplier questionnaire, a contract schedule, a portal upload requirement or a periodic compliance review.

The second is where the data is needed to support due diligence obligations. The EU Battery Regulation includes supply chain due diligence requirements for certain economic operators placing batteries on the market. Those operators need policies, risk management, third-party verification in relevant cases, and information on the sourcing of raw materials such as natural graphite, cobalt, lithium and nickel. Upstream suppliers are often the only realistic source for parts of that evidence trail.

The third is where the customer needs carbon footprint inputs. Carbon footprint rules and declarations do not mean every raw material supplier must calculate a final battery footprint. But upstream process and transport data, energy mix information, production route details and plant-level emissions data may all be requested because they affect downstream calculations.

The fourth is traceability. A customer may need to connect a battery or battery model back to batches, production sites, countries of origin or refining routes for key materials. If we cannot identify which shipments, lots or plants fed which customer deliveries, the downstream chain becomes difficult to defend.

The fifth is contractual flow-down. Many businesses are now writing battery passport and due diligence clauses into supply agreements. Even if a legal obligation does not apply to us directly under the Regulation, a customer can still require us by contract to provide specific datasets, keep them current, retain records for a stated period, and cooperate with audits or corrective actions.

The sixth is prequalification for future supply. Some customers are not yet under an active passport submission deadline, but they are already selecting suppliers based on readiness. A supplier that can answer structured data requests quickly is easier to onboard than one that relies on ad hoc spreadsheets and incomplete declarations.

So, do battery raw material suppliers need to provide passport data? Often yes in practice, because the operator with the legal duty cannot meet it without upstream inputs. The obligation to publish and the obligation to supply supporting information are different things.

The exact request will depend on the battery type, the material, the customer’s position in the chain and the implementation timetable. Still, most requests fall into a few familiar categories.

First, basic material identification. Customers may ask for product name, grade, specification, CAS number where relevant, composition range, safety documentation, production site and supplier entity details. They may also ask which battery-relevant materials the product contains and in what proportion.

Second, origin and sourcing data. This can include country of origin, mine or extraction source where known, refining location, processing site, smelter or refiner identity, and chain of custody information. Some customers will ask for this at batch level. Others will accept site-level or period-level declarations if the material is mass balanced or pooled upstream.

Third, due diligence documentation. Expect requests for supplier codes of conduct, human rights and responsible sourcing policies, grievance mechanisms, risk assessment procedures, audit reports, corrective action records and evidence of alignment with recognised due diligence frameworks. Customers may also ask whether the material includes cobalt, lithium, nickel or natural graphite sourced from affected or high-risk areas, and how that risk is assessed.

Fourth, recycled content and secondary material information, where relevant. If a customer is preparing for recycled content declarations or wants to support circularity claims, it may ask what proportion of the supplied material is primary versus secondary, how that is calculated, and what documentary support exists.

Fifth, carbon and environmental data. This may include cradle-to-gate emissions for the supplied material, methodology used, system boundaries, allocation rules, energy sources, transport assumptions, verification status and reporting period. Some customers will accept product category averages at first, but many will move toward more specific data as compliance matures.

Sixth, traceability records. Customers may ask for lot numbers, production dates, shipment references, purchase order links, invoice references, plant identifiers and records showing how delivered material maps to upstream sources. This is often where otherwise capable suppliers struggle, not because they lack the material data, but because it sits in separate ERP, quality, EHS and procurement systems.

Seventh, declarations and attestations. These can include signed statements on origin, sanctions compliance, conflict-affected sourcing, restricted substances, regulatory conformity and data accuracy. A customer may need a formal declaration even where the underlying facts are already known informally.

If you are seeing overlapping requests from different customers, that is normal. The solution is usually not to answer each one from scratch, but to organise a core dataset that can be reused. Our article on how to organise battery traceability data without gaps sets out a practical way to do that.

The best approach is to prepare for structured data sharing without building a compliance machine that is bigger than your current role requires.

Start with scope. Identify which of our products are likely to enter battery supply chains, and which customers are most likely to need passport-related information. A supplier selling a specialist lithium compound into cathode production should prepare differently from a business whose battery exposure is occasional and indirect. The point is to focus effort where the requests will actually come from.

Next, map the data we already have. In most businesses, the required information is not missing, it is scattered. Product specifications may sit with technical teams. Country of origin records may sit in procurement. Batch and lot traceability may sit in ERP or MES systems. Carbon data may sit with sustainability or EHS teams. Supplier due diligence documents may sit in legal or compliance folders. We should list each likely data field, where it currently lives, who owns it and how often it changes.

Then define a minimum controlled dataset. Not every customer needs every field at the same level of granularity. Build a core pack that covers the requests we are most likely to receive, such as product identity, production site, source information, due diligence status, traceability references and available carbon data. Keep it version-controlled, dated and attributable to named internal owners.

Assign ownership clearly. If no one owns a field, it will fail under pressure. We should decide who approves origin statements, who validates emissions data, who releases customer declarations and who handles escalations where source information is incomplete or commercially sensitive.

Set rules for evidence. A declaration without supporting records is fragile. For each key field, we should know what evidence supports it, whether that is supplier documentation, internal system data, transport records, audit reports or calculation files. This matters when customers ask follow-up questions or when data is challenged.

Build a response workflow that matches our size. For many suppliers, a simple process is enough: intake request, classify it, pull the standard dataset, review any non-standard questions, approve release, log what was sent. The problem is usually not complexity, but inconsistency. Different account managers send different answers, old templates stay in circulation, and no one can tell which declaration is current.

Be careful with confidentiality. Some customers will ask for site, source or process information that is commercially sensitive. That does not mean refusing every request. It means deciding in advance what can be shared openly, what needs an NDA, what can be shared in aggregated form, and what requires management sign-off.

Review contracts before the pressure point arrives. If customers are flowing down passport, due diligence or traceability obligations, we need to understand response times, audit rights, update duties, liability language and any promise to maintain specific records. It is much easier to negotiate these points before a supply issue arises.

Finally, avoid overbuilding. Many upstream suppliers do not need a full end-to-end battery passport platform for their own legal role today. But they do need clean, retrievable, defensible data. If customer requests are increasing, or if we sit close to cell or battery manufacturing, it is worth looking at battery data management that cuts compliance risk so the process scales before it becomes a bottleneck.

The practical answer to the question is straightforward. Raw material suppliers usually do not issue the battery passport, but they often do need to provide the data that makes it possible. The businesses that prepare early, map their data properly and answer requests in a controlled way will be easier to buy from, easier to audit and less exposed when battery passport requirements tighten across the supply chain.