Hotel Won’t Fix Wrong DoorDash Address, Guests’ Food Lands Elsewhere

A front desk worker at a hotel says DoorDash has been sending food orders to the wrong property for months, because the booking hotel’s address on the app points to a different location about ten minutes away. The booking hotel’s GM told the worker in person that the misroute was not his problem to fix. The full post about the recurring misroute surfaced on r/TalesFromTheFrontDesk under the title “Sorry Door Dash, You Have the Wrong Hotel… Again.” and has drawn other front-desk workers into the comments with similar stories from their own lobbies.

How the Recurring Misroute Plays Out at the Front Desk

The misroute is mechanical. A driver walks in, sees the front desk, hands over the bag. From the driver’s point of view, the address on the app resolved to a hotel lobby, and they delivered to a hotel lobby. The misroute stays invisible until somebody looks at the receipt and asks a question the platform does not require the driver to ask: who is this order for, and is that person in the building.

The receiving hotel’s poster has built a workaround. When a delivery shows up with no room number, the worker does three things in order before accepting the bag.

• Ask for the room number on the order. Most of the time the driver does not have one.
• Check the name on the receipt against the property management system. In the recurring misroute, the name does not match any checked-in guest.
• Ask to see the order on the customer’s phone. The poster usually ends up showing the driver the property’s own name on something to prove the address is wrong, and the driver leaves with the food.

That third step is when the misroute becomes plain. The booking hotel’s name on the customer’s screen does not match the hotel where the driver is standing. The driver has been paid for the drop-off and is holding a meal that nobody at the desk ordered.

The GM’s Refusal and DoorDash’s Hands-Off Answer

DoorDash’s answer, as the poster quotes the support line back, is that the booking hotel has to be the one to ask for the correction. DoorDash will not push an address change on a merchant’s behalf. The booking hotel has to log in and edit it. That puts the fix behind the front desk of a different property, in a different brand, in a different management chain.

The poster called the Schmintercontinental directly. The general manager’s answer, in the poster’s telling, was that the issue belonged to DoorDash and the guests, not to the property. The exact line, as the poster quotes it:

This was an issue between the guests and Door Dash, and not the hotel’s issue.

The GM is, on the platform’s published rules, correct that the fix sits with the merchant. DoorDash’s Merchant Portal is the named place where store addresses live, and the GM is the only person at the Schmintercontinental who can click that fix through.

The poster’s working theory is that the booking hotel does not see the upside. The food ends up delivered somewhere, the driver is paid, the customer complains to DoorDash, and the chain’s own guest-experience score never takes the hit. That math is what the post is really about. The chain has a way to absorb a small task and chose not to, and the cost of that choice now lives in someone else’s lobby and on someone else’s support line.

Who Pays When the Address Never Gets Fixed

Three parties absorb the cost of a misrouted DoorDash order that no merchant will fix. The table below lays out what DoorDash’s own published policies say happens to each, alongside what the Reddit poster reports actually happens in this misroute. Both columns come from public sources.

The misroute shows up in three different logs and pays a price in none of them. The guest ends up on the phone with DoorDash support arguing that the driver marked the order delivered when it was not. The driver sees a clean day because the platform records the drop-off at the address the app gave them. The booking hotel’s GM never hears about any of it. None of the three logs were designed to flag this kind of misroute, and none of them do.

That is the cost of the unfixed address, in three parts. The food, the time, and the trust land in someone else’s column. The booking hotel that owns the address sits outside that split, by choice.

What DoorDash’s Own Help Pages Say About Fixing an Address

DoorDash’s merchant documentation is short and specific about who changes a store address and how. The relevant fix lives in the Merchant Portal, the same place the booking hotel would use to set pickup instructions, change the store name, or update tax rate. The portal’s settings page spells out the path in plain language. It also flags a separate route for any address that needs a suite number, which cannot be set inside the portal tool.

None of these paths can be triggered by the receiving hotel, the original guest, or the driver. Every fix goes back to a DoorDash merchant with login access. In this story, that merchant is the Schmintercontinental’s GM. The GM has been told about the misroute and has declined to act. The misroute continues because the merchant has not made the edit.

The Wrong Order Is Also a Contract Violation for the Dasher

The driver is on the wrong end of this even when they do the job right. DoorDash tracks every drop-off against the order in the dispatch app. If the name on the bag does not match the order in the app, the drop-off counts as a wrong-order-delivered event. DoorDash’s Dasher support page on the policy is blunt about what that label means:

When a Dasher delivers the incorrect order to their client, this is considered a “wrong order delivered” violation.

The same page adds that a single instance does not deactivate a driver on its own. The deactivation bar sits inside a rolling window. Deactivations for this violation only count the driver’s last 100 deliveries, or the first 50 for new dashers.

In a one-off misroute, the driver’s record stays clean. In a misroute that keeps happening at the same property because a merchant will not fix an address, the driver who shows up at the wrong hotel with the wrong hotel’s name on the bag is the one whose record carries the drop-off. DoorDash’s published policy does not address the merchant’s bad address at all. It only describes the violation that gets logged when a driver completes the delivery. The receiving hotel’s poster is the only human in the chain who can tell the driver that the platform’s record of this drop-off is going to be wrong.

The Address Edit the Booking Hotel Has Not Made

A manager with Merchant Portal access at the booking hotel can log in, open Settings, edit the address field, pick the right entry from the dropdown, and save. The page DoorDash publishes for merchants walks through those steps in plain language. The same portal also exposes pickup instructions, store name, and tax rate, so the workflow is one the property already uses for other edits.

The booking hotel’s GM was told, by another hotel’s front desk worker, that the misroute was ongoing. The same call made clear that DoorDash had redirected the complaint back to the property. It also laid out that the cost was being absorbed by drivers and guests who did not pick the hotel. He declined.

The post on r/TalesFromTheFrontDesk ends there in the poster’s telling. The comment section fills in the rest. Front desk workers from other properties post that the same DoorDash address bug has hit their lobbies at one point or another. The pattern is consistent. A chain absorbs the cost of somebody else’s mislabeled address, and the chain that owns the mislabel declines to clear it because no one in the chain owns the cost.

That is the math the post lays out, and the comments confirm. The Schmintercontinental’s address on DoorDash, as far as the poster knows, remains the wrong one. The poster keeps triaging the bags on every shift. DoorDash’s published policy continues to point the fix at the merchant who has refused to make the edit.

Frequently Asked Questions

Who needs to fix a wrong hotel address on DoorDash?

The merchant. DoorDash’s published help pages say store addresses live in the Merchant Portal and can only be changed by a merchant with Manager or Admin access. The receiving hotel, the customer, and the driver cannot edit a merchant’s address from their side of the platform.

What happens if my DoorDash order was delivered to the wrong hotel?

DoorDash’s consumer help page on never-received orders tells the customer to open the app, pick the order, tap Help, and choose “Order never arrived.” The page also says DoorDash investigates every never-delivered report to find the root cause.

Can a DoorDash driver get deactivated for delivering to the wrong hotel?

One drop-off at the wrong address, on its own, does not deactivate a driver, per DoorDash’s Dasher support article on wrong-order-delivered violations. The same article says deactivations for that violation count only the driver’s last 100 deliveries, or the first 50 for new dashers, so repeat incidents against the same merchant’s bad address can stack up against a driver who never picked the address.

How long does it take DoorDash to update a merchant’s store address?

DoorDash’s help pages do not give a turnaround time for a merchant-initiated address edit. The merchant edits the field, picks the right dropdown entry, and saves; addresses that need a suite number have to go through Merchant Support instead, and the help page does not publish a processing window for that route either.

Why can’t the receiving hotel fix the other hotel’s address?

DoorDash’s policy treats a merchant’s address as that merchant’s own record. The platform redirects outside complaints back to the merchant, as the Reddit poster says happened to the property, and the help center’s published mechanics only let the merchant edit the field. The receiving hotel can refuse the bag, log the misroute, and tell the driver, but the edit sits one property away.