The remote store tool can be used to create files compatible with SKULabs in order to sync in orders and listings from an unsupported channel. The following fields are available for Order Items and Orders.
Here is a sample CSV.
Orders
orders_header (required) - Use "order" under this column to indicate a particular row contains order information
order_number (required) - Order number
ship_to_name - Shipping name
ship_to_company - Shipping company name
ship_to_address - Shipping address line 1
ship_to_address_2 - Shipping address line 2
ship_to_city - Shipping city
ship_to_state - Shipping state code
ship_to_postal_code - Shipping postal/zip code
ship_to_country_code - Shipping country code
ship_to_email - Shipping email address
ship_to_phone - Shipping phone number
ship_to_method - Shipping method requested by customer
total - Total for the order.
shipping - What the customer paid for shipping
tax - What the customer paid in taxes.
discount - Amount the total was discounted.
date - Date the order was placed.
ship_by_date - The date the order should be shipped by.
delivery_by_date - The date the order should be delivered by.
currency - USD / CAD / etc
note - Notes for the order
order_location - Assigned location for the order, will override tag rules as long as the location satisfies the range of locations made acceptable by the rule.
tags - Comma separated list of tags.
financial_status - Text-based status string representing if the order is paid or not, non-standardized values accepted.
status - The current status of the order according to your data. If shipped, we will set the status of the order to shipped in SKULabs. If cancelled we will set the status of the order to cancelled in SKULabs. If pending, you will no longer be able to include the order in batches, and we will warn the shipper prior to trying to ship it that the order is not yet paid and should not be delivered.
Order items
items_header (required) - Use "item" under this column to indicate a particular row contains order-items information
sku (required) - SKU of the item
variant_sku - Variant SKU for the item.
quantity (required) - Ordered number of units of the item
price (required) - The price paid per item.
personalization - Notes that will appear for this line item. e.g. embroidery, sealants, finishing touches that do not impact inventory availability
dropshipped - Boolean true/false representing if this item was dropshipped on the sales channel and should not be shipped by the pickers.
line_id - A unique ID representing this line of the order from the originating system.
Here is a sample JSON format order:
[
{
"order_number": "123-185-1241",
"status": "processing",
"date": "2017-10-07T17:23:33.000Z",
"discount": 2,
"tax": 3.78,
"shipping": 3,
"total": 67.76,
"note": "Thanks for the help over the phone!",
"ship_to": {
"name": "John Doe",
"company": "",
"address": "123 Example Way",
"address_2": "",
"city": "New York",
"state": "NY",
"postal_code": "12345",
"country_code": "US",
"phone": "123-456-7890",
"email": "john.doe@example.com",
"method": "First Class"
},
"ship_by_date": "2017-10-08T17:23:32.000Z",
"deliver_by_date": "2017-10-15T17:23:32.000Z",
"order_location": "AA0132",
"tags": "Paid,Delayed",
"items": [
{
"order_number": "123-185-1241",
"sku": "pplspoon",
"variant_sku": "",
"price": 34.99,
"quantity": 1,
"personalization": ""
},
{
"order_number": "123-185-1241",
"sku": "coloredspoon",
"variant_sku": "coloredspoon-mint",
"price": 27.99,
"quantity": 1,
"personalization": "Solid color"
}
]
}
]