NetSuite integrations that keep orders, stock and cash in step.
NetSuite is usually the system of record for money and inventory, and the orders, quotes and shipments that feed it arrive from somewhere else. We connect those systems to NetSuite on its current REST interface, and we move older SOAP integrations before Oracle switches SOAP off.
On this page
What we connect NetSuite to
- Online stores: Shopify orders, refunds and inventory, in both directions.
- CRMs: Salesforce and HubSpot, so a won deal becomes a sales order and reps can see invoices and balances.
- Other ledgers: QuickBooks or Xero at subsidiaries that haven't moved onto NetSuite yet.
- Warehouses and 3PLs, for fulfillment, tracking and stock counts.
- Banks and payment processors, for settlements and reconciliation.
- Your own databases, data warehouse and the spreadsheets finance still maintains by hand.
Oracle is removing SOAP from NetSuite
Oracle's NetSuite help center sets out the timeline. The 2025.2 SOAP endpoint is the last planned one. From the 2027.1 release, only that 2025.2 endpoint will be supported. With the 2028.2 release, SOAP will no longer be available and existing SOAP integrations with NetSuite will stop working. Oracle's instruction for new integrations is SuiteTalk REST web services with OAuth 2.0.
Many NetSuite integrations built before 2024, including some sold as packaged connectors, still run on SOAP. If one of yours does, it needs a plan well before 2028. Oracle recommends asking the vendor for a REST-based version of any partner application. For custom integrations, we rebuild the SOAP calls on REST and run the two side by side until the numbers match.
Connector, integration platform or custom code
| Option | Good for | Watch out for |
|---|---|---|
| A packaged connector, such as Oracle's NetSuite Connector for Shopify | Standard order, item and fulfillment flows | Custom fields, unusual tax or discount rules, and whether it runs on REST |
| An integration platform such as Celigo, Boomi or Oracle Integration Cloud | Many systems, and a team that will own the platform | Subscription cost, and logic spread across flows |
| Custom code on SuiteTalk REST, SuiteQL and RESTlets | Your own rules, high volume, and an audit trail | It has to be built and maintained, and it should be yours |
If a connector handles your process, we will say so and help you set it up properly. Custom work is for the parts where a silent mismatch costs you money: pricing, landed cost, multi-subsidiary rules, or inventory that must be right before a customer can order.
How we build a NetSuite integration
- We read with SuiteQL and write through REST records, using RESTlets where NetSuite's standard records don't expose what you need.
- NetSuite limits how many requests an account can run at once, based on its service tier and SuiteCloud Plus licenses. We design to fit that limit, so the integration doesn't block your users or your other integrations.
- Each order, payment and adjustment is applied once, even if the source system sends it twice.
- Records that fail NetSuite's validation go to a review queue with NetSuite's own error attached.
- A daily reconciliation compares order counts, totals and stock between NetSuite and each connected system.
- Every change is tested in a NetSuite sandbox account before it reaches production.
The general pattern is on our custom API integrations page.
Where the data problem is bigger than an integration
Sometimes the systems are connected and the decisions are still made in spreadsheets. For a distributor running 500 routes across twelve states we put routing, stock and demand on one data model. Read the case study.
What it costs
A single, well-defined flow on REST is a small project. A Shopify, Salesforce and 3PL integration across several subsidiaries, or a SOAP-to-REST migration of a large integration, is a larger one. We fix the price once the integration inventory exists: every system, record, field and rule, written down. For market figures, see what custom software development costs.
The Automation Audit
One workflow you name, mapped end to end, with the arithmetic done before anyone writes code.
- Scope
- One workflow you choose, traced end to end, including the steps nobody documented.
- Duration
- Two weeks, fixed.
- Fee
- Fixed, and quoted in full before we start. No hourly drift.
- You get
- A written map: what can be automated, what it would save in hours, what building it would cost, and what we would leave alone.
- You keep it
- The map is yours whether or not you hire us to build anything.
And if the audit shows the automation will not pay for itself inside twelve months, we will tell you, and we will not quote the build.
Questions we get asked about NetSuite integrations
How do we know whether our integrations use SOAP?
NetSuite shows web services usage in its logs, and the integration records in your account list what is connected. The audit includes that check, and the answer is a list of each integration, the protocol it uses, and who maintains it.
Can you work with our NetSuite administrator or partner?
Yes. Your administrator or NetSuite partner keeps the account configuration, and we build and support the integration. We agree who changes what before we start.
Do you write SuiteScript?
Yes, when the logic belongs inside NetSuite, for example a RESTlet or a user event script. Logic that coordinates several systems stays outside NetSuite, in code you own.
What about Shopify and NetSuite specifically?
It's the most common pair we are asked about. Our Shopify integrations page covers the order, inventory and refund flows in detail.
