Oracle NetSuite and the battery passport: integration pattern
How data from Oracle NetSuite (Oracle) 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
- Oracle
- Deployments
- Cloud (NetSuite (SuiteTalk REST web services))
- Checked
- vendor documentation, 25 October 2026
- Managed integration
- —
For new integrations use OAuth 2.0 client credentials (a certificate-signed JWT) instead of token-based authentication: partner sources name 2027.1 as the end for new TBA integrations; Oracle's pages did not confirm it.
Interfaces
| Interface | Protocol | Sign-in | Events | Objects | Checked |
|---|---|---|---|---|---|
| SuiteTalk REST web servicesRecords (items, work orders, fulfilments, returns) | REST | OAuth 2.0 client credentials, Token | none | Product/material master, Batch/serial number, Production order, Delivery/goods issue, Return | checked in the vendor documentation, 24/10/2026 |
| SuiteQLQueries, for example of the inventorynumber record | REST | OAuth 2.0 client credentials, Token | none | Batch/serial number | checked in the vendor documentation, 24/10/2026 |
| SuiteScript afterSubmit with N/httpsOwn notification after a record is saved | REST | OAuth 2.0 client credentials | Webhooks | Product/material master, Batch/serial number, Production order | checked in the vendor documentation, 25/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
- NetSuite saved search of inventory numbers: A saved search of the inventory number record (inventorynumber) in Oracle NetSuite, exported as CSV or read with SuiteQL. Assumes that the model identifier is the item name. The middleware adds the manufacturing date, for example from the work order.
- 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.