Articles in this section

Run generic flows in Shopify – NetSuite D2C template

Before enabling any transactional flows, you must run the three generic (setup) flows. These flows create foundational records in NetSuite that all order, billing, refund, payout, and other flows depend on. If these records do not exist, transactional flows will fail to locate the required custom records during processing.

Important

Run setup flows first. Do not enable any transactional flow until all three setup flows have been run successfully and the corresponding records have been verified in NetSuite.

Overview

Flow

What it creates in NetSuite

When to re-run

Shopify store to NetSuite custom record (add)

Celigo Shopify Store custom record: the anchor record for all flows

If store configuration changes

Shopify markets to NetSuite (add)

Shopify Market records in NetSuite: required for multi-market and multi-currency support

When new markets are added in Shopify

Shopify business entity to NetSuite (add)

Business entity records for Shopify Payments accounts: required for payout flows

If Shopify Payments configuration changes

Flow 1: Shopify store to NetSuite custom record (add)

This flow uses the Shopify GraphQL shop { name, id } query to retrieve your store's name and ID and creates a Celigo Shopify Store custom record in NetSuite. This record stores store-level metadata and is referenced by all other flows during processing.

How to run

  1. In integrator.io, open the Shopify – NetSuite D2C template integration tile.

  2. Navigate to FlowsGeneric and locate the Shopify store to NetSuite custom record (add) flow.

  3. Enable the flow using the On/Off toggle.

  4. Click Run.

  5. Wait for the flow to complete. Verify no errors appear in the flow run dashboard.

  6. In NetSuite, go to Customization > Lists, Records & Fields > Custom Records and confirm the Celigo Shopify Store record was created.

Flow 2: Shopify markets to NetSuite (add)

This flow uses the Shopify GraphQL markets query to retrieve all active Shopify market definitions (including region conditions, currency codes, and catalog assignments) and creates corresponding records in NetSuite. These records are used together with the Markets and Subsidiaries mapping in integration settings to route orders to the correct NetSuite subsidiary and default customer based on the Shopify market.

How to run

  1. Locate the Shopify markets to NetSuite (add) flow in the integration tile.

  2. Enable and click Run.

  3. After the run completes, open the template tile > Settings and configure the Markets and Subsidiaries mapping to link each Shopify market to the correct NetSuite subsidiary, default customer, tax code, and currency code.

    Note

    Re-run this flow whenever you add a new market in Shopify. After re-running, update the Markets and Subsidiaries mapping in Settings to add the new market.

Flow 3: Shopify business entity to NetSuite (add)

The flow syncs the Shopify business entity (store-level record) into NetSuite. 

The flow uses the Shopify GraphQL businessEntities { id, companyName, shopifyPaymentsAccount { id } } query to retrieve business entity information related to your Shopify Payments account. The resulting NetSuite records are used by all three payout flows to identify the correct Shopify Payments account when reconciling transactions.

How to run

  1. Locate the Shopify business entity to NetSuite (add) flow.

  2. Enable and click Run.

  3. Verify the flow completed without errors before proceeding to enable payout flows.

    Note

    This flow is only required if your store uses Shopify Payments. If you use a third-party payment gateway and do not use the payout flows, you can skip this flow.

After running setup flows

Once all three setup flows have been run successfully, proceed with the following steps:

  1. Run the Shopify products to item ID map flowto establish item linkages before enabling order or inventory flows.

  2. Enable the Shopify customer to NetSuite customer flow and run it once to pre-populate customer records.

  3. Enable the remaining flows step by step, verifying each flow before proceeding. For the recommended order, see Flow scheduling and dependency guide.