ShipStation Custom Store
The Custom Store option in ShipStation allows a developer to build a custom connection for a selling channel that does not have a native integration with ShipStation. In this case, Cin7 Core has handled the development so it is simple for you to connect your store through Cin7 Core. Once connected, you can then import order information from Cin7 Core to ShipStation and send back shipment information to Cin7 Core.
ShipStation supports three kinds of integration, this article covers connecting ShipStation as a Custom Store.
ShipStation store integration - This connects ShipStation store as an eCommerce channel. Orders are passed to Cin7 Core for stock management. See ShipStation Store for more information.
ShipStation Custom Store - we recommend this if you are using eCommerce channels integrated with Cin7 Core. ShipStation pulls orders from Cin7 Core (including eCommerce orders), fulfillment and shipping label printing takes place in ShipStation, then shipping information and stock movements are synced back to Cin7 Core.
Connect ShipStation as a Shipping Service - similar in function to custom store. Order (including eCommerce orders) are placed in Cin7 Core, orders can be fulfilled either through Cin7 Core or exported to ShipStation for fulfillment, shipment information is synced with ShipStation to generate shipping labels, printable in Cin7 Core. We recommend this if you are using eCommerce channels integrated with Cin7 Core and need to filter sale orders before export. See ShipStation as a Shipping Service for more information.
For more information, see the ShipStation Integrations Help guide for Cin7 Core.
Cin7 Core as a Custom Store can be connected at the same time as ShipStation store, Cin7 Core has validation to prevent the same order being sent through twice. However, for optimum performance we recommend connecting only one.
Custom Store and ShipStation Shipping Service have almost the same function and we do not recommend connecting both at the same time, as it can generate duplicate shipping labels.
Prerequisites
Familiarity with sales
Familiarity with Product and Service Management
Only one ShipStation account can be connected to Cin7 Core.
ShipStation account settings currency MUST match with Cin7 Core base currency, set via Settings → General Settings.
ShipStation account settings units MUST match with Cin7 Core default units, set via Settings → General Settings.
-
Users will need the following permissions:
User will need the Integrations → Shipment - ShipStation permission enabled to access the integration settings.
User will need the Sale → Sale Task – Pack view: Sales List & Tasks permission to enter package information and shipping instructions.
User will need the Sale →Sale Task – Ship view: Sales List & Tasks permission is required to generate the shipping label.
Connect ShipStation Custom Store
Cin7 Core as a Custom Store can be connected at the same time as ShipStation store, Cin7 Core has validation to prevent the same order being sent through twice. However, for optimum performance we recommend connecting only one.
Custom Store and ShipStation Shipping Service have almost the same function and we do not recommend connecting both at the same time, as it can generate duplicate shipping labels.
When using both types of integration (Custom Store and ShipStation Store), there are some validations to prevent user data from being damaged:
Unable to download data from ShipStation (API) if this data was first exported from Cin7 Core using (Custom Store Integration). Data will not be saved.
Unable to export (Custom Store Integration) sale orders that were downloaded from ShipStation (API).
You need to use a Cin7 Core login that is linked to a single Cin7 Core Organisation only. When trying to connect ShipStation to a Cin7 Core account with more than one organisation, error code 300 will be generated, preventing data from being exported to ShipStation.
Log in to your ShipStation account to connect Cin7 Core as a custom store.
Navigate to Integration → ShipStation. Only one ShipStation account can be connected to Cin7 Core.
Select the Custom Store tab.
Switch Status to Enabled.
Login to ShipStation.
Go to Account Settings
Select Selling Channels from the left-hand sidebar, then choose Store Setup.
Click + Connect Store or Marketplace and choose Cin7 Core.
Enter your login and password from Cin7 Core account.
IMPORTANT! The user login/password specified in ShipStation custom store should have access to no more than one Cin7 Core Organisation. If the user connecting has access to more than one Cin7 Core organisation there will be a connection issue.
Integration Settings
Access the integration settings for ShipStation Custom Store by going to Integrations ShipStation
Custom Store Integration Status
This enables or disables the Custom Store Integration.
Use Stock Locator instead of Location as Warehouse
This setting controls the value that Cin7 Core sends to ShipStation for the Warehouse field. This can either be the Location or the Stock Locator value for the product in Cin7 Core.
Export sales fulfilled externally
This setting controls whether Cin7 Core should export Amazon sales fulfilled via FBA to ShipStation. This only affects FBA sales fulfilled through Cin7 Core's native integration with Amazon FBA - sales fulfilled through Amazon FBA NOT integrated with Cin7 Core will not be affected.
Import shipping costs
When this setting is enabled Cin7 Core obtains the shipping cost value from ShipStation and automatically creates and authorizes an invoice entry under the Additional Charges section of the invoice tab in Cin7 Core.
Note: Shipping costs can only be added to the invoice in Cin7 Core when invoice has not yet been authorized. If invoice has been authorized shipping costs will not be added.
Capture ship to company as
When labels are printed in Shipstation, Ship to Company and Ship to Contact are passed with the sale order. If Ship to Company is left blank, you can:
Ignore billing customer when when Ship to Company is not specified: The field is left blank on the ShipStation shipping label when Ship to Company is not specified.
Use customer name when ship to company not specified: Customer name is printed on ShipStation shipping label when Ship to Company is not specified.
Pulling orders from Cin7 Core to ShipStation
ShipStation Custom Store pulls orders from Cin7 Core to ShipStation, including orders that Cin7 Core has pulled from other sales channels. Frequency of order pull is configured from the ShipStation side, and can be triggered manually from ShipStation with Custom Store Sync.
Sale order is authorized in Cin7 Core/ Cin7 Core receives order from connected sale channel (e.g. Shopify, WooCommerce)
-
ShipStation pulls order from Cin7 Core when the following parameters are fulfilled:
Pack tab is authorized
Ship tab contains info (Tracking # field must be blank)
Ship tab can be authorized or unauthorized
Invoice tab can be authorized or unauthorized but must have an invoice number.
Fulfillment and shipping label printing takes place via ShipStation.
-
Tracking #: Once shipment is dispatched, tracking # is sent back to Cin7 Core.
Tracking field must be blank when order sent to ShipStation.
-
Shipping Fee: If invoice is not authorized, shipping fee will be sent back to Cin7 Core and invoice will be authorized. Shipping fee will not be sent back to Cin7 Core if invoice has already been authorized.
Import Shipping Costs must be enabled in ShipStation Custom Store settings.
Shipment tab is authorized if it has not yet been authorized.
Stock movement in Cin7 Core takes place when ship tab is authorized.
Are you having problems with orders from sale channels not getting pulled by ShipStation? Here are common causes of errors:
Pick, Pack and Ship Processing Mode for online sales setting for eCommerce integration is set to No Picking or Auto-Pick - this will not authorize the Pack tab, which is the trigger to pull the order. We recommend setting Pick, Pack, and Ship Processing Mode for online sales to Auto-Pick + Pack.
Invoice Status for connected eCommerce integrations should be set to Draft - shipping costs will not be synced back to Cin7 Core if invoice is authorized when synced too ShipStation.
Invoice number should be created On sale creation - sale needs an invoice number in order to sync to ShipStation. (Edit this from Settings → General Settings → Sale process customisation)
We recommend integrating sales channels with Cin7 Core, then integrating Cin7 Core with ShipStation. Integrating ShipStation to the sales channels directly can cause issues with data flow.
Prevent orders syncing to ShipStation
It is possible to set up order filters in ShipStation to prevent syncing some Cin7 Core orders to ShipStation.
Note: If your Cin7 Core account is integrated with FBA via Cin7 Core's native integration, you can simply disable the Export sales fulfilled externally to stop FBA fulfilled sales syncing to ShipStation. This function will not work if FBA is not integrated with Cin7 Core.
We recommend using the Warehouse Location field as your filter criteria. All eCommerce native integrations with Cin7 Core have an option to specify the location for sales for that general in that integration's Setup tab.
Back in the ShipStation integration in Cin7 Core, you will need to make sure that Use Stock Locator instead of Location as Warehouse setting is disabled.
Next, log in to ShipStation to set up an order filter. Please see ShipStation documentation for more information on applying filters. Set a filter for Warehouse Location and exclude the location associated with the channel you wish to filter.
Next, set up an Automation rule using this filter, with the following settings.
Tasks not ready for ShipStation
This section displays sales which have not been able to be exported to ShipStation and the reason for the export fail. Typically, export fails due to missing shipping address in sale.
- 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