FeatureReleased 21 Oct 2026

Charging policies can share a connector, evaluated by priority

Several charging policies can now cover the same connector, and each carries a priority that sets the order they are evaluated in. An operator can layer an account's own policy over the provider's published one at the same connector, and reorder the policies through the API.

What changed

Added
  • A priority on each charging policy, numbered from 1 without gaps: one list for the provider's own policies and one per account. A new policy goes to the bottom of its list.
  • When a token is presented, the policies covering the connector are evaluated in order: account policies first, then the provider's, each by priority, and policies that apply to every charging station last. Within a policy, tariff rules are still evaluated in the order they were supplied, and the first match authorises and prices the session.
  • Endpoints to read and change the order, for the provider's policies and for an account's own. Saving an order sends back the version it was loaded with, and a stale order is refused with a conflict so two people cannot overwrite each other's changes.
  • Policy search returns results in priority order, and a new filter can leave account policies out.
Improved
  • A connector is no longer limited to one policy: creating or updating a policy that covers a connector already in another policy now succeeds.
  • Charging groups no longer carry precedence of their own. Where several policies reach a connector, their priority decides.
Upgrade notes

A charging policy now needs at least one tariff rule. Creating or updating a policy without tariff rules returns a validation error; previously an update that left them out silently removed every rule.