↑↓ selectEnter openEsc close

    1. Elbuz

    Why the price list import was blocked or the price list came in empty

    4 min readUpdated

    When a stop rule blocks an import or a price list comes in empty, Elbuz shows a banner at the top of the log: which rule triggered, its value, and whether you have new data. Shifted columns are fixed with one button.

    When you need this:

    • Import blocked — a red banner names the rule, value and threshold; the previous data stays.
    • Loaded with deviations — a yellow banner lists the warnings; the new data is in.
    • The supplier inserted a column — the banner shows which column moved where; “Apply new addresses” rewrites the field addresses.

    Where to start: the source's “Log” tab → the banner at the top.

    What the log banner shows

    • Banner color — whether you have new data: red means no, yellow means yes.
    • Rule line — which rule triggered, with what value and threshold.
    • Column shift check — spots rearranged columns and fixes the field addresses with one button.

    Do you have new data: the red and yellow banners

    If something went wrong with the last load, a colored banner appears at the top of the tab. There are two kinds, and the difference matters: one means you have the new data, the other means you don't.

    The red “Import blocked by a stop-rule” banner means a with the “Block” action rejected the new file. The price list keeps the data from the previous successful load.

    Under the title, only the rules that blocked the import are listed, with the actual value and the threshold, followed by the line “Rejected file: N rows, of which without price: M. Previous data kept in the database.”

    Rules that triggered as warnings on the same run don't make it into the red banner — except the “Price columns have moved” line. The full list of everything that triggered is in the “Last run log” panel.

    The yellow “Price list imported, but anomalies detected” banner means the opposite: a rule with the “Warn” action triggered, the data was transferred, but the deviation exceeded the threshold. The products in the price list are already new — they're just worth a look.

    Red banner “Import blocked by a stop-rule” at the top of the Log tab
    1Triggered stop-rule with its value and threshold
    2Rejected file summary
    1. The blocking rule: a sharp jump of the average price — 353.2% against a 300% threshold.
    2. The rejected file: 2 rows, none without a price; the previous data stays in the database.

    No banner at all means no rule triggered on the last run.

    How to read a rule line

    A rule line reads like this: the name, a dash, the actual value as a percentage, and the threshold in parentheses. “Sharp average price jump — 353.2% (threshold 300%)” means the average price deviated from the previous one by 353%, so it grew about four and a half times, with 300% allowed.

    This is a deviation, not a ratio: a drop of more than 100% is impossible, so with this threshold only a rise can trigger the rule.

    There are five exceptions to this format:

    • “Abnormal product price (vs. previous load)” — a product count instead of a percentage; after the threshold comes “New prices were loaded, please check them” and up to ten examples of “name: old → new”.
    • “Almost empty feed” — a row count instead of a percentage.
    • Zero rows — “Empty feed: no rows loaded”, with no number and no threshold.
    • “Price-list currency change” — the change itself, for example USD→UAH.
    • “Price columns have moved — check the column addresses” — after the dash come the columns that moved: “Price, UAH” 8→10 is the column header and its old and new number.

    Which rules exist, what each one compares the file with, and what their thresholds are — see Stop rules and supplier price control.

    The supplier rearranged the columns: the “Apply new addresses” button

    The supplier inserted a new column at the start of the file or rearranged the columns — and the addresses in the source card now point to the wrong place. The price is read from the date column, and the price list comes in empty. So you don't have to guess from the “No price” tile, the program compares headers.

    After every load in which the file produced rows (even if some rule then blocked the import), it remembers the table's header row: where it is and how each column is labeled.

    On the next load, it finds that row in the new file and checks the columns your fields read from. If a field's header has ended up in another column, the banner shows “Price columns have moved — check the column addresses” with a list of the moves, and on the right there's an “Apply new addresses” button.

    Top of the Log tab: yellow anomaly banner with the Apply new addresses button, the health card and the row of six tiles
    1Empty feed rule
    2Columns shifted, with the list of moved columns
    3Apply new addresses button
    4In price list tile showing zero
    1. Empty feed rule — no rows were loaded from the file.
    2. Columns shifted rule — lists each column whose address moved, for example the price column from 8 to 10.
    3. Apply new addresses — rewrites the source column addresses to the new positions.
    4. In price list tile — shows zero rows in the latest run.

    The button rewrites field addresses to the new column numbers: composite address 1, { }, 4 becomes 3, { }, 6; text in curly braces stays. Then you see “Column addresses fixed: N. Run the price import again”, N = fixed fields. Products aren't reloaded: the banner and empty price list stay until the next import — run it.

    If you see “Nothing to fix automatically — check the column addresses manually” instead, the button has nothing to move: the addresses were already fixed by hand, the shift was already applied earlier, or the column moved differently on different sheets. Compare the addresses with the file and run the import.

    The limits of the check, so you don't expect more from it:

    • It starts watching from the next successful load. Until the program has seen this price list's headers at least once, there's nothing to compare with, and it won't catch the first shift.
    • Tables only: Excel, , TXT, TSV. In an XML feed the address is a tag name, not a column number, so nothing there can shift. is formally checked too, but it has no header row, so don't rely on this check for JSON.
    • The header row must be among the first 30 non-empty rows of the sheet, and in the new file the program must recognize at least two of the old headers in it. Otherwise the check stays silent.
    • It stays silent if the file produced no rows. When all rows were filtered out while the file was being read — for example, a product import rule rejected everything or all cells at the field addresses are empty — the check doesn't run: you'll see neither “Price columns have moved” nor “Empty feed”.
    • It doesn't touch a field whose address you've already changed. Only fields with the same address as at the last successful load are compared.
    • It catches a move, not a rename. If a column was renamed or removed, there's no warning: the header must appear in the new file in another column, verbatim (case-sensitive) and exactly once — with two “Price” columns in the new header row, the move can't be determined.
    • Shared addresses for several sheets. If the same column moved differently on different sheets of the workbook, the button doesn't move it — fix that address by hand.
    • The shift also shows in the red banner. If another rule with the “Block” action blocked the same run, the “Price columns have moved” line and the “Apply new addresses” button appear under the blocking rules in the red banner.

    Scenarios

    The file is blocked, but the supplier really did cut the range

    What to do. Compare the “Rejected file: N rows” line with “In price” for the previous successful run. If the change is real, relax the rule for this source.

    Result. The next file goes through, and the price list is updated. How to change the rule for one source — Stop rules and supplier price control.

    The price list came in empty after the file changed

    What to do. If the banner has “Price columns have moved”, click “Apply new addresses” and run the import. If it doesn't, compare the column addresses with the file yourself.

    Result. Prices are read from the right columns again, and the banner disappears after the next import.

    A yellow banner on every load

    What to do. Check the source's products. If this deviation is normal for this supplier, raise the rule's threshold.

    Result. The banner appears only on real deviations, and the yellow dot in the source list means something again.

    What to do when a rule triggers or columns shift

    Stop rule banners and messages
    What you seeWhyWhat to do
    “Import blocked by a stop-rule” (red banner) A rule with the “Block” action triggered: the new file was rejected, the price list has the previous data Check in the banner which rule triggered and by how much the threshold was exceeded: either the supplier sent a broken file, or the threshold is too tight for this source (about the banner)
    “Rejected file: N rows, of which without price: M. Previous data kept in the database.” A snapshot of what was in the rejected file Compare it with the “In price” column of the previous successful run — the difference explains why the rule triggered (history table)
    “Price list imported, but anomalies detected” (yellow banner) A rule with the “Warn” action triggered: the data was transferred, but the deviation exceeded the threshold Check the source's products. If this deviation is normal for this supplier, raise the rule's threshold (about the banner)
    “Price columns have moved — check the column addresses — “Price, UAH” 8→10” (in the yellow or red banner) The supplier inserted or rearranged columns: the header of the column your field takes data from is now in another column Click “Apply new addresses” in the banner and run the import again (about column shifts)
    “Empty feed: no rows loaded” The file was read, but no row reached the price list. Most often the price column is off, and the price filter dropped every row If “Price columns have moved” is shown next to it, apply the new addresses; if not, compare the column addresses with the file yourself (about column shifts)
    “Nothing to fix automatically — check the column addresses manually” after clicking “Apply new addresses” The button has nothing to move: the field addresses were already fixed by hand, the shift was already applied earlier, or the column moved differently on different sheets Compare the column addresses with the file and run the import: the banner disappears if the addresses are now correct (about column shifts)
    “Import canceled, old data kept. Triggered rules: …” The same blocking case, but this is the text in the notification and in the status tooltip Open the source log — it lists the rules with their values (about the banner)
    “Check the source data. Warnings: …” The same warning, shown in the notification and in the status dot tooltip Open the log and read the yellow banner (about the banner)

    FAQ

    The red banner shows one rule, but the last run log shows three. Why?

    The red banner lists only the rules that blocked the import, plus the column shift. The “Rules triggered:” line in the last run log shows all of them, warnings included.

    Does the program check for column shifts in an XML feed?

    No. In the field address is a tag name, not a column number, so nothing there can shift. The check works for Excel, CSV, TXT and TSV.

    Why wasn't the column shift caught on the very first changed file?

    The program starts watching from the next successful load: until it has seen this price list's headers, there's nothing to compare with.

    Will the red banner go away on its own?

    Yes, after the next run on which no rule triggers. If the supplier sends the same file, it will be blocked again.

    The supplier renamed a column. Will the program notice?

    No. The check catches a move, not a rename: the header must appear in the new file verbatim, exactly once and in another column (limits of the check).

    Where to find it and who has access

    Menu
    Directories → Processing price lists → List of price lists → source → “Log” tab, banner at the top
    Other ways in
    the “Blocked” status badge in the source header or in the “Overview” grid
    Access right
    the “Price lists” window (in the menu — “List of price lists”)

    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