ShipStation Integration
ShipStation supports three kinds of integration, this article covers connecting a ShipStation store.
ShipStation store integration - This connects ShipStation store as an eCommerce channel. Orders are passed from ShipStation to Cin7 Core for stock management. This is best if you are using sales channels not integrated with Cin7 Core, and integrate channels instead with ShipStation via API.
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. See ShipStation custom store for more information.
Connect ShipStation as a shipping service - similar in function to custom store. Orders (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.
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.
ShipStation store and ShipStation shipping service can be connected at the same time without problems.
NOTE: When a refund is processed for an unfulfilled sale, this will cause an error with restocking the unfulfilled items. These will appear on the log as Pending fulfillment. If you are experiencing this error, you will need to enable the Ignore restock for non-fulfilled sales setting. This setting is not enabled automatically in order to preserve system logic continuity for users.
Prerequisites
Familiarity with sales (necessary)
Familiarity with Products and product management (necessary)
Users will need the Integration: Shipment - Shipstation permission in order to use this feature.
Only one ShipStation account can be connected to Cin7 Core.
Users will need to add an External integration licence to their subscription if they do not have one available.
ShipStation store (Cin7 Core pulls orders from ShipStation)
ShipStation store downloads order data from the ShipStation eCommerce storefront to be synced with Cin7 Core stock levels and processed in Cin7 Core.
ShipStation integration setup
ShipStation custom store and shipping service should not be connected at the same time. ShipStation store can be connected at the same time as either Custom store or shipping service.
Note: When using both types of integration (custom store and ShipStation store), there are some validations to prevent user data from being damaged:
Cannot 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 organization only. When trying to connect ShipStation to a Cin7 Core account with more than one organization, error code 300 will be generated, preventing data from being exported to ShipStation.
Users will need to add an External integration licence to their subscription if they do not have one available. Additional external integrations must be purchased from the My subscription page.
Connect ShipStation store to Cin7 Core:
Navigate to Integration → ShipStation.
Click + to connect a new store. Only one ShipStation account can be connected to Cin7 Core.
Enter your API credentials and click Connect ShipStation as a store. You can find your API credentials in the API settings of your ShipStation account.
Integration settings
In the Setup tab, several integration settings can be customized.
Capture order when it is
This option specifies when a ShipStation order will be captured: when it is created, when it is paid, when it is no longer on hold or when it is shipped. This setting is also taken into account when downloads of historical orders from ShipStation are triggered.
Consolidate orders
Cin7 Core - ShipStation integration allows two options for order consolidation:
No Consolidation
Daily Consolidation.
No consolidation indicates that sales will be captured from ShipStation once an hour as individual sales. Daily consolidation will consolidate all orders from that day into a single order. When daily consolidation is chosen, an additional setting becomes available – Consolidation time. This is your local time when all pending orders aggregated during the day will be processed.
See the Pending order processing section below for more details.
Customer
For the pending order processing to be successful, an existing customer must be selected.
When consolidation type is daily consolidation, this customer is used to create a new sale task which will combine all daily sales. A customer can be created in Cin7 Core just for this purpose.
Price tier
Choose which Cin7 Core price tier to use when Cin7 Core downloads products from ShipStation or updates product information. See Pricing and price tiers for more information.
Pick, pack, and ship processing mode
When pending orders are processed by Cin7 Core, new sale tasks are created. This setting tells Cin7 Core if it should try to auto pick, auto pack and auto ship these tasks. If there is not enough stock on hand to pick the full quantity of products in an order, then pick will remain in draft state, and pack and ship won’t be completed.
Ignore restock for non-fulfilled sales
When a refund is processed for an unfulfilled sale, this will cause an error with restocking the unfulfilled items. These will appear on the Log as Pending fulfillment. If you are experiencing this error, you will need to enable this setting. Restock/stock allocation quantities will be edited to match the fulfilled items of the sale. This setting is only applicable when Pick, pack, and ship mode for processing online sales is set to Auto pick + pack + ship.
Invoice status
You can control the Invoice status for sale tasks created as a result of pending order processing. By default, the invoice will not be authorized and will be in draft state, adjustable and waiting for authorization. However, if this setting is changed to authorized, the invoice will be automatically authorized, and pending sync will be created for it to sync with an accounting application of your choice.
Optional revenue account
Revenue account to be used for all sales downloaded from ShipStation. This will override settings at the product/customer level and any other account mapping.
ShipStation dimension units
To avoid discrepancy, this setting must match the dimension setting from your ShipStation account. You can find your ShipStation dimension settings by going to ShipStation → Account settings → Display options → Time and units.
Sales representative name
This option allows the shop name to be used as a sales representative.
Match product
An option to choose automatic mapping by SKU or manual mapping by the user when products are downloaded from ShipStation (by pressing Load products on the Catalog tab of the ShipStation integration). When automatic mapping is selected, the existing product will be searched for automatically by SKU, and if a product is found with a matching SKU, then the mapping is done automatically. When manual mapping is selected, the user will have to manually select which Cin7 Core products to link to via the catalog tab. Manual mapping can still be performed even if automatic mapping is enabled. See Linking catalog products for more information.
Create a new product if not found by SKU
This option is only available when Match product by SKU is enabled. With this option enabled, if there is a product (SKU) in the sale channel that does not yet exist in Cin7 Core, then this product can be automatically built in Cin7 Core based on the data received about the product from a sale channel. The possibility of a manual build is still always available through the Cin7 Core UI.
Use ShipStation as master source for Cin7 Core products
If this option is enabled, if a product has been changed or updated in ShipStation, the linked product in Cin7 Core will be changed to match upon catalog download. Product changes in Cin7 Core can include changed price, name, weight, length, pictures and other data (except SKU) based on the product data downloaded from ShipStation. Be aware! Turning on this feature can damage your product data in Cin7 Core.
Shipment is taxable
In ShipStation, tax is entered just as a single amount. In Cin7 Core, tax is attributed per line item, so if this option, it is distributed based on a prorated basis of total invoice lines.
-
Examples:
If No is selected, the additional charges column won't have tax attributed to it.
If Yes is selected, the additional charges column will have a tax amount attributed to it on a prorated basis taken from the total tax line amount.
Enable order routing
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. See Order routing for more information.
Process auto-assembly as
This dropdown field has two options:
For ordered quantity: Does not check stock quantity. An assembly order is created for the quantity specified in the sale order, regardless of stock availability.
-
For minimum quantity required for picking: Assemble stock required to meet the quantity of specific sale order.
If stock availability is negative, auto-assembly will produce a finished goods quantity which is more than the quantity ordered through sale order.
If there is already stock available in inventory but not enough to fulfill the sale order quantity, auto-assembly will assemble the difference in quantity needed to meet the sale order requirement.
If stock availability exceeds sale order quantity, auto-assembly is not triggered.
Stock availability is validated against the sale order location and does not take on order quantity into account.
Location mapping
ShipStation supports multiple locations. Map ShipStation warehouses to your Cin7 Core locations here.
Tax rule mapping
For businesses located in the United States, it is necessary to Add a US place of business by clicking the button and inputting the correct US address (by entering the correct ZIP code first). After that, new tax rules will be created. Generally, this will be three tax rules: State, State, County and State, County, City. These tax rules will be automatically applied to sale invoice lines (products) downloaded from ShipStation and having a shipping address in the US.
When a pending order is processed by Cin7 Core, a sale task is created. Each order and invoice line is assigned a tax rule. The tax rules specified in these settings will be used to create these lines.
Cin7 Core does not apply the tax rule to recalculate tax and is simply using the actual tax amount from the ShipStation order. This means that if certain products are not taxable or with varying tax in ShipStation, all data and totals in Cin7 Core will look identical to ShipStation, but with Cin7 Core tax rule name selected in this setting.
In the case of tax recalculation, the tax amount will be overwritten with a value calculated by Cin7 Core taxation rule.
IMPORTANT: Orders will be skipped on download if taxation mapping is not finished!
Payment account mapping
Cin7 Core can capture payments made against orders in ShipStation and is able to automatically add payments to a created sale invoice. To do this, payment account mapping must be completed on this integration settings screen. You must choose an account that is able to receive payments from the chart of accounts.
This setting is not mandatory – if payment mapping is not completed, orders are still captured and downloaded from ShipStation, but payments must be manually added to invoices in Cin7 Core. Some customers prefer to keep invoices open and then reconcile them with payouts from ShipStation.
Disconnect from ShipStation store
When you disconnect from ShipStation store, Cin7 Core removes all associations between Cin7 Core objects and ShipStation, including log and product catalog.
Catalog
The Cin7 Core ShipStation catalog page allows the user to download products from ShipStation, break the link between a Cin7 Core product and its ShipStation listing and update quantities in ShipStation according to Cin7 Core available stock.
Downloading products
Products can be loaded from ShipStation to Cin7 Core in the Catalog tab by clicking Load Products. This operation may take some time.
All products in ShipStation are mapped as simple products in Cin7 Core. ShipStation does not support product variations and does not supply quantities, which are required in Cin7 Core. If the customer has bought a product variation in their ShipStation order, information about the selected options will be provided in the order and invoice sections of the sale order for each line in the comment field.
When a product is created/updated in Cin7 Core during the download process, there is a link established between the product and variant unique ShipStation product ID and Cin7 Core unique product ID. This link is used when products are matched against sale order lines in ShipStation and when subsequent product downloads occur.
The category field is not mandatory for ShipStation but is a required field for Cin7 Core. If a product has no category specified, Cin7 Core will give it the product category Other.
When downloading products, Cin7 Core tries to match existing products first to avoid creating duplicates. In ShipStation, the product name/SKU can be non-unique whereas Cin7 Core enforces mandatory SKUs. Names that appear more than once will produce an error message, and the user will be able to link products manually.
During product download Cin7 Core automatically creates product categories for all product types in ShipStation if specified.
Normally this function is not used except for test purposes because Cin7 Core automatically creates products when processing sale orders and because there is no quantity information for products in ShipStation.
Data mapping for products between Cin7 Core and ShipStation:
Cin7 Core |
ShipStation |
SKU |
SKU |
Name |
Product name |
Category |
Category (if specified) or other |
Description |
Product InternalNotes |
Weight |
WeightOz (converted to KG on download) |
Width |
Width |
Height |
Height |
Length |
Length |
Product tags |
Product tags associated with ShipStation product |
Product type |
Always stock |
Price tier 1 (Default) |
Price |
StockLocator |
ValueProduct WarehouseLocation |
ESCCustomField1 |
Product fulfillmentSKU |
Linking catalog products
There are two possible statuses for products in the catalog: Not listed or Listed.
You can download products from ShipStation and perform automatic product mapping to products in Cin7 Core. Products in Cin7 Core cannot be listed in ShipStation.
There are three linking options:
Leave blank (do not tie to a product in Cin7 Core)
Link to an existing product
Create a new product in Cin7 Core (available if the product with the required SKU does not exist).
Orders and sales
Processing pending orders
If No consolidation is selected, each ShipStation sale is converted into an identical sale in Cin7 Core, keeping the same customer and shipping information. These orders will be captured once an hour. If Daily consolidation is selected, the single daily sale task will use the customer selected in the integration settings, and customer, billing and shipping information imported from ShipStation will be ignored.
When processing orders, the logic is identical to that of the Cin7 Core UI. DropShipping, kitting and other important scenarios are implemented in the same way as through the Cin7 Core UI.
Pending orders can be processed manually by clicking Process. They can then be viewed in the Log tab.
Cancelling an order in ShipStation will NOT cancel or void the linked sale task in Cin7 Core. The sale must be manually voided in Cin7 Core.
Downloading customers
The Load customers button can be found next to Load products.
This function downloads all customers from ShipStation to Cin7 Core. If the customer already exists in Cin7 Core, this function updates any details that have been changed in ShipStation. As Cin7 Core automatically creates customers when processing sale orders (if 'no consolidation' option is selected), this function is generally only used for testing purposes.
This function creates a customer in Cin7 Core with contact, billing and business addresses captured from ShipStation.
Downloading orders and payments
Orders are automatically downloaded every hour if they have been created or changed in ShipStation.
Note: Generally, you do not need to trigger manual order download, however, if an order was not captured by Cin7 Core or to load historical sales you can use the manual Load order option. Cin7 Core allows loading historical sales data a maximum of one year old.
Any imported order is saved to the pending orders section. It is a temporary storage of all sales and payments in Cin7 Core. If an order already has an entry in the log (i.e. was imported previously), it will be skipped. This guarantees that no duplicate sales will be created by Cin7 Core.
While saving orders, Cin7 Core captures customer information, billing and shipping addresses. All line items are captured together with quantities, prices and totals. Total order discounts are applied as are additional charges to the whole order, without distribution by lines to reduce the chance of discrepancy.
Invoice adjustment lines are also saved in the sale invoice as additional charges named shipping.
If a payment account has been specified in the integration settings, Cin7 Core will always assign associated payments to the captured ShipStation orders.
For each line in the sale order Cin7 Core tries to locate a corresponding product by SKU. If no product is found, Cin7 Core tries to download product info from ShipStation with the same logic as in Download products function. If product info is not found, Cin7 Core marks this line as service (non-product). Next, the sale line is saved to pending orders with all data from ShipStation: tax, quantity and total.
The final step in the order download is to trigger the update of stock levels in other ShipStation stores and other connected eCommerce channels.
Cancelling an order in ShipStation will NOT cancel or void the linked sale task in Cin7 Core. The sale must be manually voided in Cin7 Core.
Returns and refunds
Cin7 Core captures refunds from ShipStation. Cin7 Core will then capture the refund and return/restock and apply them to the associated sale task.
Please note that if the sale is unfulfilled, this will cause an error with restocking the unfulfilled items. These will appear on the log as Pending fulfillment. If you are experiencing this error, you will need to enable the Ignore restock for non-fulfilled sales setting.
Submit returns request via RMZ portal
Customers can submit returns requests via Cin7 Core RMA Portal if your organization subscription has this feature, allowing customers to initiate the Cin7 Core RMA workflow, and view the status of their returns. This includes sales processed through connected eCommerce channels.
Any Cin7 Core customer can submit a returns requests via the returns portal with an order number or invoice number and email address simply by accessing the relevant URL. We recommend adding the URL to the return portal to your default sale email template sent to customers. Please see detailed instructions at RMA Portal for returns requests.
Please note that refunds/restocked processed in this way will not be automatically exported to the eCommerce channel, and will have to be added manually updated within the channel. You may prefer to use the returns workflow offered by ShipStation if you do not need the additional RMA workflow features in Core.
Refunds for sales predating integration with Cin7 Core
Merchants with eCommerce channels occasionally have to process returns or refunds for a sale that predates integration of the eCommerce channel with Cin7 Core.
Sales and refund information is imported automatically from the eCommerce channel to Cin7 Core, but can also be manually imported via the Cin7 Core web portal. Historical refunds and returns are handled differently for each case.
Automatic import: Cin7 Core checks the sale order date against the date of integration with the eCommerce channel. If the sale order date predates the date of integration, credit note and refund are imported without the corresponding historical sale task.
A sale is created without order lines or invoice lines.
Credit note tab shows refunded items and if a refund was processed in the eCommerce channel it will be captured on this tab.
Restock tab is left empty and no stock adjustments are made.
Manual import: Manually loading orders from Shopify functions in the same way whether the sale took place before or after integration with Cin7 Core.
From the Pending orders tab, click Load orders and select a date to load sales, including historical sales pending orders. Process the sale associated with the refund.
The sale order with have order, invoice, pick, pack, and ship lines. It will also have credit note and restock lines.
User will have to perform a manual stock adjustment to correct any discrepancies from the refund.
Updating fulfillment in ShipStation
Cin7 Core pulls sales from ShipStation. When ShipStation is connected as the store, ShipStation is the driver of the integration. Carrier and tracking information is not pushed to Cin7 Core and will only be visible from the ShipStation side.
Cin7 Core cannot push any fulfillment data to ShipStation.
Logs
Each captured ShipStation order once saved to pending orders creates a log entry to track the link between the sale in Cin7 Core and in ShipStation. This eliminates the possibility of creating duplicated orders when capturing the same order several times during manual order load.
Each log entry has a link to the sale task in Cin7 Core. Depending on the settings selected by the user in the setup tab, this sale task could be draft or authorized, one or more of the pick, pack and ship tabs could be authorized, and payment could have been applied to the invoice.
Log entries allow you to see which sale task reflects a particular ShipStation sale. You also have the option to delete a log entry manually. This will allow reprocessing an order if required. Deleting a log entry will not void or delete its associated sale task.
Reloading orders from ShipStation
If for any reason you need to reload an order from ShipStation, this can be managed from Cin7 Core. Cin7 Core allows loading historical sales data a maximum of one year old.
Reload an order from ShipStation:
Void the sale task. A record of this will be kept in Cin7 Core for reconciliation purposes but the transactional data will be deleted.
Return to the ShipStation integration Log tab and delete the log entry. This will allow the order to be recaptured from ShipStation.
Navigate to the Pending orders tab and click Load orders, making sure the date is set to before the order to reload was made. Cin7 Core allows loading historical sales data a maximum of one year old.
Operations log
Each time the user or Cin7 Core downloads sales, an appropriate record is added to the operation log. It also contains information about results of downloading, including the count of processed, skipped or cancelled orders.
ShipStation Custom store (Cin7 Core sends orders to ShipStation to be fulfilled)
We recommend this is you are using eCommerce channels integrated with Cin7 Core, or are sending orders to ShipStation.
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. See ShipStation Custom store for more information.
- 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