NetSuite as a Source in Flxpoint supports the operation "Get Shipments". This imports shipment data from your NetSuite account into Flxpoint so you can track item-level fulfillments and keep shipping information up to date across Fulfillment Requests (FRs).
How To Connect
🧭 Phase 1: Start the Get Shipments integration+
Open the flow
Go to Channels → Integrations and add/open Get Shipments. In Step 1, choose NetSuite and click + New Connection.
Enter connection fields
Fill the fields from your NetSuite setup:
- Client ID / Client Secret (Integration record)
- NetSuite Store ID (Account ID)
- Token ID / Token Secret (TBA)
- Sandbox Store ID (optional) — leave blank to connect to Production
Note: Entering a Sandbox Store ID targets Sandbox; leaving it empty targets Production.
🔒 Phase 2: NetSuite prerequisites (required)+
Enable features
In NetSuite: Setup → Company → Enable Features → SuiteCloud tab:
- Token-Based Authentication
- REST Web Services
- SuiteTalk (Web Services)
- SuiteScript
Role permissions
- Setup: Access Token Management, Log in using Access Tokens, REST Web Services
- Transactions: Sales Order, Item Fulfillment (view at minimum)
- Lists: Items, Customers, Vendors
- Reports → SuiteAnalytics Workbook (recommended for Production REST auth)
Create tokens (TBA)
Settings portlet → Manage Access Tokens → New My Access Token → choose your Integration and role → Save. Copy the Token ID and Token Secret.
Important: Create separate tokens in Production and Sandbox.
Environment targeting & access tips
- Targeting: Leave Sandbox Store ID empty to connect to Production. Provide it to target Sandbox.
- If Test Connection fails in Production: Add SuiteAnalytics Workbook permission and regenerate tokens, then re-test.
- IP allow-listing (if your org enforces it): Ask your IT team to allow the IPs provided by Flxpoint Support.
⚙️ Phase 3: Configure Settings+
FR Lookback Period
Set FR Lookback Period for Get Shipments (default 90 days). Only FRs created within this window are considered for shipment retrieval.
🗺️ Phase 4: Define a Mapping Template+
Map shipment fields
Map NetSuite shipment fields to Flxpoint (e.g., Tracking Number, Carrier, Method, Shipped At, Shipping Cost, SKU, Quantity).
✅ Phase 5: Run & Verify+
Execute
Click Run Integration or enable a schedule. After the first run, confirm a few orders show the expected shipments.
Still failing? Review the NetSuite Login Audit Trail for blocked attempts, confirm the correct account is targeted, and verify tokens are active.
Order Operations
Get Shipments
- Orders posted via Send Accounting Orders with warehouse type = internal warehouse are eligible.
- We store Order ID and Item ID sent on the order.
- Shipments are created in NetSuite; Flxpoint retrieves and matches using the stored IDs.
Shipment Fields
| NetSuite Field | Maps To | Example | Notes |
|---|---|---|---|
| Tracking Number | Tracking Number | 1Z9999W999999999 | Optional |
| Carrier | Carrier | UPS | Optional |
| Method | Method | Ground | Optional |
| Shipped Date | Shipped At | 2025-06-01 | Optional |
| Shipping Cost | Shipping Cost | 10.00 | Optional |
| Memo/Note | Note | Handle with care | Optional |
Shipment Item Fields
| NetSuite Field | Maps To | Example | Notes |
|---|---|---|---|
| Item (Internal ID / SKU) | SKU | PROD-001-BLACK | Optional |
| Quantity | Quantity | 5 | Optional |
Matching
- Matching uses the Order ID and Item ID captured when orders were posted to NetSuite.
- 401 Unauthorized: Ensure the role includes SuiteAnalytics Workbook, regenerate tokens, and confirm the correct account (Production vs Sandbox) is targeted.
- Review NetSuite Login Audit Trail for blocked attempts or invalid logins.
- If your organization requires IP allow-listing, have IT allow the IPs provided by Flxpoint Support.
- Retrieval is limited by the configured FR Lookback Period.
- No support for Partial Shipments, Invoice Information, or Custom Fields in this operation.