NetSuite 2026.2 Preview — Integration Changes You Need to Know
- 2026.2 introduces REST API coverage for Fulfillment Request and Transfer Order records — previously SuiteScript-only, now accessible via REST without custom scripting.
- The SuiteQL query timeout limit increases from 30 to 60 seconds — directly improving large incremental sync query reliability.
- Webhook support for native NetSuite events is in Beta in 2026.2 — a major architectural shift that will eliminate many SuiteScript User Event workarounds when it reaches GA.
- TBA (Token-Based Authentication) is deprecated for new integration client creation in 2026.2 — only OAuth 2.0 M2M will be available for new integrations going forward.
NetSuite releases two major updates per year. The 2026.2 release (expected Q3 2026) contains four changes that will directly affect WooCommerce and Shopify integrators. Here is the early preview with migration guidance for each.
Change 1: REST API Expands to Fulfillment Request and Transfer Order
Previously, creating and updating Fulfillment Requests in NetSuite required either a SuiteScript or the SuiteTalk SOAP API. In 2026.2, both Fulfillment Request and Transfer Order records are added to the REST Record API. This enables direct REST calls from WooCommerce or Shopify to trigger fulfilment without a SuiteScript intermediary.
After 2026.2, you can replace the SuiteScript with a direct REST API call from your integration middleware. This removes one layer of custom code and reduces governance cost. The REST endpoint will be: POST /services/rest/record/v1/fulfillmentRequest with the same authentication as your existing REST integration.
Change 2: SuiteQL Timeout Increase to 60 Seconds
Large incremental sync queries — those fetching inventory, order, or item changes across thousands of records — sometimes time out at the 30-second limit in high-load NetSuite accounts. The 2026.2 increase to 60 seconds is a direct response to this integrator pain point. No code change required — the longer timeout applies automatically. If you previously split large queries into smaller time-window chunks to avoid timeouts, you may be able to simplify that logic after 2026.2.
Change 3: Native Webhook Support (Beta)
This is the most significant architectural change in 2026.2 for integrators. NetSuite will support native webhooks — subscribing to record events (create, update, delete) and having NetSuite push a notification to a URL without custom SuiteScript. In Beta, support covers Sales Order and Customer records.
Beta features in NetSuite can change schema, be rolled back, or have availability limitations per account tier. Plan for native webhooks as the production path in 2027.1 (expected GA). Continue using SuiteScript User Event scripts for production webhook patterns until then.
Change 4: TBA Deprecation for New Integrations
Token-Based Authentication (TBA) is no longer available for creating new integration clients in 2026.2. All new integrations must use OAuth 2.0 M2M. Existing TBA-authenticated integrations continue to work and are not immediately forced to migrate — but the migration path to OAuth 2.0 M2M should be planned for 2027.
References
- NetSuite REST Record APIOracle NetSuite Help — record types available via REST, updated with each release.
- SuiteQL DocumentationOracle NetSuite Help — SuiteQL query reference including timeout and governance behaviour.
- OAuth 2.0 M2M NetSuite SetupOracle NetSuite Help — migration path from TBA to OAuth 2.0 for NetSuite integrations.
Leave a Reply