Reading and filing price lists

What the tool reads in the supplier’s file and what it refuses to assume: country, validity, line dates, price conditions, pack sizes, same-day versions.

7 rules in force

In forceDecided on 10 October 2026 · Ref. RF-010

Price country or country of origin

What the tool does: A “Country” column is read as the country of the price (it identifies the entity concerned); “Country of origin” or “Made in” are an attribute with no effect on the price. When a column reads almost as well one way as the other, it is set “to be validated” with an alert, and the proposed reading of the price list is recomputed when the buyer corrects the column's role.
Why: Taking the origin for the price country would read the price list as a list of prices by country.
Where to see it: New supplier

In forceDecided on 10 October 2026 · Ref. RF-011

End of validity of a line or of the price list

What the tool does: An end-of-validity column is the end of the price list only if it is filled on every line. Filled on a few lines (promotions), it is a per-line validity: it is flagged, never applied to the whole price list.
Why: A time-limited promotion must not make the whole price list expire.
Where to see it: Price lists received (see the capture)

In forceDecided on 11 October 2026 · Ref. RF-012

Line-specific effective date

What the tool does: A line dated after the price list date (list effective 1 January, line effective 1 April) applies only from its own date: the agreed price, the tracking of ERP application and the export all respect it; before that date, the old price remains valid. The filing report says so. A setting allows these lines to be flagged only.
Why: Applying an increase announced for April as early as January would accuse the ERP of a delay that does not exist.
Where to see it: Price lists received (see the capture)
Price checks (see the capture)

In forceDecided on 30 September 2026 · Ref. RF-088

One price per set of conditions

What the tool does: When a price list gives several prices for the same item depending on conditions (annual commitment, order threshold, commitment period), each set of conditions is a separate price line that states its condition in full; it is never a duplicate. An unreadable condition is kept as written, with an alert. Two prices are compared only under identical conditions; otherwise the tool refuses the comparison and says why. No price is ever derived from one condition to another.
Why: A formula would produce a price nobody offered, and that price would end up in a negotiation argument with the supplier. Keeping each price with its condition leaves the buyer with figures they can defend.
Where to see it: Price list file (see the capture)
Supplier comparison

In forceDecided on 12 October 2026 · Ref. RF-089

Family or pack size changed: a new item, with the buyer's approval

What the tool does: When, from one price list to the next, the same reference changes price family or pack size (a 5 L can becoming 5.5 L), the tool detects it, asks the buyer a blocking question and shows the impact: for a pack size, the price per litre, kilo or metre on both sides. It proposes to create a new item; nothing is created without the buyer's approval, given with a reason. The old item keeps its prices and history, linked to the new one. A change of condition follows the same path, without creating an item. Until the change is approved, the line is not included in the ERP export file, and these items are left out of the analysis averages.
Why: A 5.5 L can priced above the 5 L one may be a decrease per litre: compared on the can price, the buyer would negotiate against an increase that does not exist.
Where to see it: Interpretation questions
Purchase price history (see the capture)

In forceDecided on 12 October 2026 · Ref. RF-091

Corrected version on the same day

What the tool does: A second complete file from the same supplier, with the same effective date and for the same country, is rejected at filing, before anything is written, with the name of the version already filed. To file a corrected version, the buyer uses “replace today's version”, with a reason: the first version is cancelled (reason, author, reversible operation) and its analyses become obsolete. If the filing fails, the first version comes back.
Why: Without this check, the last file filed won with no alert or trace: filing in the wrong order put the wrong version in force. Replacing a price list is the buyer's decision.
Where to see it: Price lists received (see the capture)

In forceDecided on 22 October 2026 · Ref. RF-168

A price list can be declared partial; the reading says what it guessed or cleaned; an outdated or postponed price list is flagged, never replaced silently

What the tool does: A price list received can be declared partial when it is filed (one family, a first wave): at the analysis, the references of the previous price list that it does not carry are no longer taken for deleted. A price list not declared partial is read as complete, and the declaration is never guessed. The filing flags the lines without a unit (the template's default unit is kept, but the line is said) and the lines whose date is unreadable (line and value read, without blocking the filing), and counts the references cleaned of a leading or trailing space. A price list older than the version in force on the day of the filing says so, in addition to « retroactive ». When an upcoming price list pushes back another one already announced for the same references, the tool proposes that the new one replaces the old one and the buyer decides: nothing is replaced or cancelled automatically. On a price list with quantity tiers, the tier compared is the one of the average quantity per order, failing that the one of the article's twelve-month volume, and no longer only the first. An absurd price is still put in quarantine at the analysis, and retroactivity is still judged on the real clock of the filing day.
Why: A reading had better say so than choose silently, and it is the buyer, not the tool, who decides on a replacement. These choices were made one by one, on the defects that the fictitious price lists brought to light.
Where to see it: Price lists received (see the capture)
Price list file (see the capture)

See these rules at work on your price lists

The demonstration runs on a fictitious data set, then, if you wish, on a real price list from one of your suppliers.

Try Buyvera Product tour