Elbuz selects export products by the template conditions on every run; the “Check” button shows whether a given product gets into the file.
When you need this:
- A product is in the catalog, not in the file — a test run names the cause: filter, category, stock or rules.
- Only part of the catalog goes to a marketplace — categories, brands, suppliers and field conditions live in the template.
- The file came out empty — the log flags a selected store with no products.
- Several stores, one catalog — “Store ID” keeps only that store's products in the file.
Where to start: template card → the “Export limit (filter)” tab.
What product filtering can do
- Template conditions — categories, manufacturers, contacts and the “Additional filter” are saved in the template and apply on every run.
- Eleven conditions — a table in the order in which the conditions filter a product out.
- Checking a product — the “Check” button shows a file fragment or the reason for rejection.
- Empty file — three settings that send nothing to the file.
- What doesn't filter — price, photos and description don't remove a product from the file.
Where product filtering is set
The filtering conditions live in the template card, on the “Export limit (filter)” tab. The “Set filter by:” panel gives you four tools.
- “categories” — choose the categories included in this particular export. The button shows a count of what's selected, and the menu under it offers two ways to choose: “categories as a tree” and “categories as a list”.
- “manufacturers” — limit the export to specific brands.
- “suppliers” — limit it to the suppliers the products came from.
- “Additional filter” — a condition builder over product grid fields: price, stock status, quantity, date, any catalog field and product attributes. Under the builder, the conditions are restated in plain language, and the “Reset” and “Save” buttons are right there.
1
Categories (152)2
Additional filter3
Conditions in plain words- Categories (152) — the button shows how many categories are selected for export.
- Additional filter — the condition builder with the rules already filled in.
- The row at the bottom restates the conditions in plain words: active, has photos, in stock.
The template filter isn't catalog filtering. Catalog filtering shows rows here and now; template conditions are saved and apply on every run, nightly included. So the catalog “Total” and the template summary can differ many times over: the template adds the mandatory export flag and a mandatory exported category to your conditions.
In the “Price list (XLSX, CSV)” template there are two filter tabs — “Base Catalog Items” and “Products from price lists”. The second one filters rows of supplier price lists and works only in this type; it's covered in a separate article about the customer price list.
Why a product didn't make it into the file
The most common question here. The answer is almost always in one of eleven places: Elbuz collects products in one query, and each condition cuts off part of the catalog. One is enough for a product to vanish from the file silently.
Conditions are listed in the order they apply. The first four always apply in file formats and feeds; the rest only when you've set something: categories, a filter, a cleared checkbox, a store, warehouse or language.
Exporting to your own website through Elbuz Tunnel has its own conditions — there a disabled category doesn't drop a product from the export but switches it off on the website (filtering in the tunnel).
| # | Condition | Where it's set and how to check |
|---|---|---|
| 1 | The product's “Export to file (to website)” flag is cleared | The column of the same name in the catalog grid, editable right in the cell; in the product card, a switch of the same name |
| 2 | The product has no description in the export language | The “Language ID” field in the “Export limits” section of the template card. Empty means the main catalog language — the one marked as default in the settings, not your interface language. If the catalog has two languages, set the export language explicitly, or the marketplace gets texts in the default one |
| 3 | The product isn't in any category | The product card. A product “outside the tree” isn't in any export |
| 4 | All of the product's categories are disabled or have the “Export to file (to website)” flag cleared | The category grid, “Active” and “Export to file (to website)” columns, or the switch of the same name in the category card. A product in several categories goes out if at least one is active and exported |
| 5 | The template has categories selected, and the product's category isn't among them | The “Export limit (filter)” tab, the “categories” button — its counter shows how many are selected |
| 6 | The product doesn't pass the “Additional filter” conditions | Same tab. A new template already has “Active = yes” there |
| 7 | The “Options” checkbox is cleared — option products are dropped | The “What to export” section. Applies in YML feeds; in the Google feed option products go out regardless |
| 8 | “Only export new data” is on, and the product has already been exported | The “What to export” section. The “Exported” flag is per product, not per template — see the note below |
| 9 | A “Store ID” is selected in the template, and the product isn't assigned to that store | The “Export limits” section; in the form for direct connections the field is just “Store”. The quietest cause of an empty file — see below |
| 10 | “In stock at this store only” is on, and the store has neither quantity nor the “In stock” status | The checkbox next to “Store ID”. Store quantities are kept apart from the product; a regular filter can't use them |
| 11 | A “Warehouse ID” is selected, and the product isn't there or has zero quantity | The “Export limits” section |
A demo account adds a hard limit: only the first 100 products get into the file, noted in a separate log line.
Two more causes concern more than one product, so they're not in the table:
- the “Products” checkbox is cleared in “What to export” — no products are selected at all, and the file gets only the header with categories;
- in the prom.ua feed, the main product of a family with options isn't exported — the options go instead, as the marketplace requires.
The XLSX/CSV price list and direct API connections have one more condition that feeds don't: the category needs a name in the export language. A category without a translation cuts all its products from the file. In XML and Google feeds it just goes out unnamed.
Item 2 works the other way round in direct API connections: a product without a description in that language isn't dropped — it goes out with an empty name. The API and prom.ua forms have no “Language ID” field; they always use the main catalog language.
How to check a specific product
Don't go through the eleven items by hand — ask Elbuz. The template card header has a flask-icon “Check” button with the tooltip “Trial export of one product: show the result and any errors found”. Enter a “Product ID” to get the file fragment for that product or a direct answer: “Product #123 was not exported: it does not match this template conditions (filter, category, stock, rules).”
You can leave the field empty to use the first matching product; if none matches, Elbuz says so. A test run sends nothing and doesn't overwrite your working file. It works for XML and Google feeds, the XLSX/CSV price list, prom.ua, 1C and direct API connections; for Elbuz Tunnel the answer is “The check is not available for this template format yet”.
For a single product it's faster to ask AI. In the product card, click “✦ AI” → “How the product goes to the export”: the consultant runs the template on this product and shows empty or zero fields along with the reason.
For a whole category, the category card has the hint “How the category goes to the export”: it shows which marketplace categories the category is matched to and which templates it gets into. More in the article about the AI consultant.
Why the file is empty when the catalog has products
A store is selected, but its assortment is empty. Nothing gets into the file, and the export looks broken. The log gets a separate red line: “Store “‹name›” is selected in the settings, but no product belongs to it — there is nothing to export. Store contents are set in the product card (Stores block) or by creating categories inside the store branch.”
Only stores you created by hand have an assortment — the main store usually has none at all. If you don't split the catalog between stores, leave the “Store ID” field empty: then the whole catalog is exported. The summary takes the template's store into account, so the dialog before the run will show 0 products.
The template's store was deleted. The template doesn't fall back to the whole catalog: the log shows the red line “The store (ID ‹N›) selected in the template settings has been deleted — there is nothing to export. Select a store in the template or clear the selection to export the whole catalog.” Then it depends on the template type:
- XML and Google feeds and the XLSX/CSV price list export nothing and end with the line “Data export NOT completed: the file was not generated”, while the link keeps the previous file;
- a price list in “Export category rows with products below + grouping” mode and prom.ua and 1C templates run to the end and put a file with no products at the link;
- exporting to your own website through Elbuz Tunnel and direct API connections don't run at all in this case.
To get the template working again, select another store in it or clear the selection.
“Only export new data” in two templates at once. At the end of a run with this checkbox, Elbuz marks the products in this run's file as exported. The mark is one per product, but each template has its own checkbox. So products taken by the first template don't get into a second one with the same checkbox.
If no products are left for the second one, the file isn't generated: the link keeps the previous file, and the log ends with the line “Data export NOT completed: the file was not generated”. In the Google feed this checkbox has no effect at all. Keep it in no more than one template.
What doesn't affect filtering
Price, photos, specifications, description and barcode don't narrow the selection. A product with no price and no photo goes into the file just like a complete one — Elbuz counts it separately and shows the number in the summary, but doesn't drop it. The marketplace will reject it, and you'll hear about it from the marketplace.
Stock status alone doesn't filter either: “out of stock” goes into the file unless you've excluded it with template conditions. What quantity and status the receiver sees is decided by the “Stock-based update setup” table.
Scenarios
A separate store — only its own products
What to set up: in the “Export limits” section of the template card, select a “Store ID”. If you need only the products this store can sell right now, turn on “In stock at this store only”.
What you get: the file gets the products assigned to this store. With the checkbox, only those whose store stock status means “in stock” or whose quantity is above zero. The log says “Store filter “‹name›”: ‹N› products of ‹M› in the catalog belong to it”.
What won't happen: an empty store alone won't stop the run. The pre-run summary shows zero, and the “nothing to export” stop rule only warns by default. What then happens to the file depends on the template type — see why the file is empty.
The catalog has two languages, but the marketplace needs one
What to set up: in the “Export limits” section of the template card, enter the language you need in the “Language ID” field.
What you get: names and descriptions in that language go into the file. Products without a description in it don't get into the file — that's item 2 in the conditions table. What won't happen: the direct API connection and prom.ua forms have no “Language ID” field; they always use the main catalog language.
The YML feed should get regular products only, without variants
What to set up: in the “What to export” section, clear the “Options” checkbox.
What you get: option products don't go into the feed, and the pre-run summary doesn't count them either. What won't happen: the checkbox has no effect in the Google feed — option products always go there.
What to do when a product is missing from the file
| What you see | Why | What to do |
|---|---|---|
| “No product matches this template conditions — there is nothing to export” | The test run found no product matching the template conditions | Go through the conditions table from top to bottom — most often it's the product flag, a category or the selected store (why a product didn't make it) |
| “Product #123 was not exported: it does not match this template conditions (filter, category, stock, rules).” | You entered a product ID in the check, and one of the conditions filters it out | Check this product against items 1–11: flag, description in the export language, category, filter (why a product didn't make it) |
| “Store “‹name›” is selected in the settings, but no product belongs to it — there is nothing to export.” | The “Store ID” field has a store whose assortment is empty | Clear the store selection or fill the store assortment in the product cards (about the store trap) |
FAQ
A product is in the catalog but not in the file. Where do I look?
Open the template card, click “Check” and enter the product ID. Elbuz shows a file fragment or replies that the product doesn't match the template conditions. Then go through the conditions table: product flag, description in the export language, category, filter.
The file came out empty, and the log has no errors. Where do I start?
Check three things: whether “Store ID” has a store with an empty assortment, whether “Only export new data” is also on in another template, and whether the “Additional filter” cuts off everything (why the file is empty).
Does a disabled product go into the file?
No, as long as the “Additional filter” has “Active = yes” — a new template has this condition from the start. Remove it, and disabled products go out too. Elbuz Tunnel doesn't have this condition: a disabled product goes to the website and is switched off there.
Why does the catalog show more products under the same filter than the template summary?
The template adds the mandatory product export flag and a mandatory exported category to your conditions. Catalog filtering doesn't take them into account, so the numbers can differ many times over.
A product is in several categories, and one of them is disabled. Will it be exported?
Yes, if at least one of its categories is active and has the “Export to file (to website)” flag on. Only a product whose categories are all disabled or not exported stays out.
Can I select products by quantity in a specific store?
Yes: select a “Store ID” and turn on “In stock at this store only”. A regular filter can't do this — store quantities are stored separately from the product.
Where it is and who has access
- Menu
- Directories → Operations → Data export → template card
- Other entry points
- the flask-icon “Check” button in the template card header
- Access right
- the “Export Template Setup” window; it also covers “Check”
- Prepare
- the “Export to file (to website)” flag on products and categories
Related topics
- If you need the big picture of exporting — How to set up product export.
- If the product is in the file but the price or description is wrong — Which price and description go into an export.
- If you want to see the product count before the run — How to check an export before running it.
- If you filter products by store — Stores: how a store's assortment is filled.
- If you plan to sell on marketplaces — what it gives your store.
