Your portalavailable
REST API v1 delivers models, passports and passport URLs into your interface.
Partner programme · White label
The battery passport - under your brand
You own the customer relationship, we own the regulatory logic. Three ways to deliver the EU battery passport under your name: through our API inside your own portal, as a passport page in your design on your domain, or as a partner licence with your own pricing.
3routes under your brand
71EU data points in the mandatory model
EUhosting in Germany, DPA included
Delivery under your brand
pass.your-brand.com/01/04012345678901/21/BPW-2027-00472
Your logo · your colour · your imprint
Your portal via REST API v1available
Passport page in your designin preparation
Your own domain in the QR codein preparation
Partner licence with your own customerson request
Mockup · shows the current state
How it works
One data trunk, three ways out
The regulatory logic stays with us, the brand stays with you. The same data leaves the system through whichever route you pick.
Your data
- Battery models with mandatory fields
- Serial numbers from CSV, Excel or ERP
- Supplier values through token links
- Evidence and certificates
ProcessingBatteriepasswerk
- 71 EU data points as a versioned rule base
- One passport per unit, GS1 Digital Link, short link
- SHA-256 hash chain across every version
- The three access levels of the regulation
Under your brand
Passport page in your designin preparation
Logo, colour and legal texts on the public page behind the QR code.
Partner licenceon request
Your own tenants, your own prices, your own invoice to your customers.
The route changes nothing about the data: same passport, same verifiability, same retention across the battery lifetime.
Three routes
From the API to a full partner licence
The routes differ in how much you build yourself and how much of the brand you take over. Each card states what ships today and what is project work.
Your portal, our engine
You pull models, passports and passport URLs through REST API v1 into your own interface and generate the QR codes in your system. Your customers only ever see your application - our brand appears nowhere.
- REST API v1 to OpenAPI 3.1, one key per permission set
- Per passport: public URL, GS1 Digital Link and short link for your own QR codes
- Test keys in dry-run mode before a single record is created
- Interface, design and customer communication stay entirely yours
available
Branded passport
The public passport page behind the QR code on the battery carries your logo, your accent colour and your legal texts. On request under your own subdomain, so the printed URL carries your brand too.
- Logo, accent colour, wordmark, imprint, privacy notice and support contact
- Optional own subdomain, for example pass.your-brand.com
- The QR code stays GS1 compliant, the path structure does not change
- Important: the domain in a printed code is irreversible and must stay reachable for good
in preparation · add-on
Partner licence
You sell the battery passport under your name to your own customers, set your own prices and invoice them yourself. We provide the platform, the adaptation to legal changes and second-level support behind you.
- Your own tenants under your roof, data separated per end customer
- Your pricing, your invoice, no payment relationship between us and your customer
- Priced per tenant you serve, plus the group's model and passport volume
- Processing as a sub-processor, documented properly
on request · contract
Who this pays off for
Four situations where white label is the right answer
01
System integrators and ERP partners
You serve manufacturing customers with ERP or MES and want to ship the passport obligation as a module instead of handing it to a third party.
02
Consultancies and testing houses
You advise on the battery regulation and need a tool that carries your signature instead of sending your clients to someone else's brand.
03
Manufacturers with their own portal
Your customers are used to one login. The passport belongs in there, not on a foreign page with a foreign logo.
04
Associations, clusters and platforms
You aggregate many small operators for whom a contract of their own is too heavy, and want to offer the passport under your roof.
Why not build it yourself
What you buy along by not starting from zero
The obligation logic lives as data
Which of the 71 EU data points applies to which category from which date sits in a versioned rule base, not in code somebody has to chase. When the law moves, we change the rules, not you your software.
GS1 Digital Link done properly
GTIN padded to fourteen digits, path structure per URI Syntax, resolution listed in the GS1 PINE registry. Exactly the kind of detail a first in-house draft almost always misses.
The three access levels of the regulation
Public, professional for recyclers and authorities, internal - including the application and logging path for professional users. An access model you cannot retrofit.
Tamper protection from day one
A SHA-256 hash chain across every version and an append-only audit trail. Verifiable in the browser, without extra software and without a wallet.
Data sourcing instead of empty forms
Suppliers submit through a token link without an account, evidence is proposed by document extraction and still needs approval. The bottleneck of a passport is the data, not the form.
Operations you would otherwise carry
Hosting in Germany, a data processing agreement from day one, retention across the battery lifetime, export as JSON, CSV and audit report.
Staying honest
What we do not promise
White label means your brand on our substance, not arbitrary software on demand. Four limits we state up front rather than afterwards.
No theme editor. Logo, two colours, wordmark and legal texts - no free CSS and no custom fonts.
No raw-material tracing back to the mine. Specialised vendors do that, and we say so openly in our vendor comparison.
No separate instance or dedicated database per partner. Tenant separation runs inside the database, not through copies of the application.
No transfer of responsibility. Whoever places the battery on the market remains the responsible economic operator, whatever logo sits on the passport page.
How it starts
From intro call to first batch
01
Intro call, 30 minutes
Which batteries, which customers, which volume, which deadline. At the end you know which of the three routes fits you - including the case where none does.
02
Agree tier and price
Volume, brand scope and support depth set the price. The base is the Enterprise plan from 1,290 euros per month; the partner licence is agreed individually on top.
03
Set it up technically
Test keys in dry-run, sample data, your portal or your brand on the passport page. No real passports come into existence in this phase.
04
Go live
Contract, live keys, first real batch. From here printed QR codes are final, which is why the domain is fixed beforehand.
Law and responsibility
What changes with your brand - and what does not
Responsibility for the accuracy and completeness of passport data stays with the economic operator placing the battery on the market. A different logo on the passport page moves no obligation under Regulation 2023/1542.
A partner licence creates a processing chain: your customer is the controller, you are the processor, we are the sub-processor under Article 28(4) GDPR. That is contracted explicitly, not assumed silently.
As soon as our brand leaves the passport page, the imprint and privacy notice of the visible brand become mandatory - without them we do not switch the branding on.
The passport must stay reachable across the battery lifetime. Your own domain is therefore a lasting obligation that belongs in the contract, not in goodwill.
Frequently asked
Brand, price, liability and exit
Through REST API v1, today: you pull models, passports and passport URLs into your own portal and generate the QR codes yourself, with our brand nowhere in sight. The branded public passport page and the partner licence are contracted project work - we implement them for partners, but they are not a self-service switch inside the product.
That depends on the tier you pick. On the API route your customers only see your application. On a branded passport page a discreet technology note stays by default, because auditors value a nameable technical party; it can be removed in the top tier.
The entry point is the Enterprise plan from 1,290 euros per month. Branded passport and partner licence sit on top and follow passport volume, the number of companies you serve and support depth. We name the figure in the intro call, not in a table, because without your volume it says nothing.
Yes, that is part of the branded passport. Your subdomain is pointed at our infrastructure by CNAME and the certificate renews automatically. Two things are binding: the domain has to be settled before the first label print, because a printed code cannot be changed, and it has to stay reachable permanently.
The economic operator placing the battery on the market. We supply the platform, the mandatory-field logic and the proof that data has not changed since issue. No software can take over the factual accuracy of the values entered, and nobody should promise you that.
That belongs to the partner licence, not the branded passport. The reason is plain: the public passport page is seen by your end customers and auditors, the dashboard only by your own staff, who know who they bought from.
That is exactly the partner licence. Every end customer stays a separate tenant with separated data; your staff get one access across them. Mixing client data into one shared account is deliberately not possible.
The data belongs to your customer and travels in full: export as JSON, CSV and audit report is included in every plan. QR codes already printed must keep resolving, so the contract settles the run-on period and retention before the first code is printed.
Become a partner
Let us talk about your brand
Thirty minutes are enough to work out which of the three routes fits your business and what it costs. No slide deck, just your cases against our product.