Skip to main content

Price not pulling through correctly

This article outlines how price criteria and date ranges work, and outlines what can cause a price to not be pulled through correctly.

N
Written by Noel

In Weighsoft, pricing is managed through the Prices section within Lookups. For a price to be applied to an order or job, it must meet two essential conditions:

  1. Be within the valid date range

  2. Match the criteria set against the price

1. Price Criteria

Prices in Weighsoft are configured with specific filters such as product type, waste type, account, outlet, and address. If an order or job does not meet the criteria defined in a price record, that price will not be applied. To view and filter price records in Weighsoft:

  1. Go to Administration > Lookups > Prices.

  2. Apply relevant filters, such as:

    • Product

    • Account

    • Address

    • Outlet

    • Waste type

    • Date range

  3. Click Search to locate the specific price record you need.

Common Scenario

  • A price is set for:

    • Product: 8 Yard Skip

    • Waste Type: General Waste

    • No other filters

This price will apply to any order that matches both the product and waste type, regardless of account, outlet, or address.

However, if an order has:

  • Waste Type: Construction Waste
    Then the price will not be applied, as it does not meet the waste type criteria.

Specific Account Example

  • A price is set for:

    • Product: 8 Yard Skip

    • Waste Type: General Waste

    • Account: AC0001

This price will only apply if the order matches all three criteria: product, waste type, and account.


2. Price Date Range

Each price can be configured with a From Date and a To Date. If an order or job falls outside this date range, the price will not be applied.

Example

  • A price is set for:

    • Product: Construction Waste

    • To Date: 15/11/2022

If a truck arrives with Construction Waste on 16/11/2022, the price will not be applied, as it is outside the valid date range.


3. Specific Prices Override Generic Ones

When searching for a valid price, Weighsoft prioritizes specific matches over generic ones. The system checks for prices with the most detailed criteria first (e.g., account and address), and gradually eliminates filters until a match is found.

Search Hierarchy Example

  • Account + Address

  • Product + Waste Type

  • Outlet

  • Generic (least filtered)

This ensures that tailored pricing for specific customers or locations is used before falling back on broader, default pricing.


Summary

To ensure prices are correctly applied in Weighsoft:

  • Always check that the order/job matches the price criteria

  • Confirm the price is within the valid date range

  • Understand that specific prices will override generic ones

  • Use the Recalculate Prices button to manually update prices for existing orders when necessary.

  • Regularly review price records to ensure all required fields are populated

  • Use filters to quickly locate and verify specific price records

  • Update price records promptly when changes occur in products, outlets, or other related fields

By following these principles, you can troubleshoot pricing issues effectively and ensure accurate billing.

Common Issue: Product Showing £0.00 on Weighbridge Tickets

If a product on a Weighbridge ticket shows a price of £0.00, it typically indicates that the job is not matching a valid price record or that a required field in the price record is missing. One common cause is an unset "Unit of Sale" field. To resolve this issue:

  1. Navigate to the administration panel and locate the product settings.

  2. Search for the product in question (e.g., "Weighbridge Charge") and open its details.

  3. Go to the Product Prices tab.

  4. Edit the relevant price record (e.g., the one associated with the specific outlet).

  5. Ensure the "Unit of Sale" field is set appropriately (e.g., to "Each").

  6. Save the changes. Once the required fields are correctly set, the prices should pull through accurately on Weighbridge tickets containing that product.

Did this answer your question?