↑↓ selectEnter openEsc close

    1. Elbuz

    How to send a price list to customers: link, FTP, and scheduled email

    11 min readUpdated

    Elbuz rebuilds your price list for customers and dealers on a schedule and delivers it: by permanent link, to the customer's FTP, or emailed to the whole mailing list. No manual forwarding.

    When you need this:

    • A customer complains about old prices — the schedule rebuilds the file from current prices.
    • Buyers download it themselves — the permanent link serves the latest run.
    • Wholesalers need the price list every morning — each run emails it to the whole mailing list.
    • A customer got a wrong file — a new run puts the fixed file at the same link.

    Where to start: template card → “Settings” tab → “Schedule”.

    What price list delivery can do

    • Schedule — the file is rebuilt without you, with current prices and stock.
    • Permanent link — the customer downloads the file; you share the address once.
    • FTP — after each run, the file lands on the customer's server.
    • Email — an attachment to all recipients; only price lists have this.
    • Empty file protection — if the file isn't built, the link keeps the previous one and no emails go out.

    How to update the file on a schedule

    The app doesn't recalculate the price list on its own: the file is rebuilt only during a run. Until then, the link, the server, and the email carry what was built last time.

    To keep the file updating without you, turn on automatic runs: the “Schedule” button in the “Related settings” section on the “Settings” tab. The schedule frequency is exactly how often the customer sees new prices: with a daily schedule, the file shows yesterday's prices during the day.

    Related settings card in the template Settings tab with the FTP Setup, Schedule and Description generator buttons
    1Schedule button
    2FTP Setup button
    1. Schedule — opens the export schedule settings.
    2. FTP Setup — opens the FTP upload settings.

    Without a schedule, the file updates only when someone opens the list and clicks the button. That's where complaints like “your prices are from last week” come from: someone built the file once, gave the customer the address, and considered the job done, while the file behind it stayed as of the first run.

    How the schedule works for all templates: Running manually and on a schedule.

    The file name is set in the template card and supports three macros: {DATE} — date, {DATETIME} — date and time, {TIME} — time. A slash in the name is replaced with a dot.

    {DATE} gives the date as day.month.year: August 18, 2026 becomes 18.08.2026. The format is the same in all export types — price list, , and 1C.

    The “Archive to ZIP” checkbox packs the finished file and appends .zip to its name.

    How the file gets to the customer

    Link to the finished file

    The main way: the finished file's address appears in the “File” column of the template list, with a copy button next to it. This is the usual way to share the file: the link is permanent, and its content updates with each run.

    The address in the “File” column changes slightly after each run — a new service parameter is appended. But the address you already gave the customer keeps working: in storage it's the same file as long as its name doesn't change.

    Export templates grid with the State column and the File column showing the link and copy button
    1State pill
    2File link with copy button
    1. State — a pill showing whether the template is active or disabled.
    2. File — the link to the exported file with a button to copy it.

    Don't put {DATE} in the file name if you share the file by link. After each upload, everything but the new file is deleted from the template's cloud folder, and tomorrow's file gets a new name — so the address the customer already has stops opening. A date in the name only suits FTP, where files pile up.

    FTP

    Works if the server address and user name are filled in under “FTP Setup” (a button in the “Related settings” section).

    Email

    Emailing the price list as an attachment is something no other export type offers. It's turned on with one field: in the “Email newsletter” section, use the pencil button to pick a “Newsletter template” — one that already has a recipient list. Without this field, email doesn't work at all.

    Email newsletter card and Related settings card in the template Settings tab
    1Newsletter template field
    2Archive attachments to ZIP checkbox
    3FTP Setup button
    1. Newsletter template — read-only field; the button under it opens template selection.
    2. Archive attachments to ZIP — packs the attached file into an archive.
    3. FTP Setup — opens the FTP upload settings.

    What to know in advance:

    • the file is sent again on every run. Before sending, the app resets the “email sent” mark for the recipients and restarts the mailing. So a template with a daily schedule means a daily email to the customer;
    • in one run, all recipients on the mailing list get the email;
    • the attachment is packed into ZIP — the “Archive attachments to ZIP” checkbox next to it controls this, and it's on by default;
    • the run log shows a separate “Sending emails” line;
    • recipients who unsubscribed from the mailing or are in the trash don't get the email;
    • emails go out within the run, one at a time. The app waits 5 seconds before the first one, and after each email a random pause of 5 to 30 seconds; these limits are set in the email template with the “Pause from, seconds” and “Pause to, seconds” fields. The run ends only after the last email.

    What happens during a run

    Run order

    A live run — by button, on schedule, or as part of the all-templates run — goes through these steps:

    1. The app checks the template's stop rules. If a rule fires in “Stop the export” mode, the run ends here: the file isn't built, the link keeps the previous one, and no emails go out.
    2. The new file is built in the app's working folder. In the cloud version, the link doesn't see this file yet — it still serves the previous one. Without the cloud, the link points straight to the file in the working folder, so a file with the same name replaces the previous one while it's still being built. Every thousand rows, the log writes “Rows exported 1000 of ‹total›”, and when the file is built, the same line with the final count.
    3. If FTP is set up, the file is uploaded to FTP.
    4. In the cloud version, the log writes “Uploading file to cloud storage”. The app puts the new file into the template folder, writes its address into the “File” column, and only then deletes the other files from the folder. If the file didn't reach storage, the log shows in red “The file was not uploaded to cloud storage. The previous file and its link are left unchanged”, the run ends here, and no emails go out.
    5. If a “Newsletter template” is selected, the file is emailed (the “Sending emails” line).
    6. In the cloud version, the working copy of the file is deleted. Without the cloud, the link points to this very file in the working folder, so it stays. The log shows a “Download file ‹file name›” link.

    If a formula in a column broke the query (“Error getting products!”) or the conditions let no product through, the run breaks off at step two: the link keeps the previous file, nothing goes to FTP or email, and the final log line is “Data export NOT completed: the file was not generated”.

    In the all-templates run, this line isn't written to the log — it appears as the result in the template's operation card.

    The “Run stopped”, “File built? No”, and ““Stop” clicked? Yes” branches leave the previous file at the link. Everything below “Stop” clicked? No” changes what the customer sees
    YesNoNoYesYesNoYesNoYesNoRun: by button, on schedule,or in the all-templates runDid a stop rule firein “Stop the export” mode?Run stopped.The link keeps the previous file, noemails go outThe file is built in the working folderFile built?Formula error or no products(table mode).Log: “Data export NOT completed:the file was not generated”.The link keeps the previous file, noFTP or email“Stop” clicked?Log: “Export stopped by the user!”.The link keeps the previous file, noFTP or email.The built file stays in the workingfolder“FTP Setup” filled in?The file is uploaded to FTPThe new file goes to the link,other files in the template's cloudfolder are deleted“Newsletter template” selected?Emails with the file —to all recipients on the mailing listIn the cloud version, the workingcopy is deleted.The log shows “Download file‹name›”
    • Action or result
    • Decision: the path depends on the answer

    An empty filtered set stops the run only in regular table mode. If the conditions let no product through, the file isn't built: the link keeps the previous one, no mailing goes out, and the log ends with “Data export NOT completed: the file was not generated”.

    In category tree mode, there's no such check: an empty filtered set produces a file with no products, which replaces the previous one at the link and goes out by email. There, only the “nothing to export” stop rule in “Stop the export” mode (the “Export stop rules” window) keeps such a file from going out.

    What happens to an item that is no longer in the price list

    The file is built from scratch every time, from what's in the database at the moment of the run. The app doesn't compare it with the previous file and doesn't mark anything as “discontinued”: an item that's gone is simply missing from the new file.

    • If a product no longer passes the template's filters, its row disappears from the next file.
    • When a supplier price list is imported, the app deletes all previous rows of that price list and writes new ones. An item the supplier no longer sends disappears from the price list rows, and with it — its row in the consolidated price list, its price in that supplier's column, and its row in “Export only products from price lists” mode.
    • The catalog product itself stays in the file if it passes the filters, but its cells from the price list will be empty. The exception is when a condition is set on the “Products from price lists” tab: a product with no price list rows left that match the condition drops out of the file entirely.
    • Rows from a disabled price list source don't go into the file: the query takes only active sources. This doesn't apply in “Export only products from price lists” mode or with the “Export from price lists only the products whose price was used for the base catalog product” checkbox: there, the source state isn't checked.
    • A customer who already downloaded the previous file keeps it. They learn the item is gone only from the new file — when they download it via the link or receive it by email.

    How to fix a wrong file the customer already has

    There's no “restore previous file” button. After an upload, everything except the new file is deleted from the template's cloud folder, so no previous version is kept anywhere. The only fix: correct the cause and run again.

    • First check the result with the “Check” button in the card header: it writes a separate file and doesn't send it anywhere — not to the link, FTP, or email.
    • A new run puts the corrected file at the same link if the file name has no {DATE}, {DATETIME}, or {TIME}. A customer who downloads the price list themselves gets the corrected file the next time they download it.
    • If a “Newsletter template” is selected, a new run emails all recipients again: before sending, the app resets the “email sent” mark for everyone. The app can't recall an email already sent, so customers will have two emails — the wrong one and the corrected one.

    A run breaking off and the “Stop” button

    • If the run broke off while the file was being built (before the final “Rows exported … of …” line), the unfinished file stays in the working folder. The link serves the previous file; nothing went to FTP or email.
    • If it broke off during the mailing, some recipients already got the email and some didn't.
    • A restart builds the file from scratch and emails it to all recipients again, so those who got the email in the broken-off run get it a second time.
    • The “Stop” button keeps the file from being published. The file is still built to the end, but then the log shows “Export stopped by the user!” and the run stops there: the file doesn't go to FTP, the link, or email. The built file stays in the working folder, and in the cloud version the link keeps the previous one. In the all-templates run, “Stop” only prevents the next template from starting.

    A disabled template and limits

    The schedule and the all-templates run silently skip a disabled template, but a manual run doesn't. The file at the link stays as last built and stops updating; once the template is enabled, it updates on the next run. The app doesn't limit the number of rows, except in the demo version. More: Running manually and on a schedule.

    Scenarios

    The customer downloads the price list via a link and must see fresh prices

    • What to set up: the format in the “Select Format” section; a “File name” without {DATE}, {DATETIME}, or {TIME}; a schedule via the “Schedule” button in the “Related settings” section.
    • What you get: on each scheduled run, the new file lands in the template's cloud folder under the same name, and the other files in the folder are deleted. The address the customer already has opens the file from the latest run.
    • What won't happen: the app doesn't notify the customer that the file was updated and doesn't keep the previous version. If a stop rule halted the run or the file wasn't built, the link keeps the previous file.

    Email the price list to wholesale buyers on a schedule

    • What to set up: in the “Email newsletter” section, use the pencil button to pick a “Newsletter template” with a recipient list; a schedule via the “Schedule” button.
    • What you get: on each run, after the file is uploaded, the app resets the “email sent” mark for the recipients and emails the file as an attachment to everyone on the mailing list. With the “Archive attachments to ZIP” checkbox, the attachment is packed into ZIP; if “Archive to ZIP” is on, the email carries the already packed file.
    • What won't happen: a run halted by a stop rule or one where the file wasn't built sends no emails. The app doesn't recall a sent email.

    Keep dated price lists on the customer's server

    • What to set up: set the server address and user name with the “FTP Setup” button; add a date macro to “File name”, for example price_{DATE}.xlsx.
    • What you get: each run uploads a file with the date in its name to FTP — price_18.08.2026.xlsx. The app doesn't delete old files on FTP, so they pile up there. Two runs on the same day give the same name; to keep names unique, use {DATETIME}.
    • What won't happen: the link from the “File” column won't work for the customer in this setup — after each upload, everything except the new file is deleted from the template's cloud folder, and yesterday's address stops opening. If the server address or user name isn't filled in, the file doesn't go to FTP, and the log has no separate line about it.

    What to do when the file doesn't arrive or is outdated

    Common problems
    What you seeWhyWhat to do
    The customer says the file has last week's prices The file is built only by a run, and the template has no schedule — the link serves what was last built by hand Turn on automatic runs with the “Schedule” button in the “Related settings” section (about the schedule)
    The link you gave the customer stopped opening The file name contains {DATE} or {DATETIME}: the template folder is cleared on every upload, and the new file got a new name Remove the date macro from the file name and give the customer the new address (about the link)

    FAQ

    Can I recall an email with a wrong price list?

    No. Fix the cause and run again: customers will get a second email with the corrected file (a wrong file has already reached the customer).

    In what format does the {DATE} macro put the date into the file name?

    Day.month.year: August 18, 2026 becomes 18.08.2026, as in all export types. For a file shared by link, it's better to remove the date from the name (why).

    How many times will the customer get the email with a daily schedule?

    Every day: before each sending, the app resets the “email sent” mark, and the file goes to all recipients on the mailing list on every run.

    Will the app keep yesterday's version of the price list?

    No. After an upload, everything except the new file is deleted from the template's cloud folder. If you need an archive, add {DATE} to the name and deliver the file via FTP, where files pile up.

    Why did the customer get the price list twice?

    The run broke off during the mailing, or you ran it again: a new run emails the file to all recipients again (about a run breaking off).

    Where it is and who has access

    Menu
    Directories → Operations → Data export → pencil in the template row → “Settings”
    File link
    the “File” column of the template list
    Access right
    the “Data export” window
    Prepare
    for email — a newsletter template with a recipient list

    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