With a store selected, an export sends only that store's assortment. Seven checks, in order, show where the product dropped out.
When you need this:
- A file or site got an empty export — a red run log line says the assortment is empty.
- One product is missing from the site — the product card shows whether it is in the store.
- A product out of stock at this store skips the feed — a template checkbox checks stock per store.
- Brands vanished from the site, products did not — the tunnel skips manufacturers not in the store.
Where to start: check the template's “Store” field.
What you can check
- Four checks for any export — the store in the template, an empty assortment, the product in the assortment, stock at the store.
- Three checks for API channels and the tunnel — the category and manufacturer in the store, and the “Export to website” checkbox.
- Run log lines — what each one means and what to do.
Four checks for any export
The most common question on this topic. The checks follow the system's own order — go top to bottom and stop at the first one that fails.
The first four checks are the same for any export. The last three depend on the destination: a file (, Prom, CommerceML, Excel), an channel, or your own site via the tunnel. The template itself shows the type.
- Action or result
- Decision: the path depends on the answer
- Is a store selected in the export settings? Selection is controlled by the — the “Store” field, set to “All stores” by default. Until a store is selected, there is no store filter, and none of the next checks run. A selected store, in any export type, adds one mandatory condition: the product must belong to that store's assortment. Two more — by category and manufacturer — apply only in some exports; see items 5 and 6.
- Is the store's assortment empty? The run writes a separate line about this in the log. An empty assortment shows in red: “Store “‹name›” is selected in the settings, but no product belongs to it — there is nothing to export…” A non-empty one shows in normal text: “Store filter “‹name›”: ‹count› products of ‹count› in the catalog belong to it.” Read the second line too: noticeably fewer products than expected means the assortment is incomplete. If the selected store was since deleted from the list, the line is also red: “The store (ID ‹number›) 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.” A file export then gets an empty selection; the tunnel and API channels stop at the start and send nothing to the site or marketplace.
- Does the product itself belong to this store? Product card → “Stores” block → “Show product” checkbox. Or from the other side: turn on multi-store mode and click the store node in the tree — the grid shows its assortment.
If the product is not there, ask what fills your store's assortment at all: the fix differs in each of three cases:
- categories — assign the categories and click “Assign products to stores”;
- a supplier — check the contact card, not the product card: is the supplier ticked for this store, is the store active in the list, does the supplier's price list have a line with a price for this product;
- the site via the tunnel — the assortment is edited on the site, and a checkbox set in Elbuz will not stick.
You can always tick the checkbox for one product, but with thousands of products, first find out which of the three mechanisms you use.
- Is the “In stock at this store only” checkbox on? It is in the same export template and lets through only products that have a positive quantity or the “In stock” status for this store. Per-store stock is kept apart from the product's own stock, so ordinary selection rules cannot express it — hence the checkbox.
An empty store assortment is far more common than it seems. When you select a store for an export, first check that it contains anything.
The preflight summary won't help: it counts products by the template's conditions without the store and shows the full catalog count. The only reliable signal is the red log line, and it appears only after the run starts.
Three more checks for API channels and the tunnel
These checks depend on the export destination: a file, an API channel, or your own site via the tunnel.
- Does the product's category belong to the store? This applies to two export types. In an API channel (Rozetka, Horoshop, Shopify and others), a category not assigned to the store takes the product with it — the product simply does not make it into the selection. In the Elbuz tunnel, the product stays, but the category itself is not sent to the site, so the product has nowhere to appear there. File exports — YML, Prom, CommerceML, Excel — have no category filter at all, so this check tells you nothing. Edit it in the category card, “Stores” block.
- Does the product's manufacturer belong to the store? This applies only to the tunnel and only to the manufacturer list itself: a manufacturer not assigned to the store is not sent to the site. The product does not drop out of the export — run this check when brands, not products, disappear from the site. Nobody edits the manufacturers' store assignment, by the way: it fills itself when a manufacturer or a store is created.
- Does the store have “Export to website” checked? Also tunnel-only: only active stores with this checkbox are sent to the site.
If all seven checks pass and the product is still not on the site, the cause is no longer the stores: product status, description language, template categories, stock, selection rules and stop rules are covered in the article on export templates.
Scenarios
Feed for one storefront — in-stock products only
Task: the file for a specific site should contain only products available at that particular store.
What to turn on: in the export template, select the store in the “Store” field and tick “In stock at this store only”.
Result: the export gets only products from this store's assortment that have a positive quantity or an “In stock” status for the store.
What won't happen: stock in the base catalog columns is the main store's data and does not affect the selection. If the store's assortment is empty, there is no warning before the run — only a red line in the run log.
A product disappeared from a storefront built by supplier
Task: the store is filled with products from certain suppliers, and a product stopped going into the export.
What to check: the product card, “Stores” block. Most often the product is still in the assortment, but with a zero price and the “Out of stock” status: the supplier stopped sending a line with a price.
Result: with “In stock at this store only” ticked, such a product stays out of the export until the supplier sends a price again. More in what removes a product from a store.
A store was deleted, but export templates remain
Task: the store was removed from the list, but some export templates had it selected.
What to do: in each such template, select another store or “All stores” in the “Store” field.
Result: the export selects products again. Until the template is fixed, a file export comes out empty, and the tunnel and API channels stop at the start of the run and send nothing.
What to do when the run log mentions a store
| What you see | Why | What to do |
|---|---|---|
| “Store “‹name›” is selected in the settings, but no product belongs to it — there is nothing to export…” | The export template has a store with an empty assortment selected | Either switch back to “All stores” or fill the assortment with the “Assign products to stores” button (assign products) |
| “The store (ID ‹number›) 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.” | The store selected in the export template was deleted from the list | Select another store or “All stores” in the template's “Store” field (chain of checks) |
| “Store filter “‹name›”: ‹count› products of ‹count› in the catalog belong to it.” | The filter works, but the store's assortment is incomplete | Compare the numbers with what you expect and complete the assortment by category (assign products) |
FAQ
The export came out empty although a store is selected. Why?
No product belongs to the selected store — the run log reports this in a red line. Switch the template back to “All stores” or fill the assortment (assign products).
I have one store. Should I select it in the export template?
No. With a single active store, the system creates no product-to-store links, the assortment is empty, and the file comes out empty. Leave “All stores”.
Brands disappeared from the site, but products are still there. Why?
The manufacturer is not assigned to the store selected in the tunnel template, so it is not sent to the site. The product does not drop out of the export (check 6).
Do I need to turn on “Multiple stores mode” to export one store's products?
No. The “Store” field in the export template does the filtering. The mode only shows stores as the top level of the category tree (multi-store mode).
The catalog shows the product in stock, but “In stock at this store only” filters it out. Why?
Stock in the catalog columns is the main store's data. The checkbox looks at quantity and status for the selected store, in the product card, “Stores” block (check 4).
Where to find it and who has access
- Menu
- Directories → Operations → Data export → template → “Store” field
- Log
- the export template's run log — the line about the store filter
- Product assortment
- product card → “Stores” block → “Show product”
- Access right
- the “Data export” window; to edit the assortment — the product card
Related topics
- For the big picture — How to run multiple stores from one catalog.
- If the product is not in the store's assortment — How to build a store's assortment.
- If the per-store checks pass but the product is not on the site — Export templates.
