NetSuite integration, built by engineers.
NetSuite holds the orders, the stock and the books. The store, the CRM, the warehouse and the billing system all have to agree with it, and keeping them in agreement is where most of the work goes. We build the integrations, scripts and agents around NetSuite, and move SOAP integrations to REST before Oracle switches SOAP off in 2028.
What Gigabit does on NetSuite.
Gigabit integrates and extends NetSuite for companies that already run it. We connect it to Shopify and marketplaces, CRMs, billing, payment and shipping systems through SuiteTalk REST web services and RESTlets; write SuiteScript and SuiteFlow for logic inside the account; use saved searches and SuiteQL for the data that has to leave it; and build AI agents that read and act on NetSuite records.
We are not a NetSuite partner. We do not sell licences and we do not run first-time ERP rollouts; Oracle's NetSuite Consulting team and its Alliance Partners do that. We take the engineering around it: the integrations an implementation leaves on the list, and the ones that broke after go-live.
The NetSuite work we take on.
Integrations and code around an account you already own, built to keep working through Oracle's releases.
Store and marketplace integrations
Orders, items, stock, fulfilments, refunds and payouts between NetSuite and Shopify, Amazon or a wholesale portal, with a reconciliation report when the two disagree.
CRM and billing sync
Customers, sales orders, invoices and payment status between NetSuite and HubSpot, Salesforce or Stripe, with one customer ID across systems.
SOAP to REST migration
Oracle disables every SOAP web services endpoint with the 2028.2 release. We inventory SOAP integrations and rebuild them on REST web services with OAuth 2.0, or on RESTlets where REST does not reach.
SuiteScript and RESTlets
Custom logic, scheduled and bulk scripts, and RESTlet endpoints for what the standard APIs do not expose, kept in source control and deployed with the SuiteCloud Development Framework.
Workflows and saved searches
SuiteFlow workflows cleaned up so each one has a purpose and an owner, and saved searches or SuiteQL queries that feed reporting without manual exports.
Integration health
Retries, duplicate-safe writes and alerts on every integration, plus a plan for the account's concurrency limit, which all web services and RESTlet calls share.
NetSuite Next puts AI inside the ERP. The rest of your stack is still outside it.
Use what Oracle includes first. Build where the job crosses into other systems.
Built into the platform
When we checked Oracle's pages on 23 October 2026, they described NetSuite Next, the next generation of NetSuite, built around a conversational assistant called Ask Oracle.
- Ask Oracle, for searching, analysing and acting on NetSuite data in plain language, with sources cited and inside each user's existing permissions.
- Bill Capture, Exception Management, Narrative Reporting and Text Enhance, for invoice entry, anomaly detection, report commentary and writing.
- The AI Connector Service, which links outside AI platforms to NetSuite over the Model Context Protocol, and a SuiteScript GenAI API for custom code.
- AI Units, which Oracle uses to measure AI use in NetSuite, so heavy use is something to plan for.
Agents across NetSuite and everything around it
Operations work usually starts in an email, a store or a carrier portal and ends in NetSuite. An agent that can only see NetSuite sees half of the job.
- A returns agent that checks the order and the policy, creates the NetSuite records, books the label and emails the customer, as in our published build.
- Vendor replies parsed into confirmed ship dates and tracking numbers, ready for a buyer to approve.
- Order exceptions classified and prepared as one-click fixes, with a person approving anything that moves money or stock.
- An evaluation set built from your past transactions, run before launch and after every change.
Published prices, mapped to the job.
Every figure here is the same one on the pricing page. Nothing on this platform is quoted from a separate rate card.
A price marked “from” buys the base scope set out on the pricing page. Anything larger is quoted as a fixed price before work starts. Work with no natural end, such as ongoing development, is priced per engineer per month with no lock-in.
Which NetSuite interface to build on, and the dates that matter.
From Oracle's NetSuite documentation and product pages, checked on 23 October 2026. Oracle changes these with its releases, so check the linked pages before you plan.
The ways into and out of NetSuite
| Interface | What it is | Use it for |
|---|---|---|
| REST web services | SuiteTalk's REST API for standard and custom records, authenticated with OAuth 2.0. Oracle names it the replacement for SOAP. | New integrations that create, read and update records. |
| SuiteQL | SQL-style queries sent to the REST web services query service. | Reading data in bulk for sync, reporting and agents. |
| RESTlets | Your own REST endpoints, written in SuiteScript and hosted inside NetSuite. | Objects or methods REST web services do not cover, or logic that should run next to the data. |
| SuiteScript | JavaScript that runs inside the account on record events, on a schedule or in bulk. | Validation, calculations and automation the standard features lack. |
| SuiteFlow | Point-and-click workflows on records. | Approvals and simple routing that an administrator should be able to change. |
| Saved searches | Stored queries built in the NetSuite interface and usable in reports and scripts. | Lists and exports a finance team maintains itself. |
| SOAP web services | The older SuiteTalk API. The 2025.2 endpoint is the last one Oracle plans. | Nothing new. Existing SOAP integrations need moving before 2028.2. |
| NetSuite Connector | Oracle's packaged connectors, formerly FarApp, for ecommerce, logistics and point-of-sale systems. | Standard store syncs. Added through your NetSuite account manager. |
SOAP removal: the timeline Oracle publishes
Every release also disables the oldest unsupported endpoint, so an integration pinned to an old WSDL version can stop well before 2028.2. Existing integrations and their integration records keep working until then, which makes this easy to postpone and expensive to leave late.
| NetSuite release | What changes |
|---|---|
| 2025.2 | The last planned SOAP endpoint. |
| 2026.1 | Oracle says all newly built integrations should use REST web services with OAuth 2.0. |
| 2027.1 | New integrations must use OAuth 2.0, and token-based authentication, which SOAP requires, can no longer be used to build them. |
| 2027.2 | Only the last SOAP endpoint is supported. Older endpoints still run, unsupported. |
| 2028.2 | All SOAP endpoints are disabled and SOAP integrations stop working. |
The limit to design around
Since the 2017.2 release, web services and RESTlet requests count against one concurrency limit for the whole account. Oracle documents it by service tier and number of SuiteCloud Plus licences, and requests over it fail. Every integration therefore needs retries, and an account with several integrations needs the limit split between them, which Oracle's concurrency limit per integration setting allows and its Concurrency Monitor shows.
The practical rule: read in bulk with SuiteQL instead of record by record, write in batches where the API allows it, and never let a busy sync starve the integration that takes orders.
- Oracle NetSuite help: SOAP Removal Plans FAQ
- Oracle NetSuite help: SuiteTalk REST Web Services API Guide
- Oracle NetSuite help: Using SuiteQL with REST web services
- Oracle NetSuite help: Web services and RESTlet concurrency governance
- Oracle NetSuite help: NetSuite concurrency limits
- Oracle NetSuite help: NetSuite Connector (formerly FarApp)
- Oracle NetSuite help: Integrating NetSuite Connector with Shopify
- Oracle NetSuite help: extracting data (saved searches, reports, web services)
- NetSuite SuiteScript and SuiteCloud Development Framework
- NetSuite SuiteFlow
- AI in NetSuite (AI features, AI Connector Service, AI Units)
- NetSuite Next and Ask Oracle
- NetSuite: phases of an ERP implementation
When NetSuite is the right call, and when it is not.
- You already run NetSuite, and other systems have to agree with it.
- Several sales channels, subsidiaries or warehouses feed one set of books.
- Someone in finance or IT owns the account and can approve changes.
- You need a first-time NetSuite rollout. Oracle's NetSuite Consulting or an Alliance Partner runs that project.
- A small business that only needs accounting connected to a store. QuickBooks or Xero with a connector costs far less.
- One standard Shopify sync with no unusual rules. Oracle's own NetSuite Connector may be all you need.
32 Hours Per Week Recovered: AI Workflow Automation for a Multi-Channel E-Commerce Operation
For a $28M multi-channel retailer, the returns flow checks eligibility, creates NetSuite records, books ShipStation labels and sends Klaviyo confirmations. 85% of returns now process with nobody involved, and weekly manual hours across five automations fell from 32 to 4.5.
Questions NetSuite teams ask
How much does NetSuite integration cost with Gigabit?
One scoped integration, such as Shopify orders and refunds into NetSuite or Stripe payouts into deposits, is $8,000 fixed over 3 weeks, with error handling and 30 days of support. An AI agent that works on NetSuite data is a flat fee from $8,000. A SOAP-to-REST migration, SuiteScript work or a larger integration programme is an embedded pod at $3,000–$7,500 per engineer per month. Your NetSuite licence is separate and paid to Oracle.
Is Gigabit a NetSuite partner?
No. We are not a NetSuite partner, we do not resell NetSuite and we do not run first-time NetSuite implementations. We integrate and extend NetSuite accounts our clients already own, using Oracle's published APIs and SuiteCloud tools. For a new rollout, use NetSuite Consulting or an Oracle Alliance Partner, and bring us in for the integrations.
Do you offer NetSuite implementation or consulting?
We do the engineering part of a NetSuite project and leave the functional part to specialists. Chart of accounts, revenue recognition, tax and close processes belong with NetSuite's consultants and your accountants. Integrations, data loads from other systems, SuiteScript, RESTlets and workflows are where we come in, during an implementation or after it. NetSuite's own guide puts an ERP implementation at usually six to 12 months, and integrations can be built alongside configuration instead of after it.
What is the best way to integrate Shopify with NetSuite?
There are three routes. Oracle's NetSuite Connector, formerly FarApp, offers packaged integrations for Shopify and other ecommerce, logistics and point-of-sale systems; you add it through your NetSuite account manager. Integration platforms with prebuilt NetSuite flows are the second. A custom integration on REST web services and RESTlets is the third, and it earns its cost when your rules are unusual: bundles, several locations, B2B price lists, partial refunds, or returns that need records a connector does not create. We start by checking whether the connector covers your rules.
Is NetSuite SOAP being removed?
Yes. Oracle's SOAP Removal Plans FAQ says the 2025.2 endpoint is the last planned SOAP endpoint, that from 2027.2 only that endpoint is supported, and that with the 2028.2 release all SOAP endpoints are disabled and SOAP integrations stop working. Each release also disables the oldest unsupported endpoint, so integrations on old versions can stop sooner. Oracle names REST web services as the replacement, with RESTlets where REST does not cover an object or method.
Which NetSuite API should a new integration use?
REST web services with OAuth 2.0. Oracle says all newly built integrations should use them from the 2026.1 release, and from 2027.1 new integrations must use OAuth 2.0 and can no longer use token-based authentication. Use SuiteQL through the REST query service for reading data in bulk, and a RESTlet when REST web services do not expose what you need.
Can AI agents work with NetSuite data?
Yes, in two ways. Inside NetSuite, Oracle's NetSuite Next adds Ask Oracle, which works within each user's permissions. Outside it, Oracle's AI Connector Service links external AI platforms over the Model Context Protocol, and a custom agent can use REST web services and SuiteQL directly. Either way, give the agent its own integration role with only the permissions its job needs, and keep a person approving anything that changes money or stock.
NetSuite or Odoo?
NetSuite when you run several subsidiaries across countries, consolidation is the hard problem, and you want Oracle to run hosting and upgrades. Odoo when stock, purchasing or manufacturing is central and you want a published per-user price and the option to self-host. We are an Odoo Partner, so we say that plainly; our Odoo vs NetSuite comparison sets out both from each vendor's own pages.
Still choosing an ERP? Published prices against a quote-only contract, hosting, customisation and multi-company, from each vendor's own pages. Odoo vs NetSuite
Also read: ERP and API integration
Often scoped alongside.
Odoo
Implementation, custom modules, upgrades and store integrations from an Odoo Partner, plus agents on Odoo 20.
OdooShopify
Builds, migrations, custom apps and Functions, plus support and returns agents grounded in live order data.
ShopifySalesforce
Integrations, Flow migration, Apex and Agentforce actions at a fixed price, for teams that already run Salesforce.
SalesforceBring the list of what has to talk to NetSuite.
Thirty minutes on the systems, the rules and what breaks today, then a fixed price in writing.


