For a single Shopify store with standard orders and NetSuite as the inventory owner, start with Oracle's NetSuite Connector. If you run several stores, sell kits or assemblies, or need flows you can adjust yourself, a packaged integration app such as Celigo's is usually the better fit. Choose a custom integration when your order rules are specific to your business, such as drop-ship routing or custom order splitting, or when a missed or duplicated order is expensive. Many stores end up with a packaged tool for the standard flows and a small custom piece for the one flow that keeps breaking.
This guide compares the three options side by side and shows which store each one fits. For how the data flows and what typically breaks, see Shopify NetSuite integration: how it works and what breaks.
The three options at a glance
| NetSuite Connector | Packaged integration app (for example Celigo) | Custom integration | |
|---|---|---|---|
| Who builds it | Oracle NetSuite | An integration vendor | Your developer or partner |
| Best fit | One store, flows close to standard | Several stores or systems, flows you want to adjust | Rules no packaged tool can express |
| How you change it | Field mappings and settings | Prebuilt flows you can edit and extend | Code changes |
| Pricing model | Monthly plan | Annual subscription, tiered by endpoints and flows | Build cost plus ongoing engineering time |
| Main risk | Your process outgrows its settings | Flows nobody understands a year later | No owner after launch |
NetSuite Connector
Oracle publishes NetSuite ERP Connector on the Shopify App Store. Its listing says it "automatically syncs product, pricing, inventory, sales order, and fulfillment data", and its plans include order, coupon, gift certificate, fulfillment, price and quantity, and product sync. Setup is mostly mapping item and order fields between the two systems.
It fits when your store looks like the one the connector was built for: one storefront, orders that become standard sales orders, and NetSuite as the system that knows what is on the shelf. Check refunds and returns early, because the listing does not describe them.
A packaged integration app
Integration platforms sell prebuilt Shopify NetSuite flows on top of a general integration tool. Celigo's NetSuite Integration app, for example, lists customers, items, orders, cancellations, refunds, returns and B2B, inventory from warehouses "including assembly and kit items", and syncing "multiple stores to one NetSuite instance". The flows come pre-mapped and can be changed or extended.
It fits when you have more than one store, sell kits, or expect to connect other systems later, and you have someone who will own the flows. The cost of that flexibility is maintenance: every edited flow is logic someone has to understand when it fails.
A custom integration
Code written against the Shopify Admin API and NetSuite's APIs, built for your rules. It gives full control over how orders are split and routed, how retries work, and how failures are logged and reported. It also needs an engineering owner for as long as it runs.
It fits when the rules are yours alone: drop-ship orders routed to suppliers, custom order splitting, bundles that NetSuite tracks as components in a way the packaged tools do not handle, or a volume where a missed or duplicated order is expensive enough to justify reconciliation jobs and alerts. We cover those reliability basics in Why automations fail silently and create duplicate records.
Which store fits which option
| Your store | Likely starting point |
|---|---|
| One store, standard orders, NetSuite owns inventory | NetSuite Connector |
| Several stores into one NetSuite account | Packaged integration app |
| Kits and assemblies, B2B and DTC together | Packaged integration app, tested on your real orders |
| Drop-ship routing, custom order splitting, unusual approval rules | Custom integration, or a packaged app plus one custom service |
| High volume with strict daily reconciliation | Custom integration with queues and reconciliation jobs |
Decide this per data flow, not for the whole business. Orders may fit a packaged tool while inventory for drop-ship items needs custom logic. The general framework is in Native connector, middleware, or custom API integration: how to choose.
Not sure which one your store needs? Bring a list of your storefronts, warehouses and a few orders that failed to sync to a Systems Discovery Call. If a connector covers your flows, we will tell you.
Signs you have outgrown your current setup
- Orders reach NetSuite late, twice, or not at all.
- Inventory in Shopify does not match what the ERP says is on hand.
- The connector covers the standard flows but not your custom ones.
- Refunds, returns, and partial fulfillments break the sync.
- Nobody knows a sync failed until a customer or accountant notices.
One of these is a reason to fix a flow. Several of them usually mean the tool no longer matches how your store runs.
Questions to ask before you choose
- Which system owns each field: products, prices, inventory, orders, customers and refunds?
- Which of our recent orders would the tool handle badly: gift cards, edited orders, partial refunds, kits?
- Where do we see every failed record, and who gets alerted?
- What happens when we add a store, a warehouse or a supplier?
- Who changes a mapping or a rule, and how long does it take?
How we approach it
We look at each data flow, decide which system owns it, and recommend the simplest approach that will hold up: an off-the-shelf connector, an integration platform, or custom code. If a NetSuite Shopify connector covers your flows, we will tell you. We can assess your current connector, fill its gaps, or replace the parts that do not fit, then monitor and maintain the integration as Shopify and NetSuite change. Our custom middleware syncs inventory in real time across five ecommerce stores. Details are on our Shopify NetSuite integration page.
Common questions
Is NetSuite Connector enough for most Shopify stores?
For a single store with standard orders, often yes. It becomes a poor fit when you run several storefronts, sell bundles or kits, drop-ship from suppliers, or need order rules it cannot express.
When is Celigo or another packaged app better than NetSuite Connector?
When you need more than one store in one NetSuite account, kit and assembly inventory, or flows your team can edit and extend, and you have someone to own those flows.
Can we keep our connector and add custom pieces?
Yes. Many stores keep the connector or app for standard flows and add a small custom service for one problem, such as bundles or drop-ship routing.
Next step
If Shopify and NetSuite are not agreeing, book a Systems Discovery Call. It is 45 minutes on your stores, your NetSuite setup, and where data breaks today. You leave with a map of your data flows and a clear recommendation, whether you hire us or not.
Farooq Ch
Nov 2026