Elbuz pulls the catalog from your store's database via the Elbuz Tunnel module on your hosting: categories, products, manufacturers, attributes, photos, and orders — no files.
When you need this:
- Moving to Elbuz from OpenCart, Magento, or another CMS — the catalog and its categories come over in one run.
- The site stays the main source — the tunnel pulls prices, stock, and new products on schedule.
- Orders come in on the site — they become “Customer order” documents.
- The catalog must mirror the site — products removed from the site leave the base catalog.
Where to start: put the module on your hosting and create an “Elbuz Tunnel” template.
What the tunnel can do
- Connects to a site on OpenCart, Magento, WooCommerce, PrestaShop, CS-Cart — and to a less common MySQL-based system with your own SQL query.
- Transfers categories, products, manufacturers, attributes, options, and photos — you choose what with template checkboxes.
- Updates cards it has already transferred by the site's identifiers, without duplicates; leaves alone whatever is locked with flags on the card.
- Keeps the catalog a mirror of the site — removes what is no longer on the site.
- Pulls orders from OpenCart 2, OpenCart 3, Magento 1 and 2, and PrestaShop into “Customer order” documents.
- Runs on a schedule — the Elbuz catalog regularly picks up changes from the site.
How to connect the site to the tunnel
The template form has two tabs: “Connection” — the site's , version, and address; “Import” — what to transfer. No file is needed. Until the connection is set up, the button reads “Connect”, then “Check connection”.
1
CMS selection2
Site link field- CMS selection — pick the platform your online store runs on.
- Site link field — enter the store address, then press Connect (the button is right below).
Installing the module on your hosting
The tunnel is the etrade_http_tunnel2 folder in your site's root. Until it's there, there's nothing to connect to, so the first step is always to put the module on the server. It's a one-time job of a few minutes — the module then updates itself.
- Download the module. The “Download module” button in the template's “Select CMS” block gives you the current archive. Or use the direct link: etrade_http_tunnel2.zip.
- Unpack the archive on your computer.
- Copy the contents to your hosting — into the site's root folder, where the main
index.phpis, with theetrade_http_tunnel2folder itself. An FTP client such as FileZilla is handy here. The module's address then looks like this:https://your-site/etrade_http_tunnel2/etrade_http_tunnel.php. - Connect in Elbuz: in the template's “Select CMS” block, choose your CMS (for OpenCart, also the version), enter the site address, and click “Connect”.
Elbuz does the rest itself: it sets the module's access password (on first installation) and reads your CMS configuration file for the database connection parameters — server, database name, user, password, and table prefix. No manual entry needed. When it works, you'll see the message “Module connected successfully!”.
Besides the tunnel, the module folder has empty temp and backup folders: working files go in the first, archive copies of the site's database in the second. The hosting must have the PHP extensions mysqli, zip, and curl enabled.
The label depends on whether the connection is set up. While the parameters are empty, it reads “Connect” and runs the automatic setup. Once the credentials are filled in, “Check connection” takes its place: it reconfigures nothing, only checks that the module responds, and shows the module version and the hosting's PHP settings.
There's also a “Get settings” button in the manual parameters block — it re-reads the site configuration, for example after the database moves.
Then you enter the same parameters by hand:
- Link to the module —
https://your-site/etrade_http_tunnel2/etrade_http_tunnel.php; - Login —
admin; - Password — the one set in the
etrade_http_tunnel_login.phpfile inside the module; - Database access for the site — server, port, database name, user, password, and table prefix. You'll find these values in your CMS configuration file (usually
config.phpor similar).
Common reasons the automatic connection failed: the site address wasn't entered or the CMS wasn't chosen (Elbuz warns you in a separate window); the module wasn't copied to the site's root folder; the hosting blocks access to the module file.
Elbuz support can install and set up the tunnel for you — this requires access to your hosting. It's a separate service: write to support, and they'll tell you the terms.
Updating the module
Usually there's nothing to update by hand. Click “Check connection”: Elbuz compares the module version on your hosting with the latest. If there's a newer one, the line “A new version of the E-Trade Tunnel module is available:” and an “Update” button appear — the button updates the files on the site itself, no copying needed.
The manual route is needed when the automatic update fails — for example, the hosting doesn't let the module write to its own folder. Then you take the update archive: etrade_http_tunnel2_update.zip. Unpack it and overwrite the files in the etrade_http_tunnel2 folder on the hosting.
The update archive contains only the module core — the working files that need to be replaced with new ones. It doesn't contain what appeared on the hosting while the module was running:
etrade_http_tunnel_login.php— the file with the module's login and password. That's why an update doesn't reset access: the password Elbuz set at the first connection stays, and the connection needs no new setup;- the
backupfolder — archive copies of your site's database; - the
tempfolder — the module's working files.
That's why the update archive is unpacked over the existing folder, not in place of it. The full archive (etrade_http_tunnel2.zip) is only needed for the first installation — it includes these files and empty folders.
Which CMSs it works with and when to choose the tunnel
The tunnel connects to the database of a site on a popular CMS. The form asks for a version for only two systems:
| CMS | Version choice in the form |
|---|---|
| OpenCart | 2, 3 |
| Magento | 1, 2 |
| WooCommerce | — |
| PrestaShop | — |
| CS-Cart | — |
- MySQL (SQL custom query) — for a custom-built or less common MySQL-based system: you get the data with your own database query, see SQL queries in the tunnel.
- Elbuz CMS — the same tunnel for sites on our CMS.
- Extra fields for some CMSs appear in the form once you pick the system: for a multilingual site, the language to pull data in.
Choose the tunnel when your catalog already lives on your site. It reads the database as is: with the links between products, categories, and attributes, with full descriptions and all images. A file export from a CMS often loses some of these links.
The tunnel doesn't connect to marketplaces (Epicentr, Rozetka, Prom): for those, use import via API. To compare methods, see which method to choose.
What to transfer: template checkboxes
You choose what to transfer in the “Select data to import from the site” block on the “Import” tab. A new template has “Categories”, “Products”, and “Manufacturers” turned on; you add the rest yourself.
| Checkbox | What it does |
|---|---|
| Categories, Products | The core of the transfer — the catalog structure and the products themselves. Without them, the rest of the data has nothing to attach to |
| Manufacturers | Manufacturer names from the site go into your manufacturer list |
| Attributes | Properties and specifications — into the card, on the “Attributes” tab |
| Options | Size, weight, color — things that can affect the price on the site; also on the “Attributes” tab |
| Photo | Product images — into the card, on the “Photo” tab |
| Orders | Store orders — for OpenCart 2, OpenCart 3, Magento, and PrestaShop, see orders from your site |
The tunnel takes photos as links. Elbuz takes the image addresses, the files stay on your hosting, and there's no separate switch for this. The exception is the “Cloud photo storage” service: when it's on, files are downloaded to the Elbuz cloud, twenty downloads in parallel.
The “Delete entries in the base catalog that do not exist on the site” checkbox in the “Additional” section turns the transfer into a mirror of the site. Without it, data is only added and updated. More: mirror mode.
How to run the transfer and check the result
Once the connection is set up, click “Get product catalog” at the top of the form. Products appear in the base catalog: the “Base catalog products” shortcut or the “Directories” → “Base product catalog” menu.
- Request or action
- Reply
A run has two stages. First, Elbuz pulls data sets from the site one by one and stores them. Then it sorts them into the base catalog: deletion (in mirror mode), categories, manufacturers, products, attributes, orders, photos. Then field formulas, an integrity check, and indexing, as in any import (what happens after a run).
How to tell the transfer worked. The run log should show lines with numbers:
- “Total categories imported:”, “Total items imported:”, “Total manufacturers imported:”;
- “Total orders imported:” — if you pulled orders;
- “Data import completed!” and “Time elapsed:” — at the end.
Later, the date and duration show in the “Last import” column of the template list. The log lives in the “Operations” panel, so you can close the template window. More: how to check that the import went through.
The tunnel reads your site's database, and with the “Cloud photo storage” service it also downloads images. On a large catalog this puts noticeable load on the hosting, so do the first full transfer when your site has the fewest visitors.
How long Elbuz waits for the site
There's no cap on the number of products: each data set — categories, products, prices, photos, attributes, orders — is requested separately.
| Step | How long it waits |
|---|---|
| Establishing the connection to the module | 5 minutes |
| Module's response for one data set | 55 minutes |
If the module doesn't make it within these limits, the data set simply doesn't arrive, with no error in the log: only the line with that set's record count is missing. In mirror mode, the comparison then runs against an incomplete set.
If the transfer broke off or was stopped
- Start or end
- Action or result
- Decision: the path depends on the answer
- A break during reading doesn't change the base catalog. If the site didn't open the connection or the module returned an error, the log shows the site's response in red and the line “Import stopped!”.
- A break during writing keeps what was written. In mirror mode, deletion goes first, so the catalog may stay without the removed records until the next run.
The “Stop” button in the “Operations” panel takes effect at the nearest checkpoint, and a rerun is safe. More: if a run broke off or was stopped.
Schedule and turning a template off
You set the run schedule with the “Schedule setup” button in the “Related settings” block of the template form. The active switch at the top of the form only stops automatic runs; manual runs and all settings stay. Deleting a tunnel template also removes the site database credentials and filter rules — turn off or delete a template.
What a repeat transfer overwrites
The tunnel matches records by the identifiers from the site's database, so a repeat run updates cards instead of duplicating them (how Elbuz recognizes a product). It doesn't touch a card created in Elbuz by hand. A card that came through the tunnel is updated by every run like this:
| What you changed in the card | What happens after the next transfer |
|---|---|
| Name, descriptions, SEO fields | If the site sends a non-empty value, it overwrites yours. If it sends an empty one, yours stays |
| SKU, barcodes, weight, dimensions, warranty, minimum order | The same: a non-empty value from the site overwrites, an empty one doesn't |
| Price, old price, recommended price | Taken from the site without checking for an empty value |
| Active status, stock status, sort order | Always taken from the site |
| Product categories | Links are rewritten in full: the tunnel removes all of the product's categories and assigns them as on the site |
| Related products | Also rewritten to match the site |
| Attributes | With the “Attributes” checkbox, attribute values are cleared across the whole base catalog and filled in again from the site |
| Photos | Ones not there yet are added. Pictures you added in Elbuz stay |
You can lock your value with flags on the product card: “Do not update” keeps your price, stock, SKU, dimensions, active status, sort order, name, descriptions, and SEO fields; “Fixed Price” keeps the price, old price, and recommended price. Where they are: how to lock your own value.
1
Do not update2
Fixed Price- Do not update — import skips this product entirely.
- Fixed Price — import does not change the price of this product.
“Do not update” doesn't hold categories: only the main category stays yours, and the site's categories come back to the product as additional ones. The flags don't protect against attributes being cleared either. If you maintain attributes in Elbuz by hand, don't turn on the “Attributes” checkbox in the tunnel template.
Whose price stays in the card
Two processes write to the price field: the tunnel writes the site's price, and the base catalog update from price lists writes the price with your markup. Neither source has priority; whichever runs later wins.
- Run order. The tunnel schedule and the price list processing schedule decide whose value lands last.
- “Fixed Price” on the card. Stops both: neither the tunnel nor the price list update will overwrite the price, old price, and recommended price.
If you manage prices on the site, don't let the price list update touch the price of these products. You won't see an error: the cards will just keep switching between one price and the other.
Deleted a category or manufacturer — the next run brings it back
The tunnel takes categories from the site as they are. It takes manufacturers from the site's manufacturer list, and also from the product's manufacturer field and from an attribute named exactly “Производитель” (Russian for “manufacturer”). An attribute with any other name — “Manufacturer” on an English-language site or “Виробник” — isn't treated as the manufacturer. Each such record stores its source — the name of the template it came with.
The next run will recreate a deleted category or manufacturer and assign products to it as on the site. Deleting a category also removes the products for which it is the main category — what gets deleted along with a category or brand.
How to remove from the catalog what isn't on the site
The “Delete entries in the base catalog that do not exist on the site” checkbox adds a deletion step that runs first. Whatever didn't come from the site is physically deleted, with descriptions, photos, links, and related products. Log step: “Removing categories and products in the base catalog that are not in the file”. There's no Trash.
1
Delete entries missing on the site2
Check record uniqueness per import source3
Import orders starting from ID- Delete entries in the base catalog that do not exist on the site — off by default.
- Check uniqueness of records based on this import source.
- Import orders starting from ID — the field sets the first order to load.
- What gets removed: only the sets the template pulls — categories with “Categories”, products with “Products”, attribute list entries with “Attributes”.
- Without the “Check uniqueness of records based on this import source” checkbox, everything not on the site is deleted, including products from other templates.
- With it, other templates' records stay, but products created by hand, from price lists, and by the parser are deleted all the same.
- Start or end
- Action or result
- Decision: the path depends on the answer
The comparison runs against exactly what came this time. If the module returned an empty or incomplete set — a query failed, a filter rule kicked in, it ran out of time — every missing record is removed from the catalog. File templates are protected from an empty file; the tunnel isn't (a product disappeared from the source).
How to get removed records back. Fix what the site returns and run the tunnel again without the delete checkbox: the cards are recreated with the same site identifiers. Some things won't come back on their own:
- your manual edits in the cards — they're stored nowhere but the card itself;
- matching with price lists — the “found in the base catalog” mark is removed from price list rows; manual “price list row — card” pairs the tunnel restores itself by the site identifier;
- the link between order lines and the card — the name, SKU, quantity, and price stay in the document, but the link to the card isn't restored.
Turn on “Delete entries…” only after several runs have shown the expected number in the “Total items imported:” line of the log.
How to get orders from your site
Turn on the “Orders” checkbox. Each site order becomes a “Customer order” document: the number comes from your numbering sequence, the site's number goes in a separate field and is used to recognize the order later. Products become lines: name, SKU, quantity, price, and total.
The tunnel pulls orders only during a run and skips changes older than 7 days. The Elbuz API Sync module sends an order on checkout and on every status change, with no 7-day window. Keep the catalog on the tunnel, orders on the module: orders from OpenCart 3 with a ready-made module, including switching without duplicates.
Orders are pulled from OpenCart 2, OpenCart 3, Magento (1 and 2), and PrestaShop. For WooCommerce and CS-Cart, the checkbox pulls nothing: there's no error, the “Total orders imported:” line just doesn't appear in the log.
| What | How it lands |
|---|---|
| Status | By the mapping from the “Order statuses” button (payment and delivery statuses are next to it). Without a mapping — the first status in the list, “New” |
| Payment status | By the mapping from the “Payment statuses” button. OpenCart has no separate payment status, so here you enter the site's order status names: “W trakcie realizacji,Zapłacono” → “Paid” |
| Stock and reservation | Don't change: the document is created unposted until you click “Post document” |
| Buyer | A new contact in the group from the template's “Contact group” field, or “Customer” if it's empty. Not recognized — “End consumer” |
| Repeat run | OpenCart 3 sends new orders and those changed on the site in the last 7 days; already imported ones are updated: payment, delivery, status. A status set by a manager isn't overwritten — the rules are in who overwrites whom. OpenCart 2 sends all orders every time |
| Elbuz CMS store: pickup point | The branch, parcel locker, or pickup point the buyer chose comes with the order: the branch number (for Ukrposhta, its postcode) goes in the “Delivery service: branch” field. The waybill form fills in the point itself (for Ukrposhta, the branch postcode) (waybill from an order) |
| Elbuz CMS store: company NIP | If the buyer requested a Polish invoice for a company, the NIP (10 digits) goes in the new contact's “TIN” field, and the company name becomes the contact's name. Elbuz doesn't change a buyer recognized by email or phone: the NIP isn't added to their card |
| PrestaShop | Items, delivery and billing addresses, status, carrier, and currency come in; item prices and delivery include tax. A repeat run pulls new orders and those changed in the last 7 days. Cart discounts don't come as a separate line, so the document total excludes them |
| OpenCart 3 | Orders without a status (abandoned carts) aren't pulled. After each run, Elbuz sets “Import orders starting from ID” to the highest number itself; older numbers come in only if they changed on the site in the last 7 days |
If the tunnel hasn't run for a week or longer, orders changed on the site more than 7 days ago won't update anymore — change them by hand. Keep the schedule at least once a day.
1
Schedule setup2
Order statuses- Schedule setup — opens the import schedule settings.
- Order statuses — opens the order status mapping.
Scenarios
I'm moving to Elbuz and taking the whole catalog
Goal: transfer the catalog from a live site with its structure, photos, and attributes.
What to turn on: in the “Select data to import from the site” block, keep “Categories”, “Products”, and “Manufacturers” and add “Attributes” and “Photo”. Don't check “Delete entries in the base catalog that do not exist on the site”. Run it with “Get product catalog”.
What you get: cards appear in the base catalog with the site's identifiers, and the next run updates them instead of duplicating. Nothing is deleted from the catalog; orders don't come over — they have their own checkbox.
The site stays the main source, Elbuz regularly picks up changes
Goal: prices and stock are managed on the site, and the Elbuz catalog should follow them.
What to turn on: a run schedule. On cards whose price you set in Elbuz yourself — “Fixed Price”; on cards that shouldn't change from the site — “Do not update”.
What you get: each run rewrites prices, active status, stock, and sort order to match the site; cards with flags keep their own values. The tunnel doesn't update products created by hand. If the price list update also writes the price, the value from whichever runs later stays — whose price stays.
Orders from an OpenCart 3 site must reach Elbuz
Goal: see site orders as documents in Elbuz without re-entering them by hand. If you need orders right away rather than with the next run — the ready-made OpenCart 3 module; below is how to do it with the tunnel.
What to turn on: the “Orders” checkbox; in “Order statuses” and “Payment statuses” — in each row, the site's status names, comma-separated, as in the OpenCart admin (for example, “W trakcie realizacji,Zapłacono” → “Paid”); after saving, reopen the window and check the value stayed. In “Additional” — “Contact group” and, if old history isn't needed, “Import orders starting from ID”.
What you get: new orders become unposted “Customer order” documents, buyers become contacts of the chosen group. Orders with an up to the one specified, and orders without a status, aren't pulled unless changed in the last 7 days. A site payment reaches an imported order with the next run. Stock and reservation change only after posting.
The Elbuz catalog must match the site exactly
Goal: a product removed from the site should disappear from the base catalog too.
What to turn on: “Delete entries in the base catalog that do not exist on the site”; if the catalog has products from other templates — also “Check uniqueness of records based on this import source”.
What you get: the first step of the run removes categories, products, and attributes the site didn't return. Products from other templates stay, but those created by hand, from price lists, and by the parser don't. Turn it on after several runs with the expected product count in the log — mirror mode.
What to do when the tunnel doesn't pull data
| What you see | Why | What to do |
|---|---|---|
| “E-Trade Tunnel module link not specified” (or “Login to access the E-Trade Tunnel module was not specified”, “The password to access the E-Trade Tunnel module was not specified”) | The fields of the “Tunnel connection setup” card are empty. This happens if the module on this site was already set up before: “Connect” then doesn't write a new password | Fill them in by hand: “Link to the module” — https://your-site/etrade_http_tunnel2/etrade_http_tunnel.php, “Username” — admin, password — the $new_password line in the module's etrade_http_tunnel_login.php file. Click “Check connection” |
| A red line with the site address and “Import stopped!” | The site didn't accept the connection or the module returned an error; the catalog is unchanged | Check that the module opens at the address above and run it again (transfer break-off) |
| The run finished, but there's no line with the count for one of the sets | The module didn't finish the set within 55 minutes, so it didn't arrive | Don't turn on mirror mode until the set arrives in full (wait limits) |
| The “Orders” checkbox is on, but there are no orders | Orders are pulled only from OpenCart 2, OpenCart 3, Magento, and PrestaShop; in OpenCart 3, also only with a status and newer than “Import orders starting from ID” | Check the CMS and the ID field in the “Additional” section (orders from your site) |
| The order is paid on the site, but its payment status in Elbuz hasn't changed | The site's status name is missing from “Payment statuses” or is written differently than in the OpenCart admin | Add the site's order status name to “Payment statuses” and wait for the next run |
FAQ
Why put a module on the site instead of connecting to the database directly?
Hosting providers almost always block direct outside access to the database. The module runs on the site itself, accepts requests from Elbuz with a separate login and password, and then accesses the database locally.
My CMS isn't on the list — what do I do?
If your store runs on MySQL, choose “MySQL (SQL custom query)” and get the data with your own query — SQL queries in the tunnel. Without database access, the tunnel won't work: see universal import.
Does the tunnel download photos to the Elbuz server?
No, it takes only the image address; the file stays on your hosting. Downloading is turned on by the “Cloud photo storage” service.
Will a repeat run duplicate products?
No. Items are matched by the site's identifiers, so a repeat run updates existing cards — and overwrites them with the site's data. What exactly: see the section on repeat transfers.
Mirror mode removed products I need — how do I get them back?
There's no Trash. Fix what the site returns and run the tunnel again without the delete checkbox — the cards are recreated. Manual edits in them won't come back (mirror mode).
Will orders that came from the site reduce stock?
No. The “Customer order” document is created unposted, and Elbuz counts stock and reservations only from posted documents.
Can I use the Epicentr import to bring products into the catalog?
No. The tunnel doesn't work with marketplaces, and the “Epicentr” template brings only orders. The catalog goes the other way, as an XML feed: importing orders from Epicentr and exporting the catalog to Epicentr.
An order's status changed on the site — will it update in Elbuz?
Yes, for OpenCart 3: the next run pulls orders changed on the site in the last 7 days and updates payment, delivery, and status. A status set by a manager isn't overwritten (rules).
Where it is and who has access
- Menu
- Directories → Operations → Data import
- Template
- create a template of the “Elbuz Tunnel” type
- Access right
- the “Import” window in “Group permissions”
- Have ready
- access to your site's hosting () to upload the module
Related topics
- If you need to send the catalog from Elbuz to your site — export via Elbuz Tunnel.
- If your CMS isn't on the list but the database is MySQL — SQL queries in the tunnel.
- If your site is on OpenCart 3 and orders should arrive right away — a ready-made module for orders.
- If the catalog comes as a file rather than from the site's database — importing ready-made formats.
- If you imported the wrong thing and need to find the extras — imported the wrong thing.
