For: operators (CPO admins) using Monta Hub. 

Pricing benchmarks shows, for every charging location you operate, where the per-kilowatt-hour (kWh) price sits against nearby competitor charge points, and a daily recommendation to raise, hold, or lower the price. This page is a read-only advisory view - it tells you where each site sits in its local market and recommends a target price, but it does not change prices for you.

Who can use this page

• Operator-admin permission is required. Drivers, installers, and non-admin team members cannot open the page.
• The feature is available at launch in the Nordics, DACH, BENELUX, and France. If the navigation entry does not appear, the feature is not enabled for your operator yet.

How do I open Pricing benchmarks?

1. Sign in to Monta Hub
2. In the main navigation, select Analytics → Pricing benchmarks.

The table has one row per (location, speed tier). Each row covers a single location for one speed tier — alternating current (AC) or direct current (DC) — so a location with both AC and DC charge points appears on two rows.

Location | The site name.

Tier | AC or DC.

Current price (per kWh) | Your active per-kWh price for this location and tier, shown in your operator's local currency. The Price group that sets this price is shown directly beneath, with a link to its edit page.

Recommendation | A direction (Raise to, Hold at, or Lower to) and a target price.

Median price of nearby charge points | The 50th-percentile per-kWh price of competitor charge points inside the catchment ring — half are cheaper, half are more expensive.

Nearby charge points | The count of competitor charge points used as the comparison set. Hover the count to see the catchment radius and the individual competitor prices.

Realistic? | A 👍 / 👎 control for you to flag whether the recommendation looks realistic. This is feedback for Monta's data team and does not change the recommendation.

How do I find a specific location?

• Use the search field with the placeholder Search location ID, name, or address.
• Use the Tier filter to show only AC or only DC rows.
• Click a chip in the summary banner — Raise, Hold, or Lower — to filter the table to rows with that recommendation. Click the chip again to clear the filter.

How are rows ordered by default?

Actionable rows appear first: locations with a Raise or Lower recommendation lead, followed by Hold, then rows with no usable recommendation. You can still override this by clicking any column header to sort.

How is the recommendation calculated?

For each row, Monta compares your current price against the nearby competitor prices inside a catchment ring.

• The catchment ring is a radius around the location. The radius is smaller for AC and wider for DC, and it widens automatically when too few competitors fall inside the standard radius — so the comparison stays locally relevant in both cities and rural areas.
• Your price is compared against the median of nearby competitor prices.
• Below the 25th percentile → Raise.
• Above the 75th percentile → Lower.
• Inside the 25th–75th percentile band → Hold.
• The target price moves toward the local median, but a single recommended change is capped at 10% of your current price so the price never jumps too far in one step.
• In thin markets (very few competitor charge points), the recommendation falls back to comparing against the lowest and highest nearby price rather than the percentile band.

How do I read the detail side sheet?

Click any row to open a side sheet with the full context for that location and tier:

1. A recommendation hero at the top showing the current price, the suggested price, and the percentage change. The colour reflects the direction — green for Raise, blue for Lower, neutral for Hold.
2. A short explanation of why this recommendation was made, covering the percentile position, the nearby median, and the catchment count.
3. A distribution panel with three interchangeable views — a position bar, a distribution curve, and a dot plot — all drawn from the actual nearby competitor prices.
4. A list of nearby charge points with the lowest, median, and highest nearby price, followed by the individual competitor charge points. Each entry shows the competitor's operator name, per-kWh price, and distance from your location, sorted by distance.
5. A button that opens the price group's edit page so you can act on the recommendation.

How do I act on a recommendation?

Pricing benchmarks does not change prices. To apply a recommendation:

1. In the row or in the detail side sheet, select the link to the price group.
2. You are taken to the edit page of the price group that sets the price for this location and tier.
3. Update the per-kWh price in the price group and save.

The change is reflected on the next daily snapshot.

Note: The link targets the operator-scoped edit page. If the price group is team-scoped, the link may show a 404 in the current beta — open the price group directly from the Charge points → Pricing & access area instead.

How do I give feedback on a recommendation?

Use the Realistic? column to flag whether a recommendation looks reasonable for the local market.

• Select Mark as realistic (👍) if the suggested direction and target match your view of the local market.
• Select Mark as not realistic (👎) if the recommendation does not match the local market.

Feedback is recorded as a data-quality signal for Monta's pricing-engine team. It does not change the recommendation shown to you.

What is in scope and what is not

Pricing benchmarks covers:

• Per-location market position against nearby competitor charge points.
• A daily recommendation to raise, hold, or lower the price.
• A 10% single-step cap on each recommendation.
• Local-currency display and a side sheet with the nearby competitor list.

Pricing benchmarks does not cover:

• Changing prices — done in the price groups in Charge points → Pricing & access.
• Network performance benchmarks such as utilisation and reliability — those live on a separate page.
• The internal pricing-engine model and competitor data pipeline.

Frequently asked questions

Why does the Snapshot date sometimes lag a day?

The page refreshes from one daily snapshot of platform and competitor data. The snapshot date next to Snapshot: is the date the data was captured. A small lag is normal.

Why is the recommendation capped at 10%?

A single-step cap of 10% of your current price keeps each recommendation small enough to apply with confidence. If the local median is further away, the cap is applied and you can move closer over several snapshots.

Why is my catchment radius wider than I expected?

The catchment ring widens automatically when too few competitor charge points fall inside the standard radius. The ring radius is shown when you hover the Nearby charge points count.

Why does a location not show a recommendation?

A row needs at least two competitor charge points with recent prices inside the catchment ring for a meaningful recommendation. Rows without enough nearby competitor data appear without a direction.

Why is the page not visible to me?

The page is operator-admin only and is gated behind a feature flag. If you do not see Pricing benchmarks in the main navigation, check that you have operator-admin permission, and that the feature is enabled for your country (Nordics, DACH, BENELUX, and France at launch).