Skip to content
BatteryPass
DE
Menu

Integrations

The data lives in the ERP. BatteryPass picks it up there.

Master data, serial numbers and deliveries come from your ERP, measurements from operation. For that, BatteryPass offers an API with organisation keys and a documented integration pattern for 17 ERP systems.

Discuss an integration API and MCP server

ERP systems

Integration patterns for 17 ERP systems

Per system: vendor, deployments, the matching interfaces with protocol, sign-in and events, and when and where we checked them.

Workflows

Workflows that work well

Every pattern refers to these workflows. They keep members in the loop: a key stages data, people review and approve.

  • Units from production

    Serial numbers from the production confirmation or goods receipt are staged as an import; members review, commit and approve before any passport appears.

  • Passport links back into the ERP

    The middleware follows the change feed and writes the GS1 Digital Link and the passport status to the serial number record in the ERP, so labels and delivery papers carry it.

  • Condition data from BMS and service

    A battery management system or a service tool reports measurements such as capacity fade or cycles; BatteryPass accepts newer measurements and publishes according to the organisation's policy.

  • Returns and repairs as lifecycle events

    Completed repairs, inspections and component replacements from service or return orders appear as events in the unit's history.

  • Product change leads to a new model version

    A change to the product master in the ERP triggers a notification; a member creates a new model version in BatteryPass. Declared data is never written automatically.

How it works

How the connection works

Keys with scopes

Organisation keys read data, report condition data or stage imports. They never approve and never publish.

Import by key

The ERP stages a file with units or values; members review it, take it over and approve it in BatteryPass.

Change feed

A gap-free feed reports what changed, for example published passports that the ERP stores with the serial number.

Frequently asked questions about integrations

Is BatteryPass a ready-made connector for our ERP?

No. The patterns describe which interfaces of your ERP fit and which workflows work well. Your team, your integrator or your integration platform builds the connection against the BatteryPass API. Managed connections, starting with Odoo, are planned.

Can an ERP publish passports directly?

No, on purpose. A key stages imports or reports condition data; taking over, approving and publishing stay with people in BatteryPass.

How does our ERP learn about changes in BatteryPass?

Through a gap-free change feed that it polls. Outbound webhooks are planned.

What does the check date of a system mean?

The day we read the interfaces in the vendor's documentation. It is not a review by the vendor and not a promise for every version.