Trax’ Product API enables its clients to send new products to Trax or to update already existing products in the Trax database.

Product updates sent via API to Trax will NOT be automatically added to Trax Product Database, but need to undergo a review process.

Product data should be added to a file to be sent as part of the corresponding POST request (see below).

1. Supported file formats: Excel, CSV, ZIP.

2. The ZIP file needs to contain either 1 Excel or 1 CSV file - multiple Excels or CSVs within a ZIP file are not supported.

The Excel/CSV should contain the following fields:

• Product name

• EAN code

• Brand name

• Manufacturer

• Client category

• Client Sub-Category

• Product type

• Container type

• Size

• UOM

• Pack type

• Units

• Width mm

• Height mm

• Depth mm

• 1 - Front Image Name/URL

• 2 - Left Image Name/URL

• 3 - Top Image Name/URL

• 7 - Back Image Name/URL

• 8 - Right Image Name/URL

• 9 - Bottom Image Name/URL

• Trax Product UUID

• Status

• Rejection/Deactivation reason

• Additional attributes added to the project by Trax

Important notes on the above excel/csv fields:​

1. Status can be either of the following values according to the request:​

   • active (for activating a pending or deactivated or rejected product)​

   • inactive (for deactivating an active product)

   • rejected (for rejecting a product)

2. When requesting deactivation or rejection of a product, you can provide a reason in the Rejection/Deactivation field​

3. Additional attributes added by Trax to the project can be also included in the file, in this case the column name should match the additional attribute's name​.

4. Files will be validated, during this validation it will only be checked if all rows of the file contain values for the following fields:

   1. Product name

   2. Brand name

   3. Client category

   4. Client Sub-Category

5. Rows failing this validation will be added to an error file, and Trax will only review the valid rows.​

Adding product images can be done

1. either by adding image URLs to the corresponding image fields in the CSV or Excel - when using this option, make sure that the image file(s) is (are) publicly available!,

2. or by adding the images to the ZIP file - in this case the corresponding image fields in the CSV/Excel need to contain the image name (without the extension).

Product update (regardless of sending 1 combined request or separate ones for validation and db upsert) is an async process, ie. the response contains a job ID which can be used to poll the API to get all available data incl. the status for the given upload.