SAP Business One and the battery passport: integration pattern
How data from SAP Business One (SAP) reaches the battery passport through the BatteryPass API: interfaces, workflows and when we checked them.
An integration pattern, not a ready-made connector: your ERP or integration platform reads and writes through the BatteryPass API with an organisation key. The details below come from the vendor documentation and were checked on the date given.
- Vendor
- SAP
- Deployments
- On-premise (SAP Business One with Service Layer (SQL Server and SAP HANA))
- Checked
- vendor documentation, 24 October 2026
- Managed integration
- —
The Service Layer works with sessions: the middleware signs in with POST /Login and keeps the session cookie. Webhooks are not documented for the Service Layer; the middleware finds changes by polling.
Interfaces
| Interface | Protocol | Sign-in | Events | Objects | Checked |
|---|---|---|---|---|---|
| Service Layer /b1s/v1Service Layer (OData V3) | OData V3 | Session | none | Product/material master, Batch/serial number, Production order, Delivery/goods issue, Return | checked in the vendor documentation, 24/10/2026 |
| Service Layer /b1s/v2Service Layer (OData V4) | OData V4 | Session | none | Product/material master, Batch/serial number, Production order, Delivery/goods issue, Return | checked in the vendor documentation, 24/10/2026 |
Matching workflows
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.
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.
Import presets
- Generic CSV file: For any ERP and for files a middleware writes itself: GTIN, serial number, manufacturing date, facility (name or GLN), model version and battery status, with German and English column names.