After running a price increase, you may find that orders are pulling prices from the wrong zone — for example, a Zone 2 postcode is applying a Zone 1 rate. This is usually caused by generic prices (prices with no zone criteria set) overlapping with your zone-specific prices.
How Weighsoft selects prices
When Weighsoft looks for a price to apply to an order, it searches for the most specific matching price record. Specific prices (those with zone, account, address or other criteria set) override generic ones. However, if a generic price exists with a matching product, waste type and date range, it may be selected instead of the zone-specific price if the zone-specific price does not match all criteria correctly.
How a price increase can cause this
When a price increase is run, it applies to prices that match the criteria you configure. If you run separate increases for background prices and skip order prices, or if a generic price was increased separately to a zone price, you can end up with multiple prices competing for the same order — one with zone criteria, one without. The generic price may win if its date range or criteria are a closer match.
How to diagnose the issue
Go to Administration → Lookups → Prices and search for the product and waste type combination that is pulling the wrong price.
Look for any prices without zone criteria set — these are generic prices that apply to all zones.
Check the date ranges on both the generic and zone-specific prices. If the generic price has a date range that matches the order and the zone-specific price does not, the generic price will be selected.
Check whether the generic price was updated by a price increase run when it should not have been.
How to resolve
If the generic price is incorrect or should not exist, remove it or update its date range so it no longer matches current orders.
Use the Price Increase Rollback option if the increase created incorrect price records — go to Administration → Lookups → Price Increases, find the relevant run, and click Rollback.
After rolling back, re-run the price increase with corrected criteria to ensure zone-specific prices are targeted correctly.
Once corrected, use the Recalculate Prices option on affected orders to apply the right price.
Tip: After any price increase run, check a sample of orders across different zones to confirm the correct prices are being applied before the increase goes live across all orders.