NetSuite as a Source in Flxpoint lets you pull data from your NetSuite account into Flxpoint so you can route fulfillment, keep shipping information current, and map NetSuite order data to your downstream systems. This source supports Get Orders and Get Shipments, connecting securely with your NetSuite account using token-based credentials.
Add Source and Establish Connection
- 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
Enable the required NetSuite features, set the role permissions, and create the access tokens that Flxpoint uses to authenticate.
- Token-Based Authentication
- REST Web Services
- SuiteTalk (Web Services)
- SuiteScript
- 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)
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.
Order Operations
Get Orders
The Get Orders operation retrieves orders from your NetSuite account into Flxpoint so you can route them and map the order data to your downstream systems. Flxpoint connects securely with NetSuite using your token-based credentials and brings the order data back for mapping.
Use Get Orders to keep order information current in Flxpoint and to map NetSuite order fields — including the newly exposed Sales Order Billing and Shipping address fields — to the systems you fulfill with.
The sections below walk through each step of the setup and configuration process.
Follow these steps in your NetSuite source → Get Orders:
Choose NetSuite and select your existing NetSuite connection (or create one — see Add Source and Establish Connection → Phase 1). Click Save and Proceed.
Confirm the correct account is targeted (Production vs Sandbox) and that your NetSuite role and tokens are active, then click Save and Proceed.
Map the NetSuite order fields you need to Flxpoint. This is where you map the Sales Order Billing and Shipping address fields described in Mapping Utilities below. Click Save and Complete.
Run manually first to verify the import, then enable a schedule. After the first run, confirm a few orders show the expected order, billing, and shipping data.
Sales Order Billing and Shipping address fields — including subfields such as addressee, street, and city — are now exposed in the Get Orders mapping template, so you can map them to your downstream system. This exposure lets you map those fields to your vendor systems via the NetSuite source integration, and applies to the Get Orders (purchase orders) NetSuite connector.
| NetSuite Field | Subfields Exposed | Maps To | Example |
|---|---|---|---|
| Sales Order Billing Address | Addressee, Street, City (and other essential subfields) | Billing address fields on your downstream system | Jane Doe, 123 Main St, Austin |
| Sales Order Shipping Address | Addressee, Street, City (and other essential subfields) | Shipping address fields on your downstream system | Jane Doe, 123 Main St, Austin |
- Match It — Directly map a source field to a Flxpoint field.
- Set It — Set a fixed/static value for a field.
- Transform It (Mapping Set) — Apply a transformation or mapping set to the value.
- Smart Rules — Use conditional logic to determine the mapped value.
- Skip It (Don't Map) — Ignore the field entirely.
- NetSuite connection is selected and Test Connection passes.
- The correct account is targeted (Production vs Sandbox).
- The Billing and Shipping address fields you need are mapped in the Get Orders mapping template.
- Run once manually first, then enable a schedule once verified.
- Billing or shipping fields not appearing for mapping: Only essential Sales Order fields are exposed today. If you need a field that is not yet available, additional Sales Order fields can be enabled in the future — contact Flxpoint Support to request it.
- Orders not pulling: Order filtering is unchanged by this update. Confirm the connection passes Test Connection and that the correct account is targeted, then re-run.
- 401 Unauthorized: Ensure the role includes SuiteAnalytics Workbook, regenerate tokens, and confirm the correct account (Production vs Sandbox) is targeted.
| Feature | Availability | What to Expect |
|---|---|---|
| SO Billing Address fields | Supported | Essential subfields (addressee, street, city, and more) exposed for mapping. |
| SO Shipping Address fields | Supported | Essential subfields (addressee, street, city, and more) exposed for mapping. |
| Additional SO fields | Future | Can be enabled later as needed to avoid overwhelming the template. |
| Order filtering | Unchanged | Only the data available for mapping changes — not how orders are pulled. |
Get Shipments
The Get Shipments operation 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).
The sections below walk through how the operation works, how to map shipment fields, and how to resolve common issues.
- Orders posted via Send Accounting Orders with warehouse type = internal warehouse are eligible.
- Flxpoint stores the Order ID and Item ID sent on the order.
- Shipments are created in NetSuite; Flxpoint retrieves and matches them using the stored IDs.
Set the FR Lookback Period for Get Shipments (default 90 days). Only FRs created within this window are considered for shipment retrieval.
Click Run Integration or enable a schedule. After the first run, confirm a few orders show the expected shipments.
| 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 |
| NetSuite Field | Maps To | Example | Notes |
|---|---|---|---|
| Item (Internal ID / SKU) | SKU | PROD-001-BLACK | Optional |
| Quantity | Quantity | 5 | Optional |
- 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.
Troubleshooting
Common issues and solutions for the NetSuite integration. Expand each item to learn more.
What's happening
The NetSuite connection is not authenticating, or Test Connection returns a 401 Unauthorized error.
- The role may be missing the required permissions.
- Tokens may be invalid, expired, or created in the wrong environment.
- The wrong account (Production vs Sandbox) may be targeted.
- Your organization may enforce IP allow-listing.
How to fix it
- Ensure the role includes SuiteAnalytics Workbook, regenerate tokens, and confirm the correct account (Production vs Sandbox) is targeted.
- Review the 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.
What's happening
Get Orders is not retrieving orders, or fewer orders appear than expected.
- The connection may not be passing Test Connection.
- The wrong account may be targeted (Production vs Sandbox).
How to fix it
- Confirm the connection passes Test Connection and that the correct account is targeted, then re-run.
- Note that the recent Billing/Shipping field update does not change how orders are filtered or pulled from NetSuite — it only adds to the data available for mapping after retrieval.
What's happening
A Sales Order Billing or Shipping address field you want is not showing up in the Get Orders mapping template.
- Only the essential Sales Order fields are exposed today, to avoid overwhelming the mapping template with all NetSuite Sales Order data.
- The field you need may not yet be among the exposed essential subfields.
How to fix it
- Map the available Billing and Shipping subfields (such as addressee, street, and city) in the Get Orders mapping template.
- If you need a field that is not yet exposed, additional Sales Order fields can be enabled in the future as needed — contact Flxpoint Support to request it.
What's happening
Recent orders show no shipments, or shipment data is missing fields.
- The order may fall outside the configured FR Lookback Period.
- The order may not have been posted as an internal-warehouse order.
- Shipment fields may not be mapped in the template.
- Authentication may have failed during the run.
How to fix it
- Confirm the order falls within the FR Lookback Period (default 90 days) and was posted as an internal-warehouse order.
- Map the shipment header and item fields you need (for example Tracking Number, Carrier, Method, SKU, and Quantity).
- For auth errors, confirm the role includes SuiteAnalytics Workbook, regenerate tokens, and re-test the connection.
What's happening
Data appears to be coming from the wrong NetSuite environment, or the connection targets Sandbox when you expected Production (or vice versa).
- The Sandbox Store ID field controls which environment is targeted.
- Tokens are environment-specific.
How to fix it
- Leave Sandbox Store ID empty to connect to Production; provide it to target Sandbox.
- Make sure you created separate tokens in Production and Sandbox and are using the set that matches your target environment.
Still need help? If you're experiencing issues not covered here, contact Flxpoint Support or your Flxpoint account manager.
Contact Support