You can connect your store to Inventory Planner with CSV connector even if Inventory Planner does not directly support your e-commerce platform. This is done with special TSV/Excel files which you make available via Google/Drive Dropbox or a web server. This file needs to be kept up to date on your side and Inventory Planner will automatically sync the data daily.
When you connect your store via CSV connector you will need to provide your store's primary currency and 3 TSV/Excel files:
Sales orders file
Purchase orders file (optional)
Select the CSV/Excel Integration
Enter the URL's for the hosted CSV files.
(Please note, If you use Google Docs/Drive or Dropbox, make sure to set up permissions so that anyone with the link can edit the file)
Sales orders define the demand for your products and are used to compute replenishment suggestions when combined with current stock from products file and on order quantities for your suppliers from purchase orders file. Note that you can also choose to omit purchase orders file and manage purchase orders in Inventory Planner if your e-commerce system does not have them.
When setting up CSV connector, you should provide 3 permanent URLs for these files. These URLs should not require authorization. If you use Google Docs/Drive or Dropbox, make sure to set up permissions so that anyone with the link can edit the file. Inventory Planner will automatically access these files every day.
These files must always contain all products and orders (not only updated). If a product or a sales order is removed from files it will be deleted in Inventory Planner as well.
Inventory Planner uses HTTP method GET to download the file and method HEAD to verify that the file exists during initial connection.
Inventory Planner optionally supports HTTP basic authentication for additional security. You can specify username and password when you connect your store. If you don't have it set up, leave them blank.
Product file specification:
product_id - product ID (required). All variants with same product_id will be under the same product. All variants of same product should have same vendor, brand and tags (but can have different options). If you do not have options/variations (all products have a single variant), it is possible to use SKU in this column.
title - product title (required)
SKU - stock keeping unit (required). We recommend all products to have unique SKUs.
created_at - product creation date, e.g. 2016-03-28 (required)
stock_quantity - inventory quantity (required)
price - retail price (required)
replenishable - TRUE = Replenishable / FALSE = Non-replenishable
regular_price - retail price without discount
cost_price - product cost price
landing_cost_price - product landing cost price
barcode - product barcode (e.g. UPC)
updated_at - last updated date of a product, e.g. 2016-04-28
visible - true if product is visible in your store, false otherwise
managing_stock - true if you manage inventory for this product, false otherwise
vendor - product vendor
vendor_reference - vendor product SKU
vendor_product_name - vendor product name
permalink - product URL
categories - product categories, e.g. women,dresses
image - product image URL
brand - product brand
options - product options, e.g. "Color=Red,Size=X"
tags - product tags, e.g. dress,last collection
moq - minimum order quantity
uom - units of measurement
Sale Order file specification:
order_number - order ID (required)
product_id - product ID (required)
SKU - product SKU (required)
date - order creation date, e.g. 2016-03-28 (required)
price - product price (required)
quantity - product quantity (required)
discount - line discount value (from price * quantity)
tax - line tax value (from price * quantity)
tax_included - tax is included in price flag (true/false, yes/no or 1/0), requires tax column
shipping - line shipping value
customer - email or "first and last name" (for wholesale planning)
currency - sales order currency ISO 3-letter code, e.g. USD, EUR (optional, defaults to store currency if not present or empty)
canceled - true if order is cancelled, false otherwise
Purchase Order file specification:
po_id - purchase order ID (required)
po_name - the display name of purchase order (optional)
vendor - the vendor of purchase order (optional)
date - purchase order creation date, e.g. 2016-03-28 (required)
expected_date - purchase order due date (required)
product_id - product ID (required)
sku - product SKU (required)
cost_price - line item price (required)
currency - purchase order currency ISO 3-letter code, e.g. USD, EUR (optional, defaults to store currency if not present or empty)
status - purchase order status, e.g. open, partially_received, closed (required)
notes - purchase order notes
ordered - line item ordered quantity (required)
received - line item received quantity (required)
received_date - line item received date (optional)
tax - line item tax (optional)
tax_included - line item tax is included (optional, 1/0 or true/false)
Shipping can be indicated in cost_price and tax fields in separate row with product_id value Shipping