Why your Snoonu rating dropped and what actually changes it

Snoonu is the only platform in our set that puts a number on the cost of padding a preparation time, and it does it in the confirmation dialog restaurant operators click through every day. When a Snoonu branch confirms a delivery time above the preset, the portal warns that “Putting higher than preset delivery times may result in ratings lower than 3.5!” That is a platform telling partners, in advance and in writing, which operational habit it expects to see in the rating.

Snoonu then builds its partner reporting around the same idea, surfacing recent low reviews rather than a rolling average.

Availability is not the story on Snoonu, which is unusual for this subject. Snoonu breaks often and briefly, and its interruptions are the shortest we measure anywhere. In our Kuwait panel for July 2026, Snoonu listings ran at 1.88 percent unavailability against their own stated trading hours, on an average interruption of just 23 minutes. Snoonu is a Qatari company operating across several Gulf markets, and it entered Kuwait in April 2026, so that reading covers a much shorter trading history than the other platforms beside it and is reported exactly as measured. A 23 minute gap does not build a rating problem on its own, which is why the Snoonu rating story is about time promised versus time taken, not about being offline.

What is the Snoonu Recent Low Reviews panel?

A rolling seven day view of only the bad scores. Snoonu’s merchant portal carries a widget titled “Recent Low Reviews” whose subtitle states the window explicitly: “We will show last 7 day reviews”. Its empty state says “No low reviews today – keep it up!” and defines the cut off in the line underneath: “Reviews rated 3 stars or below will appear here.” A link labelled “All Reviews” opens the full list.

The filter behind it is not a guess. The portal front end pre loads that panel with a date range of the last seven days and a rating filter set to 3, 2 and 1. So the panel is precisely a seven day, three star and below feed, and a Snoonu operator who checks nothing else is still seeing every score that could pull an average down, within a week of it happening. These strings sit in the merchant portal’s own interface dictionary at snoonu-portal.snoonu.com.

Why does Snoonu warn about delivery times and ratings?

Because on Snoonu the promise is set order by order, and the platform expects customers to punish an inflated one. The prep time dialog is titled “Confirm Delivery Time” and carries the warning “Putting higher than preset delivery times may result in ratings lower than 3.5!” alongside a confirm control and a minutes field.

Read carefully, that is a claim about expectation rather than about speed. Snoonu is not saying slow kitchens get bad ratings. It is saying that a branch which repeatedly pushes the quoted time above the preset ends up rated below 3.5. The behaviour it describes is the one every busy kitchen reaches for, adding ten minutes to buy breathing room, and Snoonu has decided to name the consequence at the moment the operator does it. No other platform in our set attaches a specific number to a specific button in this way.

What does a Snoonu review record contain?

An order id, a star rating, a written comment, a set of tags and a date. Snoonu’s review card is built from exactly those five fields, which means a Snoonu operator can take any low score straight back to the order that produced it. The card labels the order with a hash prefix and shows relative time, with strings for minutes, hours and days ago.

That structure is what makes Snoonu’s seven day window workable rather than merely alarming. A three star review with a tag and an order number is a fact about a shift. A three star review with nothing attached is only a mood. Snoonu also names the panel “Customer reviews” in its accessibility label, and shows a “New!” marker on it, which suggests the feature is recent and worth re checking as it develops.

Which Snoonu operational states feed into a rating drop?

Rejections and pauses, and Snoonu makes both explicit. When a branch refuses an order, Snoonu asks for a reason from a fixed list: “Out of Stock/Unavailable”, “Branch Closed”, “Kitchen/Staff Overload”, “Price Discrepancy/Promotion Issue” and “Customer Changed Mind”. Each of those is a customer whose order failed, and three of them are failures the restaurant caused.

Pausing matters here for a different reason, which is that it heals itself and therefore leaves nothing to review. A Snoonu pause carries a countdown and returns the branch to trading when the timer runs out, and a second kind of pause happens on its own when the connection drops. Both mechanisms are set out on why your Snoonu branch shows Orders Paused. For a rating, the consequence is that a branch can pause several times in a day, turn away the customers who arrived during each one, and produce no record anybody will ever look at.

Does Snoonu hold restaurants to a rating commitment?

It asks for one in writing. Snoonu’s merchant growth incentive application includes a commitment question phrased as “Do you commit to improving your operational metrics (prep time, cancellation rate, and ratings) over the next quarter?” with answers “Yes, I commit” and “No”. That is a platform naming the exact triple it cares about, in the exact order it cares about it, as a condition of a commercial programme.

Snoonu does not publish an averaging window for the public rating, a minimum number of rated orders, or a threshold at which it restricts a store. We are not going to supply those. What is documented is the direction of travel, which is that prep time, cancellations and ratings are treated as one connected set, and that Snoonu is prepared to make a partner sign up to improving them.

How should a multi branch chain watch Snoonu ratings?

By treating the seven day low review feed as the primary instrument and the branch star as the confirmation. Because Snoonu’s own panel shows only the last week and only three stars and below, it is excellent for catching a new problem and useless for judging whether last month’s fix held. That second question needs a record kept outside the portal.

One more asymmetry is worth naming. Snoonu warns about a 3.5 rating in the prep time dialog but does not show a partner how close a branch currently is to it, so the warning arrives without the measurement that would make it useful. A branch sitting at 4.4 and a branch sitting at 3.6 see the same sentence at the same moment, and only one of them should be changing its behaviour because of it.

Supplying the missing half is cheap and nobody does it. A chain that records each Snoonu branch rating on a fixed day each week knows which branches are inside a tenth of a point of the line Snoonu named, and can tell those branches to stop padding delivery times while telling the rest to carry on. Without that number the warning is a general instruction issued to every branch, which is the form of advice kitchens learn to ignore.

The same is true across branches. Snoonu’s portal manages branches in bulk, with a “Mark branches busy” mode and per branch pause controls, but the review feed is where a chain finds out that one branch is generating the complaints. A Snoonu pause expires by itself and leaves nothing behind. A branch can therefore pause repeatedly, quote longer delivery times each time, and slide toward the 3.5 line Snoonu warns about with no record of it anywhere. Kitchain (kitchain.co) keeps that trail by recording each Snoonu branch rating daily.

Snoonu itself, its merchant portal and the way a paused branch returns on a timer are covered at kitchain.co/aggregators/snoonu/.