NetSuite Shopify Integration: What to Set Up Before You Go Live (Checklist)

A Shopify-NetSuite integration that is not set up correctly does not fail loudly. It fails quietly: orders that are not creating NetSuite records, inventory counts that are off by three days, customer records that are duplicating. By the time you notice the problem, it has been running for weeks.

This checklist covers what to get right before you go live. Not after.

Before you map a single field

Define what “source of truth” means for each data type.

Is NetSuite the master for inventory, or is Shopify? If a product exists in both systems, which one wins when there is a conflict? There is no universally correct answer — it depends on your operations — but you need a documented decision before the integration is configured. Undefined data ownership is the most common root cause of integration problems. 99% of our implementations NetSuite is the source of truth for Products, product info, pricing and stock. If you already have product images in NetSuite, you can source them to Shopify, if not you can consider hosting them in Shopify or elsewhere in order to save space on the file cabinet. 

Document your product structure in NetSuite.

How are your products organized in NetSuite? Are you using matrix items? Kit items? Lot-controlled inventory? Drop-ship items from vendors? Each structure requires different handling in the integration. An agency that does not ask these questions before scoping the project is making assumptions you will pay for later.

Understand your subsidiary and location setup.

If you have multiple NetSuite subsidiaries, which one does Shopify order revenue post to? If you have multiple warehouse locations, which one does Shopify inventory pull from? These decisions affect tax calculations, financial reporting, and fulfillment routing.

Data mapping checklist

Work through these fields before integration configuration begins. For each one, confirm the source system, the destination field in NetSuite, and what happens when the source value is null or unexpected.

Orders:

• Order source tagging (how do you identify Shopify orders in NetSuite?)
• Customer mapping (new customer creation logic, duplicate detection)
• Shipping address mapping to NetSuite shipping fields
• Tax calculation (Shopify-calculated tax vs NetSuite tax engine)
• Payment method mapping to NetSuite payment methods
• Discount and promotion handling. Usually handling them as a separate line item.
• Gift card handling (if applicable)
• Order status mapping between platforms

Products and inventory:

• Item ID matching logic between Shopify SKUs and NetSuite item records
• Inventory location mapping
• Real-time vs scheduled inventory sync (and why you should prefer real-time)
• Matrix item and variant handling
• Out-of-stock behavior — does Shopify allow oversell, or does the integration enforce availability?

Customers:

• Duplicate customer detection (email-based vs name-based)
• B2B customer account mapping (for Shopify Plus B2B merchants)
• Customer class and category assignment in NetSuite
• Communication opt-in status handling

Fulfillment:

• Which system triggers fulfillment? (NetSuite WMS, 3PL, Shopify Fulfillment Network?)
• Tracking number push-back from NetSuite to Shopify
• Partial fulfillment handling
• Returns and refunds flow

Testing checklist

Never go live on a Shopify-NetSuite integration without end-to-end testing in a sandbox environment.

Order flow testing:

• Place a standard order — confirm it creates correctly in NetSuite with all expected fields
• Place an order with a discount code — confirm discount applies correctly in NetSuite
• Place an order with multiple line items including a kit item — confirm kit components handle correctly
• Place an order that triggers a fraud flag — confirm the flag surfaces in NetSuite
• Place a duplicate order — confirm duplicate detection fires
• Process a full refund — confirm NetSuite credit memo creates correctly
• Process a partial refund — confirm line-level credit handling

Inventory testing:

• Update inventory in NetSuite for a product — confirm Shopify reflects the change within expected sync time
• Reduce inventory to zero — confirm Shopify marks the product as out of stock or back order.
• Receive inventory in NetSuite — confirm Shopify updates

Customer testing:

• New customer order — confirm customer creates in NetSuite without duplication
• Returning customer order — confirm existing NetSuite record is matched, not duplicated

Go-live risk mitigation

Start with a limited launch window. If possible, go live during a low-traffic period. Your first live orders through the integration will reveal anything the sandbox testing did not catch. Having fewer orders in flight when you discover an issue is significantly easier to remediate.

Have manual fallback procedures documented. If the integration fails on day one, how does your operations team process orders manually while the issue is resolved? Document this before go-live, not during an incident.

Set up monitoring and alerting. The integration should have error alerting configured so that a failed order sync sends a notification immediately, not after a customer emails to ask where their order is.

Monitor for URL and server errors in Google Search Console. If your Shopify storefront underwent any structural changes as part of the integration project – URL restructuring, product page consolidation, or catalog reorganization – make sure 301 redirects are in place before go-live so search equity is preserved and customers are not landing on dead pages. After launch, keep an eye on Google Search Console for any spike in 404 (page not found) or 500-level (server error) response codes. These can surface quickly when integration activity affects page rendering or product availability, and catching them early prevents both ranking loss and a degraded customer experience. 

Agree on a cutover plan with your agency. Who is on call for the first 48 hours after go-live? What is the escalation process if a critical issue is found? This should be agreed in writing before launch day.

Getting the pre-launch work right takes more time upfront. It saves considerably more time on the back end.

[Talk to Tavano Team about your Shopify-NetSuite integration project]

Related: Shopify NetSuite Integration: Services and Connector | Shopify NetSuite Connector vs Celigo vs Custom