Sign in

For foodservice distributors selling to restaurants, caterers and hotels

Account analytics for foodservice distributors. Every kitchen, every category, every drop.

Which restaurants buy dry goods from you and fresh from someone else. Which accounts have gone from three drops a week to one. Which route has forty kitchens and a rep who visits twelve. From the order system you already run, account IDs only.

Upload sample data to try itSee a demoAI analytics for Foodservice distributorsWorks with foodservice ERP exports. Menus and prices stay in your system.
Account 3311 · categories bought against kitchen normreconciled ✓
Dry goods
$18k
Frozen
$9k
Fresh produce
$3k
Dairy
$1k
Beverages
—
Total$31k
Per accountcategories bought against the menu's needs
Per routedrops per week against the account's norm
100%reconciled to invoiced sales

Share of the kitchen, by category

A restaurant rarely buys everything from one distributor. Covirage shows each account's categories against what a kitchen of that type buys, watches drop frequency for the early sign of a lost account, and ranks the list by route.

Category share

Categories bought against the norm for that kitchen type, valued at your margins.

Drop frequency

Deliveries per week against the account's own history. A drop from three to one is flagged the week it happens.

Route coverage

Kitchens per route against visits logged, so the rep's list fits the week.

How it works

Three steps, in this order.

Export orders

By account, category, route and week.

Set kitchen types

Quick service, casual, fine dining, hotel. Defaults provided.

Work the route

Reps get category gaps and slipping accounts. The sales manager gets the roll-up.

“We found out an account had left when the orders stopped. Now we see the drop frequency fall two weeks earlier.”A sales manager at a regional foodservice distributor

Questions this industry asks

Short answers. The Help centre has the long ones.

How is this different from the distributors page?

That page is deliveries to retail stores. This one is kitchens: restaurants, hotels, caterers, with drop frequency and menu categories.

Which systems?

Any export with account, category, sales and route. Foodservice ERPs export this as standard.

Does it handle chains?

Yes. Chain and site are two levels of the roll-up.

Read more

Analytics software for foodservice distributors, compared · Alternatives to named products

Written for this desk: the measures, the data you already hold, and the arithmetic.

Wallet share and penetration · Foodservice distributors

Chain versus site: two levels of share for foodservice distributors

Why a foodservice distributor needs category share at the chain and at the site, how the two disagree and what each disagreement means, the roll-up that produces both from one delivery ledger, and the two lists the sales team works from: chain gaps for the national account manager and site gaps for the route rep.

16 Sept 20263 min read
Board and management reporting · Foodservice distributors

Delivery window adherence per kitchen: the deliveries that arrived during service

How a foodservice distributor measures whether deliveries arrive in each kitchen's agreed window, from the route telematics or proof-of-delivery timestamps and the account's window: adherence per kitchen and per route, the deliveries that landed during service, the routes whose adherence fell, the kitchens whose order frequency dropped after a run of bad windows, and why window adherence is a retention measure before it is an operations one.

16 Sept 20262 min read
Coverage and territory · Foodservice distributors

Drop frequency and category share per kitchen for foodservice distributors

How a foodservice distributor measures share of each restaurant's purchasing by category from the order system, watches drop frequency for the early sign of a lost account, and builds the route list, reconciled to invoiced sales.

16 Sept 20263 min read
Wallet share and penetration · Foodservice distributors

Menu-driven demand: what a kitchen should be ordering, given what it serves

How a foodservice distributor estimates each kitchen's expected category basket from its menu type and covers rather than from the segment average: the basket norm per menu type from the distributor's own fully-supplied kitchens, the categories a kitchen of that type buys that this one does not, and the gap valued, so the route rep's list says which categories to ask about at which door.

16 Sept 20263 min read
Data quality and reconciliation · Foodservice distributors

Order guide compliance: what a kitchen was set up to buy against what it buys

How a foodservice distributor measures how closely each kitchen's orders follow the order guide it was set up with, from the order guide file and the delivery ledger: guide items ordered, guide items never ordered, off-guide items ordered instead, the substitution pairs that recur, the kitchens whose guide is stale, and why a low compliance figure is usually a guide problem before it is a customer problem.

16 Sept 20263 min read
Wallet share and penetration · Foodservice distributors

Ten questions a foodservice distributor president asks, and the table that answers each

The ten questions the president of a foodservice distributor puts to the route and national account teams, which kitchens dropped a delivery day, which chain sites are off the agreement while the chain looks compliant, what should each kitchen be ordering given its menu, which order guides are stale, which deliveries landed during service, which accounts take a drop a day for a small order, which kitchens are dormant against their own cadence, what is contribution per account after drops, which chains are under-penetrated by site, and what changed, each with the table from the delivery ledger, the site master and the proof-of-delivery data, and the answer to send back.

16 Sept 20263 min read