Price Lists

Opening or Creating a Price List

Go to Settings > Rate > Rate.

The upper table shows the existing price lists.

To work with a price list, either:

• select an existing price list from the upper table, or
• click New in the toolbar to create a new price list.

After selecting or creating a price list, the price list details are displayed in the lower area.

Basic Price List Workflow

A price list in Logistiqo is built in several levels. The usual workflow is:

1. Select or create the price list.
   This is the main price list, for example a toll price list, a freight price list, or a customer-specific price list.
2. Select or create a version.
   On the right side, select an existing version or click New Version. Versions are used for different validity periods, for example when prices change from a certain date.
3. Select or create a zone.
   Below the versions, select an existing zone or click New Zone. Zones are pricing areas within the selected version. For example, a kilometer-based price list can contain zones such as 0–100 km, 100–200 km, 200–300 km, and so on.
4. Define the geographical relation.
   In the Geographical Relation table, define for which route, area, or distance the selected zone is valid. This can be based on kilometer ranges, rate areas, zones, countries, postcodes, or other geographical criteria.
5. Maintain the rate table.
   In the Rate table, define the actual price tiers for the selected zone and geographical relation, for example prices up to 50 kg, 100 kg, 200 kg, and so on.

This means that the price list is not just one flat table. It is built from versions, zones, geographical relations, and rate lines.

A simplified structure is:

• Price List: The main price list.
• Version: The valid price version for a certain period.
• Zone: The pricing block, for example a distance range.
• Geographical Relation: The route or distance logic for the selected zone.
• Rate Table: The actual price tiers within that zone.

You can think of the zones as the main pricing blocks and the geographical relation as the rule that tells Logistiqo when this block should apply. The rate table then defines the exact price inside that block.

Example

A kilometer-based price list may be structured like this:

• Price list: Toll Charges, Freight Cost or any other freely chosen name
• Version: Version 1, valid from 01.10.2017 to 31.12.2025
• Zone: 0–100KM
• Geographical Relation: From Km 0 to Km 100
• Rate Table:
  • up to 50 kg: price X
  • up to 100 kg: price Y
  • up to 200 kg: price Z

A second zone could then be created for MAUT 100–200KM, with its own geographical relation and its own price tiers.

Header Data and Basic Settings

The upper detail area contains the basic setup of the selected price list. These fields define the general behavior of the price list before zones and individual price tiers are added.

Important fields are:

• Name: Name of the price list.
• Description: Free-text description of the price list.
• Default Rate Unit: Default price unit, for example kg. This unit is suggested when new rate lines are created.
• Selection Criterion: Defines which value is used for the price tier, for example weight, kilometers, loading meters, pieces, or another criterion.
• Accounting Templates Revenue: Revenue accounting template for the price list, if a specific accounting template should be used.
• Entity: Entity for which the price list is valid.
• Version: Name of the selected version.
• Valid From / Valid To: Validity period of the selected version.
• Min.Price: Minimum price for the price list. If the calculated price is below this value, the minimum price can be applied.

Important options are:

• Distance from zipcode table: Uses the postcode table to determine the distance.
• Override Revenue Account: Allows a different revenue accounting template to be selected.
• Round Up Quantity: Rounds the calculated quantity up. This can be useful if decimal quantities should not be used for the price calculation.
• Surcharges/Discounts Possible: Defines whether surcharges and discounts can be applied to prices calculated from this price list.
• Without a geographical relation: The price list does not use distance, zones, or geographical relations. Only the price tiers themselves are used.
• Calculate Distance: The distance is calculated automatically when the shipment is saved or calculated. This is especially important for price lists based on kilometers.

Versions

Versions are shown on the right side of the screen.

Use New Version to create a new version of a price list. This is useful when prices change from a certain date.

A version usually contains:

• Version name: Name of the version.
• Valid From: Date from which the version is valid.
• Valid To: Date until which the version is valid.
• Min.Price: Optional minimum price for this version.
• Zones and rate tiers: The zones and prices that belong to this version.

Using versions allows you to prepare new prices without overwriting older prices immediately.

Zones

Zones are shown below the versions on the right side of the screen.

A zone is a pricing block inside the selected version. In a distance-based price list, zones often represent distance ranges.

Examples:

• 0–100 km
• 100–200 km
• 200–300 km
• 300–400 km

When you select a zone, the corresponding Geographical Relation and Rate tables are displayed in the main area.

Important fields are:

• Name: Name of the zone.
• Description: Optional description of the zone.
• Position: Sorting order of the zone.
• Time Slot: Optional time slot, if the zone should only apply to a specific time range.
• Selection Criterion: Optional selection criterion for the zone.
• Filter By: Optional filter for additional restriction.
• Ratetype: Optional rate type selection.

Each zone can have its own geographical relation and its own price tiers.

Geographical Relation

The Geographical Relation table defines when the selected zone applies.

This is where you define the route, area, or distance logic for the selected zone.

Depending on the setup, a relation can be based on:

• from and to zones
• from and to rate areas
• countries
• postcode areas
• kilometer ranges
• direction of transport

Important columns are:

• Direction: Direction of the relation.
• From Zone / To Zone: Origin and destination zone, if zones are used.
• From Rate Area / To Rate Area: Origin and destination rate area, if rate areas are used.
• From Km / To Km: Kilometer range for which the zone is valid.

For example, if the selected zone is 0–100KM, the geographical relation can define that this zone applies from 0 km to 100 km.

Rate Table

The Rate table contains the actual price tiers of the selected zone.

This is where you define which price applies up to which quantity, weight, distance, number of pieces, loading meters, or other selected criterion.

Important columns are:

• Vehicle Type: Defines for which vehicle type the line is valid. If the line should apply to all vehicle types, use All Vehicle Types.
• Delivery Type: Defines for which delivery type or transport type the line is valid.
• Contract: Defines for which contract the line is valid.
• Unit: Unit of the rate line, if required.
• To Kg / To LDM / To Pieces: Tier limit. The displayed column depends on the selection criterion of the price list. This value defines up to which quantity, weight, loading meter, or number of pieces the line applies.
• Min.Price: Minimum price for this rate line. If the calculated price is below this value, the minimum price is used.
• Fixed Charge: Fixed amount for this rate line.
• Price Per Unit: Price per selected unit.
• Per: Unit that the price per unit is multiplied with, for example kg.
• Per Stop: Price per stop in the shipment.

A typical weight-based rate table can therefore look like this:

• up to 50 kg: price X
• up to 100 kg: price Y
• up to 200 kg: price Z
• up to 300 kg: price A

Logistiqo then selects the matching line based on the shipment values.

Price Calculation

The price calculation depends on how the price list is configured.

Typical calculation logic:

• If the price list is based on weight, Logistiqo searches for the matching weight tier.
• If the price list is based on kilometers, Logistiqo first determines the correct distance or kilometer zone.
• If a geographical relation is used, the matching origin and destination relation must be found.
• If a minimum price is set, the minimum price can apply when the calculated amount is lower.
• If a fixed charge is set, it can be used as a fixed part of the price.
• If a price per unit is set, it is multiplied by the relevant quantity, for example kg, km, loading meters, or pieces.

Assigning a Price List to a Rate Group

Price lists can be grouped into rate groups.

Go to Settings > Rate > Rate Group.

A rate group can contain multiple price lists. This is useful if several customers should use the same set of price lists.

Instead of assigning each price list individually to many customers, you can assign the rate group to the customer.

Assigning a Rate Group to a Customer

Go to Contacts > Companies and select the customer.

To assign a rate group to a customer:

1. Activate the option for using price lists.
2. Select the required Rate Group.
3. Save the customer.

For new shipments, Logistiqo can use the assigned rate group and the included price lists to calculate shipment prices automatically.

When Price Lists Should Be Used

Price lists are useful when prices should be calculated automatically based on rules or tiers, for example:

• prices by weight
• prices by distance
• prices by rate area
• prices by number of pieces
• prices by loading meters
• different prices by zone or relation
• different price versions by validity date
• customer-specific price structures
• more complex shipment pricing

For simple fixed charges without complex tiering, a service under Master Data > Service is usually the better option.

Important Note

Price lists can directly affect automatic price calculation in shipments.

Before changing an existing price list, check whether it is already used by customers, rate groups, or active shipments.

If prices change from a certain date, it is usually better to create a new Version instead of overwriting the existing one.