How Does Software Handle Supplier Data for Passports?

Software for supplier data is the system that collects, verifies and transfers data from material and component suppliers into the battery passport, covering chemistry, hazardous substances, critical raw materials, recycled content and due diligence information. Supplier data are the largest source of passport content, and they are also the largest source of passport error, because supplier data arrive in many formats, with different vocabularies, different units and different verification levels. The software task is to impose a single passport vocabulary and verification standard on that varied input, without losing the source evidence.

Supplier data work is a chain exercise. A cell supplier, a cathode material supplier, a housing supplier and a battery management supplier each hold part of the passport data, and no single supplier holds the complete record. The passport software must therefore request data field by field, track which supplier provided each field, verify the field against the passport requirement, and record the verification result. A system that accepts a supplier spreadsheet as a complete passport, without field mapping and verification, transfers supplier errors directly into the legal record.

What supplier fields does the passport need?

Supplier fields for the passport include material composition, chemistry, hazardous substances, critical raw materials, recycled content inputs, and supply chain due diligence information where Annex XIII and the due diligence chapter require it. Each field must be mapped to the Annex XIII source, with the supplier, the date, the test or declaration basis and the verification status recorded. A field supplied without a basis, such as a chemistry claim without a material declaration or test reference, is unverified data, and it should be marked as such until a basis is provided.

A field catalogue for supplier data should list each Annex XIII field, the supplier role that provides it, the format required, the verification method and the escalation route when data are missing. A catalogue that lists fields without supplier roles cannot be used to request data, and a catalogue that lists roles without verification methods cannot be used to judge data quality. The catalogue should be shared with suppliers before data are requested, so that suppliers can provide data in the required form on first submission.

How are supplier data requested and tracked?

Supplier data are requested through structured templates tied to the field catalogue, with a due date, a contact route and a completeness check on receipt. Tracking should show, per battery model and per supplier, which fields have been requested, received, verified and escalated, with the age of each open request visible. A tracking system that shows only that a supplier was contacted, without field level status, cannot support a passport deadline, because the missing field is hidden inside a general request.

Worked check: a cathode supplier provides chemistry data but omits a hazardous substance declaration. The tracking system shows the chemistry field verified and the substance field missing, with an escalation after the due date. The passport preparation pauses for that field, rather than proceeding with a gap hidden in a complete looking spreadsheet. A system without field tracking would show the supplier as having responded, and the gap would be discovered at passport review, when correction takes longer.

How are supplier data verified?

Supplier data verification covers format, vocabulary, unit, completeness and plausibility, together with source evidence where the field requires it. Format verification checks that the data use the passport vocabulary and units. Completeness verification checks that every required field for the battery model is present. Plausibility verification checks that values fall within expected ranges for the chemistry and design, and that related fields agree, such as material shares summing to the stated total. Source verification checks that a declaration, test report or calculation is attached where the field requires it.

Verification results should be recorded per field, with the method and the verifier named. A field verified by format check alone should not be presented as verified by test evidence, and a field verified by supplier declaration should be marked as declaration based. The distinction matters when an authority queries the field, because the evidence that supports the field differs. A verification record that merges all methods into a single verified label hides the evidence basis and overstates the assurance.

How are changes in supplier data handled?

Changes in supplier data, such as a change in material source, chemistry, supplier identity or recycled content input, must be treated as passport change events. The change should be recorded with the old and new values, the date, the supplier, the reason and the verification of the new value, and the passport fields affected should be updated under the updating rules. A change that is recorded only in a supplier email, without a passport field update, leaves the passport describing a battery that is no longer manufactured in that form.

Change handling should include a supplier change notification duty in the supply agreement, with a notice period that allows passport updating before the changed material enters production. A notification received after the change has entered production creates a period in which batteries on the market carry a passport that describes the former material. The agreement should state the notice period, the data to be provided on change, and the hold point where production pauses until the passport is updated.

What confidentiality limits apply to supplier data?

Supplier data confidentiality is governed by the passport access tiers and by the commercial confidentiality of supplier information that is not part of the passport tiers. Data that Annex XIII assigns to a restricted tier must not be disclosed through a broader route, and data that a supplier marks as confidential but that Annex XIII requires in a tier must be handled under the tier rules, not withheld on confidentiality grounds alone. The software must separate supplier confidential data that remain outside the passport from supplier data that populate passport fields, and must apply tier control to the passport fields.

A confidentiality map should list each supplier field, its passport tier or its non passport status, and its handling route. A map that treats all supplier data as confidential will withhold passport data that must be available. A map that treats all supplier data as passport data will disclose commercial detail that the tiers protect. The map should be agreed with suppliers before data collection, so that suppliers understand which data will appear in which tier and can raise a tier question before submission, not after publication.

How is supplier data quality reported?

Supplier data quality should be reported as a field level dashboard, showing completeness, verification status and age of open requests per model and per supplier, with trends over time. A quality report that states only an overall percentage hides the field that blocks a passport, while a field level report shows the blocking field and the supplier who holds it. As checked on 28 October 2026, supplier data quality is the practical constraint on passport readiness for many operators, and the report should be reviewed in the placing workflow, not only in a quarterly review. This guide gives general educational information only and is not individual legal advice. A reader with a specific battery or market decision should check the current Regulation text and any applicable delegated act, as checked on 28 October 2026, before acting.

This guide gives general educational information only and is not individual legal advice. A reader with a specific battery or market decision should check the current Regulation text and any applicable delegated act, as checked on 28 October 2026, before acting. Supplier data are passport evidence, and each field should carry its supplier, its basis and its verification status.