↑↓ selectEnter openEsc close

    1. Elbuz

    How to check an export before it runs and avoid sending a broken file

    5 min readUpdated

    Before every run, Elbuz counts the products going into the file and how many are in stock, compares this with the previous run and blocks an obviously broken catalog, leaving the old file on the marketplace.

    When you need this:

    • First run of a new channel — “What will be exported” lists products lacking a price, photo or barcode.
    • Stock vanished overnight — a stop rule in “Stop the export” mode blocks the run.
    • A channel quietly emptied — the “nothing to export” rule warns you.
    • Finding products without photos — a summary chip opens them in the catalog.

    Where to start: template list → “Export” in a template row.

    What the pre-run check does

    • Summary — how many products go into the file, the stock breakdown and the change since the previous run.
    • Card quality — “No price”, “No photo”, “No barcode” chips that open the products in the catalog.
    • Opening the catalog and “all templates” — summary products in the catalog grid, turning the dialog off, bulk runs.
    • Stop rules — three thresholds in “Warn” or “Stop the export” mode, including for scheduled night runs.

    Pre-flight summary: what will be exported

    When you start an export from the template list, the run doesn't begin right away: first the “What will be exported” dialog opens — a based on this template's conditions.

    At the top is one large number with the caption “products will be exported” and the change since the previous run next to it. Below it is a stock bar with three buttons: “In stock”, “Out of stock”, “Pre-order” — also with the change.

    The summary counts products by the export flag, the “Additional filter” conditions, the selected categories and the template's store — together with the “In stock at this store only” checkbox. In an XML feed with the “Options” checkbox cleared, it doesn't count option products either.

    It doesn't see the template's other restrictions: description language, warehouse, the “Only export new data” checkbox or the demo limit. So the dialog's number is a ceiling, not a fact: the file may contain fewer products. The actual count appears in the run log.

    The “What will be exported” dialog for the Google Merchant template
    1Products that will be exported
    2Stock composition legend
    3Selection rules
    4Configure thresholds
    1. The large number shows how many products will go into the export, next to the change versus the previous run.
    2. The legend splits the total into in stock, out of stock and pre-order.
    3. The selection rules section lists the conditions that pick the products.
    4. The footer link opens the export stop-rule thresholds.

    The “Card quality” section shows what marketplaces reject products for: the “No price”, “No photo”, “No attributes” and “No description” chips. The “No barcode” chip appears only where a barcode is required: in the Google feed, prom.ua and the Rozetka, Epicentr, Ceneo and Allegro feeds. The “Option products” chip appears when the selection contains such products.

    The Card quality section of the summary dialog with problem chips and their counts
    1No price chip with count
    2No photo chip with count
    1. The No price chip shows how many exported cards have no price.
    2. The No photo chip shows how many exported cards have no photo.

    The “Selection rules” section restates the template filter in plain words and adds the line “Category filter: ‹N› selected”. A month after setup, this is the only way to recall what exactly you configured. A long list collapses behind the “Show all rules” button.

    At the bottom is the “Previous exports” fold with a table of up to ten recent runs and a stock chart. It shows whether this is a one-off glitch or stock has been shrinking for days. The footer shows the previous run's date, file size and duration, with the “Configure thresholds” link on the right.

    How to open products from the summary in the catalog

    Every stock button and every quality chip is clickable — it opens the catalog narrowed down to those products. Elbuz adds a temporary “Export: ‹template name›” chip to the catalog filter bar; its tooltip says what is taken into account: “the template filter and the exported categories”.

    • The chip ignores the template's store: if the template has a store selected, the catalog shows a wider list than the summary number.
    • There is one chip for all templates, and it is overwritten every time you open the dialog.
    • If the template filter has conditions on product attributes, the chip isn't created at all — the catalog then shows a wider list.

    You can turn the dialog off for the whole account with the “Show the summary before starting an export” switch in the “Export stop rules” window. It is shared by all account users and turns off only the confirmation window: the summary and stop rules keep working, and the result goes to the operation log. The dialog is on by default.

    The summary isn't always calculated. If the template filter uses fields that the fast count doesn't have, the dialog says: “Preflight summary skipped: the template filter uses fields unavailable for a fast count.” — and offers “Export” or “Cancel”.

    The same window appears if the summary query itself fails. The export itself handles such a filter fine: it joins more tables than the fast count does.

    The “Export all templates” item has its own dialog: instead of a recount, it lists the active templates with the numbers from their last runs. Its explanation says: “All active templates will be exported. The numbers below come from the last run of each template — you can see which one went out empty or lost its stock.”

    Stop rules: when Elbuz stops an export

    Before every run, Elbuz compares the new numbers with the previous successful run of the same template. If the difference exceeds a threshold, it warns you in the log and in the run window, and in “Stop the export” mode it won't export the data at all. Thresholds also work for scheduled runs — where they matter most, since nobody watches the numbers at night.

    There are three rules, and by default all three are on in “Warn” mode:

    RuleThresholdWhat it means
    “in-stock count collapsed versus the previous run”30By how many percent the in-stock count may drop versus the previous run before it counts as a failure
    “product count collapsed versus the previous run”50By how many percent the total number of exported products may shrink
    “nothing to export, products”1Minimum number of products in the export. Fewer means the template filter or the catalog is broken
    The Export stop rules window with thresholds and modes
    1In-stock collapse rule, threshold 30
    2Mode column set to Warn
    3Save for all templates
    4Show the summary before starting an export
    1. The first rule triggers when the in-stock count drops by more than 30% against the previous run.
    2. The Mode column holds Off, Warn or Stop the export for each rule; all three are set to Warn.
    3. Save for all templates overwrites the thresholds of every template.
    4. This switch turns the summary before an export on or off for the whole account.

    There are also three modes: “Off”, “Warn” (the run continues and a warning appears in the log) and “Stop the export” (the run doesn't start and the old file stays in place). The window opens from the list menu with the “Export stop rules” item.

    There are two save buttons. “Save for this template” sets per-template thresholds and appears when you open the window with a row selected. “Save for all templates” makes the thresholds common — and resets per-template settings, which Elbuz asks you to confirm separately: “The thresholds will become common for all export templates. Per-template settings will be reset. Continue?”

    The first two rules compare with the previous run, so on a template's first run there is nothing to compare with and they stay silent. The dialog says so: “This template has never been exported — nothing to compare with.” That's why you check the first file of a new channel yourself instead of relying on automation.

    Stop rules use the same numbers as the summary, so they have the same limits. The “nothing to export” rule will notice an empty file caused by the selected store, but not one caused by the warehouse or the “only new data” checkbox: those products stay in its count. Only the run log catches such cases.

    A stopped run isn't saved as the baseline — otherwise the broken numbers would become the norm for the next comparison. Likewise, a run that ended with the line “Data export NOT completed: the file was not generated” doesn't become the baseline: only a successful run does.

    Scenarios

    The first file for a new marketplace

    What to set up: start the template with the button in the list row, not from the card, and review the “Card quality” section. Clicking the “No price” or “No barcode” chip opens those products in the catalog.

    The result: you see the products the marketplace will reject before anything is sent, and you can complete them in the catalog. What won't happen: the summary doesn't exclude such products — if you start the run, they go into the file. Stop rules are silent on the first run, so check the first file yourself.

    A night update that survives an in-stock drop

    What to set up: use the “State” badge to make the template “Active”, and set a schedule with the “Schedule” button. In the “Export stop rules” window, set “Stop the export” mode for the “in-stock count collapsed versus the previous run” rule and click “Save for this template”.

    The result: if the in-stock count drops by more than the threshold (30% by default) versus the previous run, the run doesn't start, the previous file stays at the link, and the log says “Export stopped by a stop rule: ‹rule›”.

    What won't happen: on a template's first run there is nothing to compare with, so the rule is silent. If another scheduled export is running at the same time, the task is canceled with a line about a data processing conflict. This rule won't notice an empty file caused by the selected warehouse or “Only export new data”.

    One template needs different thresholds from the rest

    What to set up: select the template row, open “Export stop rules”, change the threshold and click “Save for this template”.

    The result: the per-template thresholds apply only to this template; the other templates use the common ones. What won't happen: per-template thresholds don't survive the “Save for all templates” button — it resets them after asking for confirmation.

    What to do when the summary or a stop rule shows a problem

    What you seeWhyWhat to do
    “Export stopped by a stop rule: ‹rule›. Check stock statuses in the base catalog.” A rule in “Stop the export” mode was triggered; the old file stayed in place Check the catalog. If the numbers are correct, temporarily change the threshold in the “Export stop rules” window (about stop rules)
    “Warning, the data looks suspicious: ‹rule›. Check stock statuses in the base catalog.” The same rule, but in “Warn” mode — the run continued Check the catalog before the marketplace picks up the file: it has already been generated (about stop rules)
    “Preflight summary skipped: the template filter uses fields unavailable for a fast count.” The template filter uses fields the fast count doesn't have, or the summary query itself failed Nothing. The export runs normally; only the summary is missing (about the summary)

    FAQ

    The summary showed twenty thousand products, but the file is empty. How?

    The summary counts only the export flag, the “Additional filter” conditions, the selected categories and the template's store. It ignores the warehouse, description language and the “Only export new data” checkbox, so its number is a ceiling, not a fact. The run log shows what was actually exported.

    A stop rule was triggered, but the numbers in the catalog are correct. What should I do?

    Temporarily change the threshold in the “Export stop rules” window and run the template again. A stopped run doesn't become the baseline, so the next comparison uses the previous successful run.

    The file is empty because of the warehouse, but the “nothing to export” rule is silent. Why?

    Stop rules use the same numbers as the summary, and the summary doesn't see the warehouse or “Only export new data”. Only the run log catches such an empty file (run log).

    Why is there no “No barcode” chip in my template?

    The chip appears only where a barcode is required: in the Google feed, prom.ua and the Rozetka, Epicentr, Ceneo and Allegro feeds. In other templates, the summary doesn't count products without a barcode separately.

    Can I have a stop rule that skips the export if the average price drops by more than 30%, so that near-zero prices don't go out?

    Export stop rules have no price rule. You stop on price at the import stage: price list → “Log” tab → “Import stop rules”, the “Sharp average price jump” row, threshold 30 and the “Block” action. The import is canceled and the old prices stay (import stop rules).

    Where to find it and who has access

    Menu
    Directories → Operations → Data export
    Other entry points
    the “Export” button in the template row; list menu → “Export stop rules”
    Access right
    the “Data export” window; “Export stop rules” is a separate right
    Prepare
    at least one successful run of the template — otherwise there is nothing to compare with

    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