# Epicor Kinetic and the battery passport: integration pattern

> How data from Epicor Kinetic (Epicor) reaches the battery passport through the BatteryPass API: interfaces, workflows and when we checked them.

How data from Epicor Kinetic (Epicor) 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

  Epicor

- Deployments

  Cloud (Epicor Kinetic (REST API v2)); On-premise (Epicor Kinetic (REST API v2))

- Checked

  community source only, 24 October 2026

- Managed integration

  —

From community sources only: REST API v2 needs an API key in the x-api-key header in addition to the user sign-in. Never send the key as a query parameter.

## Interfaces

| Interface                                                                                                        | Protocol | Sign-in             | Events | Objects                                                                              | Checked                                        |
| ---------------------------------------------------------------------------------------------------------------- | -------- | ------------------- | ------ | ------------------------------------------------------------------------------------ | ---------------------------------------------- |
| [REST API v2](https://www.epiusers.help/t/rest-interface-header-key-value-pairs/44309)Business objects over REST | REST     | API key, Basic auth | none   | Product/material master, Batch/serial number, Production order, Delivery/goods issue | 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.

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

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

[← 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)