Delivery-app ratings and badges: how markups and errors affect them

What we know, and do not know, about badges like Most Loved

An owner's post titled Most Loved on DoorDash drew a lively discussion, and the owner attributed a weaker standing to their menu markup. We have only a search excerpt of that thread. The causal claim is the poster's interpretation, and a rating can move for many reasons at once.

Platforms define their badges and ranking signals themselves, and those definitions change. We could not verify DoorDash's current eligibility criteria from a public source while preparing this article, so we do not list thresholds here. Check the program description in your merchant portal or help center and save a dated copy, because thresholds quoted in old posts may no longer apply. A badge built around guest love will naturally lean on guest ratings, and merchant dashboards commonly report operational measures such as errors, cancellations and wait times alongside them. Those are the levers this article covers. The pricing math itself is covered in our separate markup article.

Tag your low ratings by cause before fixing anything

Owners tend to blame whichever cause they already suspect: the markup, the drivers, or the platform. Data is cheaper than guessing. For four weeks, export or copy every rating of three stars or below, along with its written comment, and tag each with one main cause. Include issues the platform reports to you, such as missing-item claims or refunds, even when no comment was written.

Some causes are yours to fix, some are shared, and some are outside your control. Driver lateness is real, but if your prep time setting made the driver wait or arrive early to a bag that was not ready, part of it is yours. Keep the tags simple so the counts stay honest.

Accuracy: the most controllable cause

Missing and wrong items frustrate guests in a way a slightly high price does not, because there is nothing they can do about it once the driver leaves. Build a packing station with the ticket at eye level, modifiers printed boldly, and a fixed order for adding items, drinks, sauces and utensils. At peak times, a second person checks each bag against the ticket before sealing it. Requests that guests type into notes, such as no onions or extra dressing, deserve a specific check, since they are easy to miss.

Seal bags with a tamper-evident sticker, and photograph sealed bags with the order number visible during busy periods. That documentation helps when contesting claims, and the routine itself reduces errors because each bag is looked at once more before it leaves. Track missing-item claims by item; if one item appears repeatedly, fix where it is stored or how it is added to the bag.

• Ticket visible at the packing station, modifiers highlighted
• Fixed packing order: mains, sides, drinks, sauces, utensils
• Second check at peak times before sealing
• Tamper-evident seal and photo with the order number
• Missing-item claims tracked by item each week

Packaging and menu choices for food that travels

A dish that is excellent at the table can arrive limp after a 20-minute ride. Fried items steam in sealed containers and soften; vented containers help. Hot and cold items should travel separately so the salad stays crisp and the burger stays warm. Sauces and dressings on the side prevent sogginess, and lids that lock prevent spills. For some items, the better answer is to leave them off the delivery menu or create a version designed to travel.

The owner who posted Test Your To Go Orders urged others to order their own food for delivery and see how it arrives; we only have a search excerpt of that post. It is a simple, effective audit. Order to a nearby address at a busy time, wait the full delivery time, and judge temperature, texture, completeness and presentation as a guest would. Our article on auditing your own takeout describes how to run that check regularly.

Prep times, pausing and cancellations

Prep time settings shape how long a driver waits and how fresh the food is when collected. If the setting is too short, drivers wait and food may be rushed; too long, and bags sit at the pass going cold. Review whether bags are ready when drivers arrive, and adjust the setting by daypart. On a slammed night, use the platform's busy or extended-prep tools rather than letting orders pile up and then cancelling them.

Cancellations from your side can count against you on platform dashboards and leave a guest hungry with no meal. Keep availability accurate: mark items out of stock as soon as they run out, and confirm that this syncs to every app. If cancellations come from integration problems, our POS integration troubleshooting article covers the diagnosis.

Responding to reviews, and what not to do

Where the platform allows public responses, keep them short, factual and specific: acknowledge the problem, say what you have changed, and invite the guest to contact you directly. Avoid arguing about details in public, and never disclose personal information about the guest. A calm reply is mostly written for future readers deciding whether to order.

Be careful with incentives. The Federal Trade Commission's Consumer Reviews and Testimonials Rule questions and answers explain that the federal rule, 16 CFR Part 465, effective October 21, 2024, prohibits offering compensation or incentives conditioned on a review expressing a particular sentiment, positive or negative. The same guidance says asking all customers for honest reviews is permitted, and the rule restricts suppressing reviews through threats or false accusations. In practice, a bag insert inviting every guest to share honest feedback is fine; offering a discount for a five-star rating is not. Platform policies may add their own rules on top.

Price parity decisions and perceived value

Markups can affect how guests judge value, especially when they know your in-store prices. But in the tagging exercise, price is only one cause among several, and it should be judged by its count. If value complaints are frequent, look first at the most visible items: a modest markup on high-cost, high-effort dishes and a smaller one on familiar anchors such as a burger or fries can feel fairer than a uniform increase. Check that delivery portions match in-store portions, since a smaller portion at a higher price draws the harshest reviews.

Tell guests plainly that app prices differ from in-store prices if they do. Regulators are looking at this area: in April 2026 the Federal Trade Commission sought public comment on unfair or deceptive fee practices in online food and grocery delivery, listing among its topics whether platforms disclose that their prices differ from store or restaurant prices. That is an advance notice of possible federal rulemaking aimed at platforms, not a final rule, but it reinforces that transparent price differences are the safer path.

Hypothetical worked example: where the rating points actually go

All numbers here are hypothetical. Over four weeks a restaurant receives 80 ratings: 58 five-star, 6 four-star, 4 three-star, 5 two-star and 7 one-star. The total is 343 points (290 plus 24 plus 12 plus 10 plus 7), an average of about 4.29 (343 divided by 80). The owner suspects the 20% markup. Tagging the 16 ratings of three stars or below shows 8 for missing or wrong items, 4 for cold or soggy food, 2 for price or value and 2 for lateness.

Suppose a bag-check routine halves accuracy problems, and the 4 orders that would have been one-star complaints instead earn four stars. That adds 12 points (4 orders times 3 points), lifting the total to 355 and the average to about 4.44. If vented containers turn 2 two-star soggy-fry ratings into four-star ones, that adds another 4 points, to 359, an average of about 4.49. Even if removing the markup erased both price complaints, it would touch only 2 of 80 ratings. These are assumptions about guest behavior, not predictions. The lesson is that in this restaurant, accuracy and packaging hold most of the opportunity, and a different restaurant's tags could point elsewhere.

Weekly routine and records to keep

Keep the tagged rating sheet running weekly, along with missing-item claims by item, cancellation counts, prep-time settings by daypart, and the date of every packaging, menu or price change. When a rating moves, you can match it to what changed. Save a dated copy of the platform's badge description, and re-check it every few months.

• Low ratings tagged by cause every week
• Missing-item claims by item, with the packing fix recorded
• Self-ordered delivery audit at least monthly
• Prep-time settings reviewed by daypart
• Review responses that are factual; no sentiment-conditioned incentives
• App price differences disclosed; delivery portions match in-store
• Dated copy of current badge criteria from the merchant portal