Shopify NetSuite Integration (2026): Connector, Celigo or Custom, and What Breaks

A Shopify NetSuite integration connects your store to NetSuite through Oracle’s NetSuite Connector (formerly FarApp), Celigo’s Shopify-NetSuite integration app, another marketplace app, or a custom build on both platforms’ APIs. Pick a connector when your orders are standard B2C orders and its plan covers refunds and payouts the way finance needs them; build custom when bundles, multiple stores, B2B rules or volume push you outside the connector’s model.

We are integration engineers. We build syncs between storefronts, marketplaces and the ERPs behind them, so this guide looks at what each option actually moves and where it fails. Prices are list prices as of November 2026 from the vendors’ own pages; where a vendor publishes no price, we say “quote-based”. For the wider picture of NetSuite APIs, limits and authentication, see our NetSuite integration guide.

What syncs, and in which direction

The core of every Shopify-NetSuite integration is the same. Orders go from Shopify into NetSuite as sales orders or cash sales. Items, prices and stock go from NetSuite to Shopify. Fulfillments and tracking numbers go back to Shopify so customers get shipping emails. The hard part is money after the sale: refunds, returns, gift cards and Shopify Payments payouts.

Write this map for your own store before you look at products: every record, its direction, its frequency and which system owns it. Then ask each vendor to show your map in a demo, with your own orders.

Your options

Oracle NetSuite ERP Connector. Oracle’s own connector, built on the FarApp product Oracle acquired. On the Shopify App Store it is published by Oracle NetSuite with four plans: B2C Standard at $199.92 per month, POS at $249.92, B2C Premium at $249.92 and B2B at $916.58. The listing notes that Oracle NetSuite may bill external charges separately from the Shopify invoice. B2C plans cover order sync, coupon sync, fulfillment sync, price and quantity sync and full product sync, with gift certificate sync on B2C Standard and Premium; Premium makes order and price and quantity sync real-time. The B2B plan adds invoice posting, subsequent payment handling, B2B order sync and standalone B2B customer sync.

Celigo Shopify-NetSuite integration app. A prebuilt app on Celigo’s integration platform. Celigo lists flows for orders, customers, items, inventory, fulfillments, billing, cancellations and refunds, with payout report download as an add-on and store-to-store cloning of settings for multi-store setups. Celigo publishes plan names but no prices, so it is quote-based, usually an annual contract.

Other apps and iPaaS. Other marketplace apps and general iPaaS products such as Boomi or Workato can connect the two systems, usually with templates you configure rather than a finished app. They suit teams that already run an iPaaS for other flows.

Custom integration. Your own service between the Shopify Admin API and webhooks on one side and NetSuite REST web services, RESTlets and SuiteScript on the other. You pay in development hours and own the maintenance, but the data model is yours.

How to choose between them

Start with three questions. First, does your order flow look like a standard B2C checkout: one store, one subsidiary, items that exist in NetSuite one to one? If yes, Oracle’s connector on the plan that matches your channels is the shortest path, and the published monthly price makes the budget easy. Check the plan table carefully, because real-time sync, gift certificates and B2B are tied to specific plans.

Second, do you run several stores, several flows beyond Shopify, or a finance team that wants refunds and payouts automated from day one? Then Celigo or another iPaaS deserves a demo. You get more flows and more control over mappings, and you pay for it in an annual contract and in admin time. Someone on your side has to own the flows and read the error dashboard.

Third, is any core flow unusual? Bundles assembled at the warehouse, orders split across subsidiaries, customer-specific pricing pulled from NetSuite, or products configured at checkout are the usual suspects. A connector can often be bent to handle these with custom fields and scripts, but every workaround becomes something you maintain inside someone else’s product. In that case a custom integration for the core flow, possibly next to a connector for the simple parts, is usually cheaper over a few years.

Whatever you choose, ask each vendor the same things: how a failed order is shown and resent, how partial refunds post, how payouts reconcile, and what happens when NetSuite rejects requests at peak.

If you sell on more channels than Shopify, compare the wider options in our NetSuite ecommerce integration guide, and if you are still choosing the ERP itself, see best ERP for ecommerce.

Where these integrations break

1. Variants versus matrix items. A Shopify product has up to three options and, per Shopify’s help center, up to 2,048 variants. NetSuite models the same thing as a matrix parent with child items. If the option names, order or SKUs differ between the two, the sync creates orphan items or attaches orders to the wrong child. Fix: decide whether NetSuite or Shopify is the source of products, keep SKUs identical, and map option names explicitly. Bundles and kits need their own rule.

2. Taxes. Shopify calculates tax at checkout. NetSuite may calculate it again with its own tax engine. The two rarely agree to the cent on every order. Fix: choose one calculator. Most teams push Shopify’s tax amount as-is to a tax line or override field, so the order total in NetSuite equals what the customer paid.

3. Discounts. Shopify spreads order-level discounts across lines; NetSuite usually expects a discount item. A mismatch leaves rounding differences on every discounted order. Fix: agree on a discount item or line-level allocation, and test stacked codes and free-shipping discounts.

4. Multiple locations. Shopify locations and NetSuite locations or warehouses are mapped one to one only in simple setups. Fix: define which NetSuite locations feed each Shopify location, whether you push available or on-hand quantity, and how reserved stock is handled.

5. Gift cards. A gift card sale is a liability, not revenue, and a redemption is a payment method, not a discount. Fix: map gift card sales to a liability account and redemptions to a payment line, and check which plan or product includes this.

6. Refunds and returns. Partial refunds, refunds without a return, exchanges and refunded shipping each need a different NetSuite transaction. Fix: decide when a refund becomes a credit memo, a cash refund or a return authorization, and include every case in testing.

7. Payouts and fees. Shopify Payments deposits a net amount after fees, refunds and chargebacks. Without a payout flow, finance reconciles bank deposits by hand. Fix: import payouts as deposits with fees posted to an expense account. Our Stripe NetSuite integration guide covers the same problem for Stripe.

Underneath all of these sit two NetSuite constraints. All web services and RESTlet calls share your account’s concurrency limit, which Oracle sets by service tier plus 10 per SuiteCloud Plus license, so a flash sale needs a queue in front of NetSuite. And from NetSuite 2027.1 no new integrations can use token-based authentication, so any new custom build should use OAuth 2.0, and you should ask any vendor whether their connector already does.

What a custom integration costs

Pick the flows you need; hours include design, QA and project management, and the typical scope is preselected.

The preselected scope, covering products and variants, inventory by location, orders, fulfillments and refunds with alerts and reconciliation, comes to about 410 to 820 hours. 2026 outsourcing rate surveys put Eastern Europe at about $35 to $80 per hour and North America at $80 to $180 or more. At Eastern European rates that is about $14,000 to $65,000; at US onshore rates of $80 to $160 it is about $33,000 to $131,000. Payouts, gift cards and B2B add to it. Compare that with a few years of connector fees plus the cost of the workarounds you would still need, not with the connector fee alone.

How to run the project

1. Export real orders. Pull a few hundred, including refunds, gift card redemptions, stacked discounts, split shipments and international orders.
2. Map products. Variants to matrix items, SKUs, bundles and kits. Fix duplicates and missing SKUs before go-live, not after.
3. Decide tax and totals. Which system calculates tax, how discounts and shipping land, and which account takes rounding.
4. Pick the tool per flow. Many stores run a connector for orders and stock and add a small custom flow for payouts or B2B.
5. Test in a sandbox. Edge cases first, then a volume test that simulates a sale day.
6. Run in parallel and cut over. Compare daily order, refund and payment totals until they match, then switch off manual entry.

If your warehouse is run by a third party, plan that flow separately: see NetSuite 3PL integration.

From related work

We have not published a NetSuite case. The patterns below come from two-way syncs we built for QuickBooks, Amazon and WooCommerce.

For Aspect, a print workshop selling on Amazon, we connected 7 Amazon marketplaces through SP-API, with orders and stock syncing every 15 minutes and personalized orders routed into print jobs. That is the order-intake and inventory half of a store-to-ERP integration. For ProdUp, we refactored bulk product imports into WooCommerce to run as parallel tasks with retries and stored results, and added a dashboard that flags duplicate SKUs and missing data, the same product-catalog hygiene that variant and matrix item mapping depends on.

On the accounting side, our work on One Motion ERP includes a two-way QuickBooks sync with invoice sync, tax logic, duplicates and automatic remapping of item IDs, and our custom ERP system keeps purchase orders and vendor data in sync with QuickBooks. The principles are written up in our guide to two-way QuickBooks sync design.

Where OSKI fits

OSKI is a .NET and React engineering company with a team mostly in Ukraine. We build integrations, e-commerce platforms and ERP systems, and we are happy to build only the flows your connector does not cover. Send the estimator selection and a sample of your orders, and an engineer will reply with a written estimate and its assumptions.