NetSuite > Shopify - sync locations

Introduction

The NetSuite > Shopify - sync locations flow retrieves all locations from NetSuite, then runs a script to check if they exist in Shopify. New locations are created (via the first branch), and address details for existing locations are updated (via the second branch).

This blueprint includes two process flows to handle the sync of locations between Shopify and NetSuite - you only need to run ONE, depending on which way you want the sync to work:

• Shopify > NetSuite - sync locations

• NetSuite > Shopify - sync locations (this flow)

Process flow snapshot

Click to view process flow snapshot

Limitations

Limitation	Summary
Shopify GraphQL error handling	There is a known limitation with error handling for Shopify GraphQL. Please refer to the Error handling for Shopify GraphQL section for more information and a suggested approach that you may wish to adopt in your flows.

Assumptions

No assumptions to note.

Customisation

To ensure that this process flow runs as required, some customisation options are available. These are documented in the following sections:

• Flow variables

• Process shape shapes

Flow variables

This process flow does not use flow variables.

Process flow shapes

This process flow includes some shapes that can be configured with your own settings. Please see guidelines in the table below.

Shape settings determine the outcome of process flows. Do not change shape settings unless they are listed below.

Shape	Notes
Trigger	No default schedule is defined. If you decide that you want to sync locations in this direction (rather than from Shopify to NetSuite), you may decide to add a schedule.
Notify	This flow is designed in a try/catch structure, so notifications are generated if any part of the flow fails. To achieve this, the catch route includes a notify shape, which must be configured for your own notification preferences. Alert level: Defaults to error but can be changed if needed Channel: Defaults to email + log but can be changed if needed Email Limit: Defaults to 5 but can be changed if needed Notification Group: Replace the notify placeholder which your required notification group. Message: If required, you can change the placeholder message. For more information, please refer to our Notify shape and Notification groups pages.
Connector (NetSuite)	If you did not add or select a NetSuite instance during the blueprint installation process, the following settings must be configured: Source instance : Set to your required NetSuite instance. Source endpoint : Set to POST suiteQL Query: Leave as the default
Connector (Shopify)	If you did not add or select a Shopify instance during the blueprint installation process, the following settings must be configured: Source instance : Set to your required Shopify instance. Source endpoint : Set to POST Get all locations via graphql
Connector (Shopify) Route: New location	If you did not add or select a Shopify instance during the blueprint installation process, the following settings must be configured: Source instance : Set to your required Shopify instance. Source endpoint : Set to POST Add location via graphql
Connector (Shopify) Route: Update location	If you did not add or select a Shopify instance during the blueprint installation process, the following settings must be configured: Source instance : Set to your required Shopify instance. Source endpoint : Set to POST Upate location via graphql

Reference

Reference information for this process flow is documented in the following sections:

• Scripts used in this process flow

• Cross-reference lookups used in this process flow

Scripts in this process flow

Script	Summary
NS to Shopify - determine new and updated locations	Compares shopify and netsuite locations and outputs graphQL payloads for those that are new and those that are to be updated. No mappings are required - these payloads are consumed directly.

Cross-reference lookups in this process flow

No cross-reference lookups to note.