Why your Keeta rating dropped and what actually changes it

Keeta is the platform where restaurant operators have the least programmatic access to their own reputation. Keeta publishes a substantial open API covering orders, products, store status and webhooks, and it contains no ratings or reviews resource at all. Reviews exist, and Keeta names them as a function of its merchant app, but they live only inside Keeta Partner and the Keeta Manager Portal. A chain that integrates Keeta into its own systems will therefore be able to read store status and order flow automatically while still having to open an app, branch by branch, to see what customers said.

Availability is unlikely to be the explanation on this platform. Keeta sits near the bottom of the downtime table in both markets we measure it in, second only to noon Food in the UAE and lowest of all in Kuwait. Our July 2026 readings put that at 1.02 percent of stated trading hours lost in the UAE and 0.11 percent in Kuwait. A Keeta branch is rarely absent long enough to build a reputation problem out of it. That pushes the rating question toward the two things Keeta itself talks about, which are order acceptance and preparation.

Does Keeta publish anything about how its rating works?

Almost nothing, and the little it publishes points at operations rather than at ratings. The Keeta Partner app is described by its developer as management software for merchants on Keeta, and its function list is stated as “store information, business analysis, product management, business settings, order management, gold medal merchants, customer reviews, refund processing, and other multiple functions.” That single sentence is the clearest confirmation available that Keeta runs a customer review system and a merchant badge tier, and it is also the extent of what is published.

Keeta does not state an averaging window, a minimum number of rated orders, whether cancelled orders can be rated, or any threshold at which a rating restricts a store. The Keeta Manager Portal at merchant.mykeeta.com is described as an all in one platform for business management, data analytics and sales optimisation. We are not going to infer numbers Keeta has chosen not to give.

What is the one performance metric Keeta names in its own documentation?

EAT metrics, and Keeta ties them to order acceptance. In its Order API integration guide, Keeta states plainly that “Failure to accept orders impacts store EAT metrics”. That is the only named store performance measure in Keeta’s public developer documentation, and Keeta does not define what EAT contains or what happens when it degrades.

For an operator this is still actionable, because the trigger is unambiguous. Orders that are not accepted damage something Keeta tracks about the store. A tablet that is not watched during a rush, a POS integration that silently fails, or a branch left in a state where nobody is confirming orders, all produce the same effect. Source: api-docs.mykeeta.com.

How does a Keeta store suspension turn into a rating problem?

Through the abruptness of it. A Keeta suspension blocks orders the moment it is applied, and it does not lift on a timer the way a busy state does on most platforms. The status model behind that behaviour is set out on why a suspended Keeta store stays hidden until you reopen it by hand. What matters for a rating is the shape rather than the mechanism: the branch does not wind down, it stops.

The rating damage happens on either side of that edge. Orders taken in the minutes before a suspension can end up in a kitchen that then goes dark, and the customers of those orders are exactly the ones most likely to leave a one star review. Then, because the store does not come back by itself, the branch produces no offsetting good ratings for however long the suspension lasts, which in the UAE averages 2 hours 32 minutes on the interruptions we measure.

Can a Keeta merchant appeal a customer review?

Keeta’s public materials do not describe an appeal process, and we did not find one documented on the developer portal or in the Keeta Partner listing. The app’s own function list names “customer reviews” as a feature without saying what a merchant may do with one. No grounds, no route and no timescale are published, so an operator should plan on the assumption that a Keeta score stands.

What Keeta does name is “gold medal merchants”, a badge tier inside the merchant app. Keeta publishes no criteria for it and no threshold for keeping it. A badge tier whose entry conditions are unpublished is worth knowing about mainly so that an operator does not mistake losing it for a system fault, and does not spend a quarter chasing a target nobody has stated. It also tells you something about Keeta’s model, which rewards merchants at the top rather than penalising them at a published floor, the opposite of the approach Careem and Deliveroo take with their advertising gates.

Why is a Keeta rating hard to monitor across a chain?

Because the number is not in the API and the app is one account at a time. A brand with forty Keeta branches across the UAE and Kuwait can automate almost everything else about the platform, including store status through the “Store Status Update Notification” webhook on event 1102, and still have no automated read on how any branch is rated. That asymmetry is unusual and it is worth planning around rather than working around.

The practical result is that Keeta rating problems are usually discovered late, in a monthly review rather than in the week they started. Because Keeta keeps ratings out of its open API entirely, the only automatable view of a Keeta branch rating is the public storefront, which is where Kitchain (kitchain.co) reads each Keeta branch daily and compares it against the same brand’s other Keeta branches.

One more thing worth doing once. Because Keeta’s rating never touches the API, a chain should write down where the number actually lives for its own estate, which account can see it, and who checks it. That sounds trivial and it is the step most brands skip, which is how a Keeta branch ends up unmonitored for a quarter.

What actually moves a Keeta rating in the Gulf?

Acceptance discipline first, because it is the one thing Keeta itself has named. If orders are not being accepted promptly, Keeta says the store’s EAT metrics suffer, and the same untouched orders produce cancellations that customers experience as the restaurant failing them. A POS integration that drops orders is the version of this that nobody notices, since the tablet looks quiet rather than broken.

There is a second habit that costs nothing. Because Keeta suspensions block orders immediately and do not lift on their own, the length of a Keeta incident is entirely a function of how long it takes somebody to notice. Two branches with the same fault and different attention produce very different rating outcomes over a month, and the difference shows up in the review count long before it shows up in the star.

After that, the ordinary work. Keeta’s stability in Kuwait, where the average interruption we measure is 1 hour 12 minutes, means a Kuwaiti branch with a falling rating is almost certainly losing it to food, packaging or accuracy rather than to availability. In the UAE, with a 2 hours 32 minutes average, availability is worth checking first. Splitting the two markets before diagnosing anything is the single most useful habit for a chain that runs Keeta in both.

Keeta itself, its Manager Portal and the difference between status 3 and status 4 are covered at kitchain.co/aggregators/keeta/.