Elbuz builds an XML feed for Kasta from your catalog at a permanent link. Kasta HUB fetches new products, prices and stock from it itself.
When you need this:
- You're starting on Kasta — the “Kasta (XML)” template already has the tags Kasta requires.
- Categories are matched for Rozetka — Kasta maps them by the Rozetka code.
- In stock without an exact quantity — the feed gets a quantity by status, so Kasta doesn't hide it.
- Prices and stock change daily — the feed is rebuilt on a schedule; Kasta picks up changes hourly.
Where to start: setup steps — from the Elbuz template to the feed in HUB.
What the Kasta export can do
- Ready-made feed structure — the tags from Kasta's instructions are filled from the product card.
- Rozetka category codes — in
rz_id, so Kasta matches categories itself. - Stock and old price — always in the feed, so the product stays on sale.
- Permanent link — HUB fetches the file on its own.
- Assortment filtering — only the categories or manufacturers you need.
The feed doesn't bring in orders. A separate connection handles them — importing orders from Kasta.
How to connect Kasta: from template to products in HUB
- Prepare the product cards. Ukrainian name and description, manufacturer, SKU, photos; for clothing and footwear — the attributes “Колір” (Color) and “Розмір” (Size) (why).
- Match categories with Rozetka if you haven't yet: their codes go into the feed (category matching).
- Create an export template of the “Kasta (XML)” type. Elbuz sets the template language to Ukrainian (if it's enabled in your account) and a limit of 20 photos per product. The template takes the site address for the header from your details; if the placeholder https://site.com is left, the form warns you — replace it. Replace the MyStore placeholders in the header's
nameandcompanytags with your store name. - Build the file with the “Export” button and open it via the link.
- Add the link in Kasta HUB and turn on the updates you need (how).
- Schedule the template in Elbuz so the file is rebuilt with fresh prices and stock.
What goes into the feed
| Kasta feed tag | Where it comes from in Elbuz |
|---|---|
offer id | the product number in Elbuz — digits only, no Cyrillic or spaces, as Kasta requires |
category, the rz_id attribute | the number and name of your category; rz_id is the Rozetka category code, only if it's filled in for the category |
available | stock status: “In stock” — true, anything else — false |
price | product price |
price_old | the higher of the old price and the price — the tag is always there |
stock_quantity | stock (how it's calculated) |
picture | product photos, up to 20 |
vendor | manufacturer |
article | manufacturer SKU |
name_ua, description_ua | name and full description in Ukrainian |
name_ru, description | name and description in Russian — only if both Ukrainian and Russian were enabled in the account when the template was created |
param | product attributes: name, value, unit of measure |
Elbuz strips images and links from descriptions, together with the link text: Kasta doesn't allow them in descriptions. Kasta itself truncates descriptions longer than 5,000 characters.
1
Offer row2
Stock quantity3
Old price formula- Offer row — each product becomes an offer with its ID and availability status.
- Stock quantity — the stock quantity placeholder is written into the feed.
- Old price formula — the old price is the greater of the old price and the current price.
Kasta doesn't allow changing a product's id after publication, and category ids must stay the same. In the template these are Elbuz numbers, so they stay stable unless you recreate products or categories.
Without rz_id, you match the category manually with a mapping file in HUB (the “Категорія+” section). Kasta matches attributes by name; unknown names are matched in the same place, in “Каскад+”. Elbuz doesn't fill in Kasta's own category and attribute codes.
How Kasta sees availability and price
Kasta takes stock from stock_quantity, and with available="false" treats it as zero whatever the quantity. That's why the Kasta template uses the {stock_quantity} placeholder:
| Product in Elbuz | What goes into the feed |
|---|---|
| has stock, status “In stock” | actual stock, available="true" |
| no stock, status “In stock” | the quantity from the “Stock-based update setup” table, 1000 by default |
| status “Preorder” | actual stock or 500 by default, but available="false" — so stock on Kasta is 0 |
| an out-of-stock status | 0 |
You change the quantities per status with the “Stock-based update setup” button in the template form (how this table works).
Price. Kasta requires the recommended (crossed-out) price to be no lower than the selling price, and without it reports an error. That's why price_old in the template is always the higher of the old price and the price: a product without a discount goes with equal values. Kasta advises setting the selling price with its commission (royalty) included.
How variants are grouped into one product page
Kasta groups products into one product page by SKU + Brand + Color + Size. Variants of one model share the same article, vendor and category; color and size are passed as attributes.
- Clothing and footwear — the “Колір” (Color) and “Розмір” (Size) attributes are required. Add them to Elbuz products with exactly these names: they go into the feed as
paramlines. - No size range (shampoo, a battery): Kasta sets the size to “-” itself, and if there's no color — “комбінований” (combined) or “не визначено” (undefined).
- Don't put the color in the name — Kasta may remove from the name whatever is passed as a separate attribute.
- Packaged dimensions and weight affect shipping calculation. The template doesn't have them. Add attributes named “Габарити в упаковці, см” (Packaged dimensions, cm) and “Вага в упаковці, кг” (Packaged weight, kg) — without them Kasta uses the category averages.
Kasta locks this set to the product page. Change any of them in the feed and Kasta treats it as a new product that goes through moderation again. To change them, delete the product in HUB and upload it again.
How to add the feed in Kasta HUB
- In your HUB account: “Товари” → “Імпорт новинок” → the “XML” tab → “Додати новий фід” (Products → New product import → XML → Add a new feed).
- Paste the feed link from Elbuz and select the settings:
- “Завантажити товари з xml” (Upload products from XML) — turns the feed on: new products and updates;
- “Оновлювати ціни”, “Оновлювати стоки”, “Оновлювати контент” (Update prices, Update stock, Update content) — what to take from the file from now on;
- “Зняти з продажу товари, які відсутні в фіді” (Take products missing from the feed off sale) — products not in the file get their stock reset to zero;
- “Використати ціну продажу, якщо немає рекомендованої ціни” (Use the selling price if there's no recommended price) — not needed for the Elbuz template, it always has
price_old.
- Save. The feed gets its own number, which tags every product uploaded from it.
Kasta limits: file up to 1 GB, upload up to 45 minutes, up to 3 active feeds at a time. To turn a feed off, clear all the checkboxes. Clearing “Завантажити товари з xml” alone isn't enough if “Оновлювати стоки і ціни окремо” (Update stock and prices separately) is still on. You can't delete a feed in HUB.
What updates and how often
| What | How often |
|---|---|
| prices and stock | roughly once an hour; with “Оновлювати стоки і ціни окремо” (Update stock and prices separately) — every 30 minutes |
| full processing of the feed with new products and content | in the shared queue, roughly up to 6 hours; a file whose header date hasn't changed — once every 4 hours |
| name, description, photos, attributes | only with “Оновлювати контент” (Update content) on, and only for products uploaded by this feed |
The Elbuz template puts the date in the header on every run, so HUB sees the file is new. There are two schedules: Elbuz rebuilds the feed, HUB fetches it. Rebuilding the file more often than every 30 minutes is pointless. How to set a schedule — “Manual and scheduled runs”.
Scenarios
Only a few categories on Kasta
On the template's “Export limit (filter)” tab, set a condition by category or manufacturer. Products dropped from the file go off sale only if “Зняти з продажу товари, які відсутні в фіді” is selected in HUB; otherwise they stay with their last stock.
A temporarily unavailable product shouldn't disappear
Keep the product in the filtered set and give it an out-of-stock status. It goes into the feed with stock 0: the product page on Kasta stays, but nobody can buy it. Set the status back and Kasta picks up availability with the next price and stock update.
Clothing in several colors and sizes
Each color and size is a separate Elbuz product with the same SKU, manufacturer and category, plus the “Колір” and “Розмір” attributes. In the feed these are separate offer elements, and on Kasta — one product page with a choice of color and size.
What to do when Kasta doesn't accept products
| What you see | Why | What to do |
|---|---|---|
| “Помилка завантаження або валідаціі xml структури фіду” (Error loading or validating the feed's XML structure) | the file structure doesn't match what's expected — usually the XML template was edited | go back to the default template: create a new “Kasta (XML)” template and compare |
| HUB can't fetch the file | the file is on your server (the template copies it there over FTP), and protection blocks Kasta. This doesn't apply to the file at the Elbuz link | allowlist the IPs 3.78.142.138, 18.196.145.164, 3.121.252.59, 52.59.104.195, 3.126.0.144 |
| Products aren't matched to Kasta categories | the category has no Rozetka code — rz_id doesn't go into the feed |
fill in the Rozetka code in the category, or match it in the HUB mapping file (“Категорія+”) |
| “Відсутній бренд” (Brand missing) | the brand isn't in Kasta's brand list | send a request to moderator@kasta.ua |
| Variants didn't merge into one product page | different SKU, manufacturer or category, or the color is written in the name | align the SKU and manufacturer, pass color and size as attributes (how) |
| The name or photos on Kasta don't update | “Оновлювати контент” (Update content) is off in the HUB feed settings, or the product wasn't created by this feed | turn on “Оновлювати контент”; update products created another way the same way they were created |
| A product got duplicated after changing the SKU or color | Kasta treats a change to these fields as a new product | delete the extra item in HUB (what doesn't update) |
The full list of errors and stop words is in Kasta's instructions for uploading content in XML format, in your HUB account.
FAQ
Will a Rozetka template work for Kasta?
Kasta accepts a feed with the Rozetka structure, but for new templates use the “Kasta (XML)” type: it has numeric offer id, up to 20 photos and price_old in every product.
Why not through the Kasta API?
Kasta takes both new products and prices with stock from the feed, so Elbuz sends the catalog as a file. Through the API connection, Elbuz only fetches orders — orders from Kasta.
I've had a Kasta template for a long time — has it changed?
No. The new preset applies only to templates created from now on; Elbuz doesn't touch existing templates.
How fast will a new price show up on Kasta?
After the next export in Elbuz and the next update in HUB — roughly within an hour, or within 30 minutes with “Оновлювати стоки і ціни окремо” (Update stock and prices separately).
Does Elbuz send dimensions and weight?
Only if you add the attributes “Габарити в упаковці, см” (Packaged dimensions, cm) and “Вага в упаковці, кг” (Packaged weight, kg): the template has no separate tags for them.
Where to find it and who has access
- Menu
- Directories → Operations → Data export
- Create
- “Add” → type “Kasta (XML)”
- Access right
- the “Export” and “Export Template Setup” windows in “Group permissions”
- Have ready
- Rozetka category codes, SKU and manufacturer, “Колір” and “Розмір” for clothing
The general mechanics of templates — filtering, the file at a link, schedule, log — are in the article on exporting products.
1
Template name and type2
Data composition checkboxes- Template name and type — the header shows Kasta (XML) and the template ID.
- Data composition checkboxes — Categories and Products are on for the Kasta feed.
Related topics
- If you need to fetch orders from Kasta — Kasta orders via API.
- If categories don't have Rozetka codes yet — matching categories with marketplaces.
- If you also sell on Rozetka — exporting the catalog to Rozetka.
