Elbuz publishes your catalog as an XML feed (YML) at a permanent link, and Prom.ua fetches it on a schedule — prices and stock update with no manual uploads.
When you need this:
- Prices and stock change daily — each run rebuilds the feed at the same link.
- New products — they go in with their own ID; Prom adds them.
- Sizes and colors — Prom groups variants into one product page.
- Catalog broke overnight — a stop rule blocks a feed with stock gone.
- A promotion — the old price is crossed out.
Where to start: create a “prom.ua (XML)” template and paste its link into Prom.
What the Prom XML feed can do
- Permanent link — Prom fetches the feed from it on its own, so you don't upload the file by hand.
- Product ID — the same as in the file, so listings don't get duplicated.
- Editable XML template — you tailor the offer contents to Prom's requirements.
- Specifications and variants — sent as
paramandgroup_idelements. - Stock as an attribute — an out-of-stock product stays in the feed with
available="false". - Schedule and stop rules — the feed updates without you and is never overwritten with a broken one.
How to set up the feed
Prom XML is a standard YML feed: yml_catalog at the root, with a categories block and an offers block inside. The feed lives at an address: update the catalog in Elbuz, and the same link serves fresh data.
- Create an export template and choose the “prom.ua (XML)” format.
- Decide which products to export: the whole catalog, selected categories, or by filtering rules.
- If needed, adjust the
offercontents in the “XML template” section. - Click “Check” — you'll see one product exactly as it will go into the feed.
- Run the export and copy the link from the “File” column into your Prom account (or deliver the file over ).
- Set a schedule under “Schedule”, and in your Prom account set how often the marketplace fetches the feed.
For the first few runs, check the log and your Prom account: is the feed built without errors, and did the products update?
The official feed format description is in the Prom help center: Import via YML — file format. The general exchange section is Import and export.
What goes into the feed
Each product is one offer. You can change the set of elements in the template; by default it looks like this:
| XML element | What it contains |
|---|---|
offer id="…" available="…" group_id="…" | id — product ID (your UUID); available — current stock; group_id — links a variant to its main product |
url | product link |
price / currencyId | price and currency |
categoryId | product category ID |
picture (up to 10) | images; for Prom the number of photos is capped at ten |
name | product name |
vendor / vendorCode | manufacturer and part number () |
description | product description |
param name="…" unit="…" | specifications (attributes): name, unit of measure, and value |
By default, categories carry your IDs: id="{uuid}" in the category, linked to its parent, and the same key in the product's categoryId. To send Prom's own category number, use the {category_id_prom} and {category_name_prom} placeholders: they take the values filled in when you matched categories to the marketplace's list.
The ID is the same UUID as in XLSX
The offer id is our product UUID, the same key as in the “Ідентифікатор_товару” (product ID) column of the XLSX file. Prom recognizes a product by id and updates the listing; a new UUID is added as new. The formats don't conflict. Why this prevents duplicates — How Elbuz updates products on Prom without duplicates.
Don't touch the id="{uuid}" attribute in the template: it's the sync key, and changing it by hand will duplicate listings on Prom.
If the offer id was changed anyway
- Restore the attribute in the template to
id="{uuid}"— that's how it appears in the default template. - Click “Check”:
idshould contain the same long ID as the “Ідентифікатор_товару” column of the XLSX export. - Run the export. The next feed will point to the same product pages as before the mistake.
Product pages that were already created on Prom with a different id have to be removed in your Prom account: the feed has no delete commands.
Where the description comes from
By default, the feed uses the “Full Description” field from the product card: <description>{description_full}</description>. HTML markup is escaped, so the tags end up in the file as text.
- To send as is, wrap the placeholder in CDATA:
<description><![CDATA[{description_full}]]></description>. - To send different text, replace the placeholder in the “XML template” section with another field, such as
{description_short}(“Brief description”), or with your own text.
Specifications and variants
Specifications are output as param elements with name and unit attributes. To output Ukrainian names and values, use your own attribute row template with the {Атрибут: Название_ua} and {Атрибут: Значение_ua} macros.
Variants are linked through group_id: Prom groups them into one product page with a variant picker. For Prom, the feed includes the variants themselves (with the “Options” checkbox in the template), and a main product that has variants is skipped.
Sale price and crossed-out old price on Prom
For shoppers on Prom to see the old price crossed out with the new one next to it, the offer needs two prices: <price> — the discounted price, <oldprice> — the price before the discount. The “prom.ua (XML)” template sends only one price by default, <price>{price}</price>, so Prom shows no discount until you add the second tag.
How to pass a discount from Elbuz
- Set sale prices with “Promotions / Discounts” rules or by hand in the product card. The sale price goes into the “Sale price” catalog field (
{price_special}). For a discount, enter the percentage with a minus sign (-7) and don't tick “Quantity price (wholesale)” — it creates a quantity-based price, which doesn't go into the feed. - In the rules window, click “Apply rules to products” and make sure the “Sale price” column in the product grid is filled in.
- In the template card, “XML template” section, replace the
<price>{price}</price>line with these two:<price>[[IF({price_special}>0 AND {price_special}<{price}, ROUND({price_special}, 2), ROUND({price}, 2))]]</price> <oldprice>[[IF({price_special}>0 AND {price_special}<{price}, ROUND({price}, 2), '')]]</oldprice> - Click “Check” on a product with a promotion:
priceshould show the sale price andoldpricethe regular one. For a product without a promotion,priceis regular andoldpriceis empty. - Run the export. Prom picks up the discount at its next update from the link (how often Prom fetches the feed).
1
price line2
oldprice line- The price line takes the special price when it is lower than the regular one.
- The oldprice line outputs the regular price only while a special price is active.
1
Checked on product2
<price>902.00</price>3
<oldprice>1002.00</oldprice>- Checked on product — the test export ran on product #177722, the one with the sale price.
- The price line holds the sale price, 902.00.
- The oldprice line holds the regular price, 1002.00, which the marketplace shows as struck through.
The {price_special}<{price} condition guards against two mistakes: a “discount” that is actually higher than the regular price, and a crossed-out price on products without a promotion. ROUND(…, 2) is needed because inside [[…]] calculation blocks a fractional price otherwise comes out with trailing zeros: 699.50000000.
How Prom reads prices — the marketplace's rules
| Tag | What it means for Prom |
|---|---|
price | A price from 0.01 to 9,999,999,999 — regular or already discounted. Required if oldprice is present. |
oldprice | The price before the discount — this is the one shown crossed out. Prom also accepts the spellings price_old and old_price, but oldprice takes priority. |
discount | Another way: a discount as a percentage (30%) or an amount (20) off price. If the offer also has oldprice, discount is ignored. |
available | A discount applies only to a product that is in stock. A product that is out of stock or has no available gets the oldprice value as its price — no discount. |
The Prom help center says it plainly: when importing from a link, the discount date isn't passed, and the discount is set on the site for 45 days. YML has no separate tag for discount dates. So a promotion's duration on Prom is governed by the feed contents, not a date: while a product has oldprice, the discount is on; once oldprice disappears, Prom gets the regular price. If you need exact discount dates on Prom's side, upload an XLSX file with discount period columns by hand.
What happens on Prom from start to end of a promotion
| Moment | In Elbuz | In the feed | On Prom |
|---|---|---|---|
| Rule applied | “Sale price” is filled in | price — sale, oldprice — regular | after the next update: old price crossed out, new one next to it |
| Supplier changed the price | batch update recalculates the promotion from the new price | both prices are new | prices update with the same discount percentage |
| Product sold out | stock status changed | available="false" | discount doesn't apply, the price becomes oldprice |
| The rule's “End date” has passed | at the next rule application, “Sale price” is cleared and the rule is turned off | price — regular, oldprice empty | after the next update: regular price, nothing crossed out |
| Rule turned off or deleted | “Sale price” is cleared immediately | same as above | same as above |
Rules are applied by the button in the rules window, a batch price list update, saving a product card, and changing a price in the grid. Expired promotions are cleared by any catalog-wide application, so with daily price list updates the promotion ends on its own. If no application ran that day, click “Apply rules to products” the day after the end date — on the end date itself the promotion is still active. A price entered by hand in the card stays until its own end date. Details — promotion dates.
Other sources of the old price
- A permanent crossed-out price without a promotion — for example, the supplier's recommended price:
<oldprice>[[IF({price_rrp}>{price}, ROUND({price_rrp}, 2), '')]]</oldprice>. In that casepricestays{price}. - The “Old price” field (
{price_old}) — use it only if you maintain it yourself as the pre-discount price: a batch price list update writes the previous price into it on every change, so it can be equal to or even lower than the current price — then there's no crossed-out price, or a misleading one. - A percentage discount instead of two prices:
<discount>7%</discount>next to the regular<price>{price}</price>. You can take the percentage from a product field with the{Product: field name}placeholder.
Prom YML tag reference and Elbuz placeholders
All tags Prom accepts in a YML file, according to the Prom help center, and what to fill them with in an Elbuz template. Prom ignores tags not listed there. Any catalog field works in the product node — as a {field_code} or {Product: Field name} placeholder; check the result with the “Check” button.
Groups (categories)
| Tag / attribute | What it means for Prom | Elbuz placeholder |
|---|---|---|
category id | required group ID | the category's {uuid} or {category_id} |
parentId | parent group — nested structure in the account | parent category ID |
portal_id | Prom marketplace category number for the group's products; takes priority over portal_url | {category_id_prom} |
portal_url | link to the marketplace category | — |
Product (offer)
| Tag / attribute | What it means for Prom | Elbuz placeholder |
|---|---|---|
offer id | required; Prom uses it to update the listing on later imports | {uuid} — don't change it (why) |
available | true — in stock, false or empty — not in stock; without it a discount doesn't apply | {xml_stock_status} |
in_stock | true — the “Готово до відправки” (Ready to ship) status | constant true, if that's how you work |
selling_type | r — retail, w — wholesale, u — wholesale and retail, s — service; without it Prom sets “retail” | a constant, for example r |
group_id | a number from 1 to 999,999,999 that links variants into one product page | {id_parent} (variants) |
type="vendor.model" | the name is built from typePrefix + vendor + model, and name is ignored | usually not needed |
name | required name | {name} |
name_ua | name in Ukrainian; updates only together with description_ua | {name_ua} — only when the template exports in another language; if the template language is Ukrainian, use {name} |
typePrefix / model | name prefix and model — only with vendor.model | {model} |
categoryId | required group ID from the categories block | {category_uuid} |
portal_category_id | marketplace category for the product; takes priority over portal_category_url and the group's portal_id | {category_id_prom} |
price | price or discounted price | {price} or a formula with the sale price |
oldprice (price_old, old_price) | price before the discount, shown crossed out | a formula with {price} |
discount | discount as a percentage or amount, valid for 45 days | a constant or a product field |
currencyId | price currency: UAH, USD, EUR, KZT, BYR | {currency_code} |
prices → price → value + quantity | wholesale prices for types w and u | quantity-based prices from rules with the “Quantity price (wholesale)” flag don't go into the feed — only via your own template from product fields |
minimum_order_quantity | minimum order for “wholesale only” products | {order_minimum} |
quantity_in_stock (stock_quantity) | quantity in stock; quantity_in_stock takes priority | {quantity} |
picture | 1 to 10 photo links | {image_list} |
vendor | manufacturer; imported only if it exists in Prom's manufacturer database | {manufacturer_name} |
vendorCode (barcode, article) | part number up to 25 characters: digits, letters, - _ . / and space | {mpn} or {sku} |
country | country of manufacture | the {attribute_ID} specification or your own field |
param name unit | specification; up to 100 per product; several values separated by | | {attribute_list} |
dimensions: weight (kg), width, height, length (cm) | weight and dimensions | {weight}, {width}, {height}, {product_length} |
description | required description; HTML only inside CDATA | {description_full} (where the description comes from) |
description_ua | description in Ukrainian; updates only together with name_ua | {description_full_ua} — same rule; if the template language is Ukrainian, {description_full} |
keywords / keywords_ua | search queries separated by commas, up to 1024 characters | {tag} or {meta_keyword} |
regions → region | product location, up to three localities from Prom's list | a constant |
gtin / mpn | barcode and manufacturer number for the Google Merchant feed | {ean} / {mpn} |
The characters ", &, >, <, ' in feed text must be replaced with codes. Elbuz does this in ordinary field placeholders, but not in the result of [[…]] calculation blocks or in a description inside CDATA: if a formula returns text with these characters, wrap the tag in CDATA. Send HTML in descriptions only inside CDATA.
What each run overwrites
The feed isn't appended to — it's rebuilt from scratch every time. Each file contains the current value from Elbuz for every template element: price, stock, name, description, specifications, photos. Elbuz doesn't ask Prom what was edited there by hand.
To keep a field under your control, remove its element from the “XML template”: whatever isn't in the template isn't in the file. There's no separate “don't touch this field” checkbox. How Prom handles fields missing from the feed is up to the marketplace.
The “Only export new data” checkbox
With it on, only products without the “Exported” flag go into the file. The flag is set at the end of a successful run on the products that made it into the file, and cleared as soon as a product is changed — in the card or in the grid.
There's one flag per product, shared by all templates: if the checkbox is on in two templates, the second won't get the products the first one flagged. For a permanent feed the checkbox is usually unnecessary — the link would serve only what changed since the last run, not your whole range.
When a product drops out of the feed
A product doesn't get into the file if it fails the template's filtering: the “Export to file (to website)” flag, an active category, the filter, selected categories, store, warehouse. Full list — Why a product didn't make it into the file. The Prom feed has two more reasons:
- “Only export new data” is on, and the product is already flagged as exported;
- it's a main product with variants: it's always skipped, and the variants go only with the “Options” checkbox.
Zero stock doesn't remove a product from the feed. By default only the “In stock” status gets available="true"; all other statuses get available="false", and the product stays in the file. What to send for each status is set in the “Stock-based update setup” window, opened from the template card.
Stop rules catch mass disappearance: by default they warn if stock dropped by more than 30%, the total count by more than 50%, or there's nothing to export. In “Stop the export” mode the file isn't overwritten. Details — Stop rules.
1
Threshold2
Mode3
Show summary before export- Threshold — the change size at which the rule triggers.
- Mode — what the system does when the rule triggers.
- Switch that shows the summary before an export starts.
What Prom itself does with listings that are no longer in the feed is the marketplace's rule.
Schedule, log, and feed link
Running, the pre-run summary, the schedule, and the log work the same for all templates — Running manually and on a schedule, Run log. Below is what's worth knowing specifically about the Prom feed.
How a run goes
- Pre-flight summary and stop rules: in “Stop the export” mode the file isn't touched at all.
- Categories (“Export product categories”), if they're enabled in the template.
- Products: every 500 products, the log shows a line like “Export products 500 of 12,340”.
- The file goes to FTP first (if “FTP Setup” is filled in), then to storage; the template's old files are removed only after the new one is uploaded.
- The link, size, and date are written to the template; the last line is “Data export completed”.
- Action or result
- Decision: the path depends on the answer
If a run breaks off
Prom never gets a half-built feed: publishing is the last step of a run. Signs of a break: the date in “Last export” hasn't moved, and the log shows “Data export NOT completed: the file was not generated” or “Export stopped by the user!”. The “Stop” button breaks off the Prom feed at the next product.
- No product matched — the file isn't overwritten; the link serves the previous one.
- The file didn't upload to storage — the log shows “The file was not uploaded to cloud storage…”. The new file is already on FTP, since it goes there first.
Retrying is safe: the file is rebuilt from scratch, and the “Exported” flag is set only at the end of a successful run. A watchdog unlocks a stuck schedule when an hour has passed since the start and there's been no sign of life for over half an hour.
- Action or result
- Decision: the path depends on the answer
How to see what ran
The template list shows the result without opening the card: “Last export”, “In stock” with the change since the last run, and “File” with a “Copy link” button and the size. A nearly empty feed stands out by its size alone.
1
Last export2
In stock3
File- Last export — date and time of the last export run.
- In stock — how many products were put into the file.
- File — file name, copy-link button and file size.
The “Check” button shows one product's finished offer and errors: invalid XML, a formula error, unrecognized macros. In a real run an unrecognized macro is silently stripped, and the node comes out empty. Whether Prom accepts the names, categories, and specifications is up to Prom at import.
How often Prom fetches the feed
The Elbuz schedule only puts a fresh file at the link. When Prom reads it is up to the marketplace — according to the Prom help center:
- Price, stock, quantity, and discount update every 4 hours, from 6:00 to 22:00; the exact time depends on Prom's load.
- Other fields and new products — once a day, at night.
- In the import settings of your Prom account you can untick fields the marketplace shouldn't update, and set what to do with products missing from the file.
- “Оновити примусово” (Force update) and “Тільки оновлення” (Update only) don't apply to periodic import from a link — only to a manual run.
- If the file is unavailable for several days in a row, Prom sends an email on day 4 and turns off periodic import on day 6. The link stays in the account — you have to turn the import back on.
So there's no point updating the feed in Elbuz more often than every few hours: Prom will take the freshest file in its own window anyway.
Turn a template off or delete it
- A turned-off template doesn't run on schedule or in a bulk run, with no log line. The link keeps serving the last feed, which is no longer fresh. You can still run it by hand with the “Export” button.
- Deleting removes the XML template text, filtering, stock statuses, FTP, and schedule. The only way back is a new template with a new link.
Limits and numbers
- No cap on the number of products. A demo account is limited to 100 products, and the log says so.
- Up to ten photos per product. Set fewer in the template card's “Max Photos” field.
- Schedule — from one hour. The schedule builder has no “every minute” option.
- Bulk run — one at a time. “Export all templates” runs active templates one after another.
- Each template has its own link, even with the same file name.
- Feed size for Prom — up to 180 MB (the marketplace's recommendation). Split a larger catalog into several templates by category and add several links in your Prom account.
Don't put the {DATE}, {DATETIME}, or {TIME} placeholders in the file name. The name then changes with every run, and the previous copy is deleted — the link in your Prom account stops working the very next day.
XML or XLSX — which to use when
For daily automatic price and stock updates, the XML feed is handier: Prom fetches it itself. For a full exchange with all Prom columns, use XLSX. Both share the product key, so you can upload the catalog as a file, then keep it fresh with the feed. A comparison, and what happens when the same products go both ways — XLSX or XML/YML.
The feed is one-way: it brings nothing from Prom into Elbuz. For that, there's XLSX import (Prom/EVO).
Scenarios
Keep prices and stock on Prom fresh every day
What to turn on. A template in the “prom.ua (XML)” format, a schedule under “Schedule”, and the link from the “File” column in your Prom account. Leave “Only export new data” unticked.
What you get. Each run rebuilds the file from scratch with current prices and statuses, and a new file lands at the same link. An out-of-stock product stays in the file with available="false".
What won't happen. The feed doesn't delete listings on Prom: the file has no “remove” command.
Sell only part of your range on Prom
What to turn on. Choose the categories you need for the template, and set narrower filtering on the “Export limit (filter)” tab. A single product or category is excluded with the “Export to file (to website)” checkbox in its card.
What you get. Only what passes the filtering goes into the file. The pre-flight summary counts products with the same filter.
What won't happen. Products that dropped out of the filtering aren't removed from Prom — the feed simply stops including them.
Products with sizes and colors
What to turn on. The “Options” checkbox in the template.
What you get. Each variant goes as a separate offer with the main product's group_id. The main product itself doesn't go into the Prom feed.
What won't happen. Without the “Options” checkbox, variants don't get into the file, and the main product is skipped anyway — such a product disappears from the feed entirely.
Don't send Prom an empty feed after a catalog failure
What to turn on. Select the template in the list, open “Export stop rules” from the “Additional operations” menu, set the rule you need to “Stop the export”, and click “Save for this template”.
What you get. If stock or product count dropped below the threshold compared to the last successful run, the run stops before the file is built — both manually and on schedule. The link keeps serving the previous feed.
What won't happen. A stopped or unfinished run doesn't become the new baseline: only a successful export does.
I edit names and descriptions in my Prom account and only need price and stock from Elbuz
What to turn on. Remove the elements you don't want to send from the “XML template” — the description, for example. Don't touch the id="{uuid}" attribute.
What you get. The removed element isn't in the file.
What won't happen. Elbuz doesn't know what you edited on Prom. How the marketplace treats fields missing from the feed is Prom's own rule.
A 7% off promotion on a category until the end of the month, with a crossed-out price
What to turn on. In “Promotions / Discounts”, a rule: “%” -7, “Quantity price (wholesale)” unticked, the category in “Additional filter”, and the last day of the month as “End date”. Apply the rules. In the Prom template, replace the price line with the price + oldprice pair from the sale price section.
What you get. For the category's products, price in the feed is 7% below oldprice. After the next update from the link, Prom shows the old price crossed out. After the end date, the next rule application clears “Sale price”, and the feed sends the regular price without oldprice.
What won't happen. Prom doesn't see the end date in the feed — the discount stays while the feed carries it; by default Prom gives a discount a 45-day term. Any rule application clears an expired promotion; if none ran that day, click the apply button the day after the end date.
A promotion should start on Monday
What to turn on. A rule with Monday as the “Start Date”. On Monday, apply the rules with the button (or wait for a batch price list update that touches these products).
What you get. Before the start date “Sale price” isn't filled in, so the feed has the regular price. An application on the start date sets the sale price, and it goes into the feed.
What won't happen. The promotion won't switch on by itself at midnight sharp: the rules need to be applied that day.
Show the supplier's crossed-out recommended price on Prom
What to turn on. Keep <price>{price}</price> and add <oldprice>[[IF({price_rrp}>{price}, ROUND({price_rrp}, 2), '')]]</oldprice>.
What you get. Products whose RRP is higher than your price get a crossed-out RRP on Prom. The rest show no crossed-out price.
What won't happen. Prom gives such a “discount” the same 45-day term. If the product is out of stock, the price on Prom becomes oldprice, that is, the RRP.
A percentage discount without calculating two prices
What to turn on. Next to the regular price, add <discount>10%</discount> — as a constant, or from a product field if the percentage varies.
What you get. Prom calculates the discounted price from price itself and shows both.
What won't happen. If the same offer has oldprice, Prom ignores discount. The Elbuz catalog knows nothing about this discount: it isn't on your website or in other feeds.
What to do when the feed didn't update
| What you see | Why | What to do |
|---|---|---|
| “Data export NOT completed: the file was not generated” | No product matched the template's conditions, a formula in the template broke the query, or the file didn't upload to storage — in that case the log above shows “The file was not uploaded to cloud storage…” | If the file didn't upload to storage, run the export again. Otherwise click “Check”: it names the formula or placeholder error. Then check the filtering (when a product drops out of the feed) |
| “Export stopped by a stop rule: …” | There are noticeably fewer products or less stock than in the last successful run | Check stock statuses in the base catalog; if the numbers are right, raise the threshold in the “Export stop rules” window (when a product drops out of the feed) |
| “Scheduled export canceled because another template is being exported (data processing conflict).” | Two scheduled exports don't run at the same time | Spread the templates out in time under “Schedule” (if a run breaks off) |
Empty nodes in the feed: <name></name> |
A placeholder is misspelled — such placeholders are stripped from the file without warning | “Check”: the notes will say “Macros were not recognized and will be stripped from the file” (how to see what ran) |
| Only part of the range went into the file | “Only export new data” is on, and the other products are already flagged as exported | Untick it in the “What to export” section and run again (only new data) |
| The link entered in your Prom account stopped opening | The file name contains {DATE} or {DATETIME}: each run creates a new file and deletes the old one |
Remove the placeholder from the file name, export again, and enter the new link in your account (limits and numbers) |
| The promotion is set up in Elbuz, but Prom shows no crossed-out price | The template has only <price>{price}</price>; or “Sale price” is empty — the rules weren't applied or the rule has the “Quantity price (wholesale)” flag; or the product is out of stock; or Prom hasn't updated the feed yet |
Add the price + oldprice pair (how), check the “Sale price” column in the grid, click “Check” on a product with a promotion, and wait for Prom's next update (every 4 hours from 6:00 to 22:00) |
| After a “promotion” rule the price came out higher than the regular one | The rule's “%” column has a positive number — that's a markup, not a discount | Enter the percentage with a minus sign (-7) and apply the rules again (how the price is calculated) |
| The promotion has ended, but Prom still shows a crossed-out price | The rules haven't been applied since the end date — “Sale price” still holds the old value; or Prom hasn't fetched the new feed yet | Click “Apply rules to products”, export the feed, and check that oldprice is empty. Prom updates the price in its next update window — every 4 hours from 6:00 to 22:00 |
The feed has a price like 699.50000000 |
The price is placed inside a [[…]] calculation block without rounding |
Wrap the field in ROUND({price}, 2) |
FAQ
What is the product ID in the XML feed?
The offer's id attribute is the product's UUID in Elbuz — the same key as “Ідентифікатор_товару” (product ID) in XLSX. That's why Prom updates listings without duplicates.
How does Prom pick up new products from the feed?
A new product goes into the feed with its own UUID in id. Prom sees an unknown ID and adds the product as new, while updating existing listings.
Why aren't all of a product's photos in the feed?
For Prom the number of images in the feed is capped at ten per product — that's the marketplace's requirement. The first photo is treated as the main one.
Do I have to export the feed by hand every time?
No. Set a schedule for the template, and Prom fetches the feed from the link at its own interval. From then on, the catalog on Prom updates by itself.
How are product variants passed?
Through the group_id attribute: Prom groups them into one product page with a variant picker. The feed includes the variants themselves with the “Options” checkbox, and the main product is skipped.
What happens if an export breaks off halfway?
The link keeps serving the previous file: a new one goes to storage only once fully built. Running again is safe — the file is rebuilt from scratch every time.
What does turning a template off do?
The template doesn't run on schedule or in a bulk run, but the link keeps serving the last feed, which is no longer fresh. When you switch it back to “Active”, the settings are not lost.
Which product field goes into the Prom feed description, and how do I use my own?
By default, “Full Description” ({description_full}), with HTML tags escaped. To send HTML as is, wrap the placeholder in CDATA; for other text, replace it in the “XML template” (where the description comes from).
How do I send Prom a crossed-out old price and a new sale price?
Set sale prices with “Promotions / Discounts” rules (percentage with a minus sign, without the “Quantity price (wholesale)” flag) and replace the price line in the template with a pair: price — “Sale price” if it's lower than the regular one, oldprice — the regular price (ready-made lines).
Will the regular price come back on Prom after a promotion ends?
Yes. After the end date, the next rule application clears “Sale price”, the feed sends the regular price without oldprice, and Prom updates the price at its next update — every 4 hours from 6:00 to 22:00. Prom doesn't read a date from the feed: on import from a link, the discount lasts while the feed carries it, and no longer than 45 days (how a promotion runs).
How quickly do price changes from Elbuz show up on Prom?
Prom updates price, stock, quantity, and discount from the link every 4 hours from 6:00 to 22:00, and other fields and new products once a day at night (how often Prom fetches the feed).
Why does an out-of-stock product have no discount on Prom?
It's Prom's rule: a discount applies only to a product that is in stock. For a product with available="false", Prom uses the oldprice value as the price.
What other Prom tags can I add to the feed?
For example, name_ua and description_ua (Ukrainian name and description — only as a pair), quantity_in_stock, portal_category_id, keywords, dimensions, gtin. The full list with Elbuz placeholders is in the tag reference.
Where to find it and who has access
- Menu
- Directories → Operations → Data export
- Stop rules
- list menu → “Export stop rules”
- Access right
- the “Data export” window; for the template card — “Export Template Setup”
- Have ready
- access to your Prom account to paste the feed link
1
Help button2
Export and marketplaces folder- Help button — opens the menu of guide articles for this window.
- Export and marketplaces folder — the guide section with all export articles.
Related topics
- If you need a full exchange with all Prom columns and new products — Exporting to Prom as an XLSX file.
- If you need to bring the catalog or edits from Prom into Elbuz — Importing a catalog from XLSX (Prom/EVO).
- If it's unclear why a product didn't get into the feed or how to set up a schedule — Export templates.
