Google Maps takes food orders. Your POS is the storefront.

On August 6, Google turned Ask Maps into an ordering agent. You describe what you want in plain language, Maps finds the restaurant, builds the cart, and hands checkout to Square or Toast. For a local operator, that means your point-of-sale menu data is now a storefront you did not know you were running.

What actually happened

Per Google's announcement, written by Maps VP and GM Miriam Daniel:

• Food ordering is live in the U.S. through Square and Toast, with Uber Eats listed as coming soon.
• Hotels and events got the same treatment — Ask Maps compares prices and availability, then hands off to partner sites for booking and ticketing.
• Personal Intelligence connects Ask Maps to Gmail and Calendar for flight, reservation, and schedule context. It is off by default.
• Ask Maps added Australia, Brazil, Canada, Indonesia, Japan, and Mexico, plus 150+ countries and territories in English. Food, hotels, and events are U.S.-only for now.

The plumbing is the story. Google says it is co-developing the Universal Commerce Protocol for Food — a vertical extension of UCP, the open agentic-commerce standard Google is building with Amazon, Shopify, Stripe, and Walmart. It is Apache 2.0 and on GitHub. Food specifications are not published yet.

Square's own release is more concrete about what a merchant actually does: food and beverage sellers with an active Google Business Profile appear in Ask Maps automatically. Menus, hours, and location sync from the Square Dashboard. Checkout runs through Order by Cash App. Orders land in the existing Square POS and Kitchen Display System. Square says there is no added setup, contract, or fee.

Why agentic commerce matters for your business

Your menu data is now ranked, not just displayed. An agent picking between three taco shops reads structured attributes — dish names, modifiers, prices, hours, availability. Stale hours in your Square Dashboard used to mean an annoyed walk-in. Now it means the agent routes the order somewhere else, silently, and you never see the session.

Zero setup cuts both ways. Automatic enrollment is convenient, and it also means the channel opened without you auditing it. Go look at what your POS is publishing today. Check the modifier groups, the 86'd items, the holiday hours.

Build to the protocol, not to Google. UCP is open and multi-vendor. The durable move is a clean product and menu record you control, mapped into whichever protocol matters this quarter. The wrong move is a bespoke Google integration you rebuild when OpenAI or Amazon ships their version.

Sources: Google Blog, Square, TechCrunch, UCP.