Shopify and NetSuite: align locations, orders and refunds

Shopify and NetSuite should be able to recognise the same order throughout its life. Partial fulfilment, multiple locations and later refunds make that relationship a central integration task.
Separate access from data mapping
Oracle documents connecting Shopify through NetSuite Connector. Whether that connector or another solution fits depends on the required scope and installed environment.
Successful authorisation establishes access. Next, check item, variant, customer and location relationships. SKUs must be unambiguous, and changes from the owning system must reach the correct destination.
Map multiple locations deliberately
Agree which NetSuite locations supply Shopify inventory and what quantity may be sold online. Establish where returned stock is received. With several stores, each mapping needs a defined scope.
Oracle's connector management documentation treats inventory mapping, multiple locations, POS and refunds as distinct topics. Use the same separation in your acceptance plan.
Follow a purchase through correction
Take an order containing a discount and shipping. Check customer matching, amounts and references. Split the fulfilment and refund part of the order afterwards. Compare the state in both systems after each step.
If POS is used, add an in-store sale and return. A successful online order test does not automatically cover retail operations.
Hand over failure handling
Define where rejected transfers appear and who corrects them. A retry must not create duplicates. Record how staff resolve conflicting values.
The integration guide provides a shared data outline. During a Shopify migration, also agree when the previous connection will stop.