POS Integrations
Custom product data
Product fields

Product fields

These are the main fields your products.csv file should contain.

Required fields

barcodeIdentifier to link to products in your stock.csv file.
brandName of the brand or manufacturer that produced the item.
titleCustomer-facing product title.
image_urlPublic HTTP or HTTPS image URL for the product. Should be at least 250x250 pixels in size.
descriptionProduct description, ideally between 100 and 4000 characters long.

Optional fields

linkOnline product page URL, if any. Optional.

Condition of the product. Defaults to new.
Valid options: new, refurbished, used

categoryOptional Google product taxonomy value (opens in a new tab). Example value: Home & Garden > Lighting

Additional fields for apparel

For apparel products, there are a few other fields to give shoppers a better experience searching for these types of products.

Whilst they are currently not required, depending on the requirements of our upstream providers, we might make these properties required in the future.

age_groupoptionalAny of: newborn, infant, toddler, kids, adult.
genderoptionalAny of: male, female, unisex.
coloroptionalAny string, for example blue.
sizeoptionalAny string, for example 16/34 or XL.
item_group_idoptionalUsed to group variants of the same product. This property is required if there’s more than one product in the same set (i.e. different sizes or colors of the same product). Set it to the same value for each of the products in one set. This value can be any alphanumeric string, e.g. an UUID.

Additional fields for weighted product

For weighted products, we suggest specifying the measure of your product. The unit_pricing_measure attribute allows customers to understand the exact cost per unit of your product.

If your product falls into any of the mentioned categories and customers are likely to be interested in its price per unit, it is recommended that you include the unit pricing measure attribute.

Here are some examples of product categories that commonly employ this attribute:

  • Food
  • Drinks
  • Flooring
  • Perfume

To ensure that Google understands the data you submit, adhere to these formatting guidelines:

  • Type: A positive number followed by the respective unit.
  • Supported units:
    • Weight: oz, lb, mg, g, kg
    • Volume (US imperial): floz, pt, qt, gal
    • Volume (metric): ml, cl, l, cbm
    • Length: in, ft, yd, cm, m
    • Area: sqft, sqm
    • Per unit: ct


Let's say you submit '10 EUR' for the price, '500 grams' for the unit pricing measure attribute, and '1 kg' for the unit pricing base measure attribute. In this case, the unit price would be 20 EUR per kilogram.

    "unit_pricing_measure": "500g",
    "unit_pricing_base_measure": "1kg"


unit_pricing_measureTo specify the measure of your product, particularly for weighted products, you can make use of the attribute called unit_pricing_measure. This attribute allows customers to understand the exact cost per unit of your product.
unit_base_pricing_measureThe unit_pricing_base_measure attribute enables you to convey the price conversion of your product based on a specific unit. For example, if you were selling a 150-milliliter bottle of perfume, this attribute would allow you to present customers with the cost of your perfume per 100 milliliters.