Elbuz Tunnel builds the same category tree on your website as in your catalog: each selected category goes with its parents, and the catalog is tidied up first.
When you need this:
- Only a child category is selected — its parents go too, so it lands in place.
- One catalog, several websites — skip a site's root label; its sections become the top menu level.
- A category is disabled — its products are disabled in the catalog and reach the website inactive.
- Products have empty SEO URLs — the tunnel fills them in, existing ones stay.
Where to start: tunnel template card → “Product selection” section → “categories” button.
What the tunnel does with categories
- Same tree as the catalog — a selected category goes with its chain of parents.
- Root label — a category that marks a website but never reaches the website itself.
- Remove a label already on the website — the steps that keep your products.
- Catalog preparation — internal IDs, main photo, products of disabled categories, SEO URLs.
Which categories go to the website
Products are selected strictly by the categories you marked with the “categories” button. Categories are selected more broadly: each marked category goes to the website with its whole chain of parents, up to the root. Mark “Sneakers” inside “Footwear”, which sits inside “Clothing”, and all three go to the website, with the same structure as in your catalog.
The reason: the website builds its tree from each category's link to its parent. A category without a parent would become a root category on the website, and every following run would put it back at the root, even if you fixed the structure by hand in the website admin.
You don't need to mark the parent in the filter: the selection tree won't even save it unless all its children are marked, and it goes to the website anyway.
A parent category is left out in two cases: the “Export to file (to website)” switch is off in its card, or the template has a “Store” selected that the category isn't assigned to.
Then only that category is skipped: its children arrive without a parent and become root categories on the website. Products are not affected: a product from a marked child category still goes. The only product left out is one with no marked category that has the switch on.
- Action or result
- Decision: the path depends on the answer
A root category as a site label
The typical case is one Elbuz catalog for several websites. The root holds label categories that no website needs, and under them sit the sections of a particular store:
- “Clothing site” → “Women's clothing”, “Men's clothing”, “Footwear”;
- “Electronics site” → “Smartphones”, “Laptops”, “Headphones”.
To make “Women's clothing”, “Men's clothing” and “Footwear” the top menu level on the clothing website, without a “Clothing site” label:
- in the “Clothing site” category card, turn off “Export to file (to website)” and save; do the same for “Electronics site”;
- in the clothing website's tunnel template, use the “categories” button to mark the categories under the “Clothing site” label;
- run the export.
1
Export to file (to website)2
Gadgets category- Export to file (to website) — when on, the category and its products go to the site on export; turn it off to leave the category out.
- Gadgets — the root category in the tree; click a category to open its card on the right.
The switch is a property of the category, not of the template, so the label won't go to any export template: not to another website, not to a feed. For a category that only marks a website, that's exactly right.
If an intermediate category has to show on one website but not on another, the switch won't help: it works the same for all templates.
The root category is already on the website
Turning off the switch isn't enough here. The tunnel looks for the parent category among those already on the website, so as long as the label is there, child categories keep attaching to it. Disabling it in the website admin doesn't work either: it hides the label and everything inside it. Do this:
- turn off “Export to file (to website)” in the category card in Elbuz;
- delete this category in the website admin. If the website deletes its subcategories along with it (OpenCart does), that's fine: the next run recreates them as root categories, with the same names, URLs and product links. Only edits made to these categories directly in the website admin are lost;
- start a full run. If the template has “Only export new data” on, clear it for this run: otherwise unchanged categories and products won't be sent and won't land in place.
What the tunnel does to your catalog before sending
The tunnel doesn't just read the base catalog — at the start of every run it edits it. Four actions:
- Assigns internal IDs (uuid) to products, categories, manufacturers and attributes that don't have them yet. That's how Elbuz later recognizes the same item on the website.
- Fixes the main photo: each product keeps exactly one main image — the first one in the list. Extra main flags are removed.
- Disables products of disabled categories. If a product's main category is inactive, the product gets the inactive status in your base catalog and goes to the website that way. This isn't a temporary export flag, it's a change to your catalog. One exception: products with the “Do not update” flag are not affected by this rule.
- Fills in empty SEO URLs — only the empty ones; existing URLs are left alone.
You disabled a category “for a while” to keep it off the website, and then saw that all its products became inactive in Elbuz itself. That's by design: a disabled category means “these products aren't for sale”. To remove a category only from the website and keep its products active, turn off “Export to file (to website)”, not “Activity”.
If the category is already on the website, the switch alone isn't enough — see what to do with a category already on the website. The same mechanism runs when updating the base catalog from price lists, so you can see the effect even without an export.
Scenarios
One catalog for two websites, “Clothing site” and “Electronics site” labels not needed
What to do. Turn off “Export to file (to website)” in the cards of both labels, and in each website's tunnel template mark the categories under its label (step by step).
What you get. “Women's clothing”, “Men's clothing” and “Footwear” become the top menu level on the clothing website. What you won't get. The label doesn't go to any export template — not to another website, not to a feed.
Remove a category from the website but keep its products active
What to do. Turn off “Export to file (to website)” on the category, not “Activity”. If the category is already on the website, delete it in the website admin and start a full run (what to do with a category on the website).
What you get. The category no longer goes to the website, and its products stay active in the catalog. What you won't get. Products with no other marked category that has the switch on won't go to the website either.
New category URLs must reach the website
What to do. Nothing for empty SEO URLs — the tunnel fills them in before sending. For existing URLs, add your own query (extend the standard CMS update).
What you get. Empty URLs get filled in. What you won't get. The tunnel doesn't rewrite existing SEO URLs.
What to do when the website shows the wrong categories
| What you see | Why | What to do |
|---|---|---|
| After a run, products on the website became inactive, and in Elbuz they are no longer active | The product's main category is disabled: the tunnel disables such products in the base catalog before sending | Enable the category; to remove it from the website, turn off “Export to file (to website)”, not “Activity” (what the tunnel does to the catalog) |
| New root categories appeared on the website, and child sections now sit inside them | Marked categories go to the website together with their parents, if those have “Export to file (to website)” on | Turn off the switch in the root category, delete it on the website and start a full run (root category already on the website) |
FAQ
What happens to products if I disable a category?
Before every run, the tunnel disables products whose main category is inactive — in your base catalog, not just in the export. To remove a category from the website and keep its products active, turn off “Export to file (to website)”, not “Activity”.
How do I export only child categories to the website, without the root?
Turn off “Export to file (to website)” in the root category: the children become root categories on the website. If the root is already on the website, delete it there and start a full run — otherwise the tunnel keeps attaching the children to it.
Do I need to mark the parent category in the template filter?
No. Each marked category goes to the website with its whole chain of parents, up to the root, if they have “Export to file (to website)” on.
Can an intermediate category show on one website but not on another?
Not with the “Export to file (to website)” switch: it's a property of the category and works the same for all export templates.
Will the tunnel rewrite SEO URLs that are already on the website?
No. The tunnel only fills in empty SEO URLs and leaves existing ones alone. You can rewrite them with your own SQL query (example).
Where it is and who has access
- Menu
- Directories → Operations → Data export → Elbuz Tunnel template card → “Product selection” section → “categories”
- Other entry points
- the category card in the catalog — the “Export to file (to website)” switch
- Access right
- the template card; the “categories” permission block
- Prepare
- a category tree in the base catalog
Related topics
- For the big picture of the tunnel — How to export products straight into your website database.
- To choose which products go — What goes to your website through Elbuz Tunnel.
- To remove categories that aren't in the catalog from the website — How to remove products from your website that are no longer in the catalog.
- If you're building the category tree itself — Category tree settings.
