Key account gaps on delivery apps, location by location
Key account delivery gap tracking is the location-by-location check of whether each store of a chain or franchise account lists your full range on delivery apps, and lists it well, read from the 15M+ delivery storefronts Dashmote tracks. A listing agreed with a chain's head office is a promise, not a menu: see which locations miss your range, show the wrong image or leave you out of the meal deal, as a list you can send to the account.

- Account and location
- Core range per location
- Product name as shown
- Image
- Combo inclusion
- Competitor products
- Dates
The trusted intelligence layer for teams selling to Hospitality & Retail









Which locations of my key accounts miss my range?
On delivery apps the menu is published storefront by storefront, often by a franchisee, a local manager or an agency, and each one can drop a SKU, rename it, use an old photo or build a meal deal around a competitor.
Key accounts are worth checking first: for most brands a small number of large accounts carry a large part of delivery volume. A gap at one big chain repeats across many storefronts, and closing it is one conversation with one account team rather than hundreds of outlet visits.
Before the next account review you need to know:
- Which of my key accounts have gaps, and how many locations does each gap touch?
- Which SKUs are absent, store by store?
- Which stores show the wrong product name, no official image or no combo with my product?
- Did the fixes we agreed last time actually land?
What you see per account and per location
Storefronts are grouped into accounts (chains and franchises), so one account opens as a single row with every location behind it. For each location you see:
| Field | What it tells you |
|---|---|
| Account and location | The chain or franchise, the storefront, its city and the app it is on |
| Core range per location | Which of your SKUs are listed and which are absent |
| Product name as shown | Whether it matches your official name, or reads as something else |
| Image | Official image, another image, or none |
| Combo inclusion | Whether your product sits inside the meal deals or only on its own |
| Competitor products | Which competing SKUs the location lists in the same category |
| Dates | When each listing was first and last seen |
At account level these roll up into a scorecard: locations with the full core range, locations with a gap, and the gap count per SKU and issue, ranked so you start where one fix reaches the most shoppers.
How key account managers use it between account reviews
Teams that work this view settle into four habits:
- An account ranking. After each refresh, pick the two or three accounts with the most storefronts carrying a gap.
- A fix list per account. Export the locations with their app, the missing SKU and the issue (name, image, combo), and send it to the account's digital or menu team.
- A franchise read. Within one brand, compare franchise groups or regions, so you raise the gap with the operator that has it.
- A follow-up. At the next refresh, the same list shows which fixes landed and which new gaps appeared.
Your team or agency fixes the listings, working from the list. For where your product is listed or missing across independents as well as chains, use listing and availability tracking; for the same accounts on the venue's own menu, see on-premise brand tracking.
Worked example: one account, one missing SKU
A soft drink brand agreed a core range of three SKUs with a burger chain: its 330 ml can, its Zero 330 ml can and its 500 ml bottle. The chain has 150 storefronts on delivery apps in one country. The account view shows:
| Check | Storefronts |
|---|---|
| Full core range, correct name, official image, in a combo | 62 |
| Zero can missing | 41 |
| No official image for at least one SKU | 23 |
| Brand in no combo | 30 |
| Wrong product name | 18 |
A storefront can have more than one issue, so the rows below the first do not add up to 150; 88 storefronts have at least one.
The manager opens the 41 storefronts missing the Zero can. 33 of them belong to one franchise group, mostly in two cities. One email to one operator, list attached, instead of a national escalation. The 23 image gaps go to the chain's menu team as a separate list.
At the next refresh, 29 of the 41 list the Zero can. The other 12 are the agenda for the next account call.
What the view does and does not tell you
The view shows the delivery menu as a shopper sees it. It does not see your contract with the account, the volumes each location sells or why a SKU is absent: a deliberate choice, a menu error or a temporary removal while out of stock. The dates on each listing help you tell a short gap from a lasting one.
Accounts group the locations trading under the account's name; franchisees trading under their own names can be added from your own list. A listing that cannot be tied to your range with confidence is shown as unmatched, not as present, so gap counts cover the listings we can tie to your range.
Frequently asked questions
How do I find SKU gaps across a chain's locations on delivery apps?
Compare each location's delivery menu with the core range agreed with the account, SKU by SKU, and list the locations where a SKU is absent. Doing it per location rather than per account matters, because chain menus are often published store by store and drift apart.
What counts as a key account on delivery apps?
A key account is a chain or franchise that sells your products in many locations and is managed as one customer. On delivery apps it appears as many storefronts under one name, so one gap can repeat across many of them. See what a key account is.
Can I export the list for the account team?
Yes. Every view exports as a list of locations with the app, the SKU and the issue, ready to send to the account's digital or menu team.
How often is the key account view updated?
The view is updated monthly, with the date each listing was observed. Earlier observations are kept, so you can see which gaps closed since the last account review.
Is this different from availability tracking?
Yes. Availability tracking answers where your product is listed across the outlets of a city. The key account view starts from your chain and franchise accounts and checks their locations against the range agreed with each one.
Related reading
The business case for your Head of eCommerce
If you take this to the person who signs off the budget, these are the three points that matter:
- Effort where the volume is: the few accounts that carry most delivery orders are checked location by location, so one fix reaches many storefronts at once.
- Agreements you can enforce: account reviews start from a dated list of locations, SKUs and issues, not from screenshots someone took on a phone.
- Progress you can report: the same scorecard after every refresh shows how many gaps each account closed, per SKU and per issue.
