We connect NetSuite to your online store so items, inventory, orders, fulfilments and refunds pass between them reliably, built on NetSuite's REST services and designed around its concurrency limits.

REST, not SOAPConcurrency managedOrders to cash

Start a project

01Our Approach

NetSuite accepts only so many requests at once, and a store on its busiest day will ask for far more than that.

02Overview

Your storefront and NetSuite working together

01REST, not SOAP
02Concurrency managed
03Orders to cash

NetSuite ecommerce integration sends web orders into NetSuite as sales orders or cash sales, and publishes items, prices and available inventory to the store. Fulfilments, tracking and refunds travel back to the customer. We build on NetSuite's REST web services, SuiteQL and, where custom logic is needed, RESTlets, with a queueing service that feeds NetSuite at the pace your account permits.

It suits merchants and distributors who run finance and inventory in NetSuite and sell through Shopify, a custom storefront or a B2B portal. Oracle is retiring NetSuite's SOAP web services over the coming releases, so integrations built on SOAP will need replacing. New work should use REST with OAuth 2.0 from the outset, which is how we build.

Talk to us about your project

03What We Do

Capabilities, End to End

Item and order mapping

Items, matrix options, price levels, subsidiaries, locations, tax codes and payment methods are mapped between NetSuite records and the store, with the form and fields each transaction needs.

Source of each record

NetSuite owns items, pricing, inventory and financial transactions. The store owns the cart and submits orders, which NetSuite accepts, numbers and then controls.

Integration record and role

Access uses an integration record with OAuth 2.0 and a custom role granting only the permissions required, so the integration never runs as an administrator.

Error queue

An order NetSuite rejects, such as one with an inactive item or a failed validation script, is kept with the response and can be corrected and resubmitted.

Concurrency-aware retries

Requests are released within your account's concurrency limit, a refusal for too many requests is retried after a pause and external identifiers prevent duplicate transactions.

Throughput monitoring

Queue length, time from checkout to NetSuite order, rejected requests and inventory differences are tracked, with alerts before a backlog affects delivery promises.

04In Production

What It Looks Like When It Ships

app.atlasfreight.io/overview

Live

Atlas Freight

Shipments / Live

Search...

⌘K

WORKSPACE

Shipments

Fleet

Routes

Customs

Analytics

Partners

Settings

Usage

72% of plan

Inventory

1,204 SKUs across 3 warehouses

AllLowOut

Reorder

3 items below reorder point - suggested PO ready

Review

Product

SKU

Stock level

Status

Track

SKU-1042

82 units

In stock

Dispatch

SKU-1043

34 units

In stock

Documents

SKU-1044

12 units

Low

Trail Jacket

SKU-1045

0 units

Out

REST, not SOAP

Concurrency managed

Orders to cash

Order journeyQueue controlInventory viewRejected orders

05What You Receive

Handed Over, Ready to Run

SCROLL

Record and field mapping

Order to cash flow design

Integration service with source code

Custom role and integration record

Queue that respects concurrency

Error queue with resubmission

Inventory comparison report

Runbook and administrator handover

06How It Runs

From Kickoff to Launch

Review the account

Design the flow

Build in sandbox

Cut over

Review the account

We look closely at subsidiaries, locations, forms, scripts and workflows that touch sales transactions, the account's concurrency limit and any existing SOAP integrations that share it.

Design the flow

We agree how a web order becomes a sales order, when it is fulfilled, billed and paid, and how deposits, refunds, taxes and gift cards are represented.

Build in sandbox

The service is developed against a NetSuite sandbox and a development store, then tested at peak volumes to confirm the queue keeps within limits without delaying orders.

Cut over

Live orders are switched to the new flow, replacing any legacy connection. Inventory and order totals are reconciled daily until stable, then monitoring passes to your team.

07Technology

The Stack We Use

NetSuite sideREST web servicesSuiteQLRESTletsOAuth 2.0Integration serviceNode.jsTypeScriptPostgreSQLMessage queuesNetSuite sideREST web servicesSuiteQLRESTletsOAuth 2.0Integration serviceNode.jsTypeScriptPostgreSQLMessage queues

Store sideShopify Admin APICustom storefront APIsB2B portal APIsWebhooksOperationsConcurrency controlAlertingReplay toolsReconciliation jobsStore sideShopify Admin APICustom storefront APIsB2B portal APIsWebhooksOperationsConcurrency controlAlertingReplay toolsReconciliation jobs

08Who It Is For

Built for Teams Like Yours

FLAGSHIP

Web orders reach NetSuite late or not at all

Orders queue behind a connector that times out during promotions. Inventory on the site is refreshed overnight. An older integration uses SOAP and has no owner. Finance finds orders in the store that never became transactions in NetSuite.

Shopify stores on NetSuite

Custom and headless storefronts

B2B ordering portals

Selling across several subsidiaries

SOAP integrations to replace

Seasonal volume peaks

09Questions

What buyers ask before they start

If yours is not here, ask us directly. The first conversation is free and useful whether or not we work together.

Book a call

REST web services and OAuth 2.0 enabled, an integration record, a custom role with the necessary permissions and a sandbox account to build against. Concurrency is governed per account according to your service tier, and Oracle offers SuiteCloud Plus licences that raise it. We check your current limit and what else consumes it, then document every permission for your administrator to approve.

In time, yes. Oracle's documentation states that the SOAP endpoint released with version 2025.2 is the last one planned, and that SOAP web services will be removed in a later release, after which existing SOAP integrations stop working. Oracle advises building new integrations on REST with OAuth 2.0. We can assess your current integration and plan a migration well ahead of that date.

By never sending more than the account allows. Every request passes through a queue that knows the limit and how much other integrations use. Orders take priority over background jobs such as price updates. Reads are combined through SuiteQL so fewer calls are needed. During a sale the queue lengthens for a short time instead of requests being refused, and that delay is measured.

Possibly. Packaged connectors exist for common storefronts and are sensible when your order to cash process is standard. They become limiting with several subsidiaries, custom transaction forms, unusual pricing or heavy peaks, and their mapping options are finite. We compare the realistic options for your case, including their running costs, and recommend custom integration only when the difference justifies it.

Yes. A portal can show each customer their own price level, open orders, invoices and available credit taken from NetSuite. Because live calls count against concurrency, frequently viewed data is cached for short periods and refreshed when NetSuite reports a change. Sensitive figures such as credit are fetched at the moment an order is placed, so the decision uses current data.

GuidesFree to use with any company