Omacro
Book a Demo
Help Center

omacro.com

Supplier Catalogs

Supplier product catalog file format

Reference guidance for supplier product catalog files, including core identifiers, product grouping, market data, and validation expectations.

A foundational element of the omacro platform, the supplier catalog enables extended features and control. You may make product additions, edits or deletions direct from the Product Management portion of the admin. You can also download and upload/import edits, deletions and additions in bulk. The site supports both .CSV and XLSX file formats with the following fields (see sample file included and please note that the data in file is purely for example purposes).

There is no need to delete products from your omacro catalog (even if they have been discontunied or are no longer on your website). Maintaining older products will preserve analytics associated with legacy products.
Supplier Product Catalog File Format illustration 4
  • Parent Identifier
  • Brand
  • Model
  • SKUs
  • GTINs
  • Short Description
  • Product Groups
  • Attributes
  • MAP Price
  • Launch Date
  • Command

Field Details

Parent Identifier: (not required) This is a unique value (can be any value you like) that is used to associate a group of product variants (parent/child relationships) together. This field is not required unless you would like to group products together and can be used in conjunction with the "Attributes" field to distinguish variant products within the Buy Now popup. Leave this field blank though if only one product needs to be represented (default scenario) and does not contain a variant (parent/children) product(s).

Brand: The name of the brand that is registered within the Brands management page in the My Account section of the admin. This field is required.

Model: The model of the product. This field is required.

SKUs: This field can contain a list of SKUs that are associated with the product. Each value should be separated by a semicolon (1000-240V;1000-110V;1000-230V). In some cases your model and SKU may be the same. You can include multiple versions of the SKU which can improve product matching with sellers. This can come in handy if you have different SKUs for different regions or customers, i.e. 1000-240V, 1000-110V and 1000-230V. This field is required.

GTINs: This field can contain a list of GTINs that are associated with the product. Each value should be separated by a semicolon (12345;67890;111222). You can have multiple GTINs on a single model, however you cannot have multiple GTINs spread across multiple products. This field is not required (but recommended for better product matching).

Short Description: The product short description (typically 40 to 60 characters). This will show at the top of the Buy Now popup to consumers and is recommended, however this field is not required.

Product Groups: The name of the group or groups the product should be associated with. The group name must be defined in the Product Groups management page in the Products section of the admin and can be separated by a semicolon (Default Group;Online Sales;West Coast). This field is not required.

Attributes: A list of attributes associated with the product or variant to help describe parent child options such as color and or size. The value is stored in the format of the attribute name and separated by a colon to associate the value of that attribute. Multiple attributes can be defined by simply separating these values by a semicolon (Color:Red;Size:Large). The example here for variant attributes may not be real-world for your products (i.e. color:red;handles:included;accessories:yes). We suggest going with the basics that customers will shop by and only things where the products that are part of the same family have differences (i.e. color, length, etc.). It does not help to add attributes that all the products have. This is not a sales tool, but a refinement tool to filter retailer results. This field is not required unless you use Parent Identifier.

MAP Price: The Minimum Advertised Price of the product (for USA market only). A numeric field that does not contain currency symbol (no '$'). This field is not required.

Launch Date: The GMT date and time a product is scheduled to launch. Setting this date tells Omacro automated processes to run more frequently, up to a few days after the product launch, to increase the likelihood of acquiring dealer links. This field also prevents dealers from seeing the product prematurely in their feeds. This field is not required.

The date and time format can vary:
1/1/2025

01-21-2025

2025/01/23

2025-1-23

1/17/2024 1:36

1/1/2015 3:30PM

1/1/2025 18:00:00

1/1/2028 5:00PM+0200 (includes a time zone offset)

Command: The command field tells the feed processor what to do with the product line item (Insert, Update, Delete). This field is not required. Insert is assumed by default if no value is entered.