Skip to main content
All CollectionsRatesRate Card - Configuration
RATE CARD - Price tables calculation metrics
RATE CARD - Price tables calculation metrics

This article covers the calculation metric options that are available when configuring price lists based on a Price Table.

Arynne Hargreaves avatar
Written by Arynne Hargreaves
Updated over 3 months ago

Price list calculations can be set up based on a Fixed Amount, Formula or Price Table. Each calculation method has additional metrics that will be used to calculate the final price.

This article will look at the options available when using the calculation 'Price Table' as the basis of the customer price list. Price table calculations gives the widest possible configuration, however this in turn produces the most complexity and requires careful setup. There are a wide variety of options available when using a Price Table, this article will cover the most frequently used options.

Create Calculation Metric and Result of Price Table.

Select the Calculation Method: 'Price Table'. This will open the next set of metrics to select, based on how the price table results should show. Options include:

  • Fixed amount

  • Fixed per package type/product

  • Fixed per stop

  • Multiplied by a metric

Once the 'Results' metric is added, the next option will show. For Fixed amount, Fixed per package type and Fixed per stop, the option is to 'EDIT PRICE TABLE'.

When selecting 'Multiplied by a metric' another 'metric' field is exposed, where additional metrics can be selected. Each metric has an additional tiered level that is exposed, with options similar to what is available when creating a Formula price list.

Once the metric is selected, the option to 'EDIT PRICE TABLE' is exposed, along with the additional metrics that will be used to create the final price. When a price table is multiplied by a metric, the metric value is multiplied by the rate from the price table. For example, if you have a weight-based price table where 150kg falls into a bracket costing €1.5/kg, the calculation would be 150 × €1.5 = €225.

There are also special calculation modes to handle edge cases near bracket boundaries:

  • Payant pour: Takes the minimum between the normal calculation and the minimum of the next bracket. For example, with 150kg at €1.5/kg (€225), if the next bracket starts at 200kg at €1/kg (€200), it would use €200 as the final price

  • Pour en paye: Takes the maximum between the normal calculation and the maximum of the previous bracket. Using the same example, if the previous bracket was 0-99kg at €3/kg, it would compare €225 with 99kg × €3 = €297, and use €297

  • Click HERE to learn more about Payant pout / Pour en paye.

These calculation modes help prevent under/over charging for values near the beginning or end of each range.

Add Table Metrics

To configure the price table, click 'Edit price table' to create the table that will be used as the basis for the calculations. The 'RATES' page will show options to create metrics for 3 columns (Column 1, Column 2, Column 3). There are 2 tabs Metrics and Rates.

  • Metrics: Columns configured in the 'Column 1, 2, 3' fields are displayed here. Each 'column' has drop down menus that work on a tiered basis. Once the first option is selected, the next drop down menu is exposed, with options that relate to the previous selection. Add the metrics based on what the price is based on, e.g.

    • delivery location

    • amount of pallets

    This will create the first column and first row of your excel sheet.

  • Rates: Once the Metrics table is created, the table is copied to the Rates tab with the option to add the price for each line item.

When entering a range of values (ie: Starts / Ends filter), the END value is not included in the range.

Example: Setting a range from 0 - 10 will only count up to 9. To include the value '10' the range end limit should be set as 0-11.

Table metrics are extremely flexible to accommodate a variety of price configuration requirements. The metric options work on the same tiered basis found throughout the configuration, selecting the first metric exposing additional options.

  • Distance / Duration and waiting time / Goods (actual) / Goods (ordered)are the same as those used in the Formula price configuration.

  • Order:

    • Container type: Available options will pull from configured container type options. These will show in the column drop down to be selected, and will look to the container type on the order. This calculation can work with both 'Owned Containers' and 'Sea Containers' transport services. Metrics can be set for 1st pickup and last drop containers, however the system will not distinguish between loaded and empty containers when calculating prices.

    • Customer reference: These can be used as both a condition and a metric, allowing configuration of different prices based on specific customer references. Useful to large companies that may have different pricing for the same Lane or Service, based on timing or quantity.

      • TO NOTE: 'greater than/less' options may not work properly and these price lists should be carefully configured to avoid errors.

    • Requested (order import): The requested price indicates how much the customer is willing to pay for a transport order. This is typically setup as part of an integration that supports sending orders with an agreed set price.

    • Service level: Based on the service level (Next Day, 48hr, etc) defined on the order, price table calculations are set to look for exact service level values, rather than a range. This can help create price tables based on service levels, combined with additional values (zones, weight, etc).

    • Vehicle category: Vehicle category used in price calculations is based on what is entered at the order level, it DOES NOT automatically use the planned resource vehicle category.

  • Route:

    • Stops: This exposes additional tier options:

      • Postcode area + country:

        • Full: Requires the full postcode

        • Prefix (UK, NL): Only looks at the prefix of the postcode.

      • Country: Uses country codes for specific routes and will look to the country of the stops on the order.

      • Postal Code: Looks at specific postcodes. Precision is improved the more specific the postcode, ie: AB1 2EF is more precise than AB1.

      • Postcode zone: Configured in 'Zone groups' and can used to group postcodes into specific groups.

        • NOTE: when using multiple calculations on the same rate card, disable the 'Show error if metric is missing' toggle. This allows the system to check subsequent calculations if the 1st one doesn't match.

      • Requested weekday: This is useful for setting up pricing based on specific days and is commonly used for surcharges. When used alongside a service level metric, the service level metric can determine the base price and the weekday can automatically apply an extra fee if the requested day equals a Saturday or Sunday.

    • Number of collects/deliveries: Counts number of collection / delivery stops only and allows pricing to be based on the number of stops.

    • Total number of stops: Counts total number of stops and allows pricing to be based on the number of stops.

    • Total toll cost: Toll costs can be set as a percentage of the toll cost to charge, the default is 100%

      • TO NOTE: Toll costs are provided through a 3rd party service and should be considered an estimate rather than exact amounts. Toll rates may change periodically, the system relies on the service keeping their data updated accordingly.

Once rates have been entered, prices can be easily increased or decreased using the Dropdown options in the Rates tab. The default will be set to 4 decimal places, but this can be adjusted through to 0, as preferred.

*Check out the Rate Card FAQs for some of the most frequently used types of price table rate cards. These documents will include short video overviews of how these are configured.*

Price tables are complex and varied. Please contact your Account Manager if you need further assistance setting up specific price lists.

Did this answer your question?