# abas ERP

> What is known about connecting abas ERP to BatteryPass, and what still has to be clarified.

> [!WARNING]
> The facts on this page come from vendor marketing only and are not checked against developer documentation; there was
> no public one. Confirm the interface and its sign-in with the vendor or your partner before a project.

> [!NOTE]
> This page describes an integration pattern. BatteryPass ships no connector for abas ERP and has no partnership with the
> vendor; nothing here is a vendor approval.

The vendor names a REST API and abas Connect. Whichever your installation offers, a middleware reads the serial numbers
of finished production orders with a technical user that may only read, writes a file with the `generic-csv` preset and
stages it as in [units from production](https://passport.kabin.sh/docs/en/integrations/workflows/units-from-production). Change events were not
checked; poll on a schedule until they are.

## Interfaces and how they were checked

- **Vendor:** abas Software (Forterro)
- **On-premise:** abas ERP
- **Cloud:** abas ERP (hosted)

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

An integration pattern, not a connector: BatteryPass ships no ERP connector and holds no vendor certification.

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

**Notes**

- `REST API`: Sign-in not checked.

**Import presets: Generic CSV file** (`generic-csv`): 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.

| Column in the export                                          | Field in BatteryPass                                      |
| ------------------------------------------------------------- | --------------------------------------------------------- |
| `GTIN` (also EAN, GTIN-13, GTIN-14)                           | GTIN (GS1) `identification.gtin`                          |
| `Serial number` (also Seriennummer, serial_number)            | Serial number `identification.serial_number`              |
| `Manufacturing date` (also Herstelldatum, manufacturing_date) | Manufacturing date `identification.manufacturing_date`    |
| `Facility` (also Produktionsstätte, Facility GLN, Werk-GLN)   | Place of manufacture `identification.manufacturing_place` |
| `Model version` (also Modellversion, model_version)           | Model version `model_version`                             |
| `Battery status` (also Batteriestatus, battery_status)        | Battery status `identification.battery_status`            |

## Workflows

- [Units from production](https://passport.kabin.sh/docs/en/integrations/workflows/units-from-production.md): Serial numbers from the production confirmation or goods receipt are staged as an import; members review, commit and approve before any passport appears. Key scopes: import
- [Passport links back into the ERP](https://passport.kabin.sh/docs/en/integrations/workflows/passport-links-to-erp.md): 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. Key scopes: read
- [Returns and repairs as lifecycle events](https://passport.kabin.sh/docs/en/integrations/workflows/returns-and-repairs.md): Completed repairs, inspections and component replacements from service or return orders appear as events in the unit's history. Key scopes: read, condition