Aggregator Rating Dropped: Causes and How to Raise It

When your aggregator rating drops, orders fall. The usual causes of a drop and the steps a restaurant can control to raise the rating again over time.

Four usual causes of a falling aggregator rating: an order cancelled because a dish ran out, a delay, a wrong or incomplete order and food that arrived cold. The rating formula belongs to the aggregator, but a restaurant can control all four causes.

A rating on an aggregator weighs heavily when a new guest chooses. Restaurants with a low rating get opened less. Below we explain what lowers the rating and what to do.

Key points:

  • Low scores often come from sold-out dishes, delays, mistakes and cold food.
  • When orders are on one screen and go to the POS automatically, many mistakes disappear.
  • A rating can't be raised in a day, but you can close the causes one by one.

What lowers the rating?

Read the reviews with low scores and group the causes. Four groups usually appear: the dish wasn't available, it arrived late, the order was wrong and the food was cold.

Start with the largest group. The rating changes by the aggregator's own calculation, and you don't know its formula. So pay attention only to what you can control.

1. The dish ran out

The guest orders on the aggregator, the dish is gone and the order is cancelled. This is the case that drops scores most. What to do: a stop-list set in the POS should close on the aggregator too. How it works.

2. A delay

A late order gets a low score. Cause: nobody is at the tablet, the order was seen late or no courier was found. What to do: bring aggregator orders onto one screen and pass them to the POS automatically. Then you don't have to watch a tablet: one screen.

3. A wrong or incomplete order

A modifier was forgotten, a different dish was given, a drink wasn't added. Cause: the order was retyped by hand. What to do: let the order reach the POS with its full contents automatically. A rule to check the contents against the receipt before packing also helps.

4. Cold or damaged food

This is about packaging and the road. What to do: for dishes that cool or lose shape on the way, rethink the packaging and pack sauce separately. On aggregator orders this matters most, because the guest knows you only by this score.

How to answer reviews

Answer a negative review briefly and calmly: apologize and say what you did. Don't argue. Review handling is done in the aggregator's own cabinet. The reply is also seen by the next guest.

How to track the rating

Once a week, list the low scores and count them by cause. After a month you see which cause dropped. Cancelled orders belong in the same count: 6 causes of cancellation.

To reduce dependence on aggregators, run your own channel too: aggregators and own channels.

Conclusion

  1. Group low scores by cause.
  2. Sync the stop-list from the POS to the aggregator.
  3. Take orders on one screen and don't enter them by hand.

Frequently asked questions

Why does an aggregator rating drop?

Often because of a sold-out dish, a delay, a wrong order and cold food.

Can the rating be raised quickly?

No. You have to close the causes one by one, and results come with time.

Does the stop-list affect the rating?

Yes. An order cancelled because a dish ran out brings a low score. With a synced stop-list such orders don't happen.

Where do I answer reviews?

In the aggregator's own cabinet. Keep the answer short and calm.

Want to see Delever on your own venue? Book a free 30-minute demo at delever.io or message @delever_bot on Telegram.