Elbuz exports the price and description as they are in the base catalog. The template picks the price field and can calculate a formula or build a description from attributes.
When you need this:
- A marketplace needs the RRP, a customer the regular price — each template uses its own field or an “RRP if filled in” formula.
- Price 0 in the file — the export calculates nothing: the card field is empty.
- Attributes filled in, no description — the generator builds one for the export only; the card stays as is.
Where to start: template card → XML price tag or the price list “Formula” column.
What a template can do with price and description
- Price field — any price field in the catalog: “Price”, “RRP”, “Old price”, “Sale price”.
- Formula and exchange rate — “RRP if filled in”, conversion at the exchange rate right in the template.
- Description generator — a description built from product attributes, in the export only.
Price in an export
No markup is applied at the export stage. None of the formats has a percentage, a multiplier or rules: the file gets the field value exactly as it is in the base catalog. Markup is applied earlier, when the catalog is updated from supplier price lists — see pricing rules for a price list.
What you can do with the price here:
- Choose which field is the price. The template offers every price field of a product: “Price”, “RRP”, “Cost price”, “Old price”, “Sale price”, plus “Currency”, “Fixed price” and “Price dynamics”. A wholesale price list usually uses one field, a marketplace another. In an XML template, the regular price from the card is the
{price}placeholder, which the template uses by default. Any other price field is inserted with a macro named after it:{Product: RRP},{Product: Sale price},{Product: Old price}. - Write a formula. In an XML template, a formula goes in double square brackets:
[[IF({Product: RRP}>0, {Product: RRP}, {Product: Price})]]— “if the is filled in, use it, otherwise use the regular price”. In an XLSX/CSV price list, the “Formula” column in the list of selected fields does the same. - Convert at the exchange rate. The
{CURRENCY_RATE_USD}inserts the current rate from the currency list — both in the template header and inside a formula. The rate is rounded to two decimal places: for currencies with a small rate (hryvnia to dollar, tenge) this noticeably distorts the conversion.
Numbers are rounded automatically: “price” fields to two decimal places, numeric fields to four, weight to two. This doesn't apply to a formula result: it goes into the file exactly as the database calculated it, so put the rounding inside the formula itself.
The file always gets a single currency code — the account's main currency. Catalog prices are stored in that same currency, so “adding up different currencies” can't happen in an export.
A formula error behaves in two different ways, and the second is more dangerous. If the formula fails the security check, the run continues, and the calculated fields in the file come out empty.
If the formula has a syntax error — a missing comma in IF, an unclosed bracket — the whole database query fails: no file is generated at all, the link keeps serving the previous file, the log ends with “Data export NOT completed: the file was not generated”, and the export date in the list stays old.
A marketplace that fetches the file on its own schedule keeps getting the previous file — to it, this looks like “prices haven't changed”. So test any formula change with the “Check” button: it shows both the error text and a fragment of the file.
Description generator: an attribute table instead of manual work
The “Description generator” button in the “Additional” section solves a separate task: it builds a product description from its attributes and passes it to the export ready-made. Handy when attributes in the catalog are filled in but products have no full description — nobody is going to write a thousand cards by hand.
The window has two checkboxes and a template field. “Generator enabled” turns it on; “Filter: empty description” limits it to products with an empty full description, so it doesn't touch what you've already written. The template field itself is with placeholders, highlighting and hints for catalog fields.
The description is built for the export only: in the product card, the “Full description” field stays as it was. Clear the checkbox, and the next run goes out with the old description — nothing needs restoring.
Besides the attributes themselves, you can insert product fields into the template:
| Placeholder | What it inserts |
|---|---|
{{ product_head.name }} | Product name |
{{ product_head.mpn }} | Manufacturer SKU |
{{ product_head.ean }} | barcode |
{{ product_head.description_short|raw }} | Short description |
{{ product_head.description_full|raw }} | Full description from the card |
{{ product_head.tag }} | Product tags |
The |raw suffix is needed where the value itself contains HTML: without it, the tags end up in the file as text.
The template editor suggests catalog field names in curly braces, such as {Product: Name}. They don't work in the description generator: it understands only the placeholders from the table above and the attributes. An inserted suggestion stays in the description as plain text. Curly-brace macros work elsewhere in the app, for example in an XML feed template.
If a landing page has been generated for a product, its code is inserted into the description with {% if product_head.landing_url %}{{ product_head.landing_embed|raw }}{% endif %}. No need to type it: the generator window has this construction ready, with a “Copy construction” button next to it.
The condition is there for a reason — the code is inserted only for products that actually have a landing page, and in the export language.
The generator doesn't use every product attribute. A row appears only when all of these conditions are met:
- the attribute value isn't empty;
- in the attribute directory, “Active” and “Display on site in product card” are turned on;
- the attribute itself isn't a product option.
So attributes set up as options — size, color — never get into the generated description: they describe a variant, not the product.
Scenarios
A wholesale customer wants a price list by email, with the RRP where there is one
What to set up: “Add” → “Price list file (XLSX, CSV)” → “Price list (XLSX, CSV)”. For the price column, write a condition in the “Formula” column: if “RRP” is greater than zero, use it, otherwise use “Price”. Fill in the “Newsletter template”.
What you get: after each run, the file is emailed as an attachment using this newsletter template, and the log shows a “Sending emails” line. What won't happen: no markup, only what the formula gives. A category with no name in the export language drops all its products from this list; in feeds it goes out unnamed.
Attributes are filled in, but products have no full description
What to set up: in the “Additional” section of the template card, open “Description generator”, select “Generator enabled” and “Filter: empty description”, and place attributes and placeholders in the template field.
What you get: products with an empty full description go into the file with a description built from their attributes. Descriptions you wrote yourself don't change. What won't happen: the “Full description” field in the product card stays empty, and option attributes don't get into the description.
A marketplace needs the old price to show a discount
What to set up: in the XML template, put the {Product: Old price} macro into the old-price tag the marketplace requires.
What you get: the file gets the value of the “Old price” field from the catalog, rounded to two decimal places. What won't happen: a product with an empty field gets an empty tag — the export doesn't calculate anything.
On each marketplace, the price has to cover its commission
What to set up: in each marketplace's template, put a formula with its markup into the price tag. For example, for a 15% commission — [[ROUND({Product: Price} * 1.15, 0)]], for another marketplace — its own multiplier. In an XLSX/CSV price list, use the “Formula” column. Then click “Check” and look at the price in the file fragment.
What you get: each marketplace gets its own price, while the base catalog, the website and other templates keep the price they had. What won't happen: the app doesn't fetch the commission rate from the marketplace — when it changes, you update the multiplier in the template yourself.
What to do when the file has the wrong price
| What you see | Why | What to do |
|---|---|---|
| “Macros were not recognized and will be stripped from the file: ‹list›” | A macro in the template has a typo in the field name | In the template editor, press Ctrl+Space and pick the field from the list |
| The price in the file (for example, in the price_prom tag) is 0 or empty | The export doesn't calculate anything: the field the template tag refers to really contains 0 or nothing in the product card | Open the template and see which field is in the price tag; check that field in the product card; if a catalog formula fills the field, apply it first (price in an export) |
FAQ
Does the export add a markup to the price?
No. The file gets the field value exactly as it is in the base catalog. A different price is set either with a formula in the template or earlier — with pricing rules when the catalog is updated from supplier price lists.
Can I use {Product: …} in an export template?
Yes. In an XML template, this is the usual way to refer to any base catalog field, including your custom fields: {Product: RRP}, {Product: ‹your field name›}. The macro works both in the template text and inside a formula in double square brackets.
It says “Macros were not recognized”, or a custom field shows 0 in the export. What's wrong?
The name after the colon in {Product: Field name} must match the product grid column name character for character. Don't type it: press Ctrl+Space in the template editor and pick the field. If the macro is recognized but the file shows 0, the field is empty in the product.
Why does the price (for example, price_prom) come out as zero in a template export?
The field the price tag refers to really contains 0 or nothing in the product card. Check in the template which field is in the tag, and check that field in the product card. If a catalog formula fills the field, apply it first (formulas for catalog fields).
Why are size and color missing from the generated description?
The generator skips attributes set up as product options, and those with “Active” or “Display on site in product card” turned off in the directory (description generator).
Where to find it and who has access
- Menu
- Directories → Operations → Data export → template card
- Other ways in
- the “Additional” section of the template card → “Description generator”
- Access right
- the “Export Template Setup” window
- Prepare
- product prices and attributes in the base catalog
Related topics
- For the big picture of exports — How to set up product exports.
- If the price itself is wrong in the catalog — Pricing rules: that's where markup is calculated. If prices aren't yet calculated from supplier prices automatically — what it gives your store.
- If a product field is filled by a formula — Formulas for catalog fields.
- If you're writing an XML feed template — Export in YML (XML) format.
- If you plan to sell on marketplaces — what it gives your store.
