Choose a prebuilt Shopify NetSuite connector when your flows are standard, you run one subsidiary and you want something live quickly. Choose a custom build on the Shopify Admin GraphQL API and NetSuite REST web services when you have several subsidiaries, complex VAT, B2B or unusual flows. Many European brands use a connector plus custom code.
This article compares the main options available on 1 November 2026: Oracle’s NetSuite Connector, In8Sync, Celigo, Boomi, Jitterbit and Patchworks, plus a custom build. We only quote prices that vendors publish themselves, with a link. Everything else is “quote on request”. We are not a partner or reseller of any of these vendors.
Key takeaways
- There are three families: NetSuite-native SuiteApps, integration platforms (iPaaS) with Shopify–NetSuite templates, and custom builds.
- Of the vendors here, only Celigo (on its Shopify App Store listing) and Boomi (for its pay-as-you-go edition) publish prices. The rest quote.
- Licence cost is only part of the picture. Implementation, mapping, testing and support often matter as much.
- Ask every vendor how its product handles Oracle’s removal of SOAP web services and token-based authentication.
- For European multi-entity businesses, test the connector against your subsidiaries, OSS tax codes and currencies before you sign.
What are the options for connecting Shopify and NetSuite?
NetSuite-native SuiteApps install inside NetSuite and connect directly to Shopify. Configuration happens in NetSuite or the vendor’s portal.
Integration platforms sit between the two systems. They offer prebuilt templates for Shopify and NetSuite, plus a visual builder for changes. You can usually connect other systems too, such as a 3PL, a CRM or a marketplace.
Custom builds are code written for your business, using Shopify’s and NetSuite’s APIs directly, hosted in your cloud account or the partner’s.
The connectors, one by one
Oracle NetSuite Connector (formerly FarApp)
Oracle acquired FarApp in 2021 and sells it as NetSuite Connector. Oracle’s documentation covers connecting a Shopify store, multi-location inventory mapping, cancellations and a Shopify payout report sync that creates deposits with fee lines. That payout sync requires orders to be billed as cash sales, not invoices, and runs every 24 hours. You add the Shopify connector through your NetSuite account manager. No public price.
In8Sync DirectConnect
In8Sync sells a Shopify connector that installs as a SuiteApp inside NetSuite, with no separate middleware. It lists orders, customers, items, inventory, pricing, fulfilment tracking and refunds, and says it supports Shopify Plus, B2B and multiple stores. No public price.
Celigo
Celigo’s integrator.io platform has a Shopify–NetSuite template with prebuilt flows for orders, cancellations, customers, products, fulfilments and refunds. Its pricing page lists Standard, Professional and Enterprise editions without figures. However, Celigo’s NetSuite Integration listing on the Shopify App Store shows a Starting Package at $7,800 per year (two app endpoints, 10 integration flows) and a Standard Edition at $18,900 per year (three endpoints, 20 flows), billed in USD, as of 1 November 2026.
Boomi
Boomi is a general integration platform. Its Shopify connector documentation gives syncing a Shopify catalogue and orders with an ERP such as NetSuite as a typical use. You build the flows yourself or with a partner. Boomi’s pay-as-you-go FAQ states a price starting at $99 per month plus $0.05 per message, as of 1 November 2026. Its other editions are quoted.
Jitterbit
Jitterbit’s Harmony platform offers a Shopify–NetSuite template that syncs customers, products, shipments and fulfilment status and creates sales orders. Jitterbit’s own NetSuite connector documentation says the connector uses SOAP web services and requires token-based authentication, and that from NetSuite 2027.1 new integrations can no longer be built that way, while existing endpoints continue. Jitterbit’s pricing page offers custom quotes only.
Patchworks
Patchworks is a London-based integration platform with a Shopify and NetSuite accelerator package. Its pricing page lists plans as “enquire for pricing”, based on connected systems and monthly operations, with unlimited users.
Options we left out
Anchor Group, often mentioned alongside FarApp, is a NetSuite and Shopify services firm that implements and customises connectors such as NetSuite Connector and Celigo. It is not a separate connector product, so it is not in the table.
| Option | Type | Shopify–NetSuite package | Published price (checked 1 Nov 2026) |
|---|---|---|---|
| NetSuite Connector (Oracle) | NetSuite-native | Yes | None published |
| In8Sync DirectConnect | NetSuite-native SuiteApp | Yes | None published |
| Celigo integrator.io | iPaaS | Yes, template and integration app | $7,800/yr or $18,900/yr on its Shopify App Store listing |
| Boomi | iPaaS | Shopify and NetSuite connectors; you build flows | Pay-as-you-go from $99/month plus $0.05 per message |
| Jitterbit Harmony | iPaaS | Yes, template | None published |
| Patchworks | iPaaS | Yes, accelerator | None published |
| Custom build | Code you own | Built to your mapping | Scoped per project; no licence fee |
Prices change. Check each vendor’s page before you budget, and ask what triggers the next tier: endpoints, flows, messages, operations or subsidiaries. Also ask whether implementation is included, or whether you need a separate partner to configure the template for your account.
What does a custom Shopify NetSuite build look like?
A custom integration is a small service with a few clear parts:
- Shopify side. HMAC-verified webhooks for orders, refunds and customers, the GraphQL Admin API for writes, and bulk operations for large reads such as a catalogue backfill.
- NetSuite side. REST web services and SuiteQL for most records, RESTlets or SuiteScript where REST cannot do the job, and Map/Reduce scripts for heavy batch work, authenticated with OAuth 2.0.
- In between. A durable queue, idempotent writes keyed on the Shopify ID so a replayed webhook never creates a duplicate, retries with back-off, a dead-letter queue and alerts.
The strength is fit. You map your subsidiaries, tax codes, currencies and B2B rules exactly, and you own the code. The cost is that someone must maintain it when either platform changes. You also need monitoring that a business user can read, so that a failed order is visible the same day rather than at month end. Ask any custom-build partner who owns the code, the hosting account and the credentials after go-live, and how they hand over if you part ways. We describe our version on the Shopify NetSuite integration page.
Which platform changes should every option handle?
Two changes affect connectors and custom builds alike:
- Shopify. The REST Admin API has been legacy since October 2024, and new public apps must use GraphQL from April 2025, according to Shopify’s changelog.
- NetSuite. Oracle’s SOAP removal plans say no new SOAP integrations can be built from 2027.1 and all SOAP endpoints will be disabled in 2028.2. Its authentication page says new integrations cannot use token-based authentication from 2027.1 and should use OAuth 2.0.
Ask each vendor, in writing, which NetSuite API and authentication method their Shopify product uses today and what their migration plan is.
Decision table: connector, iPaaS or custom?
| Your situation | Lean towards | Why |
|---|---|---|
| One subsidiary, one currency, standard B2C flows | NetSuite-native connector | Fast to switch on, little to maintain |
| Several systems to connect (3PL, CRM, marketplaces) and an in-house integration team | iPaaS | One platform for all connections |
| Several OneWorld subsidiaries or Shopify business entities | Custom or hybrid | Entity routing and intercompany rules rarely fit a template |
| OSS plus UK and Swiss tax codes on the same store | Custom or hybrid | Tax code logic per destination needs to be exact |
| Shopify B2B with company accounts, payment terms and e-invoicing | Custom or hybrid | Customer hierarchy and invoice output vary by business |
| Very high order volume at peaks | Custom, or iPaaS with tested limits | You control queueing against NetSuite concurrency |
| Existing connector works except for two or three flows | Hybrid | Keep what works, build the gaps |
Is a hybrid approach sensible?
Often, yes. A connector might handle orders and inventory well, while payouts, B2B invoices or intercompany are where it struggles. Keeping the connector for the standard flows and adding custom code for the edges can be cheaper than replacing everything. The trade-off is two places to monitor, so agree who owns each flow and where errors appear.
Questions to ask any vendor or partner
- Show us a working example with several subsidiaries and currencies.
- How are OSS, UK and Swiss tax codes set on each order?
- What happens when NetSuite is unavailable or hits its concurrency limit?
- How are duplicates prevented when a webhook arrives twice?
- Which NetSuite API and authentication method do you use?
- What triggers a price increase: endpoints, flows, messages or volume?
- Where is personal data stored and logged, and for how long?
Our integration checklist turns these into a document you can send to vendors. For cost drivers beyond licences, read NetSuite Shopify integration cost.
FAQ
Is Celigo better than a custom build?
Neither is better in general. Celigo suits businesses whose flows fit its templates and who want a managed platform. A custom build suits businesses with multi-entity, tax or B2B rules the templates do not cover.
Do any of these connectors handle EU OSS?
Tax is usually calculated in Shopify or NetSuite, not in the connector. What matters is whether the connector can set the right NetSuite tax code and subsidiary per order. Test that with your own data.
Can we move from a connector to a custom build later?
Yes. Keep the field mapping documented and use the same Shopify ID references, so the new integration can take over without duplicates.
Next step
If you are choosing between a connector and a custom build for Europe, our free NetSuite Shopify integration assessment reviews your flows and subsidiaries and recommends one, including when a connector is the better answer. For background, see the Shopify NetSuite integration in Europe guide and our Europe hub.
