Flxpoint Knowledge

Contact us

NetSuite as a Source

Table of Contents

How To Connect Order Operations

NetSuite as a Source in Flxpoint supports the operation "Get Shipments." This functionality allows you to import shipment data from your NetSuite account into Flxpoint. By retrieving shipment details, you can efficiently track and manage the fulfillment process for your orders, ensuring that shipping information is up-to-date within your Flxpoint system. 
 

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 (Token-Based Auth)
  • Sandbox Store ID (optional) — leave blank to connect to Production
Click Test Connection → Save Connection.
Note: The tooltip in the UI is accurate — 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 (Production & Sandbox)
Assign the integration role with:
  • 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 related as needed)
  • Reports → SuiteAnalytics Workbook (required — fixes common 401/Unauthorized in Production)
Create tokens (TBA)
Use the same User + Role intended for the integration:
  1. Settings portlet → Manage Access Tokens → New My Access Token
  2. Select your Application (Flxpoint Integration), then Save
  3. Copy the generated Token ID and Token Secret and paste into Flxpoint
Important: Tokens are account-specific. Create separate tokens in Production vs Sandbox. Revoked tokens will cause 401 INVALID_LOGIN.
Production vs Sandbox, IP allow-listing & 2FA
  • Targeting: Leave Sandbox Store ID empty to connect to Production. Provide it to target Sandbox.
  • IP allow-list (if enforced): Allow our US server IP 52.44.101.151.
  • 2FA: The integration role should not require interactive 2FA.
  • If Test Connection fails in Production: Add SuiteAnalytics Workbook permission and regenerate tokens, then re-test.
⚙️ 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? Check Login Audit Trail in NetSuite for blocked attempts, confirm the correct account is targeted, and verify tokens are active.

 

Order Operations 

It imports the shipment details, ensuring a seamless integration of shipment tracking.    
 

Get Shipments 

Supported | NetSuite — Get Shipments

Get Shipments (NetSuite)
Retrieves shipment records for orders posted from Flxpoint to your NetSuite account. Shipments are created/managed in NetSuite; Flxpoint pulls them and updates Fulfillment Requests (FRs).

  • Base URL: https://%s.suitetalk.api.netsuite.com/services/rest
  • Orders posted via Send Accounting Orders with warehouse type = internal warehouse are eligible.
  • We store Order ID and Item ID sent on the order.
  • User adds a shipment manually against the order in NetSuite.
  • We retrieve and match shipments using the Order ID and Item ID.

Connection fields
  • Client ID / Client Secret
  • NetSuite Store ID (Account ID)
  • Token ID / Token Secret (TBA)
  • Sandbox Store ID (optional) — Enter to connect to Sandbox. Leave blank to connect to Production.
Tooltip (as in UI): Enter the “Store ID” to connect to NetSuite’s sandbox environment. Keep this empty to connect to production environment.
Test Connection validates credentials and account target (Sandbox vs Production).

FR Lookback Period for Get Shipments
Defines the maximum age of Fulfillment Requests considered for retrieval. Only FRs created within this window are checked for shipments. Default: 90 days.

The template controls how NetSuite shipment data populates Flxpoint shipment fields.
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 is performed using the Order ID and Item ID captured when orders were posted to NetSuite.

Capability Status Notes
Carrier & Methods SUPPORTED
Shipment Item Association SUPPORTED We use Item ID saved in DB to match products.
Partial Shipments NOT SUPPORTED User manually adds shipment against these orders.
Invoice Information NOT SUPPORTED
Custom Fields (CFs) NOT SUPPORTED

Symptoms
  • Sandbox connects successfully; Production fails.
  • REST call returns 401 Unauthorized with INVALID_LOGIN.
Quick Checks (high signal)
  • Role Permission: Ensure Reports > SuiteAnalytics Workbook is added to the Production role used by the integration.
  • Access Tokens: In Setup > Users/Roles > Access Tokens under the Flxpoint Integration application, confirm token is Active. If revoked/unknown, create a new token and update connection settings.
  • Account Target: Verify the connection points to the correct Production account (not Sandbox). Use the proper Store ID.
  • Security: Integration role should not require interactive 2FA. If IP restrictions are enabled, whitelist our US server IP 52.44.101.151.
  • Audit Trail: Ask the customer to review Setup > Users/Roles > User Management > View Login Audit Trail for blocked/invalid attempts.
Validation Endpoint
GET https://<ACCOUNT_ID>.suitetalk.api.netsuite.com/services/rest/record/v1/inventoryItem — Example failure — { "title":"Unauthorized", "status":401, "o:errorDetails":[{"detail":"Invalid login attempt...","o:errorCode":"INVALID_LOGIN"}] }
Known Fix (AID #57933 — Primary Arms): Adding SuiteAnalytics Workbook permission to the Production role and regenerating tokens resolved the issue. Production connection then passed Test Connection.
Customer Ask (copy/paste)
  • Add Reports > SuiteAnalytics Workbook to the integration role.
  • Confirm an Active Access Token for the Flxpoint Integration app (or create new and update keys in Flxpoint).
  • Ensure the Production account (Store ID) is targeted; leave Sandbox Store ID blank for Production.
  • Whitelist 52.44.101.151 if IP restrictions are enabled.

  • Retrieval window is limited by the configured FR Lookback Period.
  • No support for Partial Shipments, Invoice Information, or Custom Fields.

  • Our servers use US IPs; primary allow-list IP: 52.44.101.151.
  • If needed for investigation, your agent may request a temporary staff login to verify role/permissions in Production.

  • 2025-09-19 — Added Production connection guidance: required SuiteAnalytics Workbook permission, token revocation pattern, US IP allow-list.
 
 

 

 

Related Articles

Shipping Easy

ShippingEasy as a source supports sending fulfillment requests/fulfillment orders...