↑↓ selectEnter openEsc close

    1. Elbuz

    What goes to your website through Elbuz Tunnel: data, price and product selection

    4 min readUpdated

    Elbuz Tunnel exports only what you checked in the template, and only products meeting the selection conditions. The price comes from the catalog without markups, except for RRP.

    When you need this:

    • Multilingual website — the “Languages” checkbox sends all languages marked for export.
    • A product is disabled in the catalog — it goes to the site disabled and is switched off there, not left on sale.
    • Several websites from one catalog — the “Store” field filters out other stores' products, categories and manufacturers.
    • Daily updates — “Only export new data” sends only changes since the previous run.

    Where to start: tunnel template card → “What to export” section.

    What tunnel data selection can do

    • Data set — products, categories, manufacturers, photos, attributes, languages, warehouses, articles, reviews.
    • Price — the catalog price, or the RRP if it's filled in.
    • Product selection — categories, “Additional filter” and store; disabled products go too.

    What exactly to export

    In the “What to export” section, the “Select data to export” card has thirteen checkbox toggles in a row (an enabled toggle is highlighted), fourteen for OpenCart 3: the fourteenth, “Product Families”, appears only for this . A new template has three on: “Categories”, “Products”, “Manufacturers”. The rest are off: “Photo”, “Attributes”, “Options”, “Languages”, “Stores”, “Warehouses”, “Articles”, “Reviews”, “FAQ”, “Product Families”, “Orders”.

    The “Select data to export” card: a row of toggle chips for the data types and the “Only export new data” chip below
    1Categories
    2Languages
    3Stores
    4Only export new data
    1. An enabled chip is highlighted; categories are exported together with the products.
    2. All languages marked for export are sent, not just the main one.
    3. Prices and stock are split by store; this is not a product filter.
    4. Only what changed since the previous run is exported.

    Three checkboxes control not what data goes but how deep it goes, and they're the most common source of confusion:

    • “Languages” off — only the catalog's default language goes to the site. Turn it on, and every language marked for export goes. The tunnel has no separate export language field like feeds do.
    • “Stores” is about prices and stock broken down by store, not about selecting products. Off — the main store's data is used. To limit the export to one store, use a different setting: the “Store” field in the “Product selection” section.
    • “Warehouses” works differently: the list of warehouses always goes to the site, and the checkbox turns on stock and prices by warehouse. Off — the site gets the product's total stock, not split by warehouse.

    You can't turn off “Products” and keep “Photo”, “Attributes” or “Options”: without products, they won't reach the site.

    The app warns you right in the form: as soon as you turn off “Products” with photos, attributes or options checked, a note appears under the toggles: “Photos, attributes and options are exported only together with products: without the Products checkbox none of these blocks reaches the site.” For CS-Cart, attributes are always exported, whatever the checkbox says.

    A separate toggle below the rest is “Only export new data”. In a new template it's on: only what changed since the last run goes to the site. For daily updates, this is the cheapest mode.

    Related products

    Related products are set in the product card in Elbuz: the “Relations” section → “Related products”. They reach the site only with the “Update related and recommended products” rule, in the template card's “Additional settings” window. Without this checkbox, related products from Elbuz don't reach the store, and the lists on the site stay as they were.

    With the checkbox on, every product in this export gets exactly the related products it has in Elbuz on the site: the old list is replaced. In an Elbuz CMS store template, the rule is on from the start; for your own OpenCart site, check it yourself.

    Don't keep “Only export new data” on together with the “If the product is not in the export” rule (the “Stock-based update setup” window). The first sends only changed products, the second disables on the site everything that wasn't in this export. Together they switch off the whole site catalog except a few just-updated items.

    Which price goes to the website

    In the “Prices” section, the “Detailed settings” card has the “Update website price based on RRP” checkbox, and in a new template it's on.

    It works simply: if the product has an filled in (greater than zero), that's what goes to the site; if not, the regular product price goes. The value is rounded to two decimal places.

    There are no markups, coefficients or formulas at this step: the only price source is the , and the number goes to the site as is. If the price needs to be calculated differently, do it earlier, when the catalog is updated from supplier price lists.

    The card's second checkbox is “Update option values based on option products”. It carries the price and stock of variant products into option values on the site. This works only for OpenCart 2 and VirtueMart; for OpenCart 3 and other platforms the checkbox changes nothing.

    Which products go and which don't

    The selection conditions live in the same block as for feeds: “Export limit (filter)” in the “Product selection” section. The “Set filter by:” panel has a “categories” button (with a count of selected items and two selection modes, tree or list) and the “Additional filter” condition builder for product grid fields.

    The app adds its own conditions to yours. Altogether, a product goes to the site if:

    1. it has the “Export to file (to website)” flag;
    2. it has at least one category with the “Export to file (to website)” flag;
    3. the category is among the selected ones, if you selected any with the “categories” button;
    4. it meets the “Additional filter” conditions, if you set any;
    5. it's assigned to the store selected in the “Store” field, if a store is selected, and its category is assigned to the same store;
    6. it changed since the last run, if “Only export new data” is on.

    Here's where the tunnel differs from file exports and behaves differently.

    The tunnel has no “Active = yes” condition. A new template of any other type gets this condition in the “Additional filter” right away, and a disabled product doesn't go into the file. A tunnel template has it removed right after creation, on purpose.

    A disabled product goes to the site with its disabled status and is switched off there. The point is: you can simply leave a product out of a file, but on the site the product page already exists. It has to be disabled, or it stays on sale.

    A disabled category behaves the same way. In a feed, its products simply don't go into the file; in the tunnel, it disables its products while still in the catalog — see what the tunnel does with the catalog.

    The “Language ID” and “Warehouse ID” fields from the feed form aren't in the tunnel: the “Languages” and “Warehouses” checkboxes do their job. The “Store” field with the “In stock at this store only” checkbox is there, but it does more than in feeds. In a feed, the selected store filters out only products.

    In the tunnel, it also filters out categories and manufacturers. A category not assigned to this store doesn't go to the site, so its products have nowhere to appear. A manufacturer not assigned to the store isn't sent to the site, though the product itself still goes.

    If the template's selected store is later deleted, the tunnel sends nothing to the site. The log shows a 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.” The site stays unchanged. More on store assortments: about stores.

    A demo account has a hard limit: only the first 100 products and the first 500 photos go to the site, and the log shows a separate line about the demo version.

    Scenarios

    One catalog for two websites

    What to do. Create a separate tunnel template for each website, and in each one select its own store in the “Store” field. If only products in stock at that store should reach the site, check “In stock at this store only”. Remove each site's root label category, as described in the section about labels.

    What you get. Each site receives only the categories, products and manufacturers assigned to its store.

    What you don't get. The “Stores” checkbox in “Select data to export” doesn't limit what's exported: it's about prices and stock broken down by store.

    A product has one “already exported” mark, not one per template, and a run marks categories and manufacturers across the whole catalog. If “Only export new data” is on in both templates, the second one won't see changes to shared products, categories and manufacturers that the first one already took. Keep this checkbox on in one of them at most.

    Multilingual website

    What to do. In the “What to export” section, turn on the “Languages” toggle.

    What you get. Every language marked for export goes to the site. What you don't get. The tunnel has no separate export language field like feeds do: without the checkbox, only the catalog's default language goes.

    The website shows the RRP where there is one

    What to do. In the “Prices” section, leave “Update website price based on RRP” on.

    What you get. A product with an RRP filled in gets it on the site; the rest get the regular price, rounded to two decimal places. What you don't get. There are no markups or coefficients at this step; other price logic is set with a formula in the field settings.

    What to do when the wrong data reaches the site

    What you seeWhyWhat to do
    “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.” The store selected in the template's “Store” field was deleted. In this case the tunnel sends nothing to the site, and the run ends with the line “Data export NOT completed: the file was not generated” Select an existing store in the “Store” field, or clear the selection to export the whole catalog (about product selection)
    A product disabled in the catalog appeared on the site as disabled A tunnel template has no “Active = yes” condition: a disabled product goes to the site with its status Nothing, it's by design: the product page on the site should be switched off. To stop the product from going at all, clear its “Export to file (to website)” flag
    Only one language reached the site The “Languages” checkbox is off, so only the catalog's default language goes Turn on “Languages” in the “What to export” section (about the checkboxes)

    FAQ

    Will a disabled product go to the website?

    Yes, and this is how the tunnel differs from file exports. A tunnel template has the “Active = yes” condition removed right after creation: a disabled product goes to the site with its status and is switched off there.

    Photos, attributes and options didn't reach the website. Why?

    They're exported only together with products: if “Products” is off, no photos, attributes or options go. For CS-Cart, attributes always go, whatever the checkbox says.

    Does the “Stores” checkbox limit what's exported?

    No, it's about prices and stock broken down by store. To limit the export to one store, use the “Store” field in the “Product selection” section.

    Why does the website show total stock instead of stock by warehouse?

    The “Warehouses” checkbox is off, so the site gets the product's total stock. Turn it on, and stock and prices by warehouse go.

    How many products go to the website from a demo account?

    The first 100 products and the first 500 photos; the log shows a separate line about the demo version.

    Where it is and who has access

    Menu
    Directories → Operations → Data export → Elbuz Tunnel template card
    Other entry points
    the “What to export”, “Product selection” and “Prices” sections of the template card
    Access right
    the template card; separate permission blocks lock the data checkboxes
    Prepare
    a tunnel template connected to your website

    There are six permission blocks: categories, products, manufacturers, attributes, options, photos. A revoked block doesn't hide a checkbox but locks it: visible, not editable. In the tunnel form, the “products” block also controls the checkboxes for languages, stores, warehouses, articles, reviews, FAQ, families and orders, both “Detailed settings” options, the whole archiving section and the “Store” field.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free