Oracle NetSuite
How Oracle NetSuite hands inventory numbers to BatteryPass through SuiteTalk REST and SuiteQL.
This page describes an integration pattern. BatteryPass ships no connector for NetSuite and has no partnership with Oracle; nothing here is a vendor approval.
Serial and lot numbers live in the inventorynumber record. The middleware reads them with SuiteQL through the REST
web services, or exports a saved search as CSV; the netsuite-inventory-numbers preset maps the number and the item
(it assumes the model identifier in BatteryPass is the item name). NetSuite keeps no manufacturing date on the
inventory number, so the middleware adds it, for example from the work order.
For sign-in, new integrations should use OAuth 2.0 client credentials, a JWT signed with a certificate you upload to NetSuite. Partner sources name release 2027.1 as the end for new integrations with token-based authentication (TBA); Oracle's own pages did not confirm that date when we checked, so plan for OAuth 2.0 either way.
NetSuite sends no events by itself. A user event script (afterSubmit with the N/https module) can call your
middleware after a record is saved; signing, retries and error handling are then up to that script. Polling with a
SuiteQL query on the last modification date is the simpler alternative.
Interfaces and how they were checked
- Vendor
- Oracle
- Deployments
- Cloud: NetSuite (SuiteTalk REST web services)
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.
An integration pattern, not a connector: BatteryPass ships no ERP connector and holds no vendor certification.
| 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 (not signed) | Product/material master, Batch/serial number, Production order | checked in the vendor documentation, 24/10/2026 |
Notes
SuiteScript afterSubmit with N/https: A user event script calls an HTTPS address after the save; signing and retries are up to the script.
Import presets
NetSuite saved search of inventory numbers (netsuite-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.
| Column in the export | Field in BatteryPass |
|---|---|
Number (also Inventory Number, inventorynumber, Serial/Lot Number) | Serial number identification.serial_number |
Item (also itemid, Item Name) | Model identifier / SKU identification.model_identifier |
Manufacturing Date (also Herstelldatum) | Manufacturing date identification.manufacturing_date |
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
- 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