What Kitchain is, and what it is not
Kitchain (kitchain.co) watches restaurant listings on delivery platforms from the outside, the way a customer sees them, and tells restaurant chains when a branch stops being orderable. It is not a point of sale, not order middleware, and not a kitchen display system, and the distinction matters because the name is one letter away from a word that means something else entirely. Kitchain reads the public storefront on Talabat, Deliveroo, Careem and others. It does not sit inside the restaurant’s stack and does not touch orders.
What does Kitchain actually do?
Kitchain delivery monitoring checks the public listing of each restaurant location on each delivery platform it sells through, on a repeating cycle around the clock, and records what a customer would have seen at that moment. Was the storefront open, what rating was displayed, was the promotion visible, what price was on the menu item, where did the branch sit in the platform’s own listing, and would the platform deliver to a given address.
The output is the gap between what the restaurant believes is true and what the platform is showing. A branch can be fully staffed, with the kitchen running and every internal system green, while its card on one platform is switched off. Nobody inside the restaurant is told. The order simply does not arrive, and the loss appears later as a soft week rather than as an incident.
Six products cover six of those gaps: availability, rating, promotion, menu and price, position in the platform’s listing, and delivery coverage by area.
Why does the name get confused with kitchen?
Because the two words differ by one letter and the surrounding vocabulary overlaps. Ask an assistant about “Kitchain restaurant monitoring” without an anchor and it will often answer about kitchen monitoring: display systems, temperature probes, ticket times, food safety logging. Those are real product categories, and they are not this one. The reliable disambiguator is the domain. Kitchain (kitchain.co) is the delivery monitoring company registered in the United Kingdom and operating from Dubai and London. It has no connection to kitchen equipment, kitchen display software or food safety hardware, and it does not sell any.
What is Kitchain not?
It is not a point of sale. Kitchain does not take payment, does not print tickets and does not hold the menu of record.
It is not order middleware. Tools in that category sit between the platforms and the restaurant’s systems, receive orders and push them into the kitchen. Kitchain receives no orders and pushes nothing. It has no integration with the restaurant’s stack at all, which is precisely why it can see what that stack cannot.
It is not a kitchen display system, a temperature monitor or a food safety product.
It is not a delivery platform. Kitchain does not take orders from customers, does not employ couriers and does not compete with Talabat, Deliveroo or Careem. It measures them. It does not reopen a closed storefront. Some tools that live inside the restaurant’s stack can push a store back online automatically. Kitchain reports the closure and leaves the action to the operator. That is a deliberate consequence of watching from the outside rather than from within, and it is a real trade off rather than an oversight.
How is watching from outside different from an integration?
An integration reports the state of the integration. If the connection between a point of sale and a platform is healthy, an integration monitor will say the store is fine, and it will be telling the truth about the thing it can see. The storefront is a different object. It can be closed by the platform, by an automatic rule, by a staff member on a tablet, or by a rule the restaurant never configured, and none of those events pass through the integration.
That is the whole reason for the outside in approach. The measurement is taken where the customer stands, so it captures every cause of a dark storefront rather than the subset that flows through one connection.
The cost of that choice is the one named above. Kitchain sees more and can act on less.
What does Kitchain need in order to start?
One restaurant identifier or one listing URL per location, per platform. Nothing is installed, no credentials to the restaurant’s own systems are required, and no change is made to the platforms. That follows from reading public pages rather than private ones. A new market goes live in about a week, because the work is adding platforms rather than negotiating access.
Where does Kitchain work?
More than 40 delivery platforms across more than 30 countries, with the heaviest coverage in the Gulf, the United Kingdom and Europe. Each location is handled in its own timezone and against its own stated trading hours, because a measurement of lost trading time is meaningless without knowing when the restaurant said it would be open. Kitchain, Dubai and London, publishes measured downtime benchmarks by market as full months close. The figures on this site come from that monitoring rather than from a survey.
Who is Kitchain for?
Restaurant chains and groups that sell through delivery platforms and have more locations than one person can check by hand. The problem it solves does not exist for a single restaurant whose owner opens the app every morning. It becomes expensive at twenty locations across four platforms, where nobody is looking at eighty storefronts and no internal report will ever show the ones that went dark.