This page covers features gated by Manager-tier permissions. Managers and Admins have these by default; your administrator can adjust who has them in Settings > Team.
What you’ll see
For each area in your catchment, the breakdown table shows:| Metric | What it shows |
|---|---|
| Orders | How many orders went to this area in the period. |
| Direct vs integration | Split between your own orders and integration-sourced orders. |
| Customers | How many unique customers ordered to this area. |
| Gross sales | Total spend from this area. |
| AOV | Average order value, useful for comparing areas of similar volume. |
| Area data | Whether the row was grouped from complete, partial, or unknown address data. |
Filtering and exporting
The filter card sets the scope of the whole page:- Date range — defaults to year-to-date; change to any period.
- Date basis — fulfilment date or created date.
- Area basis — group rows by town/area, postcode area, or county.
- POS orders — include or exclude till sales.
- Locations — limit to one or more of your shops.
- Integrations — narrow to specific integration sources.
- Order sources — narrow to the order sources present in your data.
- Fulfilment methods — delivery, courier, or relay.
- Order types — gift, funeral, corporate, or event/wedding. Leave empty to include all.
Interflora demand mode
There’s an Interflora demand mode toggle at the top of the page. When you turn it on, the report narrows to Interflora orders only and the area basis locks to postcode. New columns appear for each area:- Interflora band — the rate-card band matched to the postcode (with a Mixed badge if the area spans bands).
- Monthly total — an estimated monthly code cost summed across every matched routing code.
- Cost per order — monthly estimated cost divided by Interflora orders in the selected period.
- Routing codes and Interflora reference — the rate-card entries the match is based on.
- Pricing match — whether the row matched on postcode or on a town/county reference (common for Republic of Ireland rows, where Eircode routing keys aren’t published).
How orders are mapped to areas
Orders are grouped by the delivery address on the order. Orders without a usable address sit in the Unknown areas stat at the top of the page; if a chunk of orders couldn’t be placed, a warning banner appears with the order count. Use the POS orders filter to remove till sales from the area breakdown if you only want delivery-fulfilment orders.Common questions
Why does an area show fewer orders than I expected?
Why does an area show fewer orders than I expected?
Check the POS orders filter — if you’ve excluded till sales they won’t appear in any area row. Also check Order sources and Integrations in case you’ve narrowed the scope.
Can I see this for events as well?
Can I see this for events as well?
By default the report covers every order type. Use the Order types filter to narrow to gift, funeral, corporate, or event/wedding.
How granular is the area breakdown?
How granular is the area breakdown?
Use the Area basis selector to group rows by town/area, postcode area, or county. A drill-down to postcode sector (e.g., SW1A 1) isn’t available.
What does the Unknown areas stat mean?
What does the Unknown areas stat mean?
Orders without a usable delivery address (or with partial address data) couldn’t be placed in a specific area. The Unknown areas stat shows how many, and the row-level Area data column flags individual rows as Complete, Partial, or Unknown.
What’s next?
Peaks
See your busiest days and times.
Insights
Customer and product leaderboards.