Matthew Collins, the 1st of October 2026
NetSuite businesses usually reach us with the same story. NetSuite holds the truth about stock, prices and customers. Shopify holds the orders. Someone on the team keeps the two in agreement by hand, and it gets harder every month.
A Shopify NetSuite integration fixes that. NetSuite stays in charge of the records it already owns, usually items, stock, trade pricing, customers and invoices. Shopify runs the storefront and sends orders back. You can do it with a ready-made connector or a custom build. The real work is agreeing who owns each record and testing what happens when a sync fails.
Why do Shopify and NetSuite work well together?
NetSuite is built to run the back office. Finance, inventory, purchasing and fulfilment sit in one system, often across several subsidiaries and warehouses. Shopify is built around the buyer, with a fast checkout and a large app ecosystem.
Each does its own job well. Trouble only starts when both systems try to own the same record. Then the storefront shows one stock figure and the warehouse holds another.
Which system should own what?
This is the split we start from. Your business may need a variation, and that's fine as long as it's agreed before the build.
- Items and variants. NetSuite owns codes, units and costs. Shopify adds photography, copy and collections.
- Stock. NetSuite owns it by location and pushes availability to the matching Shopify locations.
- Prices. Trade price levels live in NetSuite. Retail prices can live in either system, but only one.
- Customers. Matched on a shared reference, so an online buyer and a NetSuite customer are the same record.
- Orders. Created in Shopify and sent to NetSuite as sales orders, with payment status attached.
- Fulfilment and tracking. Confirmed in NetSuite and sent back to Shopify, so customers get their shipping email.
- Invoices and payment terms. NetSuite.
Write this list down and get your finance lead to sign it. It becomes the spec for everything that follows.
Connector or custom build?
There are two well-known connectors. Oracle NetSuite publishes its own NetSuite ERP Connector on the Shopify App Store. It lists orders, products, pricing, inventory across warehouses and fulfilment, with B2B on its own higher tier. Celigo offers a NetSuite integration app that lists customers, items, orders, refunds, returns and B2B.
Both are paid subscriptions on top of Shopify and NetSuite. For a clean retail setup, a good connector is often the right answer. You get a tested sync without building one from scratch.
We build a custom integration when the logic is yours alone. That might be order routing across subsidiaries, custom NetSuite records a connector doesn't know about, or orders that must land in a particular state. A custom app also gives you full control of logging and alerts. Our note on custom apps or public apps explains how we make that call.
Either way, someone still has to design the mapping and test the edge cases. The tool matters less than the decisions behind it.
What usually goes wrong?
The same few issues come up on almost every ERP integration we scope. NetSuite is no exception.
Matrix items come first. NetSuite builds variants from matrix options. Shopify has its own option structure. Products with many options need a mapping plan before anything syncs.
Tax comes second. NetSuite applies its own tax rules. Shopify calculates tax at checkout. The two need to agree on how an order's tax lands in NetSuite, especially when you sell across borders.
Stock timing comes third. If stock syncs every hour and a line sells fast, you can oversell. Deciding sync frequency by product type is part of the design.
Partial events come last. Split shipments, partial refunds and cancelled lines are where syncs quietly fail. Test them before launch, not after the first busy week.
What about B2B on Shopify and NetSuite?
Wholesale adds a layer. Trade buyers expect their own price, their own catalogue and their payment terms on screen. On Shopify that means company accounts and catalogues, fed by the price levels and terms already in NetSuite.
Before the build, decide how a NetSuite customer becomes a Shopify company. Decide which catalogue each one sees, and where the invoice is raised. Our note on Shopify B2B without Plus covers which B2B tools you get on each plan.
What we'd ask before we start
These questions shape the scope more than anything else.
- Who looks after NetSuite, your team or a partner?
- Do you run more than one subsidiary or currency?
- Which custom records or scripts touch items, customers or orders?
- Do trade customers have their own price levels or terms?
- How many locations do you run, and which ones serve online orders?
- What happens today when an order goes wrong?
The last answer often becomes the spec for error handling. For the phases of a full project, see our guide to what a Shopify ERP integration involves.
Where parallel helps
We don't have a published NetSuite case study yet, and we won't pretend otherwise. What we have is the wholesale pattern we shipped on Business Central for Fáilte Foods, with real-time order and customer sync. The ownership thinking carries straight across to NetSuite.
See how we approach apps and integrations, then book a call and tell us how your NetSuite is set up.