Elbuz logs every price list import per source: you see which supplier sent fewer items, got blocked by a stop rule or failed.
When you need this:
- Twenty or so suppliers — each source's dot is colored by its last import.
- Noticeably fewer items — the log shows rows read, rows kept and rows without a price.
- An import failed — the banner names the blocking rule; the step-by-step log shows where the run stumbled.
- A supplier keeps letting you down — a 0–100 health score sums up its imports over 90 days.
Where to start: a weekly supplier review from the list of price lists.
What the log does
The app records every price list import in the source log: the last 200 runs for each source.
- Status dots — the color of each source by its last run; a click opens its log.
- Health score — the supplier's score over 90 days and a tip on what to check when one of its parts drops.
- Run numbers, history and charts — what arrived this time and how it compared before.
- Stop-rule banner and column shift — why the import was blocked or the price list came in empty.
- Step-by-step log and the “✦ AI” button — which step the run failed at and what the supplier responded.
How to spot a problem supplier in a minute
You don't need to open twenty logs to check twenty suppliers. In the left panel, a colored dot sits next to each source, and its color comes from the result of the last run, not from the source settings. That's why clicking it opens the log.
1
With errors tile2
Blocked status3
Anomalies status- With errors — counts sources whose last run failed or was blocked.
- Blocked — the last run was canceled by a stop-rule and old data was kept.
- Anomalies — the run succeeded, but a rule raised a warning.
The color is picked in this order: a disabled source is gray; next, is it being imported right now; then, was the last run blocked; then, did it fail or get canceled; then, does it have stop-rule warnings. Only if all is clear does the dot take its color from the source's setup state.
- Start or end
- Decision: the path depends on the answer
What the colors mean:
- Gray — the source is still being set up: the file isn't uploaded or the columns aren't mapped.
- Green — all is well: the source is ready to import or was imported without errors.
- Red — the last run failed, was canceled or was blocked by a stop rule. The source log tells you which of the three.
- Yellow — the run went through, but stop-rule warnings fired. In the “Overview” grid, such a source also has a separate “Anomalies” badge below its status badge, and it's clickable too.
A pulsing dot means “An import is running right now.”: the source has a run whose process is alive. The dot next to a supplier shows the worst status among all its sources, and the tooltip tells you how many sources broke.
Above the “Overview” grid there's a “With errors” tile: it counts active sources whose last run failed, was canceled or was blocked. Clicking the tile filters the grid — the shortest way from “something's wrong” to a specific list.
The badge next to a source is the same as on the log card, with two overrides:
- the last run was blocked — the badge is red with a “stop” icon and the tooltip “Import blocked by a stop-rule”;
- the last run failed — the badge is red with the tooltip “The last import failed (the score averages the last 90 days)”.
So you won't see a green “93” next to a failed import.
Two more columns of the “Overview” grid matter here. In the “Last load” column, the first line is a relative date (“today”, “yesterday”, “5 days ago”) and the second is the run duration.
If the source file itself hasn't changed for more than two days, the second line becomes “file unchanged for N days” — counted from the file date, not the import date. The import may have succeeded yesterday while the file is the same one as a month ago.
Can you trust the source health score
Below the banner is a card with a large number like 78/100 and a badge next to it. This is the supplier's overall score for runs over the last 90 days. It has three parts, each shown as a separate progress bar.
- “Reliability” — the share of runs that succeeded. A blocked run also counts as a failure: the data wasn't updated. Weight in the total: 40%.
- “Data quality” — how many rows in the runs had no price or suspicious prices, as a share of all rows. Weight: 35%.
- “Freshness” — counted from the date of the last successful run: up to two days is 100%, thirty days or more is zero, linear in between. No successful run in 90 days means zero. Weight: 25%.
1
Score2
Range badge3
Reliability4
Data quality5
Freshness- Score — overall source health out of 100.
- Badge — the range the score falls into.
- Reliability — share of successful runs.
- Data quality — how clean the loaded data is.
- Freshness — how recently the file was updated.
The overall score gets a badge:
- 80 and above — “Healthy”;
- 50 to 79 — “Needs attention”;
- below 50 — “Problematic”.
While there are fewer than three runs and the score is below 80, a neutral gray “New source” badge replaces the range name. The number itself shows as usual, e.g. “74/100 · New source”. A score of 80 or above gets “Healthy” right away, even with a single run.
Below the badge there may be a one-line tip. It appears when the weakest part drops below 80% (and the tip is about that part), or when a new source doesn't have three runs yet. If reliability, quality and freshness are all 80% or higher, there's no tip: nothing to check. There are four texts:
- “Import fails often — check the format and column mapping.”
- “Many data anomalies (no price / sharp jumps) — check the source.”
- “Not updated for a while — check the import schedule.”
- “Statistics are still accumulating — the score will appear after a few imports.”
A source that hasn't been imported for more than 90 days has no health card at all — there's nothing to score. The run history below it stays where it is.
The score is a quarterly average and doesn't react to today's failure. A source that worked flawlessly for three months and broke yesterday still shows 93 and the “Healthy” badge. The current state is shown elsewhere: the color of the banner at the top of the log and the color of the status badge in the source list.
Scenarios
Weekly supplier review
A routine that takes a few minutes for the whole source list and catches almost everything worth catching.
Weekly source review
If “Deleted” has grown noticeably compared with previous runs, add an eighth item to the review: check your own ignore rules. The supplier has nothing to do with it.
Pause imports from a supplier
What to turn on. Disable the source (or the contact it belongs to).
What happens. Importing all price lists and the schedule of selected sources both skip it; a schedule that includes it writes a warning to the operation log: “Source “…” (ID …) was skipped by the schedule: the source or its supplier is disabled”.
A disabled source stays in the list with a gray dot, whatever its last run was; sources of a disabled contact aren't shown in the list at all. There are no new runs, so “Freshness” in the health score drops and reaches zero 30 days after the last successful import.
What won't happen. Disabling doesn't block the import button in the source card: you can still import such a source manually, and the run goes into the log as usual.
Disabling erases nothing: the run history and price list rows stay.
How to keep a truncated file out of the price list and set the same thresholds for all suppliers — Price list stop rules.
1
Sharp drop in item count2
Action dropdown3
Price deviation from catalog4
Apply to all sources- Rule row — the threshold is a percentage compared with the previous load.
- Action — Warn lets the import proceed with an alert, Block cancels it.
- Rule comparing product prices with the catalog.
- Apply to all sources — copies these settings to every source.
What to do when the score or the source list looks odd
| What you see | Why | What to do |
|---|---|---|
| “No runs yet” | The source has never been imported | Run the import with the “Import” button in the source header |
| A “New source” badge instead of the range name | Fewer than three runs and the score is below 80 — the app doesn't judge a source by one import | Wait for the third import; the score will become meaningful (about the score) |
| No health card at all | The source hasn't been imported even once in the last 90 days | The history below is still shown; to get a score, run an import (about the score) |
| “The last import failed (the score averages the last 90 days)” | The score is high because it's averaged over a quarter, but the last run failed | Look at the log, not the score (about the score) |
| “file unchanged for N days” in the “Last load” column | The file's own date is more than two days old, even if the import ran yesterday | Check whether the supplier updates the file at all (about the source list) |
FAQ
The score is 93, but the import failed yesterday. Why is it high?
The score is averaged over 90 days, and one failure yesterday doesn't outweigh it. The current state is shown by the banner at the top of the log and the status dot color; the badge in the source list turns red in this case (status dots).
Can I fix anything right from the log?
The log shows what happened: it won't restore the previous file, restart the import or write to the supplier. The exception is the “Apply new addresses” button for shifted columns; the consultant suggests changes to the mapping or schedule.
The source was imported yesterday, but the dot is gray. Why?
A gray dot means a disabled source or one still being set up. A disabled source is always gray, whatever its last run was (how the color is chosen).
Can I pause imports from a supplier for a while?
Yes. Disable the source or the contact: the schedule and importing all price lists skip it, and the run history stays (scenario).
The import ran yesterday, but the “Last load” column says “file unchanged for 30 days”. Why?
The label counts from the date of the file itself, not the import. The import may have run yesterday while the file is the same one as a month ago. Check whether the supplier updates the file.
Where it is and who has access
- Menu
- Directories → Processing price lists → List of price lists → source → “Log” tab
- From the “Overview” grid
- the row's status badge, the “Anomalies” badge below it, the “Log” icon in the actions column
- From the source header
- the status badge after a failed run; the “Price errors” and “Updated” tiles
- From the Operations Center
- the “Log” button on a failed import card
- Access right
- the “Price lists” window (in the menu — “List of price lists”)
- Prepare
- a source that has been imported at least once
The “Log” tab has no separate right: anyone who can open the list of price lists sees the run history and health scores of all sources. The same right protects saving stop rules. More in Price list stop rules.
The log is a tab in the source card; it has no window of its own. It's the last tab in the row, after “Products”, “Settings”, “Categories”, “Matching”, “Pricing” and “Availability”. Some of these tabs need separate rights, so for an employee without them “Log” may be the third tab.
Almost everything in the app that shows red or yellow for price lists leads here: the tooltip on the status badge even ends with “click to open the log”.
1
Log tab2
Anomaly banner3
Health card4
Last-run tiles- Log tab — the last tab in the source card.
- Banner — the price list was imported, but a stop-rule warning fired.
- Health card — a score out of 100 with its range badge.
- Tiles — counts from the last run: in price list, no price, deleted, catalog higher/lower, suspicious.
A source that has never been imported shows the heading “No runs yet” on this tab.
Related topics
- To see the problems of all sources in one list and compare suppliers, see Source analytics.
- To keep a broken file out of the price list, see Price list stop rules.
- If the source isn't connected yet or has never been imported, see How to upload a supplier price list to Elbuz.
- If you're interested in a single product's price changes rather than the run summary, see Product price history.
