NetSuite as a Channel

Work through these in order: confirm all four SuiteCloud features are enabled (SuiteScript, SuiteTalk, REST Web Services, Token-Based Authentication); verify the integration role has the required permissions including SuiteAnalytics Workbook in Production; confirm the Account ID matches your NetSuite environment exactly; regenerate the Token ID and Token Secret (Settings portlet → Manage Access Tokens) and update them in Flxpoint; and check the NetSuite Login Audit Trail (Setup → Users/Roles → User Management → View Login Audit Trail) for the exact rejection reason. If your organization requires IP allow-listing, contact Flxpoint support for the IPs to add.

Confirm the Sync Listings mapping template has the Price field explicitly mapped and the job is running on schedule. If the job completes without errors but prices stay stale, check whether Flxpoint is sending the cost value instead of the list price - a common mix-up when the source data has both. Also verify the connection points to Production, not Sandbox.

A custom NetSuite number field is receiving a string value instead of a number. Open the Send Accounting Orders mapping template and ensure the source for the failing custom field (e.g. custbody_ca_tax_cost) is mapped as a numeric type, not text. For calculated or formula fields, confirm the output type matches the NetSuite field's data type.

NetSuite received a PO or SO with duplicate line-item identifiers - commonly triggered by promotions (e.g. Buy 1 Get 1 Free) that create two line items with the same SKU on one order. NetSuite rejects duplicate sublist rows. This is an engineering-level fix for that order flow; raise a support ticket with example order numbers. In some cases the order still generates but one line item is dropped.

A 500 UNEXPECTED_ERROR from NetSuite's REST API is a NetSuite-side error, not a Flxpoint error. The error ID in the response (e.g. mmpb2najdc01a6c2sw2u) lets a NetSuite admin look up the exact cause in the NetSuite system log - common causes include a SuiteScript firing on the record and failing, a required field missing on the order, or a scripting conflict. Share the error ID with your NetSuite admin or implementation partner to diagnose on the NetSuite side.

A 404 on Send Accounting Shipments usually means Flxpoint cannot locate the NetSuite record to update - most often because the order was not yet created in NetSuite when the shipment sync ran, or its NetSuite internal ID was not saved correctly during Get Orders. Confirm the order exists in NetSuite, then re-run the shipment sync. "Index 0 out of bounds" typically indicates an empty result set - raise a ticket with the specific shipment and order numbers so engineering can investigate the record lookup.

Flxpoint may automatically pause or terminate integration jobs that fail repeatedly with errors like 403 Forbidden or 503 Service Unavailable to prevent log flooding. If this occurs, resolve the underlying issue (such as updating expired credentials or waiting for NetSuite maintenance to conclude), then manually reactivate the job schedule in the integration settings.

NetSuite Sandbox and Production environments may occasionally return 503 errors during maintenance windows or when concurrency limits are reached. Disable your job schedules temporarily until the environment is stable to avoid automatic job termination, and ensure your integration role has sufficient concurrent request permissions.

This error occurs when attempting to sync a vendor bill (invoice) to NetSuite for a Purchase Order that contains items not yet marked as received in NetSuite. NetSuite rejects bill creation if any line item in the request has a received quantity of zero. To resolve this, ensure all items on the Purchase Order are synced and received in NetSuite before triggering the invoice sync, or verify that your workflow supports partial billing for only the specific items already received.

This error may appear even if dimensions are present on the product or source inventory. It often indicates that your available box sizes are too small to accommodate the item dimensions. Flxpoint validates fit based on raw dimensions and does not account for flipping or rotating the item to fit (e.g., a 27-inch tall item will not fit in a 12-inch high box even if the width allows). To resolve this, ensure you have a box defined with dimensions large enough to house the item in its default orientation.

By default Flxpoint pulls all POs created after the date configured in Get Orders settings - there is no self-service filter on custom fields. To restrict imports by a custom body field (e.g. a "ready for Flxpoint" flag) or by lastModifiedDate instead of creation date, raise a request with Flxpoint support to configure a custom query filter for your connection. The creation-date window is set in the Get Orders integration settings.

Yes - Sync & Link Listings supports syncing custom fields and variant attributes to NetSuite. Map your Flxpoint fields (including custom fields like custitem_jcs_variantdescription) to the corresponding NetSuite item fields in the Sync Listings mapping template. Parent and variant fields can be mapped independently.

No - partial shipments are not supported. Shipments sync at the item level, but partial order or partial item shipments are not sent. Also note that one NetSuite Sales Order can have multiple Purchase Orders; each PO is handled as a separate order record in the sync flow.

Enter your Production Account ID in the NetSuite Store ID field and leave Sandbox Store ID blank to target Production. To point the connection at Sandbox instead, enter your Sandbox Account ID in the Sandbox Store ID field. Note that NetSuite Sandbox undergoes periodic maintenance windows (typically tied to Release upgrades) during which the connection is unavailable - plan test runs accordingly.

Delays are usually caused by one of three things: the sync job is queued behind other scheduled jobs and hasn't started yet; NetSuite's REST API is responding slowly due to NetSuite-side load; or the orders have mapping errors that trigger retries. Check the job logs to confirm the job started and review the error log for field-mapping failures. If the sync completes without errors but orders still appear in NetSuite late, this is typically NetSuite processing lag rather than a Flxpoint issue.

At minimum - 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 (required for Production REST auth). Use a dedicated "Flxpoint Integration" role rather than a shared admin role to isolate permissions and avoid token conflicts.