Overview
Inventory Sync is flat-file integration. Inventory Sync integration loads both immediate and WIP inventory to multiple warehouses. The integration runs once every hour. The inventory file should be a direct export from your ERP with no manual edits and must be automatically sent to JOOR's FTP server.
Requirements
The following requirements will ensure your inventory data is loaded successfully:
- We accommodate 2 common formats as file options: CSV and TXT.
- The delimiter can be standard (,), pipe (|), semicolon (;), tab, or space - we recommend using pipe (|) as the delimiter.
- The inventory integration can process stock information that matches on either:
- UPC/EAN - Minimum required columns for this formats are UPC and quantity
- SKU information - Minimum required columns for this format are style number, color name/code, size name, and quantity.
- The inventory integration can process files in two ways: overwrite and update
- Overwrite clears all existing inventory and loads the new positions included in the file for the specified warehouse. Any warehouses not included in the file will not be affected. If using the Overwrite setting, you can set a style to be “Made to Order” by not including it in your next load file.
- Update only loads the inventory positions of styles included in the file. Every SKU on JOOR that was not included in the file will remain as-is. If using Update, you cannot set a style to be “Made to Order” through the integration. You can pass through all zero quantities, which will cause the style to display with no inventory, or sold out
The table below shows all the fields you can populate through the integration. Fields marked with “Y” are required fields. Before testing the integration, make sure you are providing the required and suggested data fields in your inventory file.
| JOOR Field Name | Template Field Name | Required | Value | Max | Description |
| style_number | Style Number | N | Text | 45 | Code used to signify styles. If not using UPC, this field is required |
| style_id | Style ID | N | Integer | 10 | The JOOR unique internal ID for a style |
| color_name | Color Name | N | Text | 100 | The display name of the colour. If not using UPC, this field is required |
| color_code | Color Code | N | Date | 10 | The code associated with the colour name |
| style_color_id | Style Color ID | N | Integer | 10 | The JOOR unique internal ID for a style/colour combination |
| size_name | Size Name | N | Text | 255 | The individual size to which units are allocated. If not using UPC, this field is required |
| size_code | Size Code | N | Text | 25 | The code associated with the size name |
| upc | UPC | Y* | Text | 100 |
The universal product code for the designated SKU (Style Number, Color Size) * although not required if providing style/color/size |
| quantity | Quantity | Y | Integer | 10 | The number of inventory units available to be ordered |
| warehouse | Warehouse | N | Text | 100 | The name of the warehouse in which the inventory positions should be stored. Must be set up in JOOR before loading your data |
| date | Date | N | String | 10 | Date assigned to the inventory positions. Can be in YYYY-MM-DD or MM-DD-YYYY format if you plan to use WIP inventory. It can be populated with IMMEDIATE in case of immediate/available to sell inventory quantities |
Reporting
Success and error reports based on the inventory sync can be sent to specific email addresses each time a file is processed via integration.
If you and your team wish to receive these report emails, please specify the recipients’ email addresses, and we will set them up accordingly. Please reach out to your dedicated Integration Manager for assistance.