Prepare your product feed

A product feed is the XML file your shop already produces for price comparison or advertising. When you add it as a source of a knowledge base, the AI can search it and recommend products. The cleaner the feed, the better the matches. This page lists what to check before you add it.

Use a standard feed format

Use a Google Merchant feed, the XML format with g: fields such as g:title and g:price. Amio also reads Heureka and Zbozi style feeds and similar custom XML. It recognises the common fields by name, whatever the prefix or letter case, so g:title, title and PRODUCTNAME all count as the product name. Amio works out which tag is which during the first indexing. You do not map fields by hand.

Only XML feeds are supported as a product source. The feed file must already exist at a URL that opens without a login. A feed that is built only when someone requests it is not accepted.

What each product should contain

The AI answers from what it can read in the feed. Make sure every product has these fields, using the Google Merchant name:

Field	Why it matters
id	A unique, stable ID. Amio uses it to update the product on the next indexing. Without it, products can be duplicated or missed.
title	What the AI matches the customer’s words against.
description	Extra detail the AI can use to answer questions.
link	The product page. The product card links to it.
image_link	The picture on the product card.
price, sale_price	Shown on the card. Include the currency in the price, for example 3199 CZK. If there is no separate currency field, Amio reads the currency from the price.
availability	Products marked out of stock are not indexed, so the bot does not recommend them.
brand, product_type (or google_product_category), color, size, gender, material, age_group	Searchable and filterable attributes. The AI uses them to narrow the results, for example “black running shoes in size 42”.

gtin, mpn and condition are also recognised.

Write good titles and descriptions

• Keep entries short. A very long description makes indexing slower and more expensive. A product whose text is too long is skipped, and the knowledge base status shows a warning with the count.
• Use one pattern for titles: brand, product name, then key attributes. Example: Nike Air Max 270 - Men's running shoes, black/white.
• Start the description with a short overview and then the key features. Leave out marketing slogans and put specifications first.
• Do not paste HTML into descriptions.

Categories and attributes

• Give every product a category path, for example Men > Shoes > Sneakers or Men | Shoes | Sneakers. Amio splits it at >, |, › or » and keeps every level, so the AI can filter on any of them. Do not use / as a separator.
• Use the same words in every product. “Sneakers” in one product and “trainers” in another splits the results.
• Put synonyms customers use in the title or description, for example both “sneakers” and “running shoes”.
• Keep one attribute per field. Put the size in size, not in the title.

Sizes and colours as separate rows

Many shops list every size as its own row. Amio can merge rows that share an item_group_id into one product, with the sizes and prices as a list. This keeps ten sizes of the same shoe from filling the whole answer. Fill in item_group_id on every variant if your feed has it.

Add to cart from the chat

When your website registers onAddToCart, product cards in the webchat let shoppers pick a variant and add it to their cart. The cards are built from the feed:

• Every variant needs its own row, with an ID your cart accepts. By default that is the item ID (g:id in a Google feed), and it is what your onAddToCart handler receives as variantId.
• Rows of one product share an item_group_id. The card then shows one product with all its variants.
• g:size and g:color become the chips the shopper picks from, or a dropdown when an option has more than 8 values. An option with the same value on every row, such as one colour for all sizes, is not shown. A row without item_group_id is one variant with nothing to pick, so its card shows only the button.
• A card offers at most 50 variants.

If your cart expects a different ID, for example g:variant_id or the GTIN, tell Amio support which tag holds it. They set it as the Variant ID Tag of your feed. After any of these changes, reindex the feed.

Things to avoid

• Duplicate products that differ only slightly. Use variant fields instead.
• Missing or wrong IDs, GTINs or SKUs.
• Overloaded titles.
• Long descriptions that mix marketing text and technical data.
• Purchase prices or margins in the feed. Amio drops fields it recognises as cost or margin data, but it is safer not to publish them in the feed at all.

After you change the feed

Amio reads the feed when you index it. Open the knowledge base, run Reindex now, and check the result in the Explorer tab. See Knowledge bases.