# abas ERP and the battery passport: integration pattern

> How data from abas ERP (abas Software (Forterro)) reaches the battery passport through the BatteryPass API: interfaces, workflows and when we checked them.

How data from abas ERP (abas Software (Forterro)) 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

  abas Software (Forterro)

- Deployments

  On-premise (abas ERP); Cloud (abas ERP (hosted))

- Checked

  community source only, 24 October 2026

- Managed integration

  —

From vendor marketing only: a REST API and abas Connect are named; there was no public developer documentation.

## Interfaces

| Interface                                                            | Protocol | Sign-in | Events | Objects                                      | Checked                                        |
| -------------------------------------------------------------------- | -------- | ------- | ------ | -------------------------------------------- | ---------------------------------------------- |
| [REST API](https://abas-erp.com/en/product/connectivity-iot)REST API | REST     | Token   | none   | Product/material master, Batch/serial number | community or marketing source only, 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.

## 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.

[Guide in the developer documentation (after sign-in)](https://passport.kabin.sh/docs/en/integrations/erp/abas-erp)

[← All integration patterns](https://kabin.sh/en/integrations)

Your data, a reviewed battery passport

In 30 minutes we show you how your existing spreadsheets, supplier data and serial numbers become a maintained battery passport.

[Request a demo](https://kabin.sh/en/contact)[See an example passport](https://kabin.sh/en/example-passport)