NetSuite as a Source

July 2, 2026

Summary

NetSuite (ERP) as a source in Flxpoint pulls Sales Orders and item-level shipment data from your NetSuite account so you can route fulfillment and keep tracking current in your downstream systems. It connects over NetSuite's REST Web Services using Token-Based Authentication (TBA): an Account ID plus Integration and access-token key pairs. This source supports Get Orders and Get Shipments only.

What this integration does

Get Shipments

Imports item-level shipment and tracking data for orders posted to NetSuite as internal-warehouse orders

How to connect: credentials you need

Go to Sources → Integrations and start a Get Orders or Get Shipments job. In Step 1, choose NetSuite and click + New Connection, enter the values from your NetSuite setup, then click Test Connection → Save Connection.

Field	What to enter
Client IDRequired	The Client ID from your NetSuite Integration record (created when you set up the integration in NetSuite). Found on the Integration record in NetSuite.
Client SecretRequired	The Client Secret paired with your Client ID, shown by NetSuite when the Integration record is created. Shown only at creation: store it securely.
NetSuite Store IDRequired	Your NetSuite Account ID. Identifies which NetSuite account Flxpoint connects to. This is your NetSuite Account ID.
Token IDRequired	The Token ID from Token-Based Authentication (TBA). Create it in NetSuite via Settings portlet → Manage Access Tokens → New My Access Token, choosing your Integration and role. Create separate tokens in Production and Sandbox.
Token SecretRequired	The Token Secret paired with the Token ID, copied when the access token is created. Copied once when the token is generated in NetSuite.
Sandbox Store IDSetting	Environment toggle. Leave blank to connect to Production; enter your Sandbox account ID to target Sandbox. Blank = Production, populated = Sandbox. Tokens are environment-specific.

Test Connection returning 401 Unauthorized? Confirm the NetSuite role includes SuiteAnalytics Workbook, that the four SuiteCloud features are enabled, and that your tokens match the target environment. If your organization enforces IP allow-listing, ask IT to allow the IPs provided by Flxpoint Support, and review the NetSuite Login Audit Trail for blocked attempts.

Important: read before configuring

Five credentials are required: all from your NetSuite setup

The connection needs Client ID and Client Secret (from your NetSuite Integration record), NetSuite Store ID (your Account ID), and Token ID and Token Secret (from Token-Based Authentication). All five are required, and you must create separate tokens for Production and Sandbox: never reuse tokens across environments.

Leave Sandbox Store ID blank for Production: populate it for Sandbox

The Sandbox Store ID field is the environment toggle. Blank connects to Production; populated connects to Sandbox. If data appears to come from the wrong environment, check this field first. Token sets are environment-specific, so confirm you are using Production tokens when targeting Production.

Four SuiteCloud features must be enabled before the connection works

In NetSuite, go to Setup → Company → Enable Features → SuiteCloud and enable Token-Based Authentication, REST Web Services, SuiteTalk (Web Services), and SuiteScript. If Test Connection returns 401 Unauthorized in Production, also add the SuiteAnalytics Workbook permission to the role and regenerate tokens.

Get Shipments only covers internal-warehouse orders

Get Shipments retrieves shipments only for orders posted to NetSuite via Send Accounting Orders with warehouse type = internal warehouse. Flxpoint matches shipments using the Order ID and Item ID stored when the order was posted, and only FRs inside the FR Lookback Period (default 90 days) are considered.

Mapping: fields to know

Get Shipments

Imports item-level shipment and tracking data for orders posted to NetSuite as internal-warehouse orders

NetSuite Field	Maps To: Notes
Tracking Numbers	→ Tracking Number. e.g. `1Z9999W999999999`. Optional.
Ship Method	→ Carrier. e.g. `UPS`. Optional. Same NetSuite field also feeds Method below.
Ship Method	→ Method. e.g. `Ground`. Optional. Same NetSuite field also feeds Carrier above.
Created Date	→ Shipped At. Optional.
(No exposed mapping)	→ Shipping Cost. No NetSuite field is currently exposed for this target.
(No exposed mapping)	→ Note. No NetSuite field is currently exposed for this target.
Item Name	→ SKU. Shipment item line. Optional.
Quantity	→ Quantity. Units shipped on the line. Optional.

Matching uses the Order ID and Item ID captured when the order was posted to NetSuite. Retrieval is limited to the FR Lookback Period (default 90 days), and Partial Shipments, Invoice Information and Custom Fields are not supported in this operation. Get Orders mapping is not applicable for NetSuite as a Source.

Common issues

Test Connection failing: 401 Unauthorized

Three common causes: (1) missing SuiteAnalytics Workbook permission (add it to the NetSuite role and regenerate tokens, then re-test; (2) token environment mismatch) confirm tokens were created in the same environment (Production or Sandbox) that the Sandbox Store ID field targets; (3) incorrect credentials: re-paste Client ID, Client Secret, Store ID, Token ID and Token Secret. Also check the NetSuite Login Audit Trail (Setup → Administrators → Audit Trail) for blocked attempts that may indicate IP restrictions.

Get Shipments returns no tracking for recent orders

Confirm the orders were posted as internal-warehouse orders via Send Accounting Orders (a hard requirement), that they fall within the FR Lookback Period (default 90 days), and that shipments actually exist in NetSuite for them: Get Shipments only retrieves what already exists. A 401 during the run can also produce silently empty results, so re-test the connection.

FAQs

What role permissions does the NetSuite role need?

The role used for the integration needs: Setup (Access Token Management, Log in using Access Tokens, REST Web Services; Transactions) Sales Order, Item Fulfillment (view at minimum); Lists (Items, Customers, Vendors; and Reports) SuiteAnalytics Workbook (recommended for Production REST auth, and required if Test Connection returns 401). Missing permissions cause authentication failures or blocked data operations.

What does Get Shipments retrieve from NetSuite?

Get Shipments imports item-level shipment data: Tracking Number, Carrier, Method, Shipped Date, Shipping Cost, Memo/Note, Item SKU and Quantity. Matching uses the Order ID and Item ID captured when the order was posted to NetSuite. Partial shipments, Invoice Information and Custom Fields are not supported, and the FR Lookback Period (default 90 days) limits which FRs are eligible.

Does NetSuite as a Source support Get Orders, inventory sync or Send Fulfillment Requests?

No. NetSuite as a Source supports only Get Shipments. Get Orders, Get Inventory (Primary/Secondary) and Send Fulfillment Requests are not available in the NetSuite source integration - Get Orders is handled by NetSuite as a Channel. For pushing orders to NetSuite and syncing accounting data, see the Accounting & NetSuite documentation.

Back to ERP & Accounting Integrations