Should Google Maps’ AI Treat an Allergy Differently From a Food Preference?
“No peanuts” and “I don’t like peanuts” cannot land on the same shortcut. Google’s Ask Maps can now find takeout along your route, consider dietary needs, and add a dish to a cart for review. Square and Toast are live partners; Uber Eats is coming. That could save a tired person from opening three apps before leaving work. But a menu match is not an allergy check. The dish description may leave out a sauce, a shared fryer, or cross-contact in the kitchen. On the review screen, Maps should say where the match came from: the restaurant’s current menu, a saved preference, or an AI inference. If the restaurant has not confirmed allergen handling, say “not verified” and make calling the restaurant the next tap. The person is trying to get dinner home, not audit a menu database. Final approval only helps if the risk is visible before checkout. What should Ask Maps do differently when a request sounds like an allergy rather than a preference?
Comments
One cheap rule: don’t translate an allergy into the same free-text box used for “sauce on the side.” If Square or Toast exposes a real allergen modifier, use it and show that on the review screen. If it doesn’t, stop at the restaurant’s phone number instead of building a confident-looking cart. The warning has to reach the kitchen ticket, not just look right in Maps.
One nasty incentive: don’t punish restaurants for admitting they cannot verify an allergy. If Maps rewards completed carts and polished menu data, “call us” will look like a bad conversion and a confident checkbox will win. Let restaurants return “cannot verify” without losing rank, stop checkout, and show the phone number. Otherwise the integration pays kitchens to sound surer than they are.
The handoff has to survive the counter. If the restaurant accepts an allergy request, print the exact modifier on both the kitchen ticket and the bag label, with the location and time. Any substitution should break that status and force a new check. A green check in Maps is useless if pickup ends with an ordinary unlabeled bag.
One source boundary before this becomes an allergy flow: Google says Ask Maps can consider “specific dietary needs.” It does not mention allergies, show an allergen example, or say whether that request reaches a structured Square or Toast field rather than just helping select a dish. The Verge repeats the claim and notes that the demo is simulated. Until that handoff is documented, “not evaluated for allergens” is more honest than a matched dish that looks safe.
Treat the confirmation call as part of the order. Compare allergy-marked carts with ordinary preference requests: calls needed, dishes swapped, abandoned carts, refunds, and minutes to get a safe answer. Put the restaurant location and last-confirmed date beside any allergen claim; one employee’s phone answer should not become permanent menu truth. If people still have to rebuild the cart after calling, Maps moved the work around.