What is changing?
Prior to the Multi-Location feature, Shopify didn’t allow its users to add multiple locations for stocking inventory, fulfilling orders, and selling products. Everything was recorded in one location.
Inventory is currently set and adjusted on the product variant and is not tracked by any specific location. In anticipation of multi-location inventory being available in the Shopify admin, Shopify is releasing a new Inventory API, which includes three resources: InventoryItem, InventoryLevel, and Location. The Inventory API allows apps to retrieve, set, and update Shopify store inventory levels across multiple locations. Additionally, it allows apps to specify the location where they are fulfilling orders or restocking items.
By August 1, 2018, Shopify is going to mandate adding a location_id when creating fulfillments. location_id is the unique identifier of the location tied to the fulfillment. When creating a fulfillment, you are required to specify the location from which an item is fulfilled using location_id. As Shopify moves towards expanding its multi-location inventory capabilities, fulfillment apps will need to specify the location from which they are fulfilling orders to continue to work on stores that track inventory across multiple locations.
For more details on Shopify's API changes for the Multi-Location Inventory feature, please see here: https://help.shopify.com/en/api/guides/inventory-migration-guide
New setting in the connector
In preparation of Shopify’s upcoming Multi-location inventory feature, a new setting has been introduced in the General section of the Connector settings page as displayed in the following image:
The Map NetSuite locations with Shopify locations setting allows you to map NetSuite locations to corresponding Shopify locations. You can choose to map locations as 1:1 or many:1 (i.e. map a group of NetSuite locations to a single Shopify location).
In the case you only have a single location setup in Shopify and all your NetSuite locations map to that location, you are only required to provide the Shopify location in the Default Lookup Value drop-down field.
Note: The following UI elements are not applicable for this feature. It’s recommended you do not use any of the following elements while using Default Lookup Value :
- Fail If Unique Match Not Found
- Use Null as Default Value
- Use Empty String as Default Value
All the required changes to support this functionality have been packaged in the bundle that will be added to your connector as part of this release. To enable this feature, you are required to make the following manual changes:
- For users having only one location setup in Shopify account
If you do not wish to use the multi-location feature in Shopify and want to use a single location for fulfilling all items then all you are required to do is to verify if the location is being displayed in the Default Lookup Value drop-down list is the default location you wish to use.
Note: A location is pre-populated by the connector but If the location is not set as per your expectation, click the refresh button and select the appropriate location. Contact our support team to know if the desired location is not being displayed in the Default Lookup Value drop-down list.
- For users using the multiple -locations in Shopify
Use the 2-column table to provide locations between NetSuite and Shopify. You can choose to map locations as 1:1 or many:1.
You are also required to verify that the following changes exist in the Celigo Shopify Inventory Export saved search with in your NetSuite account:
- Remove Group or Sum value from the Summary Type You must ensure that the Summary Type column does not have any value selected in all the rows as displayed in the following image.
- Add a new row and in the Field column add Inventory Location: Internal Id as the value and in the Custom Label column add location_id as the value.
If these changes do not exist in the saved search, you are required to manually edit the Celigo Shopify Inventory Export saved search with in your NetSuite account and add these changes. Two major changes in the saved search are: the inclusion of location_id parameter and removal of grouping logic that existed in connector prior to this release.