Marketplace Feeds (Rozetka, Prom, Epicentr, Kasta) for WooCommerce

Marketplace Feeds outputs the WooCommerce catalogue in the format Ukrainian marketplaces accept: Rozetka, Prom.ua, Epicentr and Kasta. The shop doesn’t export CSV by hand and doesn’t pay for a separate service: the marketplace fetches a fresh XML from a permanent link itself.

What goes into an offer

Every product is output with a name, price, currency, link, category, images, brand, SKU and stock. A sale price goes as <price>, and the regular price as <price_old>, so the marketplace shows a struck-through old price. Product characteristics are output as <param> tags, the barcode from the GTIN field, and the brand from WooCommerce’s “Brands” taxonomy or from an attribute.

Variable products are output the way marketplaces expect: each variation is a separate offer with the parent product’s group_id and its own size, colour, SKU, price and stock. The link goes straight to the right variation.

Epicentr: its own XML instead of YML

Epicentr does not read the Rozetka/Prom YML: both the product import in the cabinet and the «Stock auto-update» by link expect yml_catalog → offers → offer without a <shop> block. Given a YML, the cabinet answers «Невідомий тег shop у рядку 3» (unknown tag shop in line 3). Since 1.4.1 the Epicentr feed (Pro) serves exactly that XML, in two versions.

• Price and stock — the short file for «Products → Import → Stock auto-update»: price, price_old and availability (in stock, to order, out of stock). The article in the cabinet = the WooCommerce product or variation ID.
• Full version — also the name, the description (only the tags Epicentr keeps), all photos in one line separated by commas and the barcode — to update products already in the cabinet.
• Out-of-stock products are always in the file, marked out of stock: Epicentr leaves a product that simply disappears from the file as it was.

New products with Epicentr characteristics (category and attribute codes) are not created by this feed — that is what the Epicentr: Price and Stock Sync module does. A shop that already served the Epicentr feed before the update keeps the old format unchanged until it switches «Epicentr feed format» in the settings; the link stays the same.

Google Merchant Center and Meta with variations

Pro gets two more feeds in 1.2.0: for Google Merchant Center and for the Meta catalogue (Facebook and Instagram ads) — RSS 2.0 with g: attributes that both dashboards accept. Every variation goes out as a separate item sharing a g:item_group_id (the parent product ID), with the size in g:size and the colour in g:color, so Google and Meta show one listing with a size picker instead of running ads on duplicates. You can point to the size and colour attributes in the settings; if you don’t, the plugin recognises them by name (size, розмір, color, колір), including local attributes with Cyrillic names.

Price and sale, availability, brand, GTIN, category path and a link to the exact variation follow the same rules as the marketplace feeds. Products without a brand get a default brand, and Google gets an optional google_product_category.

Real dispatch time — in the free version. The product’s “Shipping” tab has a new “Dispatch time (feeds)” field, and the settings have a store-wide default. Google receives g:min_handling_time and g:max_handling_time, and in the Prom.ua feed the “Ready to ship” status is set only for products that ship within one day: “in stock, but ships in 2–6 days” no longer passes for same-day dispatch.

A catalogue for AI assistants and agents

Shoppers increasingly look for products in ChatGPT, Gemini or Claude rather than in a search engine. Since version 1.4.0 the plugin makes the shop’s catalogue readable for such assistants in three ways — each is switched on separately, and everything is off after the update. The Rozetka, Prom, Epicentr, Kasta, Google and Meta feeds do not change: we compared them byte for byte before and after updating from 1.2.0 and 1.3.0, with and without Pro, on WordPress 7.1 and WooCommerce 11.2.

/llms.txt (free). A short page about the shop in the llmstxt.org format: name and description, currency and country, categories with product counts, best sellers with price and stock, policy pages. Headings follow the site language. If another plugin has already put an llms.txt in the site root, the settings screen says so.

OpenAI Product Feed (Pro). An openai.jsonl.gz file per OpenAI’s file-upload specification: one row per product or variation (group_id, variant_dict), price and sale price as in the shop — without the multiplier you set for marketplaces, GTIN only with a valid check digit, seller and returns data from the settings. A product without a brand, an image or a price is left out, and the feed table shows how many rows were skipped and why. Note: OpenAI accepts feeds from approved merchants only (apply at chatgpt.com/merchants) and takes them over SFTP or its API, and the standard upload is currently shown to shoppers in the US. The plugin prepares the file at a token-protected URL; uploading it to OpenAI is done with the credentials OpenAI issues after approval. Whether OpenAI accepts a Ukrainian shop’s catalogue in UAH, we have not verified.

Universal Commerce Protocol (Pro). The shop profile at /.well-known/ucp (UCP 2026-08-25) and catalogue search for agents: catalog/search, catalog/lookup, catalog/product — products, variations, prices and stock. Catalogue only: the plugin does not offer agent checkout. Every request checks the agent platform’s profile: HTTPS only, no redirects, private addresses refused, request rate limited. We validated the responses against the official UCP JSON schemas.

Address check. /llms.txt and /.well-known/ucp are not files on disk, so the server has to hand them to WordPress. The «Check addresses» button opens both the way an agent would and shows what came back: if nginx, a security plugin or a cache intercepts them, you see it at once.

How it works, step by step

1. Install the plugin and open WooCommerce → “Marketplace Feeds”.
2. Turn on the marketplaces you need — each one gets its own link with a token.
3. Configure prices, availability and offer content to match the marketplace’s requirements.
4. Copy the link and paste it into the marketplace’s dashboard.
5. From then on the feed updates itself on schedule; the “Regenerate now” button does it immediately.

Under the hood

The feed is written as a stream via XMLWriter, straight to the output stream or to a cache file, and products are fetched page by page by key (WHERE ID > …). So memory usage doesn’t depend on the catalogue size, and large shops don’t hit the PHP limit. The cache is stored in a separate folder with an unpredictable name and is only served through the endpoint, so the catalogue can’t be found by guessing the URL directly.

The link is protected by a token: if it leaks somewhere, the “New token” button instantly invalidates the old one. The file updates on a WP-Cron schedule, and the cache is cleared immediately when settings change — the marketplace won’t get yesterday’s catalogue.

How to install

1. Download the market-feeds-for-woocommerce-1.4.0.zip archive.
2. Plugins → Add New → Upload Plugin → choose the archive → “Install” → “Activate”.
3. Open WooCommerce → “Marketplace Feeds” and copy the link for the marketplace you need.