Skip to main content
Areas is a geographic view of where your orders are coming from. It rolls up orders by town, postcode area, or county so you can see which neighbourhoods are strongest, where orders are thin, and where to adjust delivery slots or marketing.
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: Above the table you’ll find two charts: Top areas by direct orders (highest non-integration volume) and Integration mix by area (each area’s split of direct vs integration orders). Stat cards at the top summarise total orders, direct orders, gross sales, integration share, and the share of orders that couldn’t be placed in an area. When Interflora demand mode is on, the charts switch to Top Interflora areas and Interflora bands in your top 20.

​
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.
Use the Export button to download the area breakdown for use in a spreadsheet.

​
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).
Stat cards switch to show Interflora orders, gross sales, AOV, top-20 estimated code cost, and the share of unknown areas. Estimates are derived from Interflora’s published rate card and your historical Interflora orders — they’re a planning aid, not a per-order fee.

​
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

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.
By default the report covers every order type. Use the Order types filter to narrow to gift, funeral, corporate, or event/wedding.
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.
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.
Last modified on June 2, 2026