Integration combo
Shopify to NetSuite integration
Shopify is where the orders come in. NetSuite is where the business runs: stock, finance, customers, fulfilment, the lot. Connecting them properly means deciding which side owns each piece of data, then enforcing that decision in every flow that moves between them. We design, build and support Shopify-to-NetSuite integrations as a certified Patchworks Partner Agency. Order capture, customer sync, inventory and pricing publication, fulfilment writeback, refunds and tax. Same team for delivery and ongoing support, with a defined SLA from day one.
Flow shape
Order sync: Shopify to NetSuite
The flow that runs every time a customer checks out on Shopify. Built once in Patchworks, monitored continuously, idempotent end to end.
- Trigger Shopify Order created order/create webhook
- Extract Patchworks Ingest payload queue, dedupe, normalise
- Transform Patchworks Map data line items, taxes, discounts, currency
- Decision Patchworks Customer exists? lookup by email / external ID
- Transform Patchworks Enrich item refs, subsidiary, tax codes
- Action NetSuite Create Sales Order via SuiteTalk / RESTlet
- Writeback Shopify Tag order store NetSuite document number
Illustrative only. The diagram above shows how an integration of this shape works in concept. It is not a screenshot or export of the actual Patchworks process flow; the production flow has more nodes, more branches and more error handling than a marketing page can usefully render.
What we sync
8 synchronisations between Shopify and NetSuite.
Only the data flows that both platforms actually support. Each section below describes what’s in scope, the gotchas we watch for, and how the flow is shaped inside Patchworks.
- 01
Order sync
Shopify NetSuite
Orders raised in Shopify flow into NetSuite on creation, status change and edit. The flow normalises Shopify's order schema into the record shape NetSuite expects, including line-level discounts, taxes, gift cards, shipping methods and multi-currency. Partial cancellations and post-capture edits are handled with idempotent updates so NetSuite stays the system of record without double-counting. Edge cases that come up most often on this pair: backorders, pre-orders, subscription rebills and orders placed through guest checkout with no matching customer record on the destination side.
- 02
Inventory sync
NetSuite Shopify
Stock levels in NetSuite push to Shopify on a schedule, on movement events, or both. The flow handles multi-location and multi-warehouse split, safety stock buffers, in-transit and committed quantities, and channel-specific availability rules. Where Shopify has its own location model we map NetSuite's locations onto it explicitly rather than relying on default behaviour. Throttling protects both sides during bulk recalculations; deltas only during normal operation. The goal is one source of truth for sellable inventory across the estate, with NetSuite retaining authority.
- 03
Product sync
NetSuite Shopify
Product master data syncs from NetSuite to Shopify on publish, with channel-aware enrichment so Shopify only receives the attributes it can act on. Variants, option sets, media, locale-specific copy, category mappings and metafield or extension data are handled explicitly. New SKUs flow in; deprecated SKUs are flagged rather than hard-deleted so historical orders stay intact. Where Shopify has channel-specific requirements that NetSuite does not natively model (typing rules, required attributes, image dimensions), the integration enforces them at the boundary rather than asking the merchandising team to.
- 04
Pricing sync
NetSuite Shopify
Price lists in NetSuite push to Shopify with currency, tax-class and customer-group awareness intact. Promotional pricing, contract pricing and tiered B2B pricing are handled as first-class concepts rather than overrides applied at the storefront. Where NetSuite runs effective-dated pricing, the flow coordinates the cutover so Shopify's catalogue switches at the same instant as the finance side rather than drifting by hours. Currency rounding and display-tax rules are reconciled at the integration boundary to avoid the classic 1p / 1c off-by-one that haunts multi-currency rollouts.
- 05
Customer sync
Shopify NetSuite
Customers created or updated in Shopify flow into NetSuite with a stable cross-system identifier so the same shopper isn't fragmented into duplicates across the estate. Addresses, marketing preferences, B2B account hierarchies, tax exemption flags and channel attribution are mapped explicitly rather than left to NetSuite's defaults. Where NetSuite is the customer system of record (CRM or ERP) we publish back into Shopify so storefront personalisation and segmentation reflect the canonical state. GDPR deletion and rectification are propagated across the integration in both directions.
- 06
Returns sync
Shopify NetSuite
Return authorisations created in Shopify flow into NetSuite with reason codes, inspection state, restocking decisions and refund eligibility carried through. Where NetSuite is the ERP or WMS, the return becomes an inbound record that affects available stock and accounts. Where NetSuite is the storefront, the order record updates so the customer-facing return state stays honest. Exchanges are handled as a paired return-plus-outbound rather than collapsed into a refund-plus-new-order, which keeps the accounting clean and the operational picture accurate.
- 07
Refund sync
NetSuite Shopify
Refund decisions raised in NetSuite push into Shopify as the financial event they are, with original payment method, partial-versus-full handling, tax recalculation and currency intact. The flow waits on inspection outcome where the merchant policy requires it rather than firing on RMA creation. Refunds against gift cards, multi-tender orders and marketplace orders (where the marketplace owns the refund execution) each take a different path; the integration picks the right one based on the original order's tender mix rather than a single default rule.
- 08
Tax sync
NetSuite Shopify
Tax codes, tax classes and jurisdiction rules in NetSuite push to Shopify so the storefront or marketplace charges what finance will actually post. VAT groups, reverse-charge B2B handling, marketplace-of-record tax (where the channel collects on the seller's behalf) and US sales-tax nexus are each modelled explicitly. The integration validates that Shopify's tax calculation matches NetSuite's before publishing a price; mismatches are flagged loudly rather than left to surface at month-end on a VAT return.
Typical delivery
6 to 10 weeks for a standard delivery.
Up to 5× faster using PatchBuddy- Week 1 Discovery: data-model walkthrough, NetSuite record-type choice, edge-case mapping.
- Weeks 2 to 4 Build: order, customer, inventory, fulfilment and refund flows in Patchworks.
- Weeks 5 to 6 Integration testing against real Shopify and NetSuite sandbox data.
- Weeks 7 to 8 UAT with operations and finance teams; sign-off on edge cases.
- Weeks 9 to 10 Cutover and hyper-care; transition into support retainer with monitoring and SLA.
Patchworks delivery
How Patchworks shapes Shopify to NetSuite.
Patchworks ships Blueprints for the canonical Shopify-to-NetSuite patterns: orders, customers, items, inventory and fulfilment events. Our delivery extends those Blueprints where the merchant's NetSuite account diverges from the template: custom record types, OneWorld subsidiary routing, non-standard item types, locked-period handling. We build directly in Patchworks, version flows alongside the merchant's release process, and hand over a runbook the on-call engineer can act on at three in the morning without needing to call us.
Got more connectors that need to live in this flow? A 3PL, a marketplace, returns, a PIM, anything. We can do it. Most live integrations end up larger than a pair, all built and supported as one estate. More on multi-platform estates →
Our Patchworks practiceQuestions
Common questions.
-
01 Do we need NetSuite OneWorld?
No. The integration works with single-instance NetSuite and OneWorld. OneWorld is required where you trade through multiple subsidiaries with separate ledgers; for many UK merchants single-instance is the right call. -
02 How does the integration handle Shopify gift cards?
Gift card sales post to NetSuite as a deferred-revenue line against a liability account; redemptions release the liability against the order they're used on. We don't collapse the two events into a single discount line, because that breaks the VAT trail. -
03 Can we keep Shopify's inventory native, or must NetSuite be the source?
Either pattern is supportable. The right answer depends on where the operational workflow sits. For merchants with multiple sales channels we generally make NetSuite the source of truth, with channel-aware availability rules pushing into Shopify; for single-channel Shopify merchants the inverse is sometimes simpler. -
04 What about Shopify Plus checkout extensibility?
Supported. Custom checkout fields land on the order payload and map into NetSuite custom transaction fields. We define the mapping at scoping so finance and operations both know what's where. -
05 Do you support Shopify-to-NetSuite under SLA after go-live?
Yes. The same team that builds the integration runs it under retainer. Monitoring on every shipped flow, on-call cover, monthly health checks and tiered response SLAs from £750/month.
Get in touch
Tell us what you’re trying to connect.
And what’s in the way. We will tell you whether we are the right people to do it. Drop us a line below, or open the chat in the corner of the screen.
Direct: contact@ecirql.com
Message sent
Thanks. We’ll be in touch.
Your message is in our inbox. A human will read it and reply within a working day. For anything urgent, drop us a line at contact@ecirql.com or open the chat in the corner of the screen.