Shopify NetSuite integration

What moves between Shopify and NetSuite

Shopify is where the order is captured. NetSuite is where it is fulfilled, billed and booked. An integration between the two carries eleven kinds of record, most of them in one direction.

Shopify to NetSuite

• Orders, as a Sales Order, a Cash Sale or an Invoice
• Customers, with billing and shipping address
• Payment transactions, as a Customer Deposit against the sales order
• Refunds, as a Credit Memo, Cash Refund or Customer Refund
• Return requests, as a Return Authorization
• Cancellations, which close the sales order
• Shopify Payments payouts, as a bank deposit that finance can reconcile

NetSuite to Shopify

• Items and matrix items, as products and variants
• Item fields, as metafields
• Stock per location, as inventory levels per Shopify location
• Item Fulfillments, as Shopify fulfillments with carrier and tracking number

The record type decides the rest of the flow. A Cash Sale records sale and payment in one transaction and takes the stock down at once, with no Item Fulfillment. That fits Shopify POS and digital goods. A Sales Order waits for a warehouse.

For B2B, Shopify companies map to NetSuite customers, company locations to subcustomers, and catalogs to price levels. Both systems have the same limit here: a Shopify company holds at most 10,000 locations, and a NetSuite customer hierarchy holds at most 10,000 customers and subcustomers.

Which system owns what

Each piece of data has one owner. Without that rule the two systems overwrite each other and nobody can say which value is right.

What Shopify and NetSuite store differently

Variants against matrix items. A Shopify product has up to three options and up to 2,048 variants. A NetSuite matrix has a parent item and child items, at most 2,000 combinations, and only the children appear on transactions. The link between the two is an item ID map: one row per Shopify variant ID and NetSuite internal ID. Shopify does not require a SKU to be unique, or to be filled at all. A variant without a row in the map makes its order line fail in NetSuite, which is why we check the map before every order write. More on this in variant mapping.

Discounts. A Shopify discount code is a string on the order. NetSuite needs a discount item to book it against. An order of two shirts at 40.00 with code FALL10 comes in as 80.00 minus 8.00. Without a discount item for FALL10, or a general web discount item, NetSuite cannot resolve the line and rejects the whole order.

Tax. Shopify calculates tax at checkout, per line. NetSuite recalculates tax on the sales order unless it is told to take the store's amount. Two calculations that round differently disagree by a cent on a share of orders, which blocks automatic matching of deposit and invoice. The mapping sets one side as the source: the Shopify amount written per line, or NetSuite's own calculation.

Subsidiary, location, department, class. Shopify has none of these. NetSuite wants them on the header and often on every line. They come from rules: the store decides the subsidiary, the Shopify location decides the NetSuite location, the sales channel decides the class.

Custom fields. Item data that Shopify has no field for goes into metafields. NetSuite holds it in fields such as custitem_material or custitem14. An app can define 256 metafields per resource type, and metafieldsSet writes 25 per request.

Stock states. Shopify has eight inventory states, among them available, committed, reserved and safety_stock. The API accepts writes to available and on_hand only. NetSuite has On Hand, Committed, Available and Back Ordered per location. We send NetSuite's Available, minus any buffer you set, and let Shopify keep its own committed. Which locations count is a decision per location, covered in multi-location inventory.

The technical reality of this pair

Both systems meter their APIs, in different units.

Stock, worked through. A catalog of 12,000 variants across two locations is 24,000 quantities. Reading them from NetSuite with SuiteQL takes 24 pages of 1,000 rows in one concurrency slot. Writing them to Shopify with inventorySetQuantities takes 24,000 divided by 250, which is 96 mutations. Sent one item at a time the same update is 24,000 calls, and on a standard plan that runs into THROTTLED long before it finishes. We send only the quantities that changed since the last run, so a normal cycle is a handful of calls.

Since API version 2026-04 every inventory write carries changeFromQuantity: the quantity the integration believes Shopify has. When Shopify's number has moved in the meantime, the call fails with CHANGE_FROM_QUANTITY_STALE and the integration reads again before it writes. A sale that happened during the sync is not overwritten.

Orders, worked through. NetSuite is the slower side. A sales order save that triggers user event scripts and workflows takes several seconds. At 4 seconds per order and 2 of the 5 slots on a Standard account, the maximum is 30 orders a minute, or 1,800 an hour. The other 3 slots stay free for your 3PL, your reporting and your users' own scripts. The full calculation is in NetSuite concurrency limits.

Webhooks. Shopify waits five seconds for an answer to a webhook, retries 8 times over 4 hours, and then deletes a subscription that was made through the Admin API. It guarantees neither order nor a single delivery. So the webhook only puts the order ID in a queue and answers 200. A reconciliation run then compares Shopify's recent orders with the external IDs in NetSuite and picks up anything the webhooks missed. Without the read_all_orders scope an app sees the last 60 days of orders, which bounds how far back that run can look. The Shopify API rate limits note covers the cost model in detail.

Authentication. NetSuite access runs under a dedicated role, not Administrator. Oracle points new integrations to OAuth 2.0 and stops new token-based integrations with release 2027.1. A sandbox refresh deletes the sandbox tokens. Details are on the NetSuite page; the Shopify side is on the Shopify page.

Where standard connectors stop

Standard connectors and iPaaS templates cover the common case with fixed settings. Their own documentation shows where the settings stop.

• One price level. A typical template takes one NetSuite price level for the selling price and one for the compare-at price, in one currency per store. A third price level, or a price per customer, needs custom saved-search formulas and a script.
• B2B in a separate template. Company-specific catalogs run as a second set of flows next to the consumer flows, with a filter to keep B2B orders out of the first set.
• Locations are mapped, not allocated. NetSuite locations map to Shopify locations one to one or many to one. There is no rule for priority, splitting or a reserve per channel. An item without a map record is skipped without an error.
• Saved searches by internal ID. One widely used template installs 30 saved searches in NetSuite and refers to them by internal ID. Renaming or deleting one breaks every flow that uses it.
• Scheduled, with a lag. Order flows run on a schedule with a recommended lag of 10 to 15 minutes, so that the payment status has settled before the order is picked up.

A built integration has no fixed settings. Price levels, catalogs, allocation rules and timing follow how your account works. The comparison on technical grounds is in custom integration vs iPaaS.

When it goes wrong

An order that still fails after its retries goes to a separate list with its original payload, so it can be sent again after the cause is fixed. Nothing is dropped without a trace. After a pause, the first run starts from the last order it confirmed, not from the clock: a sync that resumes from the wrong timestamp is the usual cause of missing records after a maintenance window.

Before go-live the integration runs as a dry run against your NetSuite sandbox and your live Shopify data, writing nothing, and you approve what it would do. From then on every run has a diff per record in the dashboard. This is part of every e-commerce ERP integration we build. Sibling pages: Magento NetSuite integration, WooCommerce NetSuite integration and BigCommerce NetSuite integration. Tell us how your NetSuite account is set up.