You can connect NetSuite to Shopify three ways: Oracle's own NetSuite Connector, an iPaaS such as Celigo, or a custom integration built against NetSuite's APIs. NetSuite Connector suits fairly simple setups. Celigo covers standard flows quickly, for a recurring subscription. A custom build earns its cost when you run several subsidiaries, B2B pricing or rules neither of the others can express. But the tool is the smaller decision. The ones that shape the project are NetSuite-specific: how orders are recorded, how subsidiaries are routed, and how price levels map to Shopify markets.
Option 1: NetSuite Connector
Oracle acquired the connector vendor FarApp in 2021, and its Shopify connector now ships as NetSuite Connector. It's listed on the Shopify App Store as NetSuite ERP Connector, with support provided by Oracle NetSuite, and you add it to your account through your NetSuite account manager rather than installing it yourself.
Its strength is that it's the vendor's own and covers the standard flows. Its limits show up with customisation: the consistent view from merchants who've used it is that it works well when the integration between the two systems is fairly simple. If your setup is one subsidiary, one currency and standard fulfilment, start by asking your account manager what it would cost.
Option 2: Celigo
Celigo is the best-known integration platform for NetSuite and Shopify. Its App Store listing describes syncing customers, items, orders, cancellations, refunds and returns, B2B companies and catalogues, inventory from warehouses including kits, products with variations, and multiple Shopify stores into one NetSuite account. That's broad coverage, and the flows are configurable rather than coded.
The listing shows a 30-day free trial and then a starting package at $7,800 a year, with a limit on endpoints; more endpoints and flows cost more. For a business with standard processes that wants to be live quickly, that's often good value. It's worth revisiting when most of what you're paying for is custom logic hosted on the platform, or when each new store and market adds to the bill.
Option 3: a custom integration
A custom integration is a dedicated service between NetSuite's APIs and Shopify's, with your rules written into it. It costs more up front than either option above and nothing recurring beyond hosting and maintenance. It's the right call when the logic is the point: stock exposed as available-to-sell after commitments and a safety buffer, orders routed to subsidiaries by rules that change by market, B2B customers with their own price levels and terms, or several stores behaving differently against one NetSuite account.
The decisions that matter more than the tool
Sales Order or Cash Sale
Every Shopify order has to become a NetSuite transaction, and the type you choose changes everything downstream. A Sales Order suits businesses that pick, pack and ship through NetSuite: the Item Fulfillment and the invoice hang off the order, and the tracking number flows back to Shopify from the fulfilment. A Cash Sale suits orders that are paid and complete at the point of sale. Pick deliberately, because it decides how fulfilment, returns and revenue reporting work for every order afterwards.
Subsidiaries and currencies
NetSuite OneWorld businesses run several subsidiaries, each with its own currency, tax rules and books. Shopify might be one store per market or one store using Shopify Markets. Either way, every order needs an explicit rule deciding which subsidiary it belongs to - usually the shipping country or the Shopify market it was placed in. Get the rule wrong and an order lands in the wrong set of books, which is far harder to unwind than a sync error.
Price levels and Shopify Markets
NetSuite expresses pricing as Price Levels, optionally per currency. Shopify expresses it per market and, on Shopify Plus, through B2B catalogues. Mapping one to the other is a design decision: which price level feeds which market, whether Shopify converts currency or receives a fixed price for it, and which B2B customers see which catalogue.
Matrix Items and variants
NetSuite models a product with sizes and colours as a Matrix Item - a parent item with child items for each combination. Shopify models it as a product with variants. The SKU of each child item should match the SKU of the corresponding Shopify variant, and that match is what keeps stock and orders aligned. Shopify allows up to three options per product, so any Matrix Item with more option dimensions than that needs restructuring first.
How the connection works technically
- SuiteTalk REST web services are the primary interface for reading and writing NetSuite records.
- RESTlets, written in SuiteScript, cover cases the standard endpoints don't, such as custom record logic.
- Token-based authentication with a dedicated integration role keeps access scoped and auditable.
- Shopify webhooks deliver orders the moment they're placed; stock and prices sync on a short interval.
- A queue between the two means a NetSuite outage delays an order rather than losing it.
Whichever option you choose, ask how a failed order is surfaced and replayed. An integration that fails quietly is worse than none at all, because you find out from the customer.
Choosing between them
Start by writing down your flows - what moves, which way, how often - and your subsidiary and market rules. Take that list to your NetSuite account manager for NetSuite Connector and to Celigo for a quote. If both cover it cleanly, the decision is cost and convenience. If either needs workarounds for the rules that make your business work, that's the signal a custom integration will be cheaper over the life of the store.
Want this applied to your store?
Work with the Byteex team
We help Shopify DTC brands turn more visitors into buyers. See how we can help you below, or browse real client results.
