Introduction

Inventory Sync is JOOR's flat file inventory integration. An Inventory Sync integration can load both immediate and Work in Progress (WIP) inventory to multiple warehouses in your account. The integration can run up to once per hour and pulls files from an FTP server, the credentials for which will be provided by JOOR.

Basic Requirements

• Files must be entirely generated by the ERP and may not be manually altered in any way.
• File format must be configurable in order to match the requirements of the integration.
• File name must be specified for the integration to be able to pick up new files.
  • We recomment using the word "inventory" along with a timestamp.
• Files must be automatically sent to JOOR's FTP server, hosted by BrickFTP.
  • More on BrickFTP's security technology can be found [here].
• Files must be in either .txt or .csv format. Excel formats are not supported.
  • Delimiter should be comma, tab, or pipe ("|").
• Files must not exceed 20MB.
• The inventory integration can process files in two ways. You will need to specify to your JOOR representative which of these you would like to utilize:
  • 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.
  • Update only loads the positions loaded in the file
    • Every SKU on JOOR that was not included with the file will be excluded from the inventory update.
• All integration files must be listed with one size per row.
• The inventory integration can process file format that matches on either of the following. You will need to specify to your JOOR representative which of these you would like to utilize:
  • UPC/EAN (recommended) OR
  • SKU information

Prerequisites

Before beginning to test the integration, you will need to provide the following information. All fields are optional unless otherwise noted.

• Warehouse Names and Codes (if using multiple warehouses)
• UPCs (if using UPC/SKU file format)

Tips

• When using the UPC/EAN format, the minimum required columns are UPC and Quantity. The UPC information will also need to be uploaded to the product data on JOOR before loading the Inventory Sync file.
• Alternatively, you can uniquely identify the Style-Color-Size to update inventory for using any of the following combinations:
  • Style Number, Color Code, and Size Name
  • JOOR Style ID, JOOR Style Color ID, Size Code
• If you wish to use multiple warehouses, these will all need to be loaded to JOOR beforehand. Please provide a complete list to your JOOR representative.
• The Date column is only necessary if you plan to use WIP inventory. This column should not be populated for any immediate or available to sell inventory quantities.

Testing Scenarios

A list of recommended Inventory Sync testing scenarios is also available for your reference. You may download it from the Testing Scenarios section of our Inventory Sync documentation online. Use this list as a guideline as you test different scenarios that are relevant to your business. Once all relevant tests have been executed successfully, your integration should be just about ready to activate on your Production account.

Reporting

Success and Error report emails are generated every time a file is processed via the integrations. If you and your team wish to receive these report emails, please specify the recipients' email addresses and we will set them up accordingly.

This feature is available on the Production environment. If you wish to receive the email reports during the testing period on Sandbox, please reach out to your dedicated Integrations Manager.

Inventory Sync Fields