Elbuz Tunnel lets you decide what to write to your website database and how: which fields to update, what to show for each stock status, and where to put custom field values — mostly without any SQL.
When you need this:
- Descriptions are edited right on the website — clear “Update” in its row, and the tunnel won't touch it.
- Website statuses have different names — “Title on site (in file)” matches them to Elbuz statuses.
- The website should get the RRP if there is one — the “Formula” column writes an expression instead of the value.
Where to start: tunnel template card → “Additional” column.
What the tunnel's fine-tuning settings do
- Stock statuses — quantity, product activity, and the status name on the website.
- Custom fields without SQL — website properties and price types filled from catalog fields.
- Field by field — what not to update and where to write a formula.
- Your own SQL queries — when you can't do without them.
Which windows the “Additional” column has
The “Additional” column sits to the right of the card sections (in a narrow window, below them). It has seven link rows, each opening its own window: “Schedule”, “Stock-based update setup”, “Export fields”, “SQL queries”, “Additional settings”, “Description generator”, “Restore site database”.
The eighth, “Photo”, appears after “SQL queries” once you select “Photo” in the “What to export” section; until then, a hint is shown. Three rows exist only in the tunnel: “Additional settings”, “SQL queries” and “Restore site database” (it has a separate section). In the tunnel, “Stock-based update setup” also has a block that feeds lack.
1
Stock-based update setup2
SQL queries3
Photo settings hint4
Additional settings5
Restore site database- Stock-based update setup — what to write to the site for each stock status.
- SQL queries — your own queries against the site database.
- The photo settings row appears once the “Photos” checkbox is on.
- Additional settings — where to put the values of non-standard site fields.
- Restore site database — the list of archived copies of the site database.
“Photo” (the folder on your hosting for files, the number of threads), “Description generator” and “Schedule” work the same way as in other export types.
The “Photo” window has a “Download photos linked in category and product descriptions to local disk” checkbox: the tunnel uploads the images that descriptions link to onto your website hosting and replaces the links in the text with addresses on your website.
It doesn't apply to Elbuz CMS store articles: images in blog article text stay as links to Elbuz storage (Elbuz CMS blog). The checkbox processes Elbuz CMS category and product descriptions just like on other websites.
What the website gets for each stock status
Here you set what to write to the website for each stock status in your catalog: quantity, product activity and “Title on site (in file)”. A cleared “Active” checkbox in a row means “don't substitute anything” — quantity and activity go out as set in the product card.
The “Title on site (in file)” field is for when website status names differ from Elbuz ones. Linking to the website's status list works only for OpenCart, all three versions: the app looks up the status in the website table — by your name if the field is empty, otherwise by the entered one.
For other platforms, the status list isn't touched, but the value still replaces the status name in the data sent to the website.
What to do with products that are on the website but weren't included in this run is a separate rule below the table: how to disable products on the website that are missing from the export.
How to put a value into a custom website field without SQL
The tooltip of the “Additional settings” row is “Select objects to sync with the site”. The window shows what exists on your website: stores (warehouses), languages, categories, blocks, product options, attribute blocks, product attributes, trade catalog prices and parameters.
The list isn't made up: the cloud button in the window's top row reads it from the website database (tooltip “Refresh object list”); select what takes part in the exchange. The trash button next to it (tooltip “Clear list of objects”) erases the list to read it again. These two buttons have no labels, only icons.
This is also where you do what would otherwise take : next to a website object, you specify the base catalog field whose value will go there.
Price types are matched the same way: find the price read from the website and specify which Elbuz price field to take it from. You can write an expression in the same field — for example, multiply the price by an exchange rate.
The task “put an Elbuz field value into a custom website field” is almost always solved here, without a single line of SQL. Go to “SQL queries” when the object you need isn't in this list or you need more complex logic.
How to skip updating a field or write a formula
A mapping table “catalog field → website database field”. The “Update” column turns off a single field: if you don't want the tunnel to touch the description on the website, clear the checkbox, and the description stays as it was edited on the website.
The “Formula” column lets you write an expression to the website instead of the value itself. You write it in MySQL, and refer to temporary table fields with the etrade_temp. prefix:
IF(etrade_temp.price_rrp > 0, etrade_temp.price_rrp, etrade_temp.price) — “if the RRP is filled in, send it to the website, otherwise the regular price”. Your own base catalog fields work the same way: their names look like etrade_temp.product_f451, and the field number is shown in the base catalog grid column settings.
The formula applies only when updating records that already exist on the website. A product this run creates for the first time gets the regular field value, without the formula. So don't test the formula on newly added products: check ones already on the website. Also, a fixed value on the same row takes priority — the formula is ignored.
When you need your own SQL queries
Three tabs: “After update” (opens first), “Before update” and “Open link” — the last field is labeled “Open link or execute PHP script (run after update)” and triggers something on the website after a run, such as a cache reset. It runs only if the upload succeeded. Queries run in the website database.
You come here in two cases: when the standard update isn't enough (rewrite SEO URLs of existing products, fill in a custom field) and when your CMS isn't in the list and the whole merge is written by hand. Both are covered separately — updating your website with your own SQL queries: temporary tables, the ;;; separator, ready-made query examples.
Scenarios
Product descriptions are edited right on the website
What to do. Open “Export fields” and clear “Update” in the description row.
What you get. The description on the website stays as edited in the website admin panel. What won't happen. The other fields keep updating as before.
The website should get the real quantity from the product card
What to do. In “Stock-based update setup”, clear “Active” for all statuses.
What you get. Quantity and activity go out as set in the product card. What won't happen. Quantity substitution by stock status.
What to do when a field didn't reach the website
| What you see | Why | What to do |
|---|---|---|
| fields are filled in, but and Meta title didn't reach the website | The CMS may not have these fields at all — then they're not in the field export settings either | Check whether these fields exist in the website tables. If they do but aren't in the field list, update them with your own SQL query (about queries) |
| You need to update data from an additional catalog field on the website, but it's not in the field list | Additional fields aren't part of the standard list | First check “Additional settings”: if the website object you need is there, specify the field next to it without any SQL. No such object — then an SQL query to the website table (about queries) |
| The website gets a different quantity than the one in the product card | That's by design: by default, the quantity on the website is set by the stock status, not the stock balance. The tunnel overwrites quantity and activity according to the template's stock settings | Open “Stock-based update setup” in the template card and clear “Active” for all statuses — then the real quantity from the card goes out |
FAQ
The formula in “Export fields” didn't work on new products. Why?
The formula applies only when updating records that already exist on the website. A product created by this run gets the regular field value. And if a fixed value is filled in on the row, the formula is ignored.
How do I refer to my own catalog field in a formula?
Use the etrade_temp. prefix and the field number, for example etrade_temp.product_f451. The number is shown in the base catalog grid column settings.
The status name on the website doesn't match Elbuz. What should I do?
Enter it in “Title on site (in file)”. For OpenCart, the app finds the status in the website's status list by this name; for other CMS platforms, the value simply replaces the status name.
Why is the “Additional settings” window empty?
The list isn't made up: it's read from the website database. Click the cloud button “Refresh object list” in the top row of the window.
Which employees can change these settings?
Anyone with access to the template card. Only “SQL queries” and “Restore site database” have their own permissions.
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
- Access right
- the template card; “SQL queries” has its own permission
- Prepare
- a tunnel template connected to your website
The windows in the “Additional” column have no permissions of their own: anyone who can open the template card can also open “Stock-based update setup”, “Export fields”, “Photo”, “Additional settings” and “Description generator”.
Only “SQL queries” and “Restore site database” have their own permissions: both operations can't be undone, so the permission is checked not only when the window opens but also on the action itself.
Related topics
- For the big picture of the tunnel — How to export products straight into your website database with Elbuz Tunnel.
- If you can't do without queries — Updating your website with your own SQL queries.
- To choose which data goes out at all — What goes to your website through Elbuz Tunnel.
- To hide products that aren't in the export — How to remove products from your website that are no longer in the catalog.
