Expired prices in quote drafts

The quiet risk in an old price file

An expired price list quote error is easy to miss. The product code is right, the description looks familiar and the number sits neatly in the price column. But if its valid-until date has passed, that figure may no longer be suitable for a customer quote.

This can happen when a branch exports a price file, saves it for later and keeps using it after the supplier’s terms have changed. It can also happen when a file contains several price rows for the same product, with different date ranges. The quote may look complete while one line is based on a price that has expired.

The practical rule is simple: a price with a valid-until date must be checked against the date the quote is being prepared. If the date has passed, stop that line. Do not carry the old figure forward just because it is the only one visible.

Make price dates part of the file check

Before using an exported price list, check that the date fields have come through with the prices. A spreadsheet can look tidy even when a date column was left out of the export, hidden, or separated from the rows it belongs to.

I would make these checks part of the branch routine:

• Confirm that each dated price is still within its valid-from and valid-until period.
• Check that the date belongs to the correct product and customer price row.
• Look for multiple rows for the same code, especially where one date range ends as another begins.
• Keep expired rows out of the file used for quoting, or make their status clear to the person preparing the quote.
• If a date is missing or unclear, ask for a current price rather than assuming the old one still applies.

A useful handover note should say which price file was used and when it was checked. That gives the next person a clear starting point, rather than leaving them to guess whether the file is current.

What should happen to an expired line

An expired line should not quietly fall back to an older price. Nor should someone choose a nearby product or price because it seems plausible. The right action is to pause that line and get the current price confirmed.

This matters particularly when a list has a mix of standard items and less familiar lines. A person may spot a missing price on an unusual product, but overlook an expired price on a common fitting or length of timber. Treating date checks as a rule for every line makes the process less dependent on memory.

If a quote contains several lines, keep the unaffected lines moving where your process allows it, but make the blocked line visible. Record what needs checking, who owns the check and whether the customer needs an update. Do not let a draft that still contains an expired price reach the customer as if it were ready.

Keep customer pricing and quantity breaks in view

A date check is only one part of choosing the right price. The customer may have a specific price, a customer-group price or a general list price. Quantity breaks can also change the applicable price, so the quantity on the request needs to be considered alongside the date range.

For a practical explanation of how quantity breaks affect a quote, see quantity break pricing in quotes. The key point is to check the applicable price row, not just the first matching product code in a file.

A category discount is different from a dated customer price. Keep the rules for each clear in the data and in the branch process. If a price tie or missing price leaves more than one possible answer, stop and resolve it. A quote should not depend on someone silently choosing the row that looks most convenient.

A simple review routine for counter teams

A short review can catch the common problems without turning every quote into a lengthy investigation. I would use a consistent sequence:

1. Check that the exported file is the intended catalogue and price source.
2. Confirm that the relevant customer and product rows are present.
3. Check valid-from and valid-until dates for the prices being used.
4. Review quantity breaks and any customer-specific pricing that applies.
5. Mark missing, expired or conflicting prices for a person to resolve.
6. Approve the draft only when each quoted line has a clear, current price.

If the same issue keeps appearing, fix the export or the source data rather than relying on a note beside the counter. A clear date field and a repeatable check are more dependable than asking staff to remember which file is safe to use.

Where QuoteClerk AI fits

QuoteClerk AI reads a supplier’s catalogue, customers, stock and prices from XLSX, CSV or TSV files, and can also load a catalogue as BMEcat XML. Price selection checks customer-specific pricing first, then customer-group pricing, then the general list price. Quantity breaks and valid-from and valid-until dates are applied.

A price tie or a missing price blocks the line and flags it for a person, rather than guessing. A person on the supplier’s team approves every draft before anything reaches a customer. The approved quote is available as an A4 PDF and a generic UTF-8 CSV file.

The working process starts with an export from the merchant system. QuoteClerk AI drafts the quote from that data, then the team reviews and approves it. There is no native connection to merchant systems, so the export and the approval check remain important parts of the process.