For AI assistants: this page as plain markdown is at https://docs.voicelogica.ai/raw/integrations/eshops/xml-feed.md, and https://docs.voicelogica.ai/llms.txt lists the docs by topic, one file each, small enough to read whole. Read those rather than this HTML page.
XML product feed
Ce contenu n’est pas encore disponible dans votre langue.
The XML product feed gives the agent your catalogue when your shop runs on a platform without a native connector, or when product questions are all you need. Voice Logica reads the same XML feed you publish for Skroutz, Google Shopping or car.gr, either from its URL on a schedule or once from a file you upload, and the agent searches it during the call: a caller asks for a product in their own words and the agent tells them the name, a short description and whether it is in stock. The feed is catalogue-only. It does not recognise callers, read orders or place orders; for that, use WooCommerce, Shopify, Magento, OpenCart or PrestaShop.
There is no Catalogue card and nothing to connect under Integrations. The feed is set on the agent itself: My Agents - agent - Skills - Tools & Workflows - Eshop Integration (XML feed). Each agent that should answer product questions gets its own feed settings.
What you need before you start
Section titled “What you need before you start”A product feed in the Skroutz XML format (developer.skroutz.gr/el/feedspec/), the Google Merchant format or the car.gr dealer format. Most Greek shop platforms and Skroutz, Google Shopping or car.gr plugins already generate one. You can give it in two ways:
- Feed URL. Reachable from the internet without a login or IP restriction, returning XML (gzip or zip is fine), not a JSON or HTML page. Redirects are followed. The catalogue refreshes on its own.
- XML file. The same XML saved as
.xml,.zipor.gz, up to 50 MB. Use it when the feed has no public URL. A file is imported once and never refreshes on its own.
Supported feed formats
Section titled “Supported feed formats”| Layout | Example |
|---|---|
| Skroutz, under any root name | <mywebstore><products><product> (also webstore, store, storedata or any other root) |
| Products list at the root | <products><product> |
| Products directly under the root | <catalog><product> or a single <product> |
| Google Merchant (RSS) | <rss><channel><item> with g: tags such as <g:id>, <g:price> |
| Atom | <feed><entry> |
| car.gr dealer feed | <cardealer><classifieds><classified> |
| Wolt-style item list | <root><item> or <root><items><item> |
The fields the agent uses, per product. The name in brackets is the accepted alternative, and Google g: tags work as they are:
| Field | Used for |
|---|---|
id (g:id) | Identifies the product between refreshes |
name (title) | What the agent reads out |
link | The product page |
price_with_vat (price) | The price |
availability (instock Y/N, quantity) | Whether it is in stock |
description | Matching requests by meaning, see Writing product descriptions callers can find |
category (product_type) | Narrowing the search |
manufacturer (brand) | Brand questions |
mpn, ean (gtin), sku | Codes callers read out, see Product identifier field |
image (image_link) | Product image |
Any other tags in a product are kept as extra product data.
car.gr dealer feeds
Section titled “car.gr dealer feeds”The car.gr format, common for car-parts shops, is read as it is: unique_id identifies the part, title is the name, mpn (or manufacturer_number) the part code, price the price, the first of the photos is the image and condition (for example used) is kept. The vehicles in makemodels are added to the end of the description as “Compatible vehicles: MITSUBISHI SPACE STAR (2019+)”, once each, so a caller who names their car finds the parts that fit. Every listed part counts as in stock. Set Product identifier field to MPN so callers can read out the part number.
Wolt-style feeds
Section titled “Wolt-style feeds”Item lists such as the ones made for Wolt are read too, whatever the case of the tag names: Product_ID, Name, Price and Stock work like id, name, price and availability. Stock (or instock) of Y, yes, 1 or true means in stock; N, no, 0 or false means out of stock. parent_id groups the variants of one product, idiotita or epilogi (for example a size or flavour) is kept as the variant option, and category_name is the category. Check that the feed carries your shop prices: a feed made for a delivery platform often has that platform’s prices, and the agent quotes the prices in the feed.
Bundle offers
Section titled “Bundle offers”If your shop sells bundles (a set of products at a discount), give the agent your bundle list as well, in Bundles feed URL. It is a JSON or CSV file with one row per combination:
| Column | Meaning |
|---|---|
bundle_id | The bundle, the same id on every row of that bundle |
bundle_name | The bundle name |
bundle_discount | The amount taken off the items’ total |
bundle_items_ids | The products in this combination as id x quantity, separated by |, for example 24229x1|4142x1 |
The list is read again with every refresh of the feed, and with every file import. Each combination becomes one product the agent can find and quote. Its price is the current price of its items minus the discount, never below zero, and it is out of stock when any of its items is. A combination with an item that is not in your product feed is skipped, so keep every bundled product in the feed. If the bundle list cannot be read, the products still sync, and the bundles stop showing until the next refresh that reads the list.
Catalogue filters
Section titled “Catalogue filters”When one word matches many products, for example a butcher’s shop where “beef” fits dozens of cuts, give the agent Catalogue filters. These are columns such as Animal (Pork, Beef, Lamb) or Cut (Shoulder, Ribeye, Mince), each with a fixed list of values.
- Sync the products first, then click Propose from the products under Catalogue filters.
- Each attribute in the
<attributes>block of your feed is checked and labelled: Usable as a filter, Some products lack it (for a filter column, the AI fills the products that lack it), Number (weights, prices: not a choice filter), Same for all, Different on every product or Too many values. The list is under All feed attributes, with a search box; fields on under 1% of the products are hidden until you click Show all. - The proposal uses the suitable attributes and merges their spellings into one value each, so Γουρούνι and Χοιρινά both become Χοιρινό. It also adds columns that your product names show but your feed lacks.
- Edit the column names and values, remove what you do not want, and Save the agent.
After you save, and after every sync, each product gets one value per column. The value is read from the feed attribute when the product has one. Otherwise the AI picks one from the list. The AI adds a new value only when none of the listed ones means the same, and you see it in the list next time.
During a call the agent sets the filters to what the caller said and searches only the products that match all of them. When more products still match than the agent reads out in one search, it does not read a list. It asks the caller to choose first, for example “Which cut would you like: shoulder, ribeye or mince?”, and then searches again.
Each search starts from what the caller said for that product, so a filter from the previous product is not carried over. A product that has no value in a column (for example no Origin in the feed) is not left out by that filter: the agent hears it as “not stated”. When no product matches every filter, the agent gets the products without the filter that cut them all and tells the caller which condition it dropped.
Number filters
Section titled “Number filters”A column can also be a Number, for limits callers set: Price per kilo (€/kg), Price, Pack weight, Aging days. Pick where the number comes from: a feed attribute (for example price_per_kg), the product’s own price or weight, or, when the column has neither, the product text, read by the AI. Give it a unit.
When the caller says “under 15 euros a kilo”, “between 10 and 20”, “at least 21 days” or “about a kilo”, the agent searches with <, <=, >, >=, between or around. Around covers ± a share of the value you set per column (20% by default) and lists the closest products first. When the caller asks for the cheapest, the agent sorts by price.
If you sell by the kilo, do not add a weight column. A caller who says “a kilo and a half of mince” is telling you how much to cut, not looking for a 1.5 kg product. Add a weight column only for fixed packs of different sizes.
Several values, “not”, and a catalogue per customer
Section titled “Several values, “not”, and a catalogue per customer”A caller can name more than one value of a filter, or rule one out. “Fresh or frozen beef” searches both values; “not frozen” leaves out the frozen products. Products that state no value in that column still come up, as with any filter. The agent uses only values the caller said.
When your catalogue is split per customer (each customer’s products carry their VAT number in the category), the agent searches the calling customer’s products first. If the caller asks to look further (“search the other catalogues”), it repeats the same description in the other customers’ products and says whose catalogue each one is in. The next product starts again from the calling customer. There is no search across every catalogue at once.
Checking and fixing the filters
Section titled “Checking and fixing the filters”Under each value you see how many products carry it, and each number column shows its range. To join two values that mean the same, use Merge: the old value becomes an alias of the other, and its products move across when you save, without the AI classifying them again. Use the same alias list for spellings your feed uses.
Shops where each category has its own fields
Section titled “Shops where each category has its own fields”In some catalogues every category has its own fields: basins have a basin type, shower doors an opening, mirrors a shape. One set of columns cannot fit them all. Turn on Narrow searches by each category’s own fields instead.
When a search finds more products than the agent reads out, the agent looks at the fields those products share in your feed and asks the caller with their values, for example “Wall-hung or floor-standing?” or “Chrome or black matt?”. It then searches again with the value the caller chose. Values come only from your feed: nothing is filled in by the AI, and a value counts only when the caller said it.
Fields by category shows your largest categories with the fields their products carry and how many of them carry each. The names are written once by the AI from the feed’s own field names (for example typosNiptira becomes Basin type). Leave the switch off when one set of filters fits every product, as in a butcher’s shop.
Order lines identified by description
Section titled “Order lines identified by description”For catalogues where sellers dictate orders in their own words («two kilos of neck, boneless») and many products differ by a single detail, the agent can identify each line to one product code by asking. It is switched on per agent, for now through the Claude or ChatGPT connection: ask it to read the catalogue for product identification, check the readiness report, and then turn on product identification for the agent.
- Reading the catalogue. The AI reads every product once into a few details (animal, cut, bone, skin, fresh or frozen, processing, packaging, origin, size). Only new or changed products are read again on the next run, and corrections you make are kept.
- On the call. After the seller has dictated the order, the agent works line by line: it asks only about a detail that tells the remaining products apart, names every option there is, and never asks the same thing twice. When a size is not in the catalogue it says the closest sizes and asks which to keep. Products only their names tell apart are read out by name.
- Nothing gets lost. Every line stays in the order: with its code, or as the seller said it. The agent reads the whole order back, and the call does not close while a line has neither a code nor the seller’s OK to keep it as said.
- Readiness report. Before switching it on, the report shows how many products could not be read yet, how often each detail is known, and per customer the groups of products that nothing tells apart. Fix those with clearer product text first.
Product search keeps working as before; agents without the setting are not affected.
What you enter
Section titled “What you enter”.xml, .zip or .gz file, up to 50 MB, then Import products.https:// or http://, for example https://myshop.example/feeds/products.xml.?modifiedSince= parameter. Otherwise every refresh reads the whole catalogue, which is the safe default.Writing product descriptions callers can find
Section titled “Writing product descriptions callers can find”The agent matches what the caller says against the name and description of each product in your feed, by keyword and by meaning at the same time. A request such as “something to keep coffee hot” can find a thermos even when neither word is in its description. This works on every plan, needs nothing turned on and uses only the text in your feed, so the name and description decide how well products are found. In each description, include:
- Everyday names and synonyms. The words customers actually say, not only the catalogue name: “kettle” as well as “electric water boiler”, common misspellings, and both the Greek and the English term where customers use either.
- Use and application. What the product is for and where it is used: “for outdoor use”, “suits small kitchens”, “for 4-6 people”.
- Key specs. What callers ask about: size, capacity, power, material, colour, compatibility.
An empty description, or one that only repeats the product name, gives the agent nothing to match by meaning. Description changes are picked up at the next refresh; click Sync now to apply them straight away.
First setup
Section titled “First setup”-
Open My Agents, pick the agent, then Skills - Tools & Workflows.
-
Turn on Eshop Integration (XML feed) and click Configure.
-
Paste the Feed URL, choose the Refresh interval and the Product identifier field, and click Save in the settings window.
-
Save the agent. The feed can only be synced or viewed after the agent is saved.
-
Click Sync now on the card to read the feed straight away instead of waiting for the first scheduled refresh. Give it a few minutes, then click View products to confirm your products are there.
-
Call the agent (or use Try this agent) and ask for a product the way a customer would, for example “Do you have a smart kettle?”. The agent should name matching products from your feed and say whether they are available.
Importing from a file
Section titled “Importing from a file”-
Open My Agents, pick the agent, then Skills - Tools & Workflows. Turn on Eshop Integration (XML feed) and Save the agent once, so the tool exists before the import.
-
Click Configure, set Products from to XML file (imported once) and pick the Product identifier field.
-
Drop your
.xml(or.zip/.gz) file and click Import products. A message shows how many products were imported. Click Save in the settings window and Save the agent. -
Click View products to check them.
To update the catalogue later, import the new file the same way. Each import is a full one: products already there are updated, never added a second time, and products that are no longer in the file are taken out of the agent’s answers. Sync now is hidden while the products come from a file, because there is no URL to read. To go back to a feed URL, set Products from to Feed URL, paste it and Save.
What the agent can do
Section titled “What the agent can do”| Job | What happens on the call |
|---|---|
| Product questions | Searches the catalogue as soon as the caller mentions a product or reads out a product code, trying several spellings and the English term at once, and reads back name, short description and availability. |
| Follow-up questions | Searches again when the caller narrows the request (“a smart one”, “in black”). |
| Alternatives | Suggests similar products only when the caller asks for alternatives. |
Troubleshooting
Section titled “Troubleshooting”Why do Sync now or View products for my XML feed say to save the agent first?
The XML feed settings are stored with the agent. Save the agent after entering the Feed URL, then use Sync now or View products.
Why did the XML feed tool switch itself off and we got an email about access denied?
The XML feed returned 403 (forbidden), so Voice Logica turned the tool off on that agent and emailed your company’s notification addresses. The feed is behind a login, an IP restriction or a firewall rule. Make it publicly reachable, then turn Eshop Integration (XML feed) back on and Save.
Why did we receive E-shop Sync Failed emails about our XML feed?
Each failed refresh of the XML feed sends an email numbered out of 3. After 3 failures in a row the XML feed tool is turned off on the agent. Open the Feed URL in a browser to check that it loads and is valid XML, fix the feed, then turn the tool back on and Save. A successful refresh resets the count.
Why does my XML feed sync fail with ‘No products found in the feed’?
The feed loaded but its layout is not one we read. The error names the root tag it found, for example root found: <shopdata>. Change the feed to one of the supported formats, most simply <products><product> inside any root, then Sync now.
Will importing the same XML file again create duplicate products?
No. Each product is matched by its id (unique_id in car.gr feeds), so importing the same or a newer file updates the existing products. Products missing from the new file are removed from the agent’s answers.
Why do the products from our XML file not update by themselves?
A file is imported once: there is no URL to read again, so there is no scheduled refresh and no Sync now. Import the new file under Configure, or switch Products from to Feed URL if your feed has a public address.
Why can't the agent find a product from our XML feed when the caller reads out its code?
The agent matches spoken codes against the Product identifier field. Set it to the code your customers actually see (for example SKU if that is printed on your site), Save and Sync now. For MPN, EAN, Skroutz ID and Group Code only the digits are kept; SKU keeps letters and dashes.
