---
title: "Rate cards: 'Any stop' conditions and metrics (what, why and how)"
description: "The 'Any stop' metric on rate cards and auto-assign resource rules removes the need to specify a stop position when conditioning charges or resource assignment on stop-level attributes."
url: https://help.qargo.com/us/articles/669052-rate-cards-any-stop-conditions-and-metrics-what-why-and-how
locale: us
updated: 2026-05-13
---

# Rate cards: 'Any stop' conditions and metrics (what, why and how)

## Summary {#h_a5f69143ac}

-   **What is the "Any stop" metric?**

    -   A new metric option on rate card conditions, rate table columns and auto-assign resource rules. It checks a stop-level attribute against every stop on the order, without requiring the user to select a specific stop position (1st pickup, last delivery, 2nd stop, etc.).
-   **Why was it introduced?**

    -   Conditioning a charge or rule on the country, ZIP code, 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. It also 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 pickup" and "Last delivery". When selected, the rule passes if at least one stop on the route meets the condition. When combined with **Fixed per stop** rating, a separate charge is calculated for each matching stop.

* * *

## Prerequisites {#h_f5629110ed}

-   Customer or contract carrier rate cards must already be configured in **Rates > Customer price lists** or **Rates > Cost calculation load**. See [Rates – Rate card customers](https://help.qargo.com/us/articles/133865-rates-rate-card-customers) for the basic setup.
-   For auto-assign use, planning resource rules must be configured in **Rates > Order input > Planning resources > Resource assignment**. See [Planning – Auto-assign resources](https://help.qargo.com/us/articles/407559-planning-auto-assign-resources) for the underlying mechanism.

## Use cases {#h_28c6c11f1c}

-   **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.
-   **ZIP code zone surcharges per stop.** A rate card with zone-based rating (for example, zone A = 75 EUR, zone B = 100 EUR) can now be configured once per zone. The surcharge is applied per matching stop instead of per fixed position.
-   **Auto-assigning third-party costs by intermediate hub.** When a load 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 contract carrier at a transfer hub). The hub no longer needs to be the first or last stop.
-   **Customs cost auto-assignment.** A rule that adds a customs link contract carrier whenever a load contains a stop with the **Customs** stop extra can now be configured directly. This avoids manual cost entry per load.

## Terminology {#h_2e59d0fbf4}

| **Term** | **Definition** |
| --- | --- |
| _Stop position_ | The role of a stop in the route, such as 1st pickup, last delivery or a numbered position. |
| _Stop-level attribute_ | A property that belongs to a single stop, including country, ZIP code, ZIP code 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 (pickup, delivery, transfer, empty). |

:::callout{tone="info"}
🧰 The **'Any stop' metric** is available out of the box. No feature flag is required, and existing rate cards continue to work without changes.
:::

* * *

## Using _'Any stop'_ on rate card conditions {#h_5cf32b930e}

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

1.  Navigate to **Rates > Rate card customers** (or **Cost calculation load > Contract carrier rates** for cost-side rate cards) and open the relevant rate card.
2.  Select the charge line that requires a per-stop condition.
3.  Open the **Conditions** panel and add a new condition.
4.  Choose a stop-level metric: **country**, **ZIP code**, **ZIP code zone**, **location**, **stop extras** or **stop action type**.
5.  Select **Any stop** in the position selector instead of a fixed position such as 1st pickup or last delivery.
6.  Configure the operator and value as usual (for example, _country IS NL_).
7.  Save the condition.

![](https://help.qargo.com/media/f9af3a8b0aa4-image.png)

:::callout{tone="info"}
📚 Existing conditions that reference a fixed stop position (for example, "1st pickup / country") continue to evaluate exactly as before. No migration is required, and there is no automatic conversion to "Any stop". Users must update the rules manually to select 'Any stop'.

::video{src="/media/video/7d475cf1dbe1-2026-05-13_11-00-57-1-.mp4"}
:::

* * *

## Using _'Any stop'_ in rate tables {#h_8d062069f4}

Rate table columns can also use the new "Any stop" metric. This lets the rate table look up a rate based on attributes of any stop on the route.

1.  Open the rate table on the relevant rate card.
2.  Add or edit a column.
3.  Choose a stop-level metric and select **Any stop** as the position.
4.  Define the lookup values (for example, country codes NL, BE, DE) and the corresponding rates.
5.  Save the rate table.

![](https://help.qargo.com/media/df5388576fc1-image.png)

:::callout{tone="info"}
📚 **When the rate card line is configured with a Fixed per stop calculation method, the system goes through each stop on the order.** For every stop that matches the rate table values, the corresponding rate is applied as an individual charge. A route with three stops in NL and one in BE automatically produces three NL charges and one BE charge.
:::

* * *

## Using _'Any stop'_ in auto-assign resource rules {#h_97e72c63de}

The "Any stop" concept extends to the **Route** metric in **auto-assign resource rules**. Rules can now evaluate intermediate stops that were previously out of reach.

1.  Navigate to **Configuration > Rules > Auto-assign > Load resource assignment**
2.  Create or edit a rule.
3.  Set the action and resource for the rule (for example, assign a specific contract carrier or third-party resource).
4.  Add a condition using the **Route** metric.
5.  Select **Any stop** in the position selector.
6.  Choose the stop-level attribute to evaluate (location, country, ZIP code/ZIP code zone, stop extras or stop action type).
7.  Define the condition value, for example _Location = Rotterdam Hub_ or _Stop extra = Customs_.
8.  Save the rule.

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

![](https://help.qargo.com/media/da0324d9c679-image.png)

* * *

## Troubleshooting {#h_d34f51e376}

| **Issue** | **Resolution** |
| --- | --- |
| The "Any stop" option is not visible on a rate card or auto-assign rule | Confirm that the metric in use is a **stop-level metric** (country, ZIP code, ZIP code 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 | Check 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. The _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 behavior. |
| 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 that the rule uses the **Route** metric with **Any stop** selected. Rules using **First pickup** or **Last delivery** continue to ignore intermediate stops. |


## Related articles

- [Rate card FAQ: rating by location](https://help.qargo.com/us/articles/320191-rate-card-faq-rating-by-location.md)
- [Rate card: multimodal rating condition configurations](https://help.qargo.com/us/articles/669575-rate-card-multimodal-rating-condition-configurations.md)
- [Rate card: rate table calculation metrics](https://help.qargo.com/us/articles/246412-rate-card-rate-table-calculation-metrics.md)
- [Rate card FAQ: extra charge for stops](https://help.qargo.com/us/articles/316775-rate-card-faq-extra-charge-for-stops.md)
- [Configuration - Use rules to auto-assign fields.](https://help.qargo.com/us/articles/545498-configuration-use-rules-to-auto-assign-fields.md)
