↑↓ selectEnter openEsc close

    1. Elbuz

    How to export products straight into your website database with Elbuz Tunnel

    11 min readUpdated

    Elbuz Tunnel sends catalog products, prices and stock straight into your site database: no file or manual import, and new prices go live right after the run.

    When you need this:

    • Site on OpenCart, WooCommerce or another listed CMS — the tunnel reads database credentials from the site config.
    • Daily price and stock updates — a schedule with “Only export new data” sends only changes.
    • A faulty export reached the site — the tunnel backs up the database before merging.
    • Custom-built site — “MySQL (SQL custom query)” mode lets you write merge queries yourself.

    Where to start: put the module on your hosting, then “Add” → “Elbuz” → “Elbuz Tunnel”.

    What the tunnel can do

    • Data without a file — products, categories, manufacturers, photos, articles and reviews go straight into the site database.
    • Connecting the site — installing the module; the app sets up the password and database access itself.
    • Choosing data and filtering — what to export, which price goes out and which products.
    • Categories — the site tree matching the catalog, labels for multiple sites.
    • Cleaning up the site — disable or delete whatever is not in the export.
    • Backup copy — a database copy before the merge, and restoring from it.
    • Fields and statuses — what to write to the site, formulas, non-standard fields.
    • Custom SQL queries — for a not on the list and for add-ons.

    How the tunnel differs from a file feed

    A feed has a file: the app builds it, puts it in your account folder and gives you a link to hand to the marketplace. A tunnel has no file.

    The app writes the data to internal files, and the , a module on the site hosting, picks them up.

    It loads them into temporary tables in the site database and runs a set of merge queries. After that, the internal files and temporary tables are deleted.

    What this means in practice:

    • The “File” column in the template list is empty, and the tunnel template has no “Copy link” button. This is not a fault: a tunnel template creates no file — the data goes straight to the site.
    • Data appears on the site immediately — at the moment of the run, not when the marketplace decides to fetch the feed.
    • It sends more than products. A feed carries products and categories. The tunnel can also send manufacturers, attributes, options, photos as files, languages, stores, warehouses, articles, reviews, FAQ and product families.
    • Mistakes cost more. You can simply not hand a faulty feed to the marketplace. The tunnel has already written the data to the site database — that's why it has a backup copy and restore.

    The tunnel has no test run for a single product. The flask button “Check”, which tests one product in feeds, replies here: “The check is not available for this template format yet”. You can only test with a full run and its log — all the more reason to keep the backup copy turned on.

    Running and scheduling

    You run a tunnel template like any other — with “Export” in its list row. The “What will be exported” dialog opens first (you can turn it off for the whole account), and the run starts from it. The template card itself has no run button: its header only has the state badge and the chart button “Run history”.

    Stop rules always apply: if a rule is in “Stop the export” mode and the threshold is exceeded, the run never reaches the site. Details are in the articles on running and on stop rules.

    You set the schedule with the “Schedule” row in the “Additional” column on the right of the template card.

    A run goes in batches: per batch the module gets 50 rows and works up to 15 seconds, then the app polls its status and sends the next batch. Polling runs every 3 seconds; the log shows “N rows loaded” lines. That's why a large catalog takes long: the module works in short bursts, not one long request.

    The “Stop” button in the Operations center acts between batches: the app waits for the current batch to finish and writes “Export stopped by the user!”. What has happened by then depends on the step.

    During data transfer the storefront doesn't change at all — everything sits in temporary tables. Once the merge starts, some data is already on the site; that's normal, and the next run completes it. In an Elbuz CMS store, stopping also affects the photo upload step.

    The order of steps in the log is the same in every run. Transfer comes first — the “Export …” lines: currencies and rates, languages, contacts, units of measurement, stores, warehouses, product categories, products, manufacturers, attribute groups, attributes, attribute values, photos, articles, reviews, FAQ, product families.

    Which lines appear depends on what you have selected. Then the merge starts, and its lines depend on the site's engine.

    For OpenCart: “A backup copy of the site database has been created:”, “Deleting items from the site database that were deleted earlier”, “Running SQL before updating”, “Synchronizing item IDs with the site database”, “Updating site”, “Updating attributes”, “Executing SQL queries after update”, “Deleting temporary tables and files”. The last line is “Data export completed” with the time taken.

    Before the first run

    Elbuz CMS store: exporting changed products only

    An Elbuz CMS store template with the “Only export new data” toggle on compares product data in Elbuz with the previous send to this site before sending, and sends only the products that differ. In a new store the toggle is on by default.

    Where the product change came from doesn't matter: an edit in the card, an import or a price list. A product missing from the site is sent too, even if it was deleted there by hand. On a catalog of 127 thousand products, a run with no changes takes under a minute versus 18 for a full send.

    Only products that pass the template filter are compared. Categories, manufacturers, attributes and articles, if selected, are sent in full in every run that updates the site. The log line “Change check: N of M products will be sent to the site” shows how many go out, where M is the products that pass the filter.

    If neither products nor reference data changed, nothing awaits deletion, and the template has no custom SQL queries or script, the site isn't updated: the log shows “No changes: products and reference data match the site, the site was not updated”.

    A demo account and “Test export” do no comparison: they send a limited number of products.

    When the whole catalog is sent automatically

    • Once a week and in the first run with this toggle.
    • Template settings or attributes changed: data and deletion flags, filter conditions, fields, statuses.
    • “Delete if not in export” is on: this rule needs the full list, so the catalog is sent in every run.
    • More than half of the products changed.
    • The comparison failed. The run doesn't fail with an error; it sends the whole catalog.

    The comparison doesn't notice changes to the description template or SQL queries. After such a change, click “Export everything”.

    The “Export everything” button

    It sits below the “Export” button in the right column of the template card and sends the whole catalog even if nothing changed. The run starts at once, without the “What will be exported” dialog. The button is visible when the toggle is on and the store has had its first export.

    Store card header with the Export everything and Export buttons
    1Export everything
    2Export
    1. Export everything — sends the whole catalog to the store again, not only the changed items.
    2. Export — sends only what has changed since the last run.

    The comparison doesn't see edits made on the site or in its database: it doesn't read the site. Such an edit stays until the product changes in Elbuz or a full export runs; then the exported fields get the Elbuz data. To keep an edit, make it in Elbuz. To restore Elbuz data on the site at once, click “Export everything”.

    How stopping affects the photo upload

    During the photo upload, “Stop” takes effect between batches: the current batch finishes, usually within 30 seconds, at most about 45. A stopped run doesn't count as completed, so the next run sends the same products again.

    Scenarios

    Update prices and stock on the site every day

    What to do. In the “What to export” section, keep “Categories”, “Products”, “Manufacturers” and “Only export new data” on. Set a schedule with the “Schedule” row in the “Additional” column.

    What you get. Each run takes only the products, categories and manufacturers changed since the last run. After a successful load to the site, it marks as exported the sent products with their photos and attribute values, plus the categories, manufacturers and attributes of the whole catalog.

    If the load breaks off (an error in the “After update” queries, a lost connection to the module), no marks are set, and the next run sends the same changes again. The site price is the RRP if it's filled in and “Update website price based on RRP” is on; otherwise it's the regular product price.

    What you won't get. A product that hasn't changed in the catalog isn't rewritten on the site: an edit made in the site admin stays until this product next changes in Elbuz. Products, categories and manufacturers aren't deleted from the site while no flag is selected in the “Deletion” section. In an Elbuz CMS store this mode works differently.

    Your site's CMS isn't on the list

    What to do. In the “Site and CMS” section, choose “MySQL (SQL custom query)”, enter the database details by hand, and describe the merge with queries in the “SQL queries” window.

    What you get. The tunnel loads the selected data into temporary tables in the site database, then runs your queries. What you won't get. The app won't read the site configuration, and no database backup copy is taken in this mode. Step by step — updating the site with custom SQL queries.

    What to do when a run fails

    What you seeWhyWhat to do
    “Scheduled export canceled because another template is being exported (data processing conflict).” Two scheduled exports overlapped Spread the template schedules apart in time (on running)
    “Export stopped by the user!” Someone clicked “Stop” in the Operations center; the run ended at a batch boundary Nothing. Some data is already on the site; the next run sends the rest
    “The check is not available for this template format yet” The tunnel has no single-product test run Run a full export and watch the log in the Operations center
    “Warning: you are using the DEMO version! Product export is limited to 100 products.” Demo account: the first 100 products and 500 photos go to the site Top up your balance — menu Account → Balance → Payment

    FAQ

    Why is the “File” column empty for my tunnel template?

    Because a tunnel has no file. The data goes straight into the site database, and no link to hand to anyone is created. An empty “File” column for a tunnel template is normal.

    Can I test one product before a full run?

    No. The “Check” button in a tunnel replies “The check is not available for this template format yet”. The only test is a full run and the log in the Operations center, so keep the backup copy on before the first run.

    My site isn't on a CMS from the list. Won't the tunnel work?

    It will: the engine list has a “MySQL (SQL custom query)” item for any other engine. You enter the database details by hand, and the merge queries go in the “SQL queries” window.

    How is the export tunnel different from “Data import” through the tunnel?

    Direction. Export takes the catalog from Elbuz to the site. Orders, customers and reviews from the site are fetched by “Data import” — the neighbouring menu item with its own template, through the same module (import through the tunnel).

    Why does a large catalog take long to export?

    A run goes in batches: per batch the module gets 50 rows and works up to 15 seconds, then the app sends the next batch. The log shows progress as “N rows loaded” lines. In an Elbuz CMS store an unchanged catalog goes through faster: only changed products are sent.

    I fixed a price directly on my Elbuz CMS store. Why doesn't the run touch it?

    The comparison checks Elbuz data against the previous send and doesn't read site content. The edit stays until the product changes in Elbuz or a full export runs, for example the weekly one or via the “Export everything” button. Then the fields the template exports get the Elbuz data.

    Where to find it and who has access

    Menu
    Directories → Operations → Data export
    Other entry points
    “Add” → “Elbuz” group → “Elbuz Tunnel”; the “Export” shortcut on the desktop
    Access right
    the “Data export” window and, separately, the template card
    Prepare
    the module in the site root; PHP mysqli, zip and curl on the hosting
    Directories → Operations menu with the Data export item
    1Data export
    2Data import
    1. Data export — opens the window where export templates to your site are set up and run.
    2. Data import — the opposite direction: loading data into Elbuz, easy to confuse with export.
    Add menu of the Data export window scrolled to the Elbuz group
    1Elbuz group
    2Elbuz Tunnel
    1. Elbuz — the group of Elbuz's own destination types.
    2. Elbuz Tunnel — the destination type for exporting to your own site through the tunnel module.

    The tunnel has no menu item of its own: it is one of the template types in the shared export window. Everything about templates in general — the list, the pre-run summary, stop rules, the run log — is covered in the article on export templates.

    The tunnel is in every account, no separate module needed. Users with access to the window but not to the template card see the list of channels but can't open the settings.

    How data travels from the base catalog to your CMS working tables
    “Stop the export” modeWithin the threshold or“Warn”Elbuz base catalog: products,categories, manufacturersPreparation: uuid, main photo,empty SEO URLs, deactivatingproducts in disabled categoriesFiltering: product flag, category flag,“Additional filter”, selectedcategories, storeStop rules: difference from theprevious run above the threshold?Run stopped, the site is not changedCSV files in the account folder, oneper entityTunnel module on the site hostingTemporary tables in the sitedatabaseBackup copy of the site DB in theetrade_http_tunnel2/backup folderSQL “Before update”Merge: categories, products,manufacturers, attributes, options,photosDeletion on the site, if deletion flagsare onSQL “After update” and URL callCMS working tables: the site showsthe new dataTemporary tables and files aredeleted
    • Action or result
    • Decision: the path depends on the answer

    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