Elbuz fills each store's assortment itself — by category, by supplier or from your site's data — and exports take only that store's products.
When you need this:
- Sites split by catalog section — one operation assigns thousands of products to stores by category.
- A storefront sells specific suppliers' products — the base catalog update adds them to the store itself.
- Stores are managed on the site — the assortment arrives with the site's data.
- A product must appear on one site only — a checkbox in the product card, with its own price and stock.
Where to start: set stores in category cards and run “Assign products to stores”.
What it does: where a store's assortment comes from
- Assortment from the site — if your site is connected through a tunnel and sends its stores, the site sets the assortment.
- Product card and category card — add a single product or category to a store, with a per-store price and stock.
- “Assign products to stores” — build the assortment for the whole catalog by category; you see the scale before you run it.
- Automatic paths — products of a supplier or a price list source, new categories and new products reach the store by themselves.
- What removes a product from the assortment — eight actions, none of which warns you about the scale.
While only one store is active, none of these mechanisms work. What a store is and why you might need several is covered in How to run multiple stores from one catalog.
When your site sets the store's assortment
First, the condition that overrides everything else. If your site is connected through the Elbuz tunnel and sends its stores, the site becomes the source of truth. Such an import creates and updates the stores themselves in the directory, taking their name, link, active status, order, description, image and coordinates from the site.
For products the site sent an assortment for, all stores are removed first, then the ones sent are written; if more than one store is active, the default store is added as well.
Manual checkboxes in Elbuz survive the base catalog update, but do not survive the import of data from the site: for products the site sent anything about, the assortment is overwritten entirely.
Products the site sent no assortment for keep their stores. If the site sends no stores at all, the import leaves the directory alone and writes links only for new products: with two or more active stores, they go to the default store.
The bottom line: when stores come from the site, distribute the assortment on the site side — in Elbuz this work will not hold.
- Start or end
- Action or result
- Decision: the path depends on the answer
For everyone else, store assortments are set in Elbuz — manually or automatically.
How to add a single product or category to a store
Product card, “Stores” block
The block lists all stores in the directory, each with a “Show product” checkbox and the columns “Price”, “RRP”, “Cost price”, “Stock”, “Quantity”.
- You select the checkbox — the product joins the store, and the price, stock status and quantity you enter are saved for that store specifically.
- You clear the checkbox — the row is deleted entirely, together with the price and stock for that store. You can only restore them manually.
- You edit the default store's row — the same price, stock status and quantity are also written to the product itself, changing what you see in the base catalog columns.
It works the other way too: when you save the product card, the price and quantity from it are copied to the default store's row. Other stores are not affected — their prices are kept separately.
Two things about this block that trip people up:
- next to a store the product is not in, the “Stock” column shows “Out of stock” — this is a placeholder for the missing row, not the product's status;
- the per-store cost price is set right here — the “Cost price” column in this block is saved, while the “Cost price” field in the product card itself is read-only because it comes from the price list or the set composition.
1
Show product2
Stock- Show product — the checkbox that assigns the product to the store.
- Stock — availability, along with price and quantity, is kept separately for each store.
Category card, “Stores” block
Same idea for categories: checkboxes for active stores. The block appears only when two or more stores are active — with one there is nothing to choose, so the app hides it. While you have one storefront, don't look for it in the category card: it appears as soon as you add a second active store.
Inside is a simple list: all active stores, the default one first, each with a checkbox and a name. Clearing a store removes the category from its tree and from exports set up for that store; the category and its products stay in place. Details are in the article on the category tree.
Don't mix these up: this links the category. The products inside it do not join the store because of it — that is the job of the “Assign products to stores” operation.
How to assign products to stores by category
This is the window's only bulk operation and the main way to build store assortments when you have thousands of products. The logic is simple: a product follows its categories.
The menu item first runs an estimate — it asks the server how many links will be added and how many removed — and only then shows a confirmation that describes exactly what will happen:
Estimate: links to be added — ‹count›, to be removed — ‹count›.
A product will belong to the stores its categories belong to. Store membership is rebuilt: extra links are removed, missing ones added. Links holding a store price, cost or stock are kept — they contain data.
So you see the scale of the operation before you run it, not after. The confirmation button is “Assign”. The app then does three things:
- adds a link for each “product — store” pair where at least one of the product's categories belongs to that store and there is no link yet;
- removes extra links — but only empty ones: where price, RRP, cost price, quantity and stock status are zero, and no supplier or product from its price list is attached to the link;
- leaves products without categories alone — they have no source for an assortment, and there is nowhere to take one from.
The operation does not see disabled stores at all: it works only with active ones. If your second store is still disabled, the button will neither fill nor clean it.
The result comes back as numbers: “Done. Links added: ‹count›, removed: ‹count›.” If some extra links were not empty, a second line follows — “Kept links with prices or stock: ‹count› — edit those in the product card.” So the operation never loses data: a link with a price or stock stays, and you are told.
- Start or end
- Action or result
- Decision: the path depends on the answer
Order matters: assign categories to stores first, and only then press the button. If no category is assigned to any store, the answer is “Done. Links added: 0, removed: 0.” — the operation ran, it just had nothing to build an assortment from.
The operation is synchronous and has no size limit: on large catalogs it runs for minutes under the blue “Please wait...” message. For scale: on an account with a few dozen stores and a full catalog, one click would create over 4.3 million links — that's why the estimate comes first. Run it when you can wait.
When it finishes, the app leaves a line in the work log with the same numbers of added and removed links. The operation cannot be undone, and the log entry is the only way to recall when it was run.
How the assortment fills itself
Five cases where a link appears without you (and all of them stay silent while only one store is active). The first two are bulk: that's how people with many stores fill a store's assortment.
- A supplier assigned to a store. The contact card has a “Stores” section listing stores with the columns “Activity” and “Store name”. Every base catalog update adds to that store all products with a price list row from its suppliers that has a price or stock, and writes their price, RRP, cost price, stock status and quantity for that store. This splits storefronts by supplier, not by catalog. Only enabled stores are filled: a store disabled in the directory is skipped by the update even if suppliers are assigned to it.
- A store set for a price list source. The “Link products to store” field in the source card, “New products” section, defaults to
---. Despite the section's name, the store is set for all rows of this price list, and every catalog update adds to the store all matched products of this supplier that have a price — not only new ones. - A new category. Created inside a specific store's branch — it goes to that store only; created anywhere else — to all active stores, including the default one. You don't need to finish anything by hand. One exception: when only one store is active, the app writes no links at all — they serve no purpose there.
- A new manufacturer and a new contact. Added to all active stores.
- A new product from a file import or an channel. An import puts the product into its source's store; channels (Rozetka, Shopify, eBay, Amazon and others) put it into the store with
ID= 1, and only Horoshop puts it into the default store.
1
Activity2
Store name- Activity — the checkbox that adds this supplier's products to the store.
- Store name — the store the supplier's products can be added to.
On top of that, one more setting changes the rule for all imports at once: “New product store membership follows categories” in Account → System settings → Catalog → “Data processing rules”. It is off by default. The app describes it as: “A product added by a price list or an import joins the stores its categories belong to.”
When on, after every import it runs the same assignment by category, but only for that import's products and only adding links: it removes nothing and keeps the source's store. You need it when your stores are split by catalog structure rather than by supplier.
1
Multiple stores mode2
New product store membership follows categories- Multiple stores mode — shows the category tree separately for each store; off by default.
- New product store membership follows categories — a product added by a price list or an import joins the stores its categories belong to; off by default.
What removes a product from a store
The flip side of the same list. Eight causes, and none of them warns you about the scale:
| What happened | What exactly is removed |
|---|---|
| The “Show product” checkbox cleared in the product card | One product from one store, together with its price and stock for that store |
| The “Assign products to stores” button | Only empty extra links; those with a price or stock stay |
| A store deleted | All links of that store: products, categories, contacts, manufacturers, articles |
| A category or tree branch deleted | Products for which this is the main category are deleted entirely — with all their stores, prices and stock. Products linked to the category as an additional one stay. The category itself disappears from all stores |
| A product deleted — one by one or in bulk | All stores of that product |
| Import of data from the site through the tunnel | All stores of the product; then the ones the site sent come back, plus the default store |
| CommerceML, or Prom import | Stores of the products the import marked as deleted |
| “Database integrity check” | Links between products and stores that no longer exist |
What is not on this list, although many people expect it: the does not delete store links.
If a product loses its supply, the row stays in place — the app zeroes the price and stock and sets the status to “Out of stock”. The product does not disappear from the store's assortment, and you won't need to bring it back by hand.
But for stores built by supplier, this is the most common reason a product vanishes from the storefront: the supplier stopped sending a row with a price — the product stays in the store as “Out of stock” and no longer goes into exports with the “In stock at this store only” checkbox.
Scenarios
Storefronts split by catalog section
Task: each site has its own set of categories, and products must follow their categories.
What to turn on: in each category card, “Stores” block, select the checkboxes of the stores you need; in the “Stores” window, click “Assign products to stores”; to have new products from price lists and imports assigned the same way, turn on “New product store membership follows categories”.
Result: a product joins every active store that contains at least one of its categories, and empty links to other stores are removed.
What won't happen: products without categories stay as they were; links with a per-store price, cost price or stock are not removed — the app reports how many; a disabled store is neither filled nor cleaned. The setting for new products only adds links and removes nothing.
A storefront built from specific suppliers' products
Task: the site should only get products from specific suppliers, with their own prices and stock.
What to turn on: in the supplier's contact card, “Stores” section, check the store you need in the “Activity” column.
Result: every base catalog update adds to the store the products with a price list row from these suppliers that has a price or quantity, and writes their price, RRP, cost price, stock status and quantity for that store specifically. The store must be enabled in the directory — the update does not fill a disabled one.
What won't happen: a product the supplier no longer offers will not disappear from the store — it stays with a zero price and the “Out of stock” status. To keep it out of exports, use the “In stock at this store only” checkbox in the export template.
Stores and assortment managed on the site
Task: the site is connected through the Elbuz tunnel, and products are already distributed across storefronts on the site side.
What to turn on: nothing in Elbuz — stores and assortment arrive with the import of data from the site.
Result: the store directory is updated with the site's data, and products the site sent an assortment for get the stores it sent; if more than one store is active, the import also adds the default store to each of its products.
What won't happen: manual checkboxes in these products' cards are not kept — the next import overwrites the assortment again. Products the site sent no assortment for keep their stores.
What to do when the assortment comes out wrong
The assignment was interrupted
The assignment runs two steps: first it removes extra empty links, then adds missing ones. Before step one, the work log gets “Assigning products to stores by category started.”; the line with numbers comes only after both steps.
If the server does not respond, a red error message replaces the numbers, and the log has the start line but no summary. What was written stays — say, extras removed, missing links not yet added.
A rerun is safe: the operation recalculates what is missing and extra each time, and the app allows no duplicate “product — store” links, so it just finishes the rest. The estimate shows how much is left.
Products were assigned wrong
The app keeps no list of removed links: the work log has just two numbers, and the base catalog grid has no stores column.
But the removal rule is reproducible: an active store lost the empty links of products whose categories all lie outside it. So restore the assortment with the mechanism that built it, not by searching products:
- built by category — fix the checkboxes in the “Stores” block of category cards and click “Assign products to stores” again; it links every product whose category belongs to the store. Only links with zero price, RRP, cost price, quantity and stock status and no supplier or price list product attached were removed — no per-store data was lost;
- built by supplier — links a base catalog update ever filled have a price, quantity or stock status (after lost supply — “Out of stock”) and stay. Removed ones return with the next base catalog update for products the store's suppliers have data for, as it always fills such a store;
- from the site through the tunnel — the next import rewrites the assortment for products the site sends it for.
Check the result in multi-store mode: a store's node in the tree shows its assortment.
| What you see | Why | What to do |
|---|---|---|
| “Done. Links added: 0, removed: 0.” | No category is assigned to any active store | Select checkboxes in category cards, “Stores” block, and rerun (assign products) |
| “Kept links with prices or stock: ‹count› — edit those in the product card.” | Extra links with a price or stock hold data and are not removed | Remove manually: product card → “Stores” block → “Show product” (product card) |
| The grid under a store node is empty, though the catalog has products | No product is assigned to this store — multi-store mode shows the assortment | Product card checkbox or “Assign products to stores” (assign products) |
| The product card shows “Out of stock” for a store, though the product is in stock | There is no row for this store, so the column shows a placeholder | Select “Show product” and set the store's stock status (product card) |
| The “Cost price” field in the product card is not editable | It is read-only: the value comes from the price list or the set composition | Set it in the product card's “Stores” block — the “Cost price” column there is saved (product card) |
| “Please wait...” stays on screen for a long time | The assignment is one synchronous request and takes minutes on a large catalog | Wait for the numbers; don't close the window |
| Manually set stores disappeared after an import from the site | A tunnel import removes a product's stores and restores them from the site's data | Distribute the assortment on the site — in Elbuz these checkboxes won't hold (assortment from the site) |
FAQ
Our stores are split by supplier. Will the “Assign products to stores” button help?
No, it builds the assortment only by category. Check the store in the contact card, “Stores” section — every base catalog update will add the supplier's products with a price or stock to it by itself (automatic paths).
What happens to manual checkboxes if the site is connected through a tunnel?
They won't hold: every import of data from the site removes all stores from a product and restores the ones the site sent, plus the default store. Distribute the assortment on the site side (assortment from the site).
Why is there no “Stores” block in the category card?
The block appears only when two or more stores are active. Add or enable a second store — the block appears by itself (category card).
Can I specify the store with a column in the supplier's price list?
Yes, but the app needs the name in the column to exactly match the store name in the directory; any difference leaves the product without a store. It's safer to set the store in the source card, “Link products to store” field (automatic paths).
Does the store's stock go down when I post an order?
No. Posting a document changes the stock and reservation in the document's warehouse but does not touch “Stock” and “Quantity” in the product card's “Stores” block. Those are written by the base catalog update, the tunnel import from the site and manual edits in the card.
Where to find it and who has access
- Menu
- Directories → Base product catalog → Shops → menu
- Cards
- product, category and contact cards — the “Stores” block
- Price list source card
- “New products” section → “Link products to store”
- Settings
- Account → System settings → Catalog → “Data processing rules”
- Access right
- the “Stores” window and the block “Operation "Distribute products across stores"”
- Prepare
- a second active store in the directory
Related topics
- For the big picture — How to run multiple stores from one catalog.
- If the assortment is built but the product is not on the site — per-store checks.
- If a supplier fills the assortment and you need to know when prices and stock arrive — Base catalog update.
- If you need to assign categories to stores — Category tree.
