Who Removed the Salad? A Franchise Dispute Settled on Dates, Not Memory
A dish drops off one delivery app. The franchisor blames the franchisee. A dated record shows what the customer actually saw, and protects both sides.
This is a scenario, written as an example. It is not a Kitchain client. The numbers around it are real.
Picture a café franchise with franchisee-run branches in Kuwait. The network standard is simple: one menu, and a brand-wide discount for a fixed period. Head office sets both. Franchisees run the branches and the delivery listings.
Then a screenshot arrives. On one platform, one franchisee’s signature salad is missing.
The franchisor attributes the missing dish to a broken standard; the franchisee says they did not remove it.
Both may be telling the truth. Without a record, there is no way to find out.
Memory against memory
Most disputes like this run the same way. One side has a screenshot from one day. The other side has a recollection. Neither has a date for when the dish disappeared, or a view of the other platforms where the same branch sells the same menu.
So the conversation turns on who is more confident. Every dispute becomes memory against memory.
The questions behind it repeat:
- What price was on the storefront?
- Was the promotion live?
- Was the dish on the menu?
- Was the listing open?
Your own systems hold the answers you meant. The price list, the menu, the campaign plan: that is intent. What the customer saw in the app is the fact, and the two do not always match.
The menu moves even when nobody moves it
It would be easy to assume that a missing dish means someone removed it. The data says otherwise.
Among restaurants monitored by Kitchain, we took the dishes on each restaurant’s delivery menu on 1 August 2026 and looked at what had happened by month end. In Kuwait:
- 5% of the items on the 1 August menu had vanished;
- 86% of restaurants lost at least one dish;
- 84% of disappearances were a listing problem: the dish was still selling at month end on another platform of the same brand.
A listing problem is not a withdrawal. The restaurant did not take the dish off sale; it dropped off one storefront. In Kuwait, that described more than four in five disappearances.
Get Konstantin Dotsenko’s stories in your inbox
Join Medium for free to get updates from this writer.
The pattern holds elsewhere in the Gulf. In the UAE, 79% of disappearances were listing problems, and in Saudi Arabia 86%.
And gaps last. A vanished UAE dish stayed missing for a median 17 days, and one in ten for 25 days or more. Over that span, what either side remembers of a specific screen is not a record.
What the record shows
Now replay the salad dispute with a dated record in the franchisor’s own systems.
The record shows the date the salad stopped showing on that platform. It shows on which dates the salad was seen on the other two platforms. This is an example of the broader listing-problem class, which accounted for 84% of Kuwait disappearances: the dish was still selling at month end on another platform of the same brand.
The same record answers the second question in the standard. It shows on which days the brand discount was visible on each platform, and which checked days showed no promotion.
The conversation changes. It moves from blame for a broken standard to the question of from which day, and on which platform. The dispute ends on dates, not on memory.
The record protects both sides
This is the part franchisors tend to miss. A dated record is not only a control tool for head office.
For the franchisor, the standard on price, menu and promotions becomes measurable. It can be checked against a dated record instead of a store visit and a screenshot.
For the franchisee, the same record is a defence. In four of five UAE disappearances, the dish dropped off one storefront while it kept selling on another. A franchisee accused of removing a dish can point to the date and to the platforms where it stayed live.
Three records cover most of these conversations:
- Price by dish, with dates: what each dish cost on each platform, and from which day.
- Daily promo history: which offers and dish discounts the customer could see, on which days, on which platform.
- Storefront status history: when each listing was on and when it was off.
Be precise about what this is. It is a record for the conversation: dates and prices as the customer saw them. It does not say why a dish dropped off, and whether a platform acts on it is the platform’s decision.
Start before you need it
There is one catch. The day you need a dated record, it is too late to start one. The record is an asset you build every day you keep it, and your own copy keeps it next to your own sales data for as long as you need.
Kitchain monitoring starts with no integration and no platform login. It shows menus, prices, promotions and storefront status as customers actually see them. If you want that fact inside your own systems, next to the price and the standard you set, that is an option, available to customers on request.
Full analysis on kitchain.co: https://kitchain.co/intent-vs-fact-price-promo/
