Elbuz puts the finished file at a permanent link you give the marketplace once, and can also send it to FTP or by email. The old file is replaced only once the new one is saved.
When you need this:
- The marketplace fetches the feed itself — the “File” column link never changes.
- A customer needs the file on their server — it goes to FTP or SFTP.
- FTP rejects the file — the server code in the log names the cause.
- A wholesale customer wants the price list by email — attached via the newsletter template.
Where to start: “File” column in the template list → “Copy link”.
What file delivery can do
- Permanent link — the address you give the marketplace; every run puts a new file there.
- FTP and email — delivering the file to a server or as an email attachment.
- File name and FTP codes — why the file didn't reach the server.
- File replacement — what the link serves during a run and after a failure.
- Fixing a mistake — how to replace a wrong file the marketplace has already fetched.
Where the file goes
The finished file is first written to your account's folder and then delivered wherever you configured.
- Link. The address of the finished file is shown in the “File” column of the list, next to the “Copy link” button (clicking it shows the “Link copied” toast). This is the address you give the marketplace.
- FTP. Works if the server address and user name are filled in under “FTP Setup”. The same form has the port, password, the “SFTP (SSH File Transfer Protocol)” switch, “Destination path”, “Number of threads” and the “Check Connection” button. Click it before the first run: you get either “Connected successfully!” or “Error: ‹server response›”. If the server, port, user and password aren't all filled in, the button answers “Fill in the required fields!”.
- Email. An email attachment works only in the “Price list (XLSX, CSV)” type and only when “Newsletter template” is filled in. The attachment can be zipped.
- Direct connection. Types in the group have no file at all — the data goes to the marketplace's service as requests.
The file name is set in the template card and supports three macros: {DATE} — today's date, {DATETIME} — date and time, {TIME} — time. Use them when the marketplace or customer wants a separate file for each day. A slash in the name is replaced with a dot, and the .php extension and its variants are forced to .xml.
After a run, the system records the file size and the time spent — both numbers appear in the list and in the summary dialog next time. A file smaller than 4 KB counts as 4 KB: on disk it takes up a block anyway.
File name and FTP: where export errors come from
On FTP the file gets the same name as at the link and goes to the folder from the “Destination path” field. When an FTP export fails, check the “File name” field in the template card and the FTP settings against this list:
- Latin letters, no spaces. The system inserts the file name into the FTP address as is, without encoding it. Use Latin letters, digits, dots, hyphens and underscores:
feed_rozetka.xml, not “прайс розетка.xml” (Cyrillic with a space). - An empty name isn't an error. The default name of the export type is used, for example
export_elbuz.xmlfor . - You can't set a subfolder in the name. A slash becomes a dot; the folder goes only in “Destination path”, and it starts with a slash:
/public_html/feeds. - A file with that name already exists — it's overwritten, no versions are kept. Need a separate file per day — add
{DATE}to the name.
When the file didn't reach FTP, the run log keeps the server response code — it usually shows the cause right away, no guessing:
| Code | What it means | Where to look |
|---|---|---|
| 226 | transfer completed successfully | all good, the file is on the server |
| 530 | the server refused login: wrong user name or password | the credentials in “FTP Setup”; on some hosts the user name includes the domain |
| 550 | no access to the folder, or it doesn't exist | the “Destination path” field: the folder needs write permission; for FTP the system tries to create missing folders itself, for SFTP the folder must exist |
| 552 | disk quota exceeded | space on your hosting |
| 425, 426 | the data channel didn't open or broke off | most often passive mode and a firewall on the server side |
The system waits 10 seconds to connect to the FTP server and up to 120 seconds to transfer the file. A server that doesn't respond in time gives an “Error:” line with the cause in the log.
The first digit of a code tells you the main thing: 2 — success, 4 — temporary failure (worth retrying), 5 — a refusal that won't go away by itself.
The result appears in the run log as “Files exported via FTP: N of M”; if the FTP transfer failed, it's followed by “Error: ‹code› ‹text›” — read the code using the table above.
For SFTP, a failed login writes “SFTP server login failed!” with the server's reason; if the login succeeded but the file wasn't saved, the “Files exported via FTP” line won't appear in the log at all.
What the link serves while a new file is being built
A file export does one thing: it builds a product file from the template and puts it at the permanent link, where the marketplace fetches it.
The system sends the marketplace no separate commands — neither “delete the product” nor “take it off sale”. All it learns from us is in the latest file at the link. Which products get in — the template's selection conditions.
When the link points to the new file
The new file is built separately, in the system's working folder, in parts (500 products at a time in XML templates). Meanwhile the link serves the previous file. The finished file is written to storage, and only after a successful write does the link point to it.
If the write fails, the log says “The file was not uploaded to cloud storage. The previous file and its link are left unchanged”, the export ends with “Data export NOT completed: the file was not generated”, and the template's “File Link (#1)” and “Export date” stay as before.
- The “Stop” button stops the export after the current product. The incomplete file stays in the working folder; the link keeps the previous one.
- If a template condition has an error, the file isn't published and the link keeps the previous one. If the selection is empty, the file isn't published in XML feeds (YML, Google feed) or “Price list (XLSX, CSV)”, except in the “Export category rows with products below + grouping” mode. prom.ua XLS templates and “1C (CommerceML2)” publish an empty file, and it replaces the previous one.
- If the template's file name contains
{DATE},{DATETIME}or{TIME}, the name — and the link — changes with every run. A marketplace that fetches from a single address needs a name without them. - In the cloud version,
?uuid=with a new number is appended to the link after each export. The file stays at the same address; the number only bypasses browser caching.
What happens to a product that dropped out of the file
On our side — nothing, except that it's not in the new file. The product stays in the catalog unchanged. What the marketplace does with an item missing from the file (hides it, takes it off sale, deletes it or keeps it) is up to the marketplace; the system can't affect it. Check your marketplace's rules.
- For the marketplace to see the product as unavailable, it must stay in the file: pass the selection conditions, with its stock status mapped to “Out of stock” in the template's availability settings (the quantity such a product gets is set there too).
- If you make the product inactive and the template has a “product is active” condition, it isn't marked “Out of stock” — it drops out of the file entirely.
- A product that comes back (enabled again or passing the conditions again) appears in the file on the next export.
How to tell from the log that the file is built
Follow the export in the Operations center. The file is built and at the link if the log has a “Download file” line with the file name and ends with “Data export completed”. If the file wasn't generated or storage rejected it, the last line is “Data export NOT completed: the file was not generated”.
After a successful run, the template list updates “Export date” and “File Link (#1)”. If the file wasn't generated, “Export date” stays old; only “Time spent” changes. Each log line is explained in the table below.
How to fix a wrong export
There's no “restore previous file” button: the new file replaces the previous one, and the system keeps no copies. The only remedy for a wrong file is to fix the cause and export again. The new file replaces the wrong one at the same link.
- If the wrong products got into the file, or fewer than needed, fix the template's selection conditions, the “Export to file (to website)” flags on products and categories, and the store or warehouse choice. Before running again, check the numbers in the “What will be exported” window.
- If the products in the file are right but their data (prices, availability, descriptions) is wrong, fix the data in the catalog and run the export again.
- If the template uses the “Only export new data” checkbox, the products from the wrong file are already flagged “Exported” and won't go out again on their own. Change them in the catalog or clear their “Exported” flag, otherwise the fix won't reach the file.
- What the marketplace managed to do with the wrong file before fetching the fixed one depends on the marketplace: the system doesn't control when it rereads the file or how it processes changes.
To keep a mistake out of the file next time, switch the export stop rules to “Stop the export” mode. If the template filter can't be counted, the log says “Preflight summary skipped…”, and stop rules don't fire in that run.
Scenarios
The marketplace fetches the feed from a link
What to set up: in the “File” column of the template list, click “Copy link” and paste the address into the marketplace account. Leave the file name in the template card without {DATE}, {DATETIME} and {TIME}.
What you get: each run puts a new file at the same link, and the marketplace fetches it on its own schedule. What won't happen: until the new file is written to storage, the link serves the previous one.
A customer wants a separate file for each day on their FTP
What to set up: under “FTP Setup”, fill in the server, user, password and “Destination path”, then click “Check Connection”. Add {DATE} to the file name.
What you get: a new file with the date in its name appears on the server every day, and the earlier ones stay. What won't happen: the link in the “File” column also changes with every run — such a name won't work for a marketplace that fetches the file from a single address.
A price list for a wholesale customer by email
What to set up: a “Price list (XLSX, CSV)” template with the “Newsletter template” field filled in; if needed, turn on zipping the attachment.
What you get: after each run, the file goes out as an email attachment. What won't happen: other template types have no email attachment.
What the log says when the file didn't arrive
| What you see | Why | What to do |
|---|---|---|
| “Files exported via FTP: 0 of 1 Error: …” in the run log | The server didn't accept the file: credentials, path, write permission, or a file name with spaces or Cyrillic | “Check Connection” in “FTP Setup”, a path starting with a slash, a file name in Latin letters (file name and FTP) |
| “Export products 500 of …” | The file is being built: the first number is how many products are already written, the second is how many were selected in total. In XML templates the line appears every 500 products and once more at the end | Nothing, wait for it to finish |
| “Uploading file to cloud storage” | The file is fully built, and the system is replacing the previous one at the link with it | Nothing, wait for the “Download file” line |
| “The file was not uploaded to cloud storage. The previous file and its link are left unchanged” | The file was built, but storage didn't accept it. The export isn't completed; the link keeps the previous file | Run the export again |
| “Data export NOT completed: the file was not generated” | The selection returned no products, a template condition contains an error, storage didn't accept the file, or the export was stopped. The link keeps the previous file | Check the pre-flight summary numbers and the selection conditions. A stop rule or schedule conflict in the log — run troubleshooting |
FAQ
The FTP export fails — could the file name be the problem?
Yes. The system puts the file name into the FTP address without , so suspect spaces and Cyrillic first: rename it in Latin letters, like feed.xml. The code in “Files exported via FTP: … Error:” names the cause: 530 — login or password, 550 — folder or write permission.
Are old versions of the file kept?
No. Each run replaces the previous file; there are no “as it was last week” versions. If you need an archive, export to FTP with {DATE} in the file name.
Why is the “File” column empty for some templates?
Elbuz Tunnel templates and direct API connections have no file at all: the tunnel writes data straight into the site database, and the API sends requests to the marketplace's service.
Can I email the file from any template?
No. An email attachment exists only in the “Price list (XLSX, CSV)” type and only with “Newsletter template” filled in.
Why does a small file show 4 KB in the list?
A file smaller than 4 KB counts as 4 KB: on disk it takes up a block anyway.
Where to find it and who has access
- Menu
- Directories → Operations → Data export → “File” column
- Other entry points
- template card, “Related settings” section → “FTP Setup”
- Access right
- the “Export Template Setup” window
- Prepare
- for FTP — the server address, user name, password and a folder with write permission
Related topics
- For the big picture of exports — How to set up product export.
- To read the whole run log — How to run an export and read the log.
- If the file came out empty — Why the file is empty when you have products.
- If the customer price list is made of columns — Customer price list in XLSX and CSV.
- If you plan to sell on marketplaces — what it gives your store.
