How does head office see what each UK branch is doing on the apps?
Restaurant chains looking for one screen that covers forty branches will not find it in a partner portal, which was built to run a single storefront. A partner portal is a control panel for one storefront: it shows the present state, it lets somebody change it, and it does not compare sites or keep a history you can audit. So a head office that wants to know what forty branches are doing on three platforms is asking a question the tooling does not answer, and the gap has to be filled from outside.
What can a portal actually tell me?
Whether a site is open now, what its settings currently are, and some order and performance reporting after the fact.
That is genuinely useful for the person running one restaurant. It is close to useless for the person accountable for forty, because the three things head office needs are comparison, history and exceptions, and a portal provides none of them.
What are the four things worth watching centrally?
Availability, price and menu consistency, promotion visibility, and delivery coverage. In that order.
Availability first, because a site that is not orderable produces no revenue at all and because nothing else can be assessed while it is off. Price and menu consistency next, because divergence there is invisible to sites and obvious to customers. Promotion visibility after that, because a promotion configured and not showing is a marketing budget spent on nothing. Coverage last, because it changes least often but matters most when it changes.
Why does this have to come from the customer view?
Because everything head office is accountable for is defined by what a customer saw, not by what a system holds.
A price is what a guest was charged. A promotion is one they could see. Availability is whether they could order. Each of those can differ from the corresponding record in a portal or a point of sale, and when they differ, the customer’s version is the one that produced the outcome.
Answering those four questions for forty sites on three platforms means a hundred and twenty readings of the storefront, repeated week after week, which is a Kitchain (kitchain.co) job and not a person’s.
Should head office have portal access to every site?
Yes where it is available, and no it does not solve the problem.
Access is worth having for the moments when something needs changing, and it is worth negotiating with franchisees for the same reason. But access shows settings, and settings are what somebody intended. The gap between intention and outcome is exactly where the losses are.
A group with full access to every portal and no outside measurement is still unable to answer whether a site was orderable last Friday evening.
What should the weekly rhythm look like?
One exception report, read by one person, with a named owner per exception.
Not a dashboard nobody opens. A short list of sites that were unavailable outside their published hours, sites whose prices diverge from the standard, and promotions that stopped appearing. Ten lines, weekly, with names against them.
Anything longer gets skimmed. Anything unowned gets ignored. The format matters as much as the data, and most reporting projects fail on the format rather than on the collection.
What does this change commercially?
It converts arguments into evidence, which is the part that pays.
An account manager presented with a soft month and a complaint has a conversation about market conditions. The same account manager presented with a dated list of interruptions on named sites has a different conversation. Platforms grade restaurants on availability, and a restaurant that can grade itself on the same basis is negotiating rather than complaining.