02-27-2026 04:54 PM
Toast Community,
We have noticed a significant uptick recently on online orders for our 9-unit group going to the wrong location and are wondering if anyone else has noticed the same issue, and if so, if you all were able to figure out a way to reduce that. This is more than simple user error (though I am certain some of it is likely tied to that), and the recent uptick suggests (last month or so) makes me think there is something else going on here.
@Sdaniel @Rob: Is there any known issue that you are aware of that would be leading to this spike?
Tinku
02-27-2026 05:24 PM
Yes, we’ve encountered this issue before, often enough that we created a comp code specifically for situations like this.
In the most recent case, we traced the problem back to the “View Menus by Location” section on the website. Previously, the locations in that section were organized by address rather than by location name, which may have contributed to customers ordering from the wrong location. There may be a deeper underlying issue that I haven’t identified yet, but the “View Menus by Location” section stood out as the most likely cause. It would explain why the location Elmhurst continued receiving orders that were intended for other locations, as they are the first location in that section.
I updated it to display by location name instead with the location names toggle in website editing. However, the downside is that it does not list them in alphabetical order. I believe this may be related to the location's GUID. I submitted a request to be able to organize that section in alphabetical order.
Listed by Address
Listed by Location Name
02-27-2026 05:45 PM
Thanks for the quick response. We already have it set up by location name, so that's not the issue. We have also created a specific comp for that purpose. Just to confirm, you have not seen any recent uptick in that type of issue?
02-27-2026 07:31 PM
As of recently I have not seen an uptick of this type of issue. Managers will usually flag it, but I may run the report to see if there's a spike in that comp usage.
03-02-2026 01:07 PM
I have not seen this issue reported, but I have relayed it to my team to see if they have seen any reports of similar behavior!