Elbuz builds an XML feed for EVA.UA from your catalog at a permanent link, and EVA fetches your prices and stock from it every hour.
When you need this:
- You're starting on EVA Marketplace — the “EVA.UA (XML)” template already has EVA's required tags.
- In-stock products without an exact quantity — the feed gets a quantity by status, so EVA doesn't hide them.
- Descriptions contain links and images — Elbuz strips them from the feed, as EVA requires.
- Prices and stock change daily — the feed is rebuilt on schedule; EVA picks up changes without moderation.
Where to start: setup steps — from the Elbuz template to EVA auto-update.
What the EVA export can do
- Ready-made feed structure — EVA's required tags are filled in from the product card.
- Stock in the feed — the real quantity or a quantity based on the stock status.
- Clean descriptions — images and links are cut out.
- Permanent link — EVA fetches the file itself, and prices and stock update every hour.
- Assortment filtering — part of the catalog, a single warehouse.
The feed doesn't bring in orders. A separate connection fetches them — importing orders from EVA.UA.
How to connect EVA: from the template to products on the marketplace
- Prepare your product cards. Ukrainian name and description, manufacturer, photos and attributes — according to EVA requirements.
- Create an export template of type “EVA.UA (XML)”. Elbuz sets the template language to Ukrainian and the limit to 15 photos per product right away. The form warns you about the placeholder address https://site.com — replace it with your website address in the XML template.
- Narrow the assortment with a filter if you're not sending the whole catalog to EVA.
- Build the file manually with the “Export” button and open it via the link: check that all products are there and that names, brands and stock are filled in.
- Paste the feed link into your EVA account and turn on auto-update.
- Put the template on a schedule in Elbuz so the file is rebuilt with fresh prices and stock.
EVA matches your categories to its own by name, so name your categories the way they're named on the EVA website. EVA also matches attributes by name against its category's reference list; a value that isn't there yet is added by an EVA manager on your request.
What goes into the feed
| EVA feed tag | Where it comes from in Elbuz |
|---|---|
offer id | product number in Elbuz |
available | stock status: “In stock” — true, anything else — false |
price | product price |
price_old | old price — only when it's higher than the price, otherwise the tag is omitted |
stock_quantity | stock quantity (how it's calculated) |
currencyId | default currency |
category, categoryId | number and name of your category in Elbuz |
picture | product photos, up to 15 |
vendor | manufacturer |
article | manufacturer's SKU |
name_ua, description_ua | name and full description in Ukrainian |
name, description | name and description in Russian — only if Russian was enabled in the account when the template was created |
param | product attributes: name and value |
Elbuz cuts images and links, together with the link text, out of the descriptions that go into the feed: EVA doesn't allow them in descriptions. HTML markup for paragraphs and lists stays — the description goes inside CDATA, as EVA recommends.
1
Product row start2
Stock quantity3
Product name- Product row start — one offer per product, with its ID and availability.
- Stock quantity — the stock_quantity placeholder.
- Product name — the name_ua placeholder.
EVA doesn't allow changing product and category id values once the products are live on the website. In the template, these are Elbuz numbers, so they stay stable as long as you don't delete and recreate cards or categories. A new card gets a new number, and for EVA it's a different product.
How EVA sees stock
EVA shows a product as in stock only while stock_quantity is greater than zero and available is true. EVA treats an item without a stock tag as unavailable. That's why the EVA template has a dedicated {stock_quantity} placeholder:
| Product in Elbuz | What goes into stock_quantity |
|---|---|
| has stock, and the stock status gives a non-zero quantity | real stock quantity |
| no stock, status “In stock” | the quantity from the “Stock-based update setup” table, 1000 by default |
| status “Preorder” | real stock quantity, or 500 by default if there's none; available is false in this case, so EVA shows the product as unavailable |
| an out-of-stock status (in the default list — “Out of stock”) | 0, even if the card has stock |
You change the quantities per status with the “Stock-based update setup” button in the template form (how this table works). Set 0 for a status that shouldn't be sold on EVA, and the product goes into the feed as unavailable.
Stock in your feed doesn't change by itself after an order — EVA explicitly asks sellers to keep track of this. The new quantity reaches the marketplace with the next file, so the schedule frequency in Elbuz determines how quickly EVA sees that a product has sold out.
EVA product requirements
EVA checks not only the file structure but also the content of the cards. A summary of the requirements that most often lead to rejections:
| What | EVA requirement |
|---|---|
| File | UTF-8 encoding, static link, up to 300 MB |
| Name in Ukrainian | required, up to 255 characters; two identical names in a file aren't allowed; the brand in the name must match vendor. Formula: product type + brand + model + attributes + color + (SKU) |
| Name in Russian only | not allowed; without a Russian name, the product is shown only on the Ukrainian version of the website |
| Description in Ukrainian | required, 30 characters or more, no links, phone numbers, addresses, prices or promotions |
| Brand | required; a product without a brand — No Brand plus the actual country of manufacture in the attributes |
| Photos | 1 to 15, square, at least 512×512 (2048×2048 recommended), up to 10 MB; links without Cyrillic characters or spaces; no watermarks or black backgrounds |
| Attributes | at least 2, name and value filled in, value up to 255 characters |
| Old price | higher than the current price and reflects a real discount |
| Variants | each color, size or volume is a separate product with its own offer id |
Elbuz doesn't resize photos: the feed gets links to the images that are in the card. Prepare square photos at the required resolution in advance.
Requirements change, so check EVA's help center when in doubt:
- Підготовка прайс-листу XML (Preparing an XML price list) — tags, required fields, limits.
- Назва товару (Product name), Опис товару (Product description), Зображення товару (Product images), Параметри товару (Product parameters), Бренд товару (Product brand).
How to turn on auto-update in your EVA account
The feed doesn't update anything by itself — EVA has to fetch it. In your EVA seller account:
- Go to «Товари» → «Імпорт товарів» (Products → Product import).
- In the «Адреса XML файлу» (XML file address) field, paste the link to your feed from Elbuz.
- Select the update options you need — at least one.
- Check «Автоматичне оновлення увімкнено» (Auto-update enabled) and click «Зберегти» (Save).
The auto-update status changes from «Неактивне» (Inactive) to «Активне» (Active), and product prices and stock will update every hour. Auto-update doesn't add new products from the file: to get them into your account, click «Оновити каталог» (Update catalog) in the «Імпорт» (Import) section.
There are two schedules: in Elbuz the feed is rebuilt, and EVA fetches it every hour. Rebuilding the file more often than once an hour makes no sense. How to set up a schedule — “Running manually and on a schedule”.
Each feed import fully replaces your product list on EVA: anything missing from the current file is unpublished by EVA. Don't split the catalog into several files: EVA reads a single link, and anything in another file doesn't exist for it.
Which changes send a product to re-moderation
EVA re-checks a product when its content changes, but not when its price or stock changes:
| No moderation | Re-moderation |
|---|---|
price, old price, stock, available, SKU, exchange rates | name, description, brand, photos, category or its name, attributes |
A change in the file structure also triggers moderation — even replacing one tag with another that has the same value. So don't edit the EVA XML template unless you need to: the default one already matches EVA's format. And make bulk changes to names, descriptions or photos in batches, so your products don't all disappear from sale at once.
Scenarios
Only a few categories on EVA
On the template's “Export limit (filter)” tab, set a condition by category or manufacturer. Only products that meet the condition go into the file, and EVA unpublishes everything that dropped out of the file at the next import. Restore the condition and the products come back with the same numbers.
Sell only what's in one warehouse
On the “Data export settings” tab, select a warehouse in the “Warehouse ID” field. Only products that are in stock at that warehouse go into the file. When a product sells out there, it disappears from the file, and EVA unpublishes it instead of showing it as out of stock.
The warehouse only selects products: the quantity in stock_quantity and availability come from the product's total stock and status, not from that warehouse.
A temporarily unavailable product shouldn't disappear from EVA
Keep the product in the template's filtered set and give it an out-of-stock status (“Out of stock”). It goes into the feed with available="false" and stock 0: the product page on EVA stays, but the product can't be bought. When it's back, restore the status — EVA picks up the availability within an hour, without moderation.
Supplier products without exact stock
Products from supplier price lists often have the “In stock” status but an empty stock quantity. They go into the feed with the quantity from the status (1000 by default). To be more cautious, set a lower quantity for the “In stock” status in this template's “Stock-based update setup” table.
What to do when EVA doesn't import the feed
EVA shows import errors in the seller account. The most common ones:
| What you see | Why | What to do |
|---|---|---|
| «403 Заборонено» (403 Forbidden), «429 Забагато запитів» (429 Too many requests), «Помилка з'єднання» (Connection error) | the file is on your own server (the template copies it there via FTP), and bot protection blocks EVA. This doesn't apply to a file at an Elbuz link | allowlist the IPs 138.197.179.150 and 164.92.129.224 and the User-Agent EvaMerchantBot/1.0 |
| «404 Ресурс не знайдено» (404 Resource not found) | there's no file at the link in your EVA account — the file name was changed in the template, the template was deleted, or it has never been exported | run the export and compare the link in your account with the link in the template up to the “?” character — the tail after it changes with every run and doesn't affect the address |
| «401 Доступ обмежено» (401 Access restricted) | the file is password-protected, but EVA fetches the feed without authentication | give EVA a public link without a login and password |
| «Неможливо декодувати вміст XML-файлу за допомогою UTF-8» (Unable to decode the XML file content using UTF-8) | the file isn't saved in UTF-8 | make sure the encoding in the template header <?xml … encoding="UTF-8"?> hasn't been changed |
| «Розмір файлу не повинен перевищувати 300 МБ» (File size must not exceed 300 MB) | the feed has too many products or large descriptions | remove what you don't need with the template filter; you can't split the feed into parts (why) |
| Products show as out of stock on EVA, although they're in stock in Elbuz | available is false — the product status isn't “In stock” (for example, “Preorder”), or custom text is entered for it in the status table; stock_quantity is 0 — the status has quantity 0 in the table |
check the stock status and the template's quantity table (how it's calculated) |
| Products keep going to moderation | names, descriptions, photos or the XML template itself change | don't edit the template unless you need to; change content in batches (what triggers moderation) |
| Some products disappeared from EVA | they're missing from the latest file: they dropped out of the filter or sold out at the selected warehouse | bring the products back into the template's filtered set; keep temporarily unavailable ones in the feed with an out-of-stock status |
To investigate, EVA support asks for the exact error text, the feed link and the time of the import attempt — full list of errors in EVA's help center.
FAQ
Why not via the API, like orders?
The EVA API doesn't handle products, prices or stock — only orders. EVA accepts the catalog only as an XML feed at a link.
Do I need a Russian name?
No, the Ukrainian name and description are required. Without Russian ones, the product is shown only on the Ukrainian version of the EVA website. The template adds them automatically if Russian was enabled in the account when the template was created.
Does Elbuz fill in EVA category and attribute codes?
No. The template passes your categories and attributes by name, and EVA matches them to its own by name. The template has no eva_id, paramid or valueid attributes.
How quickly does a new price appear on EVA?
After the next export in Elbuz and the next hourly fetch on EVA. A price change doesn't need moderation.
How do I get orders from EVA?
With a separate import template using your EVA account login and password — orders from EVA.UA. Order items find your cards by the same product number as in the feed.
Where to find it and who has access
- Menu
- Directories → Operations → Data export
- Create
- “Add” → type “EVA.UA (XML)”
- Access right
- the “Export” and “Export Template Setup” windows in “Group permissions”
- Have ready
- Ukrainian names and descriptions, manufacturer, square photos from 512×512
One template — one feed. The general template mechanics — filtering, the file at a link, the schedule, the log — are in the article on exporting products; here, only what's specific to EVA.
1
Template name and type2
Data selection checkboxes- Template name and type — EVA.UA (XML) with its ID in the form header.
- Data selection checkboxes — Categories, Products and the other data included in the feed.
Related topics
- If you need to fetch orders from EVA — orders from EVA.UA via API.
- If a product didn't get into the file, or you need to set up filtering and the schedule — Exporting products to a marketplace, website and file.
- If you also list products on Epicentr — Exporting your catalog to Epicentr.
