Battery Passport ERP & MES Integration Guide

Manual passport entry works for pilot batches. It fails at production scale. High-volume manufacturers need battery passport ERP integration and battery passport MES integration to automatically create, publish, and label passports as batteries roll off the assembly line — without operators switching between systems.

Why Integration Matters

A single EV pack line may produce 200+ units per day. Each unit needs a unique identifier, populated Annex XIII fields, a published registry URL, and a printed QR label — all tied to the production serial number in your MES. Manual entry at this volume guarantees errors, delays, and enforcement risk.

Integration Architecture Options

Method	Best for	Latency
REST API (real-time)	MES-triggered passport at end-of-line test	Seconds
Bulk CSV import	Batch backfill, legacy inventory, nightly sync	Minutes
Serial pre-allocation	Reserve UID ranges before physical assembly	At planning stage
Webhook callbacks	Downstream ERP update on passport publish	Event-driven

Typical MES Integration Flow

1. Work order created — MES requests UID pre-allocation from PassCell API
2. Assembly complete — MES sends test results (capacity, voltage, SoH baseline)
3. Passport published — PassCell returns QR URL and label asset
4. Label printed — MES triggers print station with QR + human-readable UID
5. Ship confirmation — ERP marks unit as EU-compliant and ready for export

ERP Data Mapping

Your ERP already holds much of the data Annex XIII requires. Map these fields first:

• Material master → chemistry, model, weight
• BOM → cell supplier, component composition
• Production order → manufacturing date, facility, batch/lot
• Quality records → test results, conformity certificates
• Customer/shipment → EU destination, importer reference

Gaps — typically carbon footprint, due diligence, and recycled content — must be sourced from supplier portals or LCA systems and merged at passport creation time.

PassCell API Endpoints

Growth and Enterprise plans include REST API access:

• POST /serials/allocate — reserve UID block for a production run
• POST /passports — create and publish passport with Annex XIII payload
• PATCH /passports/{uid} — update lifecycle fields (SoH, performance)
• GET /passports/{uid}/qr — retrieve QR code asset for label printing

Full API documentation is available in the PassCell dashboard under Integrations. See also our data checklist for required field mappings.

Implementation Timeline

Phase	Duration	Deliverable
Field mapping workshop	1–2 weeks	Annex XIII ↔ ERP/MES field matrix
API integration dev	2–4 weeks	End-of-line passport automation
Pilot line validation	1–2 weeks	100-unit scan-test batch
Production rollout	1 week	Full line activation with monitoring