NetSuite as a channel in Flxpoint lets you sync and link product listings, retrieve orders, and keep order data synchronized between NetSuite and Flxpoint for accurate inventory and seamless processing.
How to Connect
📋 Phase 1: NetSuite Setup Prerequisites+
Enable Features
Setup > Company > Enable Features → SuiteCloud tab:
- SuiteScript
- SuiteTalk (Web Services)
- REST Web Services
- Token-Based Authentication
Role Permissions
- Setup: Access Token Management, Log in using Access Tokens, REST Web Services
- Lists: Items, Customers, Vendors
- Transactions: Purchase Order, Sales Order, Item Fulfillment
- Reports: SuiteAnalytics Workbook (recommended for Production REST auth)
Tip: Use a dedicated “Flxpoint Integration” role for this connection.
Generate TBA Tokens
Settings portlet → Manage Access Tokens → New My Access Token → choose your Integration and role → Save. Copy Token ID and Token Secret.
🔐 Phase 2: Create Your NetSuite Channel Connection+
Add Channel
Go to Channel → + Add Channel → search NetSuite.
Select Type
Choose NetSuite Purchase Order (channel) to enable order flows.
Enter Credentials
- Connection Name
- Client ID / Client Secret
- NetSuite Store ID (Account ID)
- Token ID / Token Secret
- Sandbox Store ID (optional)
Note: Leave Sandbox Store ID blank to target Production.
Test & Save
Click Test Connection → Save Connection. Follow prompts to configure operations.
🧩 Phase 3: Configure Listing Sync+
Sync & Link Listings
Sync updates product quantity, price, and mapped fields. Optionally enable:
- Allow updating custom quantity — if enabled, the custom quantity in NetSuite can be updated by sync.
Mapping Template
Map custom fields to control which product attributes are updated. Variant attribute sync is supported.
📦 Phase 4: Configure Orders+
Get Orders
Pull Sales Orders (SO) and/or Purchase Orders (PO). Order & item IDs are saved to align future syncs. Map custom fields as needed (e.g.,
custbody_*
).Sync Orders
Synchronize shipments and optional custom fields. One SO can have multiple POs; each PO is handled as a separate order record.
🛠️ Phase 5: Troubleshooting & Limitations+
Connection checks
- Confirm role permissions (incl. SuiteAnalytics Workbook in Production).
- Regenerate tokens if revoked/unknown and re-test connection.
- Verify correct environment targeting (Production vs Sandbox).
- If your organization requires IP allow-listing, have IT allow the IPs provided by Flxpoint Support.
Known limitations
- Listings: no “hide/delist” or inventory tracking config changes via sync.
- Orders: no order acknowledgement or shipping selection; digital items/donations not supported.
- Sync Orders: shipments sync at item level; partial shipment flows aren’t supported.

Listing Operations
Sync & Link Listings
- Sync custom fields
- Sync variant attributes
- Update quantity, price, and mapped fields
- Allow updating custom quantity — when enabled, sync can update a custom quantity field in NetSuite.
- Use the mapping template to control which product attributes are written.
- Hiding / Delisting via sync
- Inventory tracking configuration changes via sync
Order Operations
Get Orders
- Download Purchase Orders (PO) and/or Sales Orders (SO)
- Order & payment statuses, receipts/invoices, currency
- Custom fields (e.g.,
custbody_*
) - Weight & dimensions (units)
- Orders are pulled per your configuration (PO, SO, or both).
- Order IDs and item IDs are saved to keep data aligned.
- Fetches are filtered by creation date from integration settings.
- Map NetSuite custom fields to Flxpoint order fields as needed.
- Order acknowledgement
- Shipping selection
- Digital items / donations
Sync Orders
- Sync shipments at the item level
- Optionally update custom fields
- Matches use the Order ID and Item ID saved during Get Orders.
- One Sales Order can have multiple POs; each PO is handled individually.
- Platform “Notify Customer” flow
- Partial order or partial item shipments
- Post-shipment status updates