IMPLEMENTATION WITHOUT CHAOS
We start with one model and real source data. We confirm the scope, responsibilities and completion criteria before we begin.
IMPLEMENTATION AT YOUR SITE
We go through your products, source documents and the work of individual teams. We set up who supplies the data, who approves it and how it will be maintained going forward.
Battery categories, your company's role, suppliers, number of models and units. The output is a list of requirements and a plan.
We map data and documents, identify gaps and align requirements for suppliers. We do not replace missing measurement results with estimates.
We set up the template, a sample of unit-level data, the content behind the QR code and access rights. We verify everything on real source data.
Depending on the scope, we connect systems, test imports and labels and train the team. We review the registration steps against the currently available interfaces. This is followed by acceptance and a go-live plan.
Extension to further models, data updates, support, availability monitoring and the procedure for changing or ending the cooperation.
A responsible person, a data sample, supplier contacts, cooperation from your system administrator and approval of the product information.
Implementation coordination, application setup, agreed checks, system integration, testing and handover to the agreed operations.
Both the start and the completion date depend on the readiness of the data, the application and the required interfaces. We confirm the scope and cooperation in advance, including any on-site work at the customer's premises.
SCOPE BASED ON YOUR COMPANY
Some need to prepare their first import. Others need to connect production, warehouse, service and several companies. We build the scope around the work that needs to be done — not the size of your logo.
You have the source data. You need to get it into the application correctly.
Approx. 2–3 weeks
You need to connect data, suppliers and responsible people.
Approx. 4–8 weeks
Passports must work as part of day-to-day operations.
Approx. 2–4 months
A common standard for multiple companies, countries or plants.
Approx. 3–9 months
If the standard template and import cover your needs, a self-service setup without an individual implementation project may be enough. Using the API (application programming interface) does not in itself mean a large implementation. We will confirm the availability of this option based on the readiness of the application and your data.
The stated durations are for planning guidance only, not a guaranteed deadline. The schedule starts from the agreed kick-off with the necessary source data and cooperation. Waiting for suppliers, missing tests and new requirements may extend the project. The pilot scope is not automatically the same as the scope of the live deployment.
WHY OFFERS DIFFER
Volume affects operations and capacity testing. The rollout effort, however, is often determined mainly by the state of the source data, the number of data links and who is responsible for them.
MODEL EXAMPLE A
Five models, one verified spreadsheet, clear serial numbers and approved documents. We set up the structure, test the import and train the administrators.
Project focus: setup and review.
MODEL EXAMPLE B
Dozens of variants, multiple manufacturers, inconsistent documents, automatic transfers from the warehouse and service access. First, we need to connect both the information and the way of working.
Project focus: alignment, integration and testing.
Both examples are illustrative; they are not references or price quotes. The same number of units does not in itself mean the same implementation.
What changes the effort: An approved spreadsheet is different work from several versions of PDFs, emails and missing specifications.
What we deliver: We identify sources, match the data, list discrepancies and pass the items to be completed to the responsible people.
The result for you: You know what can be published and what still needs confirmation.
What changes the effort: The same 5,000 batteries can mean two models, or dozens of variants from multiple manufacturers.
What we deliver: We set up the assignment to models, revisions and documents and a common procedure for completing data.
The result for you: Each specific battery has the correct version of its source documents.
What changes the effort: A one-off import is not the same as a daily data exchange between warehouse, production and service.
What we deliver: We agree on mapping and transfers; we test duplicates, error states and retries after an outage.
The result for you: The result does not depend on manual retyping or on a single error-free batch.
What changes the effort: A public manual, an internal document and a service document do not always have the same readers.
What we deliver: We design roles, approvals and separation of organisations; we verify access rights on specific scenarios.
The result for you: Everyone sees and changes only what matches their permissions.
What changes the effort: The scope may include manuals in further languages, service, repurposing and handover to a recycler.
What we deliver: We assign content to revisions and set up change owners and the handover of events between participants.
The result for you: The passport remains usable after the sale; it is not just a one-off web page.
What changes the effort: A pilot on one model does not test all data volumes, teams or operating situations.
What we deliver: Depending on the scope, we carry out acceptance and capacity tests, prepare a fallback procedure and hand over support.
The result for you: Before go-live, you know what has passed review, who handles incidents and how to proceed in case of an error.
SPECIFIC DELIVERABLES
Categories, company role, an overview of available data and specific gaps to fill.
One model, an agreed sample of units, import, content and verification of access rights.
Test results, open items, the extension budget and go-live conditions.
NO HIDDEN ASSUMPTIONS
Availability of documents, approved specifications and manufacturer contacts.
The quality of serial numbers and their link to the model, revision and specific battery.
Data owner, decision-making, system administrator capacity and available interfaces.
We don't sell an unconditional deadline. You will receive a schedule after the scope and source data have been verified. Laboratory tests, additional calculations and extensive data corrections are commissioned separately.
THREE DIFFERENT ITEMS
An API is a programming interface through which systems exchange data. Making it available, building a specific integration and its subsequent management are different services.
Access to the application and standard data exchange options according to your plan. Do you have your own developers? By agreement, they can build the integration themselves.
Capacities and available features are determined by the price list and the confirmed scope of service.
Mapping your fields, access to the source system, update rules and error checking. Testing and handover are part of the agreed project.
One-off work. The interface is not a ready-made connector for every enterprise system.
Monitoring transfers, handling failed batches and agreed maintenance. Optional, if you don't want to run the integration with your own team.
A recurring service with a defined support scope and a procedure for larger changes.
If building a specific integration is part of an implementation package, we list it within its scope — we don't charge it again as another project.
BUDGET UNDER CONTROL
You don't have to approve a large project blindly. First, we validate one model and a specific data flow. The subsequent extension gets its own scope, deliverables and decision point.
You will see setup, data preparation, integrations, testing, training and any migration. Separately from that: subscription, operations and optional services.
We confirm models, systems, companies, languages and cooperation. Work outside the scope will have its impact on price and timeline described in advance and will be submitted for your approval.
We agree on what the tests must demonstrate, who accepts the result and which open items block go-live. A pilot is not an automatic commitment to a company-wide deployment.
If you will print in your own facility, the rollout will also include the choice of device, label layout, a sample and training according to the agreed scope. On a specific battery, we verify that the label opens its correct passport.
On an agreed sample, we verify the assignment of the passport to the specific battery and the correct documentation. For integrations, we also test invalid input, a repeated batch and the procedure after a transfer interruption.
We go through public, internal and, where applicable, service access. We hand over the update procedure, the responsible persons and a list of unresolved items. For live operation, we additionally confirm service availability, recovery and support in line with the contract.
New measurements, expert calculations, legal opinions, professional translations, third-party licences, physical labels or changes to other systems are not automatically included in the flat fee. The offer will state explicitly what is included, what your team will supply and what may be ordered separately.
GUIDES
Explore a sample passport, documents, approvals and service. Fictitious data, clearly described simulations and a demo walkthrough without registration.
Read the guideHow to prepare a passport for e-bike and e-scooter batteries. Categories, suppliers, serial numbers, documentation and a single-model pilot.
Read the guideWhat to address for industrial batteries over 2 kWh: product boundaries, models, identity, supplier data, service and integration.
Read the guideA practical list for manufacturers and importers. Distinguish identity, model and unit data, documents, owners and missing source data.
Read the guideNEXT STEP
We will go through your batteries and source documents. We will propose the pilot scope, the cooperation required and the price. No automatic commitment to live operation.
Book an initial consultation