To choose a Shopify NetSuite integration partner, first pick the model: Oracle’s NetSuite Connector, an iPaaS such as Celigo, Boomi or Patchworks, a NetSuite consultancy, or a Shopify-side agency that builds custom. Then test any partner on payouts, refunds, subsidiaries, VAT, error handling and who owns the integration after go-live. The model matters more than the brand name.
We are a Shopify Plus agency in Dubai that builds custom Shopify–NetSuite integrations, so we sit in one of the four groups below. We have tried to describe all four fairly, and there is a section near the end on when we are the wrong choice. We are not a partner or reseller of any connector or integration platform named here. This is general information, not tax or accounting advice.
Key takeaways
- Choose the model before the firm. Each of the four models puts maintenance with a different owner, and that shapes cost and risk for years.
- Standard flows in one subsidiary rarely need custom code. Oracle’s NetSuite Connector or an iPaaS template is often enough.
- Subsidiaries, VAT, B2B and payouts are where the models differ most. Test every option against your own data.
- Ask about failure, not just features. Retries, monitoring and who gets paged decide how the integration feels six months after go-live.
- Get ownership in writing. Code, flows, hosting and credentials should belong to you.
What are the four ways to get a Shopify NetSuite integration?
Most proposals you receive will fall into one of four models. The model decides who maintains the integration, how it changes and what it costs each year, so compare models first and firms second.
1. Oracle’s NetSuite Connector (formerly FarApp)
Oracle acquired FarApp in 2021 and sells it as NetSuite Connector. You add the Shopify connector through your NetSuite account manager. Oracle’s documentation covers connecting a Shopify store and a Shopify payout report sync, which requires orders to be billed as cash sales and runs every 24 hours. It fits one subsidiary, standard B2C flows and a preference for a product with vendor support over a project.
2. An iPaaS run by a partner or in-house
Integration platforms such as Celigo integrator.io, Boomi and Patchworks sit between Shopify and NetSuite. Celigo offers a Shopify–NetSuite template, Patchworks an accelerator package, and Boomi gives you connectors to build flows with. The vendor maintains the platform. Whoever runs your flows, a partner or your own team, maintains the mapping. An iPaaS fits best when you have several systems to connect, such as a 3PL, a CRM and marketplaces, and someone who will own the platform long term.
3. A NetSuite consultancy or Solution Provider
These firms implement and support NetSuite itself. Many also set up a connector or iPaaS for Shopify as part of a wider NetSuite project, and some write SuiteScript for the gaps. They fit best when NetSuite is being implemented at the same time, or when the hard questions are about accounting design: subsidiaries, revenue recognition and intercompany. Ask how much Shopify work they do, because checkout apps, Markets and B2B settings all change what an order looks like.
4. A Shopify-side agency that builds custom
This is where ConversionsKing sits. The agency writes an integration on the Shopify Admin GraphQL API and webhooks on one side, and NetSuite REST web services, SuiteQL and RESTlets on the other. It fits Shopify and Shopify Plus brands with several subsidiaries, complex VAT, B2B or unusual flows, especially when the same team also works on the storefront. The trade-off is that someone must maintain the code when either platform changes, so support terms matter as much as the build.
How do the four options compare?
| Option | Who owns maintenance | Typical fit | Strengths | Weaknesses |
|---|---|---|---|---|
| Oracle NetSuite Connector | Oracle maintains the product; your admin or a NetSuite partner maintains the configuration | One subsidiary, standard B2C flows, vendor support wanted | Native to NetSuite, bought through your account manager, includes a payout sync | Less room for unusual tax, entity, B2B or payout rules |
| iPaaS such as Celigo, Boomi or Patchworks | The vendor maintains the platform; a partner or your team maintains the flows | Several systems to connect and a team to own the platform | Templates, a visual builder and one place for 3PL, CRM and marketplace links | Recurring licence that grows with endpoints, flows or volume; needs platform skills |
| NetSuite consultancy or Solution Provider | The consultancy under a support agreement, or your NetSuite admin | NetSuite being implemented, finance-led projects | Depth in NetSuite accounting, subsidiaries and SuiteScript | Shopify checkout, apps and Markets may get less attention |
| Shopify agency building custom | You own the code; the agency or your developers maintain it under agreement | Shopify and Plus brands with multi-entity, VAT, B2B or unusual flows | Exact fit to your mapping, no integration licence, one team for storefront and integration | Someone must maintain it; quality depends on monitoring, documentation and handover |
Many brands end up with a hybrid: a connector or iPaaS for the standard flows, and custom code for payouts, B2B invoices or intercompany. That can work well, as long as one named person owns each flow. Our connector vs custom comparison covers named products and the prices vendors publish, and NetSuite Shopify integration cost explains what drives the budget in each model.
10 questions to ask any Shopify NetSuite partner before you sign
Send these in writing and compare the answers side by side. They work whether the proposal is a connector, an iPaaS or a custom build. Our Shopify NetSuite integration checklist expands them into a full scoping and test plan.
- How will you reconcile Shopify Payments and our other payment providers? A good answer: one clearing account per provider and currency, payouts posted from each provider’s transaction-level report, fees posted gross, and a deposit that equals the bank line.
- How do refunds, partial refunds and returns reach NetSuite? A good answer: a credit memo and customer refund dated when the refund happens, closed periods left closed, and one agreed restock rule so both systems do not put the same unit back on sale.
- How do you post orders to the right OneWorld subsidiary? A good answer: a named key, such as the Shopify business entity or market, mapped to one subsidiary in a document finance signs. A strong answer also knows that Oracle lists its EU One Stop Shop feature as incompatible with Multi-Subsidiary Customer, which changes how consumer records are modelled.
- How do you set VAT and OSS tax codes on each order? A good answer: a tax-code map per destination country, separate UK and Swiss treatment, a rule for the B2B reverse charge, and sign-off from your finance team and tax adviser rather than the partner.
- What happens when a record fails or NetSuite is unavailable? A good answer: a durable queue, writes keyed on the Shopify ID so a repeated webhook never creates a duplicate, retries with back-off, and a dead-letter queue where failed records wait with their reason. Nothing is dropped.
- How will we know something is wrong? A good answer: monitoring a business user can read, covering failed records, order-to-NetSuite delay, inventory drift, ageing clearing balances and unusual silence.
- Who gets paged, in which hours, and how fast do they respond? A good answer: named roles, support hours stated in your time zone, response targets in the contract, and a plan for month-end and peak trading weeks.
- What documentation do we get at handover? A good answer: the signed field mapping, an architecture note, a runbook that explains how to retry a record and who to call, a list of credentials and where they live, and the test results.
- How do you handle API version upgrades? A good answer: a routine for Shopify’s API versions, released every three months and each supported for at least 12 months, and a plan for Oracle’s removal of SOAP web services. New builds should use REST web services and OAuth 2.0. Ask who pays for upgrades.
- Who owns the code, the flows and the credentials? A good answer: you do. Custom code sits in your repository, iPaaS flows sit in your tenant or can be exported, keys sit in your accounts, and the contract says how handover works if you part ways.
Red flags when choosing an integration partner
- A fixed price before anyone has asked about your subsidiaries, tax setup, payment providers and order volumes.
- A demo that only shows one standard order. Ask to see a partial refund, a split shipment and a failed record.
- “Finance can reconcile payouts in a spreadsheet.”
- No written answer on who maintains the integration after hypercare.
- New builds on NetSuite SOAP web services or token-based authentication, despite Oracle’s published removal dates.
- Code, hosting or credentials that stay in the partner’s accounts with no exit terms.
- Errors that only reach an email inbox or a log file.
- VAT treatment decided by the partner without your accountant or tax adviser.
- Shopify apps for subscriptions, bundles or loyalty treated as out of scope, even though they change what each order looks like.
When ConversionsKing is a fit, and when it isn’t
We would rather say this now than three weeks into discovery.
We are likely a good fit if
- You sell on Shopify or Shopify Plus and run NetSuite, or have a NetSuite partner implementing it.
- You want a custom integration that you own, with documentation another team could pick up.
- Your flows include several subsidiaries or currencies, OSS and UK VAT, B2B, payouts from several providers, or rules a template does not cover.
- You care about the storefront too, and want the team that changes your checkout, apps and theme to understand what that does to NetSuite.
- You trade in the UK, Europe or the GCC. Our team in Dubai works on UTC+4, which overlaps most of the European working day.
We are probably not the right choice if
- You need NetSuite implemented. We integrate with NetSuite. We do not implement, configure or license it, so a NetSuite consultancy or Solution Provider is the right first call.
- You need accounting or tax advice. We build to the rules your accountant and tax adviser set. We do not set them.
- You want an off-the-shelf connector with vendor support. Oracle’s NetSuite Connector or an iPaaS template gives you a product and a support contract with the vendor. For one subsidiary and standard flows, that is often the better answer, and our assessment will say so.
- Your team already runs every integration on an iPaaS. Keeping Shopify on the same platform, with a partner who specialises in it, is usually simpler than adding a custom service.
FAQ
Who should I hire to integrate Shopify with NetSuite?
It depends on your flows. For one subsidiary and standard B2C orders, start with Oracle’s NetSuite Connector or an iPaaS template. If NetSuite itself is being implemented, use a NetSuite consultancy. For several subsidiaries, complex VAT, B2B or an integration you own, hire a team that builds both sides and answers the 10 questions above in writing.
Is a NetSuite partner or a Shopify agency better for the integration?
Neither is better in general. A NetSuite firm usually knows the accounting side in more depth. A Shopify agency usually knows checkout, apps and Markets in more depth. Whichever you choose, check how they cover the other side, and make sure finance signs the mapping.
What should an integration proposal include?
The flows and their direction, the mapping approach, a test plan, cutover steps, monitoring, support hours, exclusions and who owns what after go-live. A proposal that is only a price and a timeline leaves out most of the work.
Does a Shopify NetSuite partner for Europe need to be based in Europe?
Not necessarily. What matters is overlap with your finance and operations hours, and real knowledge of European VAT, OSS, currencies and subsidiaries. Ask how quickly an issue raised at 09:00 in Berlin is looked at. Our Shopify NetSuite integration guide for Europe covers the European rules in detail.
If you are comparing proposals now, our free NetSuite Shopify integration assessment reviews your flows, subsidiaries and tax setup and tells you which of the four models fits, including when it is not us. You can also see how we build it on the Shopify NetSuite integration page, or start from the NetSuite Shopify integration for Europe hub.
