Integrating your store with Kasta: feed, API and orders
A Kasta integration connects your store to the HUB supplier account: products with attributes, stock, prices and orders with statuses. Kasta accepts XML only in the Rozetka feed structure, and its API has separate methods for stock, prices and statuses. We have no ready-made module and have not worked with Kasta yet: we build the exchange for your task, drawing on stores with Rozetka connected and exports for Prom. The first step is a free check of your feed against HUB rules.
API, XML, an Excel template, manually or via Horoshop, Foks Biz, TradeEVO — Kasta supplier page, checked 12 September 2026
after a free audit
Price
3012345678900123456789
Guarantee
days after project sign-off
API, XML, an Excel template, manually or via Horoshop, Foks Biz, TradeEVO — Kasta supplier page, checked 12 September 2026
Ways to upload to HUB
not accepted; the exception is a feed in the Rozetka structure (Kasta's XML instructions, file dated 12 August 2026)
Third-party XML
article number + brand + color + size; the card is grouped by color, with the size grid inside
Product card key
updated roughly once an hour, or every 30 minutes in a separate mode
Prices and stock from XML
none: this is development for your task, drawing on stores with Rozetka connected and exports for Prom
Experience with Kasta specifically
Who it's for
Situations where this service delivers results
Scenario 1 of 4
You already have a Rozetka feed
Then the base for Kasta is ready: Kasta's instructions say plainly that XML with any other structure will not upload, and the Rozetka feed structure is the exception. But “we have a feed” does not yet mean “the feed will pass”: for clothing and footwear Kasta requires separate Color and Size parameters, the brand has to be in its reference list, and the article number is marked mandatory in Kasta's field table. That is what we add.
We'll review your situation in a free audit
Scenario 2 of 4
Clothing, footwear, underwear — products with a size grid
Kasta builds the card by the item's color, with sizes inside each color. If the color is not passed in the feed or is not found in its reference list, HUB sets “combined/not set”, and the buyer sees a card without a proper choice. So we split variants into separate Color and Size params.
Scenario 3 of 4
Stock moves faster than the hourly feed cycle
From XML, prices and stock on Kasta update roughly once an hour. When that is not enough, stock and prices go through the API: separate methods by the supplier's unique ID, in batches of up to 1,000 SKUs. Kasta currently sets no rate limit on these methods but asks you to send only changes — and that is how we build it.
Scenario 4 of 4
Your manager retypes Kasta orders by hand
The API returns an order list with a change cursor, up to 100 per request, and accepts statuses back: confirmed, packed, handed to the carrier, cancelled with a reason. From there you can also pull Nova Poshta and Ukrposhta PDF labels. Orders are then processed in the system you already work in.
Cases
Tasks and results in numbers — all metrics measured by us
Adjacent work, not Kasta: the store of an official garden tool seller with the Rozetka marketplace connected
Task
Show a catalog where the manufacturer's article number is already in the product URL: from such an article number the Kasta card key is assembled without manual entry.
Solution
OpenCart 3, two language versions (uk/ru), connected to the Rozetka marketplace. This store has no connection to Kasta.
Result
Measured 31 July 2026: the manufacturer's article number is in the URL of 1,120 cards out of roughly 1,213, with about 70 categories. Whether the article number sits in a separate field in the remaining cards cannot be seen from outside — the review checks that.
What's included
Complete list of work and what you get as a result
A review of which route to take: a Rozetka-structure feed, the HUB API or both — you do not pay for the API if an hourly update is enough for your catalog
A feed with the fields Kasta marks as mandatory: brand, article number, photos, UAH currency, Color and Size for products with a size grid — items do not drop out on the very first upload
Explicit stock in every item — without a stock tag Kasta puts a product with available=true on sale as 10 units, even when the warehouse has zero
A price rule for the royalty: the sale price already includes Kasta's percentage, and the strikethrough price is not lower than it — otherwise HUB returns an error and the product does not go on sale
Support during the first upload and mapping in HUB together with your manager — you can see which items got stuck and why
Stock and prices via the API in batches of up to 1,000 SKUs, only on change — a sold product comes off sale without waiting for the feed cycle
Orders from HUB into your store or CRM and statuses back in the sequence Kasta requires — no manual retyping
Automatic confirmation with the ConfirmedBySupplier status as soon as an order reaches your system — otherwise Kasta deducts the ordered quantity from stock you have already reduced
Nova Poshta and Ukrposhta PDF labels from HUB and receipt data for orders, if fiscalisation is on your side
An exchange log with upload rejections and status errors — you see what broke without logging into the account
A 30-calendar-day warranty from the date the acceptance act is signed
When this service isn't right
What's not included — so there are no surprises at delivery
The contract with Kasta, its terms and royalty — between you and the marketplace
Product moderation: your Kasta manager handles it
A new brand in Kasta's reference list — only through its manager
Descriptions and filling in cards as content work
Promotions and advertising inside Kasta
Fulfilled by Kasta warehousing and logistics
Process steps
Transparent stages with approval at every step
Total duration:4–19 days
01
Catalog review and choosing the route
2–3 working days, free of charge
We run the feed or export through Kasta's requirements, count the unusable items and decide with you: feed, API or both.
02
A Rozetka-structure feed built to Kasta's requirements
2–5 working days
Brand, article number, explicit stock, UAH currency, price and strikethrough price in the right ratio, Color and Size for products with a size grid, a description without links.
03
First upload and mapping in HUB
1–3 working days
Together with your Kasta manager we go through category and attribute mapping, read the upload report and fix whatever dropped out.
04
Stock and price API — if needed
2–4 working days
A background job sends changes in batches of up to 1,000 SKUs by the supplier's unique ID; in the feed settings we switch off price and stock updates so the two sources do not overwrite each other.
05
Orders, statuses, waybills — if needed
3–6 working days
Receiving orders by change cursor, confirmation, packing before the waybill, cancellation with a reason, carrier labels, receipt data. The queue keeps within Kasta's status limits.
06
Handover
1 working day
We show the exchange log to the person who runs the HUB account and leave instructions on what to do with rejections. Then a 30-day warranty.
Free feed check against Kasta HUB rules
HUB checks every feed item separately: whether it has a card key, stock, a price in the right ratio and photos. The review looks at exactly that and answers whether you need the API.
What we measure
Whether your feed works as a baseRozetka structure or another, and whether the tag names match Kasta's documentation. Kasta does not recognize tags with a different name: prices upload as zeros until someone does the mapping.
Card key: article number, brand, color, sizeAfter the first upload these fields cannot be edited: for HUB a change to any of them means new content and new moderation. So we check the key during the review.
Stock in every itemWe count the items without a stock tag. On Kasta, exactly these become “10 in stock” when available=true.
PricesThe strikethrough price is not lower than the sale price, the promotional price is lower than the regular one. You know the royalty percentage from your contract; we check where to build it in.
Description and photosA description of up to 5,000 characters and without links, 1 to 20 photos of up to 10 MB each. Kasta truncates longer descriptions, and links in descriptions are prohibited.
Where orders are handledWho processes them now, in which system, and under which model you work with Kasta — this decides whether the status part is needed.
What you get
A list: how many items meet Kasta's requirements, how many do not, and which field is to blame.
A recommended route: feed only, feed plus the stock API, or a full exchange with orders.
An estimate of the work by stage with timelines.
A 30-minute call with you and the person who runs the HUB account.
Timeline: 2–3 working days
Why is it free
Because we have not worked with Kasta yet and want to be the first to see whether your catalog meets its requirements at all. If the integrator you already use is enough, we will say so.
What's next
After the review — an estimate broken down by stage and a contract with a fixed amount. If part of the catalog is not ready for Kasta, we show which items and what they are missing.
Short form: your contact and site URL
We work officially
Contract, act and invoice — for every project, not just large ones.
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
02
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
03
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
04
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
05
Sites in nine countries
Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.
06
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
07
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
08
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.
01
Contract, act and 30-day warranty
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
02
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
03
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
04
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
05
Sites in nine countries
Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.
06
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
07
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
08
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.
We sign NDAs on request. After completing the work, we delete our access to your services ourselves.
Did not find your case?
Describe how it works on your side — we will tell you whether “Kasta marketplace integration” fits and what it means in your situation. No brief and no call: one question, one answer.
What affects the price
Why two seemingly identical tasks are priced differently
Exchange routeA feed in the Rozetka structure on its own is the shortest option. The stock and price API adds a separate stage, and orders with statuses add another, the largest one: that is where the status sequence, cancellation reasons and request limits come in.
Products with a size gridFor clothing and footwear every variant has to carry Color and Size as separate parameters. If your variants are packed into the name or description, they first have to be split into fields.
State of the card keyIf every item has an article number and brand, the key is assembled automatically. If article numbers are missing or the brand is not in Kasta's reference list, that has to be fixed first, and part of it depends on the marketplace's manager.
Stock sourceIf stock is in the website database, we pass it from there. Kasta will receive stock from 1C or BAS no earlier than it reaches the website database, so the exchange with the accounting system is a separate estimate.
Where orders are processedIf orders are processed in the HUB account, the status part may not be needed at all. If they are processed in your CRM or store admin, you need order intake, confirmation, waybills and statuses back.
Technologies & integrations
What we build on and what it connects to
Stack
XML in the Rozetka feed structure — the only third-party structure Kasta accepts; the catch is that the Color and Size fields and a brand from Kasta's reference list still have to be added
HUB API — Swagger 2.0, JSON, a token in the Authorization header; 35 methods as of 12 September 2026
OpenCart 3 / 4 — a module or our own generator; the Rozetka template in a module is only a base, we add the Kasta fields
WooCommerce — a ready-made Rozetka feed plugin after reviewing its code, or our own generator
A background job with a queue — the site does not wait for HUB to respond, and the queue keeps within the status limits: 300 per minute, 10 per order per 10 minutes.
Exchange log — upload rejections and status errors with date and reason
Checkbox or another software cash register (PRRO) — receipt data for orders
1C / BAS, KeyCRM — the stock source and the place where orders are processed
Feed and API versus the HUB account and an Excel template
How this option differs from the alternative
Manual entry in the HUB account or an Excel templateOur approach
Stockchanges when the manager gets to the account or uploads a new Excel filetaken from the store database explicitly in every item; via the API — right after a change
New productentered in HUB separately, a second time after your websiteappears in the feed and goes into the HUB import queue, then to moderation
Ordersare processed in the HUB window, separately from the rest of your ordersarrive in your CRM or admin panel, and statuses go back to Kasta automatically
Order confirmationuntil the manager confirms, Kasta deducts the ordered quantity from the stock you sentConfirmedBySupplier is set automatically, and Kasta knows the stock is current
Waybilldownloaded from the account one order at a timethe Nova Poshta or Ukrposhta label is pulled from HUB into the order
What we need from you
We can't start without this — best to prepare in advance
1Access to the HUB account or an API token, which you create in the account yourself.
2Your cooperation model with Kasta: Marketplace 3P or Fulfilled by Kasta.
3A link to your current feed or catalog export.
4The royalty percentage from your contract — without it the sale price cannot be set.
5Access to the website and its admin panel, with rights to install modules.
6A person who runs the HUB account and talks to the Kasta manager.
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ
Most frequently asked questions — with concrete answers
Will our Rozetka feed work for Kasta?
As a base, yes: Kasta's XML instructions say plainly that files with any other structure are not accepted, and the Rozetka feed structure is the exception. That does not make it ready, though. Clothing and footwear need separate Color and Size parameters, the brand has to come from Kasta's reference list, and the article number is marked mandatory in Kasta's field table. In our own measurement of 21 public feeds of Ukrainian stores (5 September 2026, 88,991 products), only one passed Rozetka's own mandatory fields without violations.
Why is a product with no stock in the feed suddenly “in stock”?
That is Kasta's rule: if there is no stock tag and available=true, HUB sets the quantity to 10. A product you have zero of goes on sale, and the cancellation later falls on you. In the same measurement of 21 feeds, six had no stock_quantity or quantity_in_stock tag in a single item. So we pass stock explicitly in every item and flag the items without it during the review.
XML or API — which should we choose?
The feed, if your range changes slowly and orders are few: prices and stock from it arrive roughly once an hour, or every 30 minutes in a separate mode. The API, when that is not enough or you want to process orders in your own system: stock goes out right after a change, and orders and statuses travel both ways. A mix also happens: content via the feed, stock via the API. In that case we switch off price and stock updates in the feed settings, otherwise the two sources overwrite each other. New products from the feed go through Kasta's general queue — roughly up to ±6 hours, and once every 4 hours if the date in the feed header does not change. So we update the generation date on every build.
What happens if we change an article number or color after upload?
HUB treats it as a new product and sends it to moderation again. The supplier's article number, brand, color and size are fixed to the card on first upload and are not updated; to change them, the product is deleted and uploaded again. So we check the card key before the first upload — afterwards a fix costs another round of moderation for everything it touched.
How do we avoid selling on Kasta something already bought on the website?
We pass stock via the API right after it changes, without waiting for the feed cycle. We confirm Kasta orders with the ConfirmedBySupplier status as soon as they land in your system: until confirmation Kasta itself deducts the ordered quantity from the stock you sent, and if your warehouse has already written it off, the item is deducted twice and disappears from sale before it has actually run out. The honest limit: a window between a sale and the update always remains; it can be narrowed but not removed.
Can Kasta orders land in our CRM?
Yes, through the API: an order list with a change cursor, up to 100 per request, orders available from 1 January 2023. In the other direction, we send statuses in the sequence Kasta requires: for example, a waybill is registered only after the “packed” status, and a cancellation only with one of the reasons from its list. Statuses have limits, including 300 requests per minute and no more than 10 per order per 10 minutes, so requests go through a queue.
You have not worked with Kasta yet — so what do you rely on?
Right, we have not worked with Kasta, and the page does not hide it. We have built stores with the Rozetka marketplace connected (case below), feeds and exports for Prom are described on the Prom integration page, and we analyzed 21 public feeds separately. The description of Kasta on this page was checked against its supplier documentation on 12 September 2026. What protects you: a fixed scope in the contract, a free review before the contract and a 30-day warranty from the date the acceptance act is signed.
How do we account for Kasta's royalty in the price?
Kasta shows the sale price to the buyer, and the royalty percentage has to be built into it from the start — its documentation says so. The strikethrough price cannot be lower than the sale price, otherwise the upload returns an error. HUB calculates the supplier price itself. You know the percentage from your contract; we write a rule in the generator so the Kasta price is not kept in a separate spreadsheet.
How long does it take?
After the free 2–3-day review: feed only — 4–9 working days (feed 2–5, first upload and mapping 1–3, handover 1). Feed plus the stock API and orders — 9–19 working days. We will be more precise after the review: what shifts the timeline most is products with a size grid, where variants have to be split into fields.
Send us your feed URL and we will count how many items HUB will accept
Within 2–3 working days we come back with a list: how many items meet Kasta's requirements, which fields are missing and whether you need the API. If the integrator you already use is enough, we will say that too.
There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.