Connecting NetSuite to the rest of your systems

Most dissatisfaction with an ERP in a growing company does not come from the ERP itself. It comes from the gaps around it: orders typed twice, bank lines copied from a spreadsheet, stock figures that differ between the shop and the warehouse. A well-chosen NetSuite connector closes those gaps. A badly scoped one simply moves the re-keying into an error log that nobody reads.

This page is for finance directors, operations managers and IT leads in UK small and mid-sized businesses who are weighing up how Oracle NetSuite should talk to their other systems. It covers the NetSuite API, the extension marketplace, the usual UK integration candidates and, most importantly, how to define a flow and decide who looks after it.

The three ways to connect NetSuite

Every NetSuite integration falls into one of three families. The choice shapes cost, speed and long-term upkeep far more than the technology behind it.

There is no universal winner. A business with an online shop, a bank and a payment provider will often use packaged connectors for each. A manufacturer with a bespoke planning tool will lean on the API. The honest answer comes from the flow list, not from a preference for one technology.

Understanding the NetSuite API

The programming interface most people mean by API NetSuite is SuiteTalk, the web services layer. It exists in two forms, and the difference matters if you are inheriting or commissioning work today.

REST web services

The REST web services of SuiteTalk offer create, read, update and delete operations on records, access to metadata, filtering of collections, record actions and transformations, and asynchronous processing. They can also run SuiteAnalytics workbook datasets and SuiteQL queries. A notable point in Oracle's documentation is that this works without deploying a script, which distinguishes it from RESTlets, where you write and deploy your own SuiteScript endpoint.

In practical terms, REST suits most new work: reading customer and item data into a portal, pushing orders in, pulling reporting data out for analysis. It is also the direction Oracle recommends.

SOAP web services and their retirement

The older SOAP web services use a Document encoding, meaning XML messages rather than remote procedure calls. They run over HTTPS only, use role-based access control (a "Web Services Only" role exists) and support synchronous or asynchronous requests. Many existing connectors and in-house integrations were built on them.

Here the timetable is important. Oracle's documentation states that the 2025.2 WSDL is the last SOAP endpoint planned, that only this endpoint will be supported from release 2027.1, and that SOAP will no longer be available after release 2028.2. For any new project, the documentation recommends REST with OAuth 2.0.

If a supplier proposes a new SOAP-based flow today, ask why. If you already run SOAP-based flows, ask the publisher or your integrator when each will move to REST, and put that work in your budget rather than discovering it late.

Scripts, RESTlets and customisation

Where the standard web services do not fit, NetSuite can be extended with scripts and custom endpoints. This is powerful, but it becomes code that your business must keep alive through every release. Our page on NetSuite customisation and development explains when this is justified and how to keep it tidy.

Extensions and the SuiteApp marketplace

NetSuite has a marketplace of add-on applications published by Oracle and third parties. For a UK buyer it is a sensible first stop when a flow is common, because a tested app is usually quicker to put in than a build. Treat it as a shortlist, not a guarantee.

Before choosing an app, ask the publisher:

• Which NetSuite editions and modules it supports, and how it behaves if you add subsidiaries or currencies later.
• Whether it uses REST or SOAP behind the scenes, given the retirement timetable above.
• How errors are reported, and to whom.
• Who provides support when the fault sits between the two systems.
• What happens to your data and your mapping if you stop paying for it.

Your integrator should be able to answer these from experience. If they cannot, that is information about the integrator. Our guidance on choosing a NetSuite partner lists further questions.

Integrations UK businesses ask for most

The list below follows the order in which UK companies commonly raise them. Whether a ready-made connector exists for your exact combination must be confirmed with your integrator, not assumed.

E-commerce shops and marketplaces

Online selling is the most frequent request. The flow usually carries orders into NetSuite, stock levels and prices back to the shop, and fulfilment and tracking information out to the customer. Marketplace sales add their own fee, refund and VAT treatment. Decide early whether NetSuite or the shop is the master for product data, and who handles returns. Our page on e-commerce ERP goes deeper on these choices.

Banks and payments

Bank feeds are what let your finance team reconcile without retyping statements. Payment providers add settlement files, fees and chargebacks, which must be matched to customer invoices. Pay attention to how supplier payment files are produced for UK bank transfers, and who approves them. The NetSuite accounting and finance page covers the ledger side of the same process.

HMRC, Making Tax Digital and payroll

VAT returns under Making Tax Digital and payroll submissions through RTI are the two UK-specific links that surprise newcomers. The principle is that the software used to submit must meet HMRC's requirements, and your accountant may prefer a particular route. Read our guides on Making Tax Digital and ERP and payroll and RTI before you fix the design, and involve your accountant in the decision.

E-invoicing and EDI

Some customers, particularly large retailers and public bodies, require invoices or orders in a structured electronic format. These exchanges often run through a specialist network provider, with NetSuite on one side. Our overview of electronic invoicing and ERP explains the terms you will meet.

Office tools, reporting and signature

Spreadsheets, email, calendars and document signature are low-risk integrations that save a surprising amount of time. For reporting, NetSuite's own SuiteAnalytics can run datasets and SuiteQL queries through the REST layer, which allows external business intelligence tools to read the same figures your finance team sees. Agree which system holds the official definition of each measure, otherwise two dashboards will disagree.

Customer-facing systems

A CRM, a support desk or a customer portal often needs a reliable view of accounts, orders and balances. If NetSuite holds the commercial record, decide whether the other tool reads it live or keeps a copy. The sales and CRM page shows where NetSuite's own functions may remove the need for a separate tool.

How to scope one integration flow

A flow that is described in a sentence will be built badly. Write each one on a single page, using the headings below. This is also the quickest way to compare quotes.

1. Purpose. What business event starts it, and what should be true afterwards?
2. Direction. From NetSuite, into NetSuite, or both? If both, which side wins on a conflict?
3. Trigger and timing. Immediate, on a schedule, or on demand? A daily stock update and an instant order confirmation are different engineering jobs.
4. Data and mapping. Which fields, which reference lists, and who keeps the mapping tables current?
5. Volumes and peaks. Sale periods and month-end can multiply traffic well beyond a normal day.
6. Errors. What counts as a failure, who is alerted, and how is a rejected record corrected and replayed?
7. Security. Which account or role is used, what can it see, and how are credentials rotated?
8. Testing. Which realistic cases, including refunds, part shipments and foreign currency, must pass before go-live?
9. Owner. A named person on your side, and a named supplier on theirs.

Keep the list of flows short at first. Companies that try to connect everything on day one often delay go-live. A better pattern is to launch with the flows the business cannot run without and add the others in later phases, as described in our page on NetSuite implementation.

Who maintains an integration after go-live

This is the question most contracts leave vague, and it is where the real cost sits. An integration is not finished when it works; it must keep working when NetSuite is updated, when the shop changes its checkout, when the bank alters a file format and when your own product range grows.

Whichever model you pick, the support agreement should mention integrations explicitly. See NetSuite support and maintenance for what a sensible agreement covers.

Budgeting for integrations

Integration cost is rarely a single line. It includes the connector subscription or the build effort, testing time on your side, training for the people who will monitor errors, and the continuing cost of keeping it alive. Do not accept a single figure for "integrations". Ask for a price per flow, with assumptions listed. Our page on NetSuite pricing explains how the main cost elements fit together, and the UK page for NetSuite covers local considerations such as VAT and reporting.

Common mistakes to avoid

• Treating the connector as a product rather than a service. The software is only part of it; someone must watch it.
• Starting with the tool. Decide the flow and the data owner first, then pick the connector or the API.
• Ignoring data quality. An integration will transmit duplicate customers and inconsistent product codes faithfully. Clean the data first.
• Building new work on retiring technology. Check the interface used behind any connector or script.
• Forgetting the exit. Know how you would replace a connector without losing history.

Next step

If you already have a list of systems to connect, send it with your request. We pass it to an integrator who has handled similar NetSuite environments, so that flows, owners and maintenance are discussed from the first call.

Our service is free for the buyer and neutral between ERP vendors. If you are still deciding whether NetSuite is the right system, the pages on how the service works and on the modules available are good places to continue.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.