Battery passport platform: features explained
The short answer
AkkuPass is a web-based battery passport platform for manufacturers, importers and authorised representatives who must provide a battery passport under Regulation (EU) 2023/1542. All you need is a browser: you describe each battery model once, add individual batteries through a form, an import or the API, publish the passport and print the QR label.
This article walks through how that works day to day: the workflow, the 24 official EU languages with optional AI translation, connecting your ERP, what people see when they scan the code, and how the pages carry your brand. For a short overview of the product, see the AkkuPass battery passport software page.
Last updated: 13 November 2026.
The workflow: models once, batteries every day
Most companies have a handful of battery models and a large number of individual batteries. AkkuPass keeps the two apart: you maintain a model's data once, and serial numbers are added as you produce or import.
1. Company profile and battery model
Your company name, postal address, website and contact e-mail go into the company profile once. Every new model receives a copy of these details, so nobody types them again.
The model form is built from the requirements of the Regulation and split into tabs. Each field shows its legal reference, a short explanation and an example. Your entries are saved automatically. For a similar model, duplicate an existing one and change only what differs.
2. Individual batteries: form, serial number range or import
You can add batteries one at a time, as a range of serial numbers or by import. For imports, AkkuPass generates an Excel or CSV template in your language. Rows with errors are reported with their row number, column and reason; the remaining rows are imported.
3. Check, approve, publish
Before publication, AkkuPass checks every battery against the rules for its category and lists what is still missing. If you want a second pair of eyes, switch on the approval step in the settings and a colleague approves each passport before it goes live. You can publish many batteries at once: AkkuPass tells you the exact number first, and any battery that fails the check is listed in the report with the reason.
A published version never changes. When you later edit a model's data, you work in a working copy. Published passports stay exactly as they are until you apply the change and publish the batteries again, which creates a new version.
4. Labels and codes
For published batteries you print labels on A4 sheets or thermal labels, as PDF or as ZPL for industrial printers. The code is a QR code or a Data Matrix code following GS1 Digital Link.
Each model's overview shows how many batteries are at each stage: “Draft”, “Checked”, “Published”, “Code issued”. Every role – editing, approval, printing, administration – sees its own open tasks. Two-factor authentication is mandatory for administrators.
A multilingual battery passport on three levels
For a battery passport, languages go beyond the user interface. AkkuPass distinguishes three levels:
- The portal. Each person on your team works in any of the 24 official EU languages, whatever their colleagues have chosen.
- The data fields. Field names and explanations exist in all 24 languages. For technical terms such as state of health or rated capacity, AkkuPass uses the wording of each language version of the Regulation.
- Your own texts. Some information you write yourself, for example the safety measures, the usable extinguishing agent and the information on the prevention and management of waste batteries. You keep these texts in the languages you choose for your company.
The public passport opens in the language of the phone that scans the QR code. Readers can switch languages, and your languages are listed first. If one of your texts is missing in the chosen language, the page shows it in your default language and says so. Labels are printed in the language you choose for each print job.
AI translation: every language sooner, and reviewed
If your texts so far exist only in English or one other language, AI translation fills in the rest much faster. It is optional: an administrator switches it on for the company with explicit consent, and without that consent it stays off. You can also never use it and enter your own translations.
A translation runs like this:
- You choose the text, the source language and the target languages – for each translation only the ones you need, from your company's languages.
- The AI suggests a text for each target language. AkkuPass checks every suggestion automatically: are numbers, units and codes unchanged, are the official terms of the Regulation there, is the translation roughly as long as the original?
- You see the suggestions language by language next to the current text, edit them if needed and accept each language separately. Suggestions with a warning are not selected automatically.
- Accepted texts go into the form and are saved like anything else you enter.
A suggestion that nobody has accepted is never published. If the source text changes later, AkkuPass marks its translations as possibly out of date.
Connecting ERP and other systems: REST API and webhooks
If your battery data already lives in an ERP, MES or online shop, there is no need to type it again. Through the versioned REST API and webhooks of the battery passport platform you can connect external systems such as SAP, Oracle or your own ERP. Specific integrations are tailored to your company's requirements.
Through the API, your system can:
- create and change models, batteries and their data, and start imports;
- check data and publish passports – an approval step you have switched on applies to the API as well;
- create print jobs and collect the finished labels;
- read the registration status and the scan statistics.
Webhooks notify your system when a passport is published, when an import or print job finishes and when the status of a registration changes. Every message is signed so that your system can verify where it came from.
An administrator manages access in the portal: each integration gets its own API key with exactly the permissions it needs, which can be limited to certain IP addresses, renewed without downtime or revoked immediately. The technical documentation is available to customers after sign-in as an OpenAPI file and a PDF guide, in English. For an example request, see the developer section of the home page.
What does someone see when they scan the QR code?
No app is needed: the phone's camera opens a web page whose basic view works without JavaScript. The key facts about the battery come first, followed by sections such as life cycle, voltage, efficiency and capacity, composition, marking and conformity, and legal basis.
The Regulation decides who may see which data. Public data is open to everyone; market surveillance authorities sign in with two-factor authentication to see restricted data. Which data point belongs to which level is set out in our battery passport checklist. On a real passport, the page also checks the digital signature and shows the result.
To see it for yourself, open the sample battery passport in English, with invented data for an e-bike battery. It is rendered with the same layout AkkuPass uses for real passports.
Your brand: accent colour, logo and own domain
- Accent colour. You choose one colour for links and buttons on the public page. AkkuPass only accepts colours with a contrast of at least 4.5:1 on white (WCAG AA), so the page stays easy to read.
- Logo. Your logo (PNG, JPEG or WebP, up to 128 KB) appears in the header of every public passport.
- Own domain. With a subdomain such as
pass.yourcompany.comand a CNAME record, your passports are served from your own address. Once the DNS record is verified, new QR codes use your domain; until then AkkuPass uses a subdomain of the platform.
An administrator can change the colour and logo at any time. The change applies to all public pages, including passports that are already published, whose data stays unchanged. The structure and order of sections are the same for every passport, so each one remains readable and accessible.
Frequently asked questions
Do we need to install anything to use AkkuPass?
No. AkkuPass runs in the browser. You only need the REST API if your own systems should transfer data automatically.
Can AkkuPass be connected to SAP or another ERP?
Yes. External systems such as SAP, Oracle or your own ERP connect through the REST API and webhooks. How the connection looks in detail depends on your system; specific integrations are tailored to your requirements.
Is AI translation mandatory?
No. It stays off until an administrator switches it on with consent. Even then, you decide for each translation which languages to translate into, and no suggestion is applied without your review.
In which language does the battery passport open after scanning?
In the language of the phone, if it is one of the 24 official EU languages. Otherwise it opens in your default language. Readers can switch languages at any time.
Can we change the colour and logo later?
Yes. An administrator changes them in the portal whenever needed. The public pages then show the new look, including passports already published; their data and versions do not change.
Next step
Open the sample passport on your phone to see the public page as a buyer sees it after scanning. If you first want to clarify who must create the passport and which data you need, read Who must create the battery passport? and the complete guide to the EU battery passport. To try the battery passport platform with your own data, apply for the pilot programme.