Every e-bike pack gets
its own passport.
From 18 February 2027 each e-bike battery sold in the EU needs an electronic passport behind a QR code. We built the data pipeline, the identifiers and the role-based views so the exporter's buyer stopped waiting for spreadsheets.
This is a composite scenario built from how we deliver this kind of work. The client is fictional and the figures are targets, not measured results. We will replace it with a named engagement when a client agrees to be quoted.
A bicycle exporter in Bangladesh shipping electric-assist bikes to Germany and the Netherlands, about 900 staff, cells and packs bought from two suppliers abroad
- The exporter's largest buyer sent a 38-field data request in August 2026: cell chemistry, weight, capacity, hazardous substances, dismantling information, test reports. Most of it lived in supplier PDFs, three spreadsheets and an ERP that identified batteries by purchase order, not by pack.
- No pack had a unique identifier. Nobody could say which fields were public and which were restricted to repairers and authorities. The team's estimate for answering one buyer by hand was three weeks per model.
How we approached it.
Scope against the regulation
We mapped the buyer's 38 fields to Regulation (EU) 2023/1542 and the Commission's data-point guidance, which lists 49 mandatory points for LMT batteries, and marked the ten that can stay empty in February 2027.
Identifiers first
Each pack received a unique identifier in a GS1 Digital Link, printed as the QR code that the regulation requires on every battery from 18 February 2027.
Supplier evidence intake
A portal where both cell suppliers upload values with the document that proves them. Missing or conflicting values land in an exception queue instead of a passport.
Role-based views
One identifier resolves to four views: public, legitimate interest, authorities, and the individual battery's own data, following Annex XIII.
Registry connector
Registration of each passport through the EU DPP Registry API as a verified economic operator, tested in the registry's test environment.
Try it yourself.
A simplified illustration with made-up data. It plays once when it scrolls into view, and you can pause it or step through.
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
Step 1 / 4 Public: 12 fields, such as pack model, chemistry and the carbon footprint class.
What we built.
- Passport data model covering all 71 guidance data points, with mandatory, optional and not-yet fields
- Supplier evidence portal with attachments, validation rules and an exception queue
- Identifier and QR generation at pack level, printed on the label line
- Resolver with four role views and an access log
- Registry connector and open-format export (JSON, CSV) without vendor lock-in
- Document versions in Dynodoc so a changed test report keeps its history
Outcomes (targets).
These are the results we would aim for. They are not measured results from a named client.
- Target49 / 49mandatory LMT fields mappedwith the ten not-yet fields marked for 2027 and 2028
- Target3 wks to 4 dayssupplier data turnaroundper model, from first request to validated values
- Target0passports with unverified mandatory fieldsevery value carries its evidence document
- Target1,200packs registered in the test environmentbefore the first commercial shipment
Timeline and stack.
10 weeks from discovery to a working pilot on two bike models
What we learned.
- The identifier comes before everything else. Without a pack-level ID there is nothing to attach data to.
- Supplier evidence is the hard part. The portal matters more than the passport page.
- Who may see what is a product decision. It has to be designed, not left to a database setting.
How we would deliver it.
Want this
for your business?
Message an engineer on WhatsApp or send a brief. We agree scope and price before work begins and build in small working steps you can test.