Summary

What is the "Any stop" metric?
- A new metric option on rate card conditions, price table columns, and auto-assign resource rules that looks at a stop-level attribute against every stop on the order, without requiring the user to select a specific stop position (1st collection, last delivery, 2nd stop, etc.).
Why was it introduced?
- Conditioning a charge or rule on the country, postcode, location, stop extras, or stop action type of a stop previously required selecting a fixed position. This made it impossible to express conditions on intermediate stops and forced the duplication of configuration lines for every possible stop position.
How does it work?
- Wherever a stop-level metric is used, a new 'Any stop' option is now available alongside positioned options like "1st collection" and "Last delivery". When selected, the rule passes if at least one stop on the route satisfies the condition. When combined with "Fixed per stop" pricing, a separate charge is calculated for each matching stop.

Prerequisites

Customer or subcontractor rate cards must already be configured in RATES > Customer Price Lists or RATES > Cost Calculation Trip. See RATES - Rate Card Customers for the foundational setup.
For auto-assign use, planning resource rules must be configured in RATES > Order Input > Planning Resources > Resource Assignment. See PLANNING - Auto Assign Resources for the underlying mechanism.

Use Cases

Per-stop surcharges by country. A customer agreement charges a fixed amount for every unloading stop based on the country of that stop (for example, NL = 50 EUR per stop, DE = 100 EUR per stop). Previously, this required duplicating the rate card line for every possible stop position. With the "Any stop" metric, a single line per country covers all stops.
Distance-based tolls applied per stop. Tolls such as the German Maut depend on the country a stop is in, regardless of its position on the route. The "Any stop / country" condition applies the toll automatically to every relevant stop.
Postal code zone surcharges per stop. A rate card with zone-based pricing (for example, zone A = 75 EUR, zone B = 100 EUR) can now be configured once per zone, with the surcharge applied per matching stop instead of per fixed position.
Auto-assigning third-party costs by intermediate hub. When a trip passes through a specific intermodal hub or location at any stop, the rule can now automatically add a third-party cost (for example, a cleaning subcontractor at a transfer hub) without needing the hub to be the first or last stop.
Customs cost auto-assignment. A rule that adds a customs link subcontractor whenever a trip contains a stop with the Customs stop extra can now be configured directly, avoiding manual cost entry per trip.

Terminology

Term	Definition
Stop position	The role of a stop in the route, such as 1st collection, last delivery, or a numbered position.
Stop-level attribute	A property that belongs to a single stop, including country, postal code, postcode zone, location, stop extras, and stop action type.
Route metric	The metric used in auto-assign resource rules to evaluate route or stop characteristics.
Stop extras	Configurable add-ons on a stop, used to flag actions such as customs, refrigeration, or temporary storage.
Stop action type	The classification of what happens at a stop (collect, deliver, transfer, empty).

🧰 The 'Any stop' metric is available out of the box. No feature flag is required, and existing rate cards continue to operate without changes.

Using 'Any Stop' on Rate Card Conditions

The "Any stop" option is available wherever a stop-level metric is referenced in a customer or subcontractor rate card condition.

NAVIGATE to RATES > Rate card customers (or Cost Calculation Trip > Subcontractor Rates for cost-side rate cards) and open the relevant rate card.
SELECT the charge line that requires a per-stop condition.
OPEN the Conditions panel and add a new condition.
CHOOSE a stop-level metric: country, postal code, postcode zone, location, stop extras, or stop action type.
SELECT Any stop in the position selector instead of a fixed position such as 1st collection or last delivery.
CONFIGURE the operator and value as normal (for example, country IS NL).
SAVE the condition.

📚 Existing conditions that reference a fixed stop position (for example, "1st collection / country") continue to evaluate exactly as before. There is no migration required, and no automatic conversion to "Any stop"; users must manually update the rules to select 'Any stop'.

Using 'Any Stop' in Price Tables

Price table columns can also use the new "Any stop" metric, allowing the price table to look up a rate based on attributes of any stop on the route.

OPEN the price table on the relevant rate card.
ADD or EDIT a column.
CHOOSE a stop-level metric and SELECT Any stop as the position.
DEFINE the lookup values (for example, country codes NL, BE, DE) and the corresponding rates.
SAVE the price table.

📚 When the rate card line is configured with a Fixed per stop calculation method, the system iterates through each stop on the order. For every stop that matches the price table values, the corresponding rate is applied as an individual charge. A route with three stops in NL and one in BE produces three NL charges and one BE charge automatically.

Using 'Any Stop' in Auto-Assign Resource Rules

The "Any stop" concept extends to the Route metric in auto-assign resource rules, allowing rules to evaluate intermediate stops that were previously unreachable.

NAVIGATE to CONFIGURATION>Rules>Auto-assign>Trip resource assignment
CREATE or EDIT a rule.
SET the action and resource that the rule should perform (for example, assign a specific subcontractor or third-party resource).
ADD a condition using the Route metric.
SELECT Any stop in the position selector.
CHOOSE the stop-level attribute to evaluate (location, country, postcode/postcode zone, stop extras, or stop action type).
DEFINE the condition value, for example Location = Rotterdam Hub or Stop extra = Customs.
SAVE the rule.

The rule passes if at least one stop on the trip matches the criteria. Where multiple stops match, the action is still performed once per trip.

Troubleshooting

Issue	Resolution
The "Any stop" option is not visible on a rate card or auto-assign rule	Confirm that the metric being used is a stop-level metric (country, postal code, postcode zone, location, stop extras, stop action type). Route-level aggregations such as "total countries on route" are not supported.
A charge configured with "Any stop / Fixed per stop" is applied only once instead of per stop	Verify that the calculation method on the rate card line is set to Fixed per stop, not Fixed per order or Fixed per route.
The condition fires for routes that should not match	Recheck the operator. IS and IN operators behave differently from NEQ and NOT IN on "Any stop" conditions: NEQ with "Any stop" passes when at least one stop does not match, which is rarely the intended behaviour.
Existing duplicated rate card lines for each stop position still apply	The migration to a single "Any stop" line is manual. Existing duplicated lines continue to work but can now be consolidated.
Auto-assign rule does not trigger on intermediate stops	Confirm the rule uses the Route metric with Any stop selected. Rules using First collect or Last delivery will continue to ignore intermediate stops.