Elbuz Tunnel disables or deletes website products that are no longer in the catalog or the export, as you choose. With no delete checkbox selected, nothing is deleted.
When you need this:
- A product was discontinued — the “If the product is not in the export” rule disables it and sets stock to 0.
- The website shows products long gone from the catalog — on OpenCart 3, “Delete if not in export” removes them after the run.
- You deleted a product in the catalog — with “Delete data immediately on the site”, it disappears without a run.
Where to start: tunnel template card → “Deletion” section.
What site cleanup can do
- Deletion by entity — twelve checkboxes: products, categories, manufacturers, photos and more.
- Deletion without a run — a product removed from the catalog disappears from the website right away.
- Disabling instead of deleting — products missing from the export are disabled on the site.
Deletion on the site
The “Deletion” section is the collapsed “Select data to delete on the site” card; click its title to expand it. It holds twelve checkbox toggles, one per entity: “Categories”, “Products”, “Manufacturers”, “Photo”, “Attributes”, “Options”, “Languages”, “Stores”, “Warehouses”, “Orders”, “Articles”, “Reviews”. The row below has the “Delete data immediately on the site” toggle, and for OpenCart 3 one more next to it — “Delete if not in export”.
1
Products chip2
Delete data immediately on the site3
Delete if not in export4
Clear delete flag- Choose which entities may be deleted on the site; while none is enabled, the site loses nothing.
- A product deleted in the catalog disappears from the site without waiting for an export run.
- OpenCart 3 only: removes on the site whatever is missing from the export.
- Resends the items that were already deleted.
As long as none of the twelve checkboxes is selected, the program deletes nothing on the site. This is the first thing the program checks before any deletion. You can't forget to turn deletion off, because it is off by default.
- “Delete data immediately on the site” — deletion without an export. The hint says it plainly: “For example, if you delete a product in the base catalog, it will be instantly deleted on the site”. So you remove a row in the catalog grid, and the product page on the website disappears right away, without running the export. Works only for enabled templates.
- “Delete if not in export” — “If an item on the site is missing from the exported data, it will be deleted from the site”.
“Delete if not in export” doesn't combine with “Only export new data”, for the same reason as the missing-products rule: the batch holds only a handful of changed items, and the rest of the website catalog is treated as surplus. Turn on one or the other.
The Elbuz CMS store blog removes articles and sections its own way. Records deleted in Elbuz (or taken off “Export to website”) disappear from the blog only in a run that meets all three conditions:
- the “Articles” toggle in the “Deletion” section is on;
- “Only export new data” is off;
- no branch is selected in the “Select article category” field.
In other runs the blog deletes nothing, because the export doesn't contain all articles. “Delete data immediately on the site” has no effect on blog articles. Store pages — articles marked for the header or footer, or with the “Landing page” type — are never deleted by the export: remove such a page in the store admin. How articles get into the blog: Elbuz CMS blog.
Below the toggles is the “Clear delete flag” button, with the hint “Clear the delete flag to delete products on the site again”. You need it when items were already deleted in Elbuz, the export somehow never reached the website, and there's nothing to retry the deletion with: the log of deleted items is already marked as processed. After you click it, the message “The log of deleted products is ready to be exported!” appears, and the next run deletes them again.
How to disable products on the site that are missing from the export
Where: the “Additional” column on the right of the template card → “Stock-based update setup”, the block below the status table.
Only in the tunnel does the “If the product is not in the export” block appear below the table, with the “Active” checkbox and the “Quantity” field. This rule covers products that already exist on the website but weren't included in this batch.
While the “Quantity” field holds -100, the rule is off and the program leaves such products alone. Enter any other number, and every website product that wasn't in the batch gets the specified status and stock.
1
Quantity field2
Active checkbox3
Product status on site column- The quantity assigned to products missing from the export (-100 here).
- Turns the “product is not in the export” rule on or off.
- Shows whether the product is active on the site for each stock status.
A typical case: you export only what's in stock. Products that weren't in the batch can get your own quantity and be deactivated, so they don't stay on the website as available. The rule works for OpenCart 2 and 3, CS-Cart, Magento and PrestaShop; it isn't available for WooCommerce or the “MySQL (SQL custom query)” mode.
The rule doesn't combine with “Only export new data”: the latter sends only changed products, while the rule disables everything on the website that wasn't in this batch. Together they disable the whole website catalog except a few just-updated items.
Scenarios
Disable products missing from the export on the website instead of deleting them
What to do. In the “Additional” column, open “Stock-based update setup”. In the “If the product is not in the export” block, clear “Active” and enter 0 in “Quantity”. In the “What to export” section, turn off “Only export new data”.
What you get. After the merge, every website product that wasn't in this batch becomes inactive with stock 0.
What you don't get. Product pages aren't deleted from the website — only disabled. While “Quantity” holds -100, the rule is off. The rule also catches products you created directly in the website admin: they are never in the export from Elbuz. The program doesn't have this rule for WooCommerce, HostCMS or “MySQL (SQL custom query)”.
Remove products from the website that are no longer in the catalog
What to do. This scenario is for OpenCart 3. In the “Deletion” section, expand the “Select data to delete on the site” card and turn on the “Products” toggle (plus “Categories” and “Manufacturers” if needed) and “Delete if not in export”. Turn off “Only export new data”. The “Additional filter” in the “Export limit (filter)” block must be empty.
What you get. At the end of the run, products that weren't in the export are deleted from the website database, together with their descriptions, photos, and category and store links.
What you don't get. If the “Additional filter” has even one condition, the checkbox deletes nothing. In platforms other than OpenCart 3, “Delete if not in export” has no effect.
The “categories” button and the “Store” field don't turn deletion off: a website product outside the selected categories or outside the chosen store also counts as missing from the export and is deleted — just like a product created only in the website admin.
A product deleted in the catalog should disappear from the website without a run
What to do. In the “Deletion” section, expand the “Select data to delete on the site” card and turn on the “Products” and “Delete data immediately on the site” toggles. The template must be enabled — see the status badge in the card header.
What you get. Deleting a product in the base catalog by itself, without running the export, sends a delete request to every website whose template has these two checkboxes on.
What you don't get. Nothing is deleted through a disabled template. Without the “Products” checkbox in the “Deletion” section, a product deletion isn't sent to the website, even with “Delete data immediately on the site” on: entity checkboxes work separately — categories need “Categories”, manufacturers need “Manufacturers”.
What to do when deletion didn't work as expected
| What you see | Why | What to do |
|---|---|---|
| “The log of deleted products is ready to be exported!” | You clicked “Clear delete flag” | Run the export — the deletions on the site are repeated (about deletion) |
| After a run, products created directly in the website admin were disabled on the site | The “If the product is not in the export” rule is on: such products are never in the export from Elbuz | Set the “Quantity” field back to -100 — the rule turns off (about the rule) |
| “Delete if not in export” deleted nothing | The “Additional filter” has at least one condition, or the website isn't on OpenCart 3 | Clear the “Additional filter”. In other CMS platforms this checkbox has no effect — disable products with the stock rule |
FAQ
Will the tunnel delete anything on my website if I haven't turned anything on?
No. As long as none of the twelve checkboxes in the “Deletion” section is selected, the program deletes nothing on the site: deletion is off by default.
I deleted a product in the catalog — when will it disappear from the website?
With “Delete data immediately on the site” and the “Products” checkbox selected — right away, without a run, but only through an enabled template. Without the “Products” checkbox, the product deletion isn't sent to the website at all.
Which CMS platforms support the “If the product is not in the export” rule?
OpenCart 2 and 3, CS-Cart, Magento and PrestaShop. It isn't available for WooCommerce or the “MySQL (SQL custom query)” mode.
What is the “Clear delete flag” button for?
It removes the “processed” mark from the log of deleted items, and the next run deletes them on the website again. You need it when items were deleted in Elbuz, but the deletion never reached the website.
Can I turn on deletion together with “Only export new data”?
No: the batch holds only a handful of changed items, and the rest of the website catalog is treated as surplus. Turn on one or the other.
Where to find it and who has access
- Menu
- Directories → Operations → Data export → Elbuz Tunnel template card
- Other entry points
- the “Additional” column on the right of the template card → “Stock-based update setup”
- Access right
- the export template card
- Prepare
- a backup of your website database before the first deletion
Related topics
- For the big picture of the tunnel — How to export products straight into your website database with Elbuz Tunnel.
- For a safety net before deleting — Website database backup and restore.
- To remove a label category from the website — How the tunnel exports categories.
- If you're setting up what the website shows for each stock status — Fields, statuses and website data in the tunnel.
