Connect Shopify to NetSuite

The store runs in Shopify, the business runs in NetSuite, and between them sits a person exporting orders to a CSV each morning, or a rigid connector that drops an order when a SKU is missing. Order volume grows and the gap turns into backlog and mis-shipments.

• Paid orders become NetSuite sales orders as each webhook arrives, so fulfillment and invoicing start the same day
• Shoppers are matched to customers on email and an external ID, and a missing item holds the order for review instead of dropping it
• High-risk orders, flagged by Shopify's fraud analysis, wait for a person before they ever reach finance
• Fulfillment, tracking, and inventory levels flow back, so the storefront shows the truth and support stops guessing

The order-to-cash flow most stores turn on first.

Paid Shopify order to a NetSuite Sales Order, with a fraud hold and a SKU guard

Started when an order is paid, with two branches that keep bad data out of NetSuite.

1. 1
   Trigger: a Webhook trigger with Auto Register With Shopify for orders/paid, carrying the order, line items, customer, and addresses.
2. 2
   Risk check: read the order's risks. If the recommendation is cancel or investigate, a Wait for form step sends a reviewer the order link, and the flow continues only when they release it.
3. 3
   Resolve customer: NetSuite Upsert by external id on Customer, keyed on externalId = shopify_customer_id, from the mapping below.
4. 4
   Resolve items: for each line, match NetSuite Item by line.sku → itemId. If any SKU does not match, send the whole order to a reviewer rather than creating a partial order.
5. 5
   Write order: NetSuite Upsert by external id on SalesOrder, keyed on externalId = shopify_order_id, adding a shipping line and a discount line from the order totals.
6. 6
   Write back: write the NetSuite internal ID to a Shopify order metafield custom.netsuite_so_id.
7. 7
   Ongoing: a second flow polls NetSuite item fulfillments with the Record Created or Changed trigger and creates the Shopify fulfillment with the tracking number, and a scheduled flow pushes inventory levels from NetSuite to the Shopify location.

The starting map for the Shopify order to NetSuite Sales Order step.

• Orders and customers. Paid orders become sales orders. New shoppers become customers. Refunds create credit memos against the original order. (Shopify to NetSuite)
• Fulfillment and tracking. An item fulfillment in NetSuite creates the Shopify fulfillment with the carrier and tracking number, which notifies the shopper. (NetSuite to Shopify)
• Inventory levels. Available quantity per item is pushed to the matching Shopify location on a schedule, so the storefront does not oversell. (NetSuite to Shopify)
• Products and pricing. New items and price changes keep the Shopify catalog and the NetSuite item list aligned, with one system set as the source of truth. (Either direction)

The same controls apply to this sync as to every other Neblex workload.

• Run history. Every order is a run with the payload, the customer and item resolution, and the sales order it wrote. A failed run can be replayed from the step that failed, and the upserts stop a second order.
• Approval and holds. High-risk orders and orders with unmapped SKUs go to a reviewer as Wait for form tasks. A person releases or rejects each one.
• Scoped access. Shopify uses an admin API token with only the order and inventory scopes. NetSuite uses a role limited to sales orders, customers, and items.
• Environments. Build against a Shopify development store and a NetSuite sandbox, then promote the same flow to production.