Can an AI Order From Your Restaurant Now?
← Ramblings

Can an AI Order From Your Restaurant Now?

2026-08-09 · Clara F. & agents

Somewhere this week, someone told Google Maps "order me a pad thai for pickup on my way home," picked a restaurant from the list it gave them, and watched a cart fill itself in on Square or Toast (the same ordering screen the restaurant already uses) before they'd typed anything else. Nobody at that restaurant signed up for a new app. Nobody got an email. It just started working on 6 August 2026, inside a Google feature called Ask Maps.

If that sentence made your stomach drop a little, or made you shrug because "I don't do the online AI stuff," both reactions are a bit off, and I want to walk through why, because the actual mechanism here is worth understanding properly. It's not really about Google Maps. It's about what "AI acting on your behalf" means once you take away the chat window.

What actually happens, precisely

Ask Maps doesn't place the order. It finds the restaurant, then builds the cart (adds the pad thai, the size, whatever you specified) and hands it to you to review and pay, on Square's or Toast's own checkout, same as if you'd typed it in yourself. A human still confirms and still pays. Nothing about how the order reaches your kitchen has changed. The part that changed is who does the typing before that point: an assistant, reading your menu, instead of a customer scrolling it.

That's a smaller change than the headline makes it sound, and also a bigger one, for a specific reason.

The bigger reason: your menu is now something a machine reads, not just a person

Here's the mechanism, in plain words, because it's the actual lesson and it outlives this one Google feature. An "agentic" AI tool (one that acts instead of just answering) works by calling into other systems directly: your calendar, your inbox, or in this case, your restaurant's ordering catalogue inside Square or Toast. It doesn't browse your website the way a person does. It reads a structured record: this dish, this price, in stock or not. If that record is accurate, the assistant can act on it cleanly. If it's stale (a price that changed in June, a dish marked available that sold out weeks ago), the assistant either gets it wrong or, more likely, just quietly leaves you off the list of options it offers. It won't call you to check. It has no reason to.

I wrote about this same idea from the technical side recently. What actually makes something an "agent" rather than a chatbot is exactly this: it observes, decides, and acts, using a tool. Ask Maps ordering is that loop, running against your menu.

Were you signed up for this? Yes, quietly

This is the part that surprises people the wrong way. If your restaurant already takes online orders through Square or Toast, you're already part of this: no form to fill in, no toggle to switch on. The connection was built once, between Google and the two platforms, not restaurant by restaurant. So "I haven't touched any AI tools" doesn't mean you're not involved. It means the involvement runs entirely on however carefully you (or whoever does your admin) has kept that ordering system's menu current.

Honest limits

One thing to check today

If you already take online orders through Square or Toast, open that dashboard now, not later, and check three things: every item on the menu is actually available, every price is current, and nothing is sitting there marked "in stock" that quietly ran out weeks ago. That used to be housekeeping a human customer might notice and forgive. Now it's the exact record an assistant reads before deciding whether you're even an option worth offering. The admin didn't get more interesting. It just started mattering to someone new.