# Feeds
Feeds help facilitate data imports into Orderwave. They act as an interstitial layer between your data, and Orderwave's data. This is useful, because data often needs to be manipulated to fit into Orderwave's formats, and if problems occur, the feed data can be queued, edited, and attempted to sync again, or simply discarded.
TERMINOLOGY ⚡
Feeds are data that you are importing into, or sending to Orderwave for synchronization. Feed data (after import) is viewable in , and import mappings are at .
By default, the import configuration expects Windows-style file endings (\r\n), tab delimiters (\t), and fields enclosed in double-quotes if necessary ("). You can update these settings in your Import Mapping configurations located at . Do not include headers in your feed files.
# Inventory Items
These are the inventory SKUs that will import into the wms/inventories bucket. It is a very simple data format with the following fields:
| Field | Description |
|---|---|
| SKU | The globally unique identifier for the inventory item. UPCs and ISBN numbers are best, but you can use whatever naming scheme works best for your organization. |
| Stock Number | The identifier for the product line / related product variations. For example, for apparel, different sizes will have matching stock numbers, and unique SKUs. |
| Description | The descriptive name of the item. |
| Weight | The weight of the individual item. |
# Inventory file import mapping
Orderwave allows you to create your own file mappings, but by default, we do include some common mappings for you. The inventory item feed mapping is included, and follows this format:
# I Inventory data record
| Field | Sample | Description |
|---|---|---|
| Record Identifier | I | The first column of your file data should be an identifier that dictates what record this is. In this case, it is an I for inventory. |
| SKU | 0123456789012 | The globally unique identifier for the inventory item. UPCs and ISBN numbers are best, but you can use whatever naming scheme works best for your organization. |
| Stock Number | SN001 | The identifier for the product line / related product variations. For example, for apparel, different sizes will have matching stock numbers, and unique SKUs. |
| Description | Sample item description - Blue | The descriptive name of the item. |
| Weight | 0.75 | The weight of the individual item. |
Sample inventory item feed data:
I 0123456789012 SN001 Sample item description - Blue 0.75
I 0987654321012 SN001 Sample item description - Green 0.75
Set up an Automated Task (Import Job) to automatically fetch files from a (S)FTP server and load it into the feed section.
To view inventory feed data, navigate to .
# Inventory Syncs
To send current inventory quantities to Orderwave from a warehouse or ERP, create a tab-delimited file with the following columns:
# I Inventory sync record
| Field | Sample | Description |
|---|---|---|
| Record Identifier | I | The first column of your file data should be an identifier that dictates what record this is. In this case, it is an I for inventory. |
| SKU | 0123456789012 | The globally unique identifier for the inventory item. |
| Subset Code | DEFAULT | The identifier for the inventory subset for these quantities. By default, this value is DEFAULT. |
| Warehouse Code | WH1 | The unique identifier for the warehouse for these quantities. |
# Product Items
To send product definitions to Orderwave, create a tab-delimited file with the following columns:
# P Product Header Record
| Field | Sample | Description |
|---|---|---|
| Record Identifier | P | Record identifiers signify that the current record is for a certain kind of data. Each product in your file will need at least a P record for the product data, and a M record for the mapping data (mapping information to the inventory items). |
| Product Code | PR001 | The unique identifier for the product (product master). |
| Product Number | PR-LINEA | A non-unique product line identifier. |
| Title/Description | Superior Cotton Dress (Cobalt Blue) | A product title or short description of the product. |
| Product Type Code | Standard | One of three types: Standard, Variation, or Virtual-Kit. |
| Final Sale | false | Products designated with finalSale = true cannot be returned or exchanged. |
# M Product Mapping Record(s)
| Field | Sample | Description |
|---|---|---|
| Record Identifier | M | The record identifier for the mapping record. |
| Variation Description | Superior Cotton Dress - Large - Cobalt Blue | A product title and description of the variation option. |
| SKU | SCD-L-CB | A UPC or unique value that exists in your Orderwave inventory. |
| Quantity | 1 | The quantity of this inventory/SKU to map to this product. This is not the stocked quantity. |
| Price Per Unit | 49.99 | The price for this item. The total product price is the sum of the mapped prices. |
⚠ Create your inventory data first
Inventory items must exist in Orderwave before you send product data to Orderwave.
A sample product feed file will look like the following:
P PR001 PR-LINEA Superior Cotton Dress (Cobalt Blue) Standard false
M Superior Cotton Dress - Small - Cobalt Blue SCD-S-CB 1 49.99
M Superior Cotton Dress - Medium - Cobalt Blue SCD-M-CB 1 49.99
M Superior Cotton Dress - Large - Cobalt Blue SCD-L-CB 1 49.99
M Superior Cotton Dress - X-Large - Cobalt Blue SCD-X-CB 1 49.99
P PR002 PR-LINEA Superior Cotton Dress (Magenta) Standard false
M Superior Cotton Dress - Small - Magenta SCD-S-M 1 49.99
M Superior Cotton Dress - Medium - Magenta SCD-M-M 1 49.99
M Superior Cotton Dress - Large - Magenta SCD-L-M 1 49.99
M Superior Cotton Dress - X-Large - Magenta SCD-X-M 1 49.99
# Shipment Updates
The shipment update feed allows you to import data into the shipment update feed section. Once the data is there, the data will be synchronized with your orders with an App Job, updating tracking number, performing the dispatch processes, and canceling line-items and orders as needed. If there is a problem synchronizing any of the shipment update data, the shipment update records will be queued for a team member to correct or remove.
The data feed should be in the following format:
# S Shipment header record
| Field | Sample | Description |
|---|---|---|
| Record Identifier | S | The first column of your file data should be an identifier that dictates what record this is. Each shipment should include 1 shipment header record, signified by S. |
| Order Number | 1045 | The order number for the order. |
| Tracking Number | 505635289269 | Tracking number for the shipment. |
| Service code | FEDEX-GROUND | The service code mapping. These mappings are defined under Settings > Services. This maps the shipping method that the warehouse used to the shipping method that should be updated on the shipment. |
# I Shipment item record(s)
| Field | Sample | Description |
|---|---|---|
| Record Identifier | I | These records identify the item-records from the shipment. Item records should directly follow their respective header records. |
| SKU | 021365843659 | The unique identifier for the inventory item that was shipped. This should match the item on the order. |
| Quantity | 1 | The quantity of the item that was shipped. |
| Update Status Code | Shipped | The type of record that this action represents. Available options: Shipped and Canceled. |
A sample file that contains two orders (each with two items each) will look like the following:
S 1045 505635289269 FEDEX-GROUND
I 021365843659 1 Shipped
I 095216849354 1 Shipped
S 1046 505631655440 FEDEX-GROUND
I 168432468132 1 Shipped
I 169843287744 1 Canceled
To utilize this import process, you will need an Automated Task Import Job to fetch these files.