One Passport Platform, Every Market: The Multi-Jurisdiction Strategy

The nightmare scenario: a separate passport system for EU, another for the UK, a third for US state laws, and a fourth for Asian export requirements. The smart scenario: one battery passport platform with jurisdiction-specific field mappings on a shared data core.

The Hub-and-Spoke Model

Think of Annex XIII as the hub — the most mature, detailed schema with the nearest deadline. Every other jurisdiction is a spoke adding or modifying fields:

• EU (hub) — full Annex XIII, QR public registry, carbon footprint, due diligence
• UK (spoke) — EU fields + UK producer registration number
• US (spoke) — EU fields + IRA sourcing documentation references
• India (spoke) — EU fields + CPCB registration and swap-network ID

Why One Platform Wins

• Single supplier data collection effort
• One UID registry — no duplicate serial collisions across systems
• Unified API for MES integration
• One team trained on one dashboard
• Lower total cost than 3–4 point solutions

Implementation Principle

Capture the superset of data fields today. Publish the subset each market requires. When a new country mandates additional fields, activate them — don't rebuild.

PassCell is architected for this: category-aware forms, configurable public disclosure, and API-first design that scales across jurisdictions without platform migration.