Order routing for eCommerce integrations
When a customer places an order, Cin7 Core can automatically route the order to the seller's inventory location nearest to the provided shipping address for fulfillment. Cin7 Core provides an order routing setting that facilitates this process. Based on this setting, the location in the sales task header will be pre-filled with the order routing location, although this can be manually changed on the order if necessary. This feature simplifies the sales order process.
Note: Order routing is available only for eCommerce sales such as Amazon, eBay, Etsy, WooCommerce, Handshake, Magento, ShipStation, and Shopify regular sales. It is NOT available for Shopify POS sales channels.
Prerequisites
Integration between your online store and Cin7 Core has been set up with at least one eCommerce channel.
Set up Locations and bins for your store.
Users will need the Sale: Order routing permission in order to use this feature. Users will also need the relevant integration permission from the Integration permissions.
Setting up order routing
Users can enable and configure order routing from General Settings → Reference Books. When enabled, you can specify which inventory locations are used to source products for orders made from different geographical locations.
Navigate to Settings → Reference books → Order Routing.
Click On to turn on order routing.
Keep routing if you want Cin7 Core to keep the order routing even if an item is out of stock. If keep routing is disabled, Cin7 Core will automatically route a sale order to the default location. By default, this setting is turned off/disabled.
-
Click +Location, then enter the location's details. At the minimum, you must select a country and location that will serve customers from that country. Repeat until all your locations have been set up, if necessary.
Note: Field names for Country, State, Zip/Postcode, City/Suburb must be the same in the appropriate fields on the eCommerce Platform Integration (in the delivery address) and on Cin7 Core. e.g. Victoria and Victoria (VIC) will not be treated as the same location.
Click Save.
If some lines match each other, the priority for selection is as follows:
First we check if the field Zip/Postcode is the same. If the field matches, we choose the location from the line with the same Zip/Postcode .
If the field Zip/Postcode is empty we check the field City/Suburb.
If the field City/Suburb is empty we check the field State.
If the field State is empty we check the field Country.
Import/export order routing locations via CSV file
Click Export to export all order routing information as a CSV file. CSV file can then be edited and re-imported into Cin7 Core to make changes.
Click Import to enter new order routing locations or update existing order routing locations via CSV file. Opening the Import page allows you to download the order routing template, make your changes, and then re-upload the edited file.
Using order routing for eCommerce integrations
To configure order routing for Amazon, Shopify, eBay and other online marketplaces in Cin7 Core, you need to set to link the location for your online sales to Order Routing. This is commonly set up from the Integration page for the store in Cin7 Core. See the screenshots below for an example.
For example, on the WooCommerce Integration page, we can set the Link WooCommerce sales to Cin7 Core Location from All Locations to Order Routing.
This setting helps to avoid issues with incorrect order routing. For example, Cin7 Core allocates an order from Norway that should supposedly go out from your Denmark warehouse to your Amazon EU location instead.
Note: Order routing should be enabled in Settings → Reference Books before you can use it in your eCommerce platforms. See Setting up order routing for more information.
Tips and tricks
When creating your order routing locations, keep the following in mind:
The minimum required to define an order routing location is the Country where the customer resides and the inventory Location that will serve that country. Optionally, you can specify the State/Province, City/Suburb, and Postal Code.
Each routing zone can only be mapped to a single inventory location.
The same inventory location can be mapped to several routing zones.
If a shipping address for a sale corresponds to a mapped zone in order routing, the sales task header is pre-filled with the appropriate location.
The location in the sales task header field can be changed manually by selecting the appropriate location from the list.
When a sale has been made in an online store (of any eCommerce application) without defining a location and order routing is turned ON, Cin7 Core will either map a location for the order based on the shipping address or set a default location for the order.
If the inventory location is out of stock and the Keep Routing setting is disabled, Cin7 Core will automatically pick a random location with stock to process the sale.
If you are encountering delays in pulling online orders into Cin7 Core, this might be due to order routing not being configured for your store. Check that order routing is turned on, ensure that there are inventory locations servicing your customer's locations, then run the process again to ensure that the delays have been resolved.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB