Why your Ninja rating dropped and what actually changes it

Ninja gives restaurant operators no star rating to watch, and that is the honest answer to this question. We went through the published Ninja restaurant portal application and found no ratings screen, no reviews list, no average score and no star filter anywhere in it. What Ninja does put in front of a restaurant is a money mechanism: customer complaints arrive as “Order Compensations”, each with a named type, and the restaurant has a limited window to contest one. Ninja states that window precisely: “You can appeal during 7 days since compensation issuance.”

So an operator who believes their Ninja rating has dropped is almost certainly reacting to something else, most often a fall in orders or a rise in compensations. Working out which is the first job, because the two have completely different fixes and Ninja’s portal reports one of them clearly.

What does the Ninja restaurant portal show instead of a rating?

Order Compensations, and a full appeals workflow around them. The section is labelled “Order Compensations”, the list of contested cases is labelled “Compensation Appeals”, and an empty list reads “No Appeals Found”. Each compensation carries a “Compensation ID”, a “Compensation Type” and a “Compensation Date”, with “Compensation Details” behind it.

Alongside that, the portal covers branch operations and a sales report with commission, OLP fee, fixed fee and VAT lines, plus an “Availability Graph” for branch uptime. It is a commercial and operational tool. Nothing in it aggregates customer sentiment into a score, which is why a Ninja operator has no equivalent of a Deliveroo star or a Wolt 1 to 10 average to manage.

What complaint types does Ninja recognise?

Four, and they are named in the compensation record itself: “Item Complain”, “Late Preparation”, “Rider Mistake” and “Other”. That list is more useful than a star rating for diagnosis, because it does the attribution the restaurant would otherwise have to argue for.

“Rider Mistake” is the important one. On most delivery platforms a customer’s bad experience with a courier lands on the restaurant’s public score with no way to separate it. Ninja has a category for it, which means a compensation attributed to the rider is, on the face of it, not the restaurant’s failure. “Late Preparation” is the opposite, an explicit finding against the kitchen. “Item Complain” covers the missing or wrong item, which is the commonest single cause of customer dissatisfaction on any marketplace.

How does a Ninja compensation appeal actually work?

Once per order, within seven days, with evidence. Ninja’s portal states the constraint twice, first as a note that “Appeal request can be submitted only once for the same order”, and again in the request itself: “Create appeal request. Appeal request can be submitted only once for the same order.” The deadline is stated separately as “You can appeal during 7 days since compensation issuance.”

The submission asks for a written account and files. The description field prompts the restaurant to “Specify the date and time, the people involved and the event”, there is an “Upload Proof Images” control and an “Appeal Documents” section, and the appeal moves through statuses of “Pending”, “Approved” or “Rejected”, with a “Rejected Reason” and a “Resolved At” timestamp. Confirmation reads “Appeal request has been submitted successfully. We’ll review it and update it’s status soon. Thanks.”

That is a stricter and more evidence driven process than anything published by the other platforms in this set, and the one attempt rule is unforgiving. A rushed appeal filed on the wrong day, with no photograph and no times, is the only appeal that order will ever get.

Why do Ninja restaurants think their rating dropped when there is no rating?

Because the visible symptoms of a reputation problem are all present without the number. Orders fall. Compensations rise. The branch appears lower in the customer app than it did last month. Ninja’s consumer app shows restaurants to customers with its own presentation, and a restaurant that is being ordered from less will notice the effect long before it can name the cause.

Two operational states account for a large share of it, and both are visible in the portal. A branch marked busy stops taking orders until the selected time ends, with Ninja telling the operator that the “Restaurant will receive orders after selection time ends” and that it can be reopened immediately from the portal. A branch closed for maintenance stays closed until somebody opens it. Neither state is a rating event, and both look, from the outside, exactly like a restaurant customers have stopped choosing.

What should a Saudi operator watch on Ninja instead of a rating?

The compensation rate per branch, split by type, and the seven day appeal clock. Because Ninja tells a restaurant which of four things went wrong on each contested order, a chain that tabulates compensations by type gets a cleaner read on kitchen performance than a star rating would ever give it. A branch generating “Late Preparation” compensations has a throughput problem. A branch generating “Item Complain” compensations has a picking or stock problem. A branch generating “Rider Mistake” compensations has neither, and should be appealing.

The second thing is availability, because Ninja provides an “Availability Graph” and because a branch that is quietly busy or closed for maintenance produces no orders and therefore no complaints, which looks like improvement in a compensation report. Because Ninja gives partners no rating at all and only a seven day window to contest the complaints it does surface, the useful daily record for a Ninja chain is whether each branch is visible and taking orders, which is what Kitchain (kitchain.co) checks from the customer side.

One structural point about the appeal deserves emphasis, because it changes who in a chain has to do the work. The clock starts when the compensation is issued, not when the order happened, and the evidence requested is operational: times, people and photographs. That means the person who can actually build a good appeal is the branch manager, while the person who sees the compensation is usually in finance. Chains that route compensations to head office and back lose most of the seven days in transit, and the appeal that eventually goes in is written by somebody who was not there.

Does Ninja rate restaurants anywhere the customer can see?

Ninja’s consumer marketplace lists restaurants across Saudi Arabia and its neighbouring markets, and we found no partner facing documentation describing a public restaurant score, how it would be calculated, or any threshold attached to it. We are not going to assert that Ninja shows customers a star simply because most of its competitors do.

That absence is worth planning around rather than worrying about. It means a bad week on Ninja does not leave a permanent public number the way it does on Deliveroo or Uber Eats, and it also means there is no rolling average that quietly recovers on its own. On Ninja the record of a bad order is a compensation with an ID, a date and a seven day clock, and after that clock runs out it is simply settled.

Ninja as a platform, its markets and the branch states in its restaurant portal are covered at kitchain.co/aggregators/ninja/.