Shopify NetSuite Integration
Bi-directional Shopify ↔ NetSuite ERP integration built by senior engineers — orders down to NetSuite, inventory and fulfilment back to Shopify, idempotent and reconcilable, and architected around NetSuite's governance limits so it survives a Black Friday spike.
Our NetSuite integration process
- Map the records. We document the field-level mapping between Shopify and NetSuite record types — Sales Order, Customer, Inventory Item, Item Fulfilment — including subsidiaries, tax, and custom fields. Undocumented custom fields in NetSuite are where ERP integration timelines actually slip, so we surface them first.
- Build the connector. Custom middleware over SuiteTalk REST web services or RESTlets, authenticated with Token-Based Authentication (TBA). Shopify webhooks push orders to NetSuite Sales Orders; a delta job reads NetSuite inventory and fulfilment back to Shopify. Built queue-first so it respects NetSuite's concurrency governance instead of hitting limits.
- Reconcile + test. Saved-search-driven delta sync, real-order replay, and a reconciliation pass that diffs Shopify against NetSuite across orders, inventory, and fulfilment status — covering the edge cases connectors miss: partial fulfilments, multi-location stock, refunds, and tax lines.
- Monitor + support. Dead-letter queue, alerting on failed syncs and governance throttling, and a scoped support window agreed in writing. An ERP sync that silently stops is a month-end-close disaster — we instrument so failures surface in hours, not at reconciliation.
What's included
- Shopify orders → NetSuite Sales Orders in real time, with customer, tax, discount, and line-item mapping (including subsidiary assignment for OneWorld accounts)
- NetSuite inventory → Shopify, multi-location aware via getItemAvailability, so storefront stock reflects the ERP source of truth
- NetSuite Item Fulfilment → Shopify fulfilment and tracking writeback, so customers get accurate shipping notifications
- Customer and item/product master-data sync in the direction that matches your source of truth
- Token-Based Authentication (TBA) over SuiteTalk REST or RESTlets — no stored passwords, concurrency-governance aware
- Idempotency and reconciliation — external-ID mapping stops duplicate Sales Orders, and a scheduled diff keeps Shopify and NetSuite in agreement
Integration timeline
Typically 4-10 weeks
A one-directional order push (Shopify → NetSuite Sales Orders) is the fast end — 3-5 weeks. Full bi-directional with multi-location inventory, fulfilment writeback, OneWorld subsidiaries, and B2B price lists is 6-12 weeks. We confirm a window in writing once the record-mapping scan surfaces the real shape — the cost driver is the number of custom fields and the cleanliness of the NetSuite instance, not the Shopify side.
FAQ
- How does Shopify connect to NetSuite?
- Through NetSuite's SuiteTalk web services — the modern path is the REST web services API, with RESTlets (custom SuiteScript endpoints) for anything the standard records don't cover. Both authenticate with Token-Based Authentication (TBA), so no passwords are stored. In practice Shopify webhooks push new orders into NetSuite as Sales Orders, and a scheduled delta job reads inventory levels and Item Fulfilment records back out to Shopify.
- Do I need a connector app like Celigo or FarApp, or a custom integration?
- iPaaS connectors (Celigo, FarApp/Shopify's NetSuite Connector) are a genuinely good fit when your data maps cleanly to NetSuite's standard records, and we'll tell you when that's the case rather than bill you for custom work. Custom is the honest answer when you have bespoke custom fields, multiple subsidiaries (OneWorld), B2B price lists, non-standard fulfilment flows, or governance pressure the connector's sync schedule can't handle. We scope both and recommend the option that actually fits.
- What syncs between Shopify and NetSuite, and in which direction?
- Typically: orders flow down from Shopify to NetSuite Sales Orders; inventory and Item Fulfilment (with tracking) flow up from NetSuite to Shopify; and customer and item master data syncs in whichever direction matches your source of truth. We confirm the directionality per object during mapping — getting "who owns inventory" right is the single most important decision in an ERP integration.
- How do you handle NetSuite's governance and API limits?
- NetSuite enforces concurrency governance and per-request usage limits, and naïvely hammering the API is how connectors get throttled during peak. We build queue-first: events drain in order at a rate the account's concurrency governance allows, TBA + RESTlets give higher concurrency headroom than user-credential calls, and bulk operations use list batches sized to NetSuite's guidance (around 20 transactions per list). A traffic spike fills the queue and drains safely rather than failing.
- Can it handle multi-location inventory?
- Yes. We read availability per location from NetSuite (via getItemAvailability) and map each NetSuite location to the corresponding Shopify location, so multi-warehouse stock stays accurate on the storefront. Without that mapping, multi-location merchants oversell — the storefront shows total stock while fulfilment can only ship from one site.
- How do you stop duplicate Sales Orders in NetSuite?
- Each Shopify order is mapped to NetSuite with an external ID, so a webhook Shopify retries — which it routinely does — updates the existing Sales Order rather than creating a duplicate. We pair that with a saved-search reconciliation that diffs Shopify orders against NetSuite Sales Orders on a schedule, so any drift is caught and corrected long before month-end close.
- How much does a Shopify NetSuite integration cost?
- A one-directional order push is typically £12K-£25K. Full bi-directional with multi-location inventory, fulfilment writeback, and OneWorld subsidiaries usually runs £25K-£60K. We share firm pricing in writing after the record-mapping scan — the variable is the number of custom fields and how clean the NetSuite instance is, which we can only assess by looking at it.