# Delivery coverage monitoring

> Delivery coverage monitoring measures, from the customer side, where a restaurant can actually be ordered from on each delivery platform, zone by zone, and how that area changes over time. It compares the area customers really get from one capture to the next, and reads every reading against the branch's stated trading hours. Kitchain does not read the merchant account. This is a different measurement from availability monitoring: availability asks whether a store is orderable at all, coverage asks from where.

Full page: https://kitchain.co/coverage-monitoring/

## Why the two maps diverge

A restaurant's delivery area exists in two versions. The configured version is drawn once and lives in the merchant account. The live version is what a customer at a specific address sees at a specific moment, and platforms move it: peak demand, courier supply and unannounced configuration changes all contract it. The merchant dashboard shows the configured version only, so divergence between the two maps is structurally invisible to the restaurant. The failure mode this produces is described at https://kitchain.co/delivery-zone-shrinkage/

## What coverage monitoring records

- Deliverability per zone: from points across the city, per platform, whether a customer standing in that zone can order from the brand at all.
- Zone history: each capture appends to a per zone record, from which zones classify as always delivering, flaky at certain hours, or dropped.
- Peak versus quiet: captures booked at commercially important hours, compared with the same zones on earlier runs, with a zone lost while the branch was closed told apart from a zone lost while it was open.

## Reading coverage data honestly

Three distinctions keep coverage data truthful, and any implementation that skips them produces false alarms:

- A closed store is not a lost zone. A capture during closing hours shows mass non delivery that is just the schedule. Coverage is read against trading hours and alongside availability data.
- A failed probe is not evidence of no delivery. Could not measure and measured not delivering are different results and are recorded differently.
- A single capture is not a conclusion. Zones flap with courier supply. Classification needs repetition, which is why captures accumulate into per zone history rather than replacing each other.

## What it is used for

Verifying that each branch serves the districts it is supposed to serve. Diagnosing district level revenue decline, where the first question is whether the district is still inside the live area. Grounding conversations with platforms in a dated, per zone record instead of an impression.

Kitchain Coverage implements this measurement, with captures booked for the hours that matter. Product page: https://kitchain.co/coverage/ · Reference: https://kitchain.co/ai/products/coverage.md