IFS Cloud
How IFS Cloud could supply serial numbers to BatteryPass through its OData projections.
The facts on this page come from community sources only and are not checked against IFS documentation. Confirm the interfaces, sign-in and entities with IFS or your partner before a project.
This page describes an integration pattern. BatteryPass ships no connector for IFS Cloud and has no partnership with IFS; nothing here is a vendor approval.
According to community sources, the APIs of IFS Cloud are OData projections of the applications, and sign-in uses
OAuth 2.0. A middleware would read the serial numbers of finished shop orders through such a projection, with a
service user that may only read, and write a file with the generic-csv preset for
units from production.
Change events were not checked; until they are, the middleware polls on a schedule. IFS is often used for service processes as well, so returns and repairs and condition data may fit too.
Interfaces and how they were checked
- Vendor
- IFS
- Deployments
- Cloud: IFS CloudOn-premise: IFS Cloud (remote deployment)
From community sources only: the APIs are OData projections and sign-in uses OAuth 2.0.
An integration pattern, not a connector: BatteryPass ships no ERP connector and holds no vendor certification.
| Interface | Protocol | Sign-in | Events | Objects | Checked |
|---|---|---|---|---|---|
Projections (OData)OData projections of the applications | OData V4 | OAuth 2.0 client credentials | none | Product/material master, Batch/serial number, Production order | community or marketing source only, 24/10/2026 |
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: 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: 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
- 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. Key scopes: readcondition
- 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. Key scopes: readcondition
- 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. Key scopes: read