What Square's ChatGPT and Claude Integrations Teach Us: Preparing for the Day AI Chat Becomes a New Ordering Channel
Square has announced integrations that let customers find restaurants, browse menus, and complete orders and payment inside ChatGPT and Claude conversations. This free learning material walks through the no-extra-fee, zero-setup design and what Japanese food-service and retail companies in the Philippines should do now to prepare for agentic commerce — from AI visibility to their own ordering channels.

A customer chats with ChatGPT or Claude, picks a restaurant in the conversation, and completes the order and payment right there — with a new integration from US payments giant Square, that way of buying is now a real, live service. This learning material unpacks what is happening at the entry point of "agentic commerce" and what Japanese food-service and retail companies in the Philippines should do about it.
On July 1, 2026, Square announced an integration in which "ChatGPT and Claude can find Square merchant restaurants, display their menus, and take orders directly within the conversation." Eligible restaurants are enabled automatically, with no new contracts and no additional marketplace fees. For now it is limited to restaurants in the US, but Square has signaled expansion into retail and services. Using this case, this material works through what to fix first in your own customer acquisition and ordering flow, in order from Part 1 to Part 4.
Part 1: Read, Then Draw Out the Implications for Your Company
Step 1: Pre-Reading (3 min)
Before reading, put your own business in the picture.
- If you ask ChatGPT or Claude about your restaurant or company today, does accurate information come up?
- When a customer asks an AI "What's a good Japanese restaurant in Makati?", would your business make the list of candidates?
- Is the path to ordering or booking in a form an AI can guide customers through (website, online ordering)?
Step 2: First Reading (10 min)
The following is a fictional corporate-planning report, written from the perspective of a Japanese company in the Philippines, based on the facts of the news story.
Internal Report: Square's AI Chat Ordering Integration and Its Implications for Our Manila Locations
On July 1, 2026, US payments giant Square announced integrations with ChatGPT and Claude. Users can discover Square merchant restaurants in a conversation with the AI, view menus, and complete the order and payment without leaving the chat. Orders flow directly into the restaurant's existing Square online ordering system and arrive at the POS and kitchen display just like any other order.
Three points deserve attention. First, eligible restaurants (US restaurants with online ordering enabled) are included automatically, with no new setup or contracts required. Second, Square has stated it charges no additional marketplace fees on orders through this channel — merchants pay only the standard online ordering processing fee (3.3% + 30 cents per transaction, or 2.9% + 30 cents on higher-tier plans). For restaurants that have watched delivery-app commissions eat into their margins, that difference is not small. Third, while this launch is limited to US restaurants, expansion into retail, services, and appointment-based businesses has been signaled.
Bringing this back to our Manila locations: the integration itself is not something we can use today. But it is now a fact that "customers choosing a restaurant and completing an order inside an AI conversation" has been turned into a real product by a major payments company. Our current customer acquisition depends on social media and delivery apps, and we are not prepared to be discovered via AI — our business information is not in order, our menu is not published in a form AI can read, and our online ordering path is not in place. Rather than scrambling after the wave arrives, we need to examine the foundations we should be putting in place now.
Note: The business scenario above is a fictional internal report created for learning purposes from publicly available facts. Please refer to the primary source linked above for details.
Step 3: Comprehension Check (5 min)
- With Square's integration, where can customers now complete an order and payment?
- On fees, what is different for the restaurant compared with conventional delivery apps?
- What is covered at launch, and where has expansion been signaled?
Step 4: The 3-Minute Briefing (10 min)
Practice explaining the story in your own words, in three minutes, as if briefing your management meeting. A structure of "what happened (the facts) → why it matters (fees and changing buying behavior) → what we should do (get our AI visibility and ordering paths in order)" makes the report land.
Related: What Claude Cowork's Web and Mobile Expansion Teaches Us: Preparing for a Workday Where You Hand Work to AI and Walk Away explains this in detail.
Part 2: Key Terms Explained (for Executives)
Agentic commerce — A form of buying in which an AI agent handles everything from discovering products and businesses to ordering and payment, inside a conversation. The traditional flow of "search, compare, order on a website" gives way to "ask the AI and order right there."
Marketplace fees — The sales commissions that delivery apps and marketplaces charge on revenue. Square's "no additional fees" design is a challenge to that fee structure, and it goes straight to the merchant's margins.
Automatic enablement (no opt-in) — A mechanism in which eligible merchants are included in a new channel without applying for it. The onboarding effort drops to zero, but it also means "a new sales channel is running without your knowledge," so merchants need to understand the mechanics too.
AI visibility (GEO) — The question of how generative AI perceives your business and whether it surfaces you as a recommendation. Where SEO targets search engines, GEO is the practice of getting your information to appear correctly in AI answers. The more AI chat becomes a sales channel, the more this matters.
Related: A Practical Guide to ChatGPT 5.5: Business Automation and Dashboard Building for Japanese Companies in the Philippines explains this in detail.
Part 3: Applying It to Your Own Business
Start by checking how your business looks from the AI's side
Actually ask ChatGPT or Claude: "What's a good (your business type) in (your city)?" Your business doesn't come up, the information is stale, the address or opening hours are wrong — establishing the current state is the starting point for everything. Since business information in the Philippines is published primarily in English, check whether your English-language information is in order as well.
Related: Claude Tag in Depth: Putting a Slack-Based Virtual Employee to Work at Your Philippine Operation explains this in detail.
Publish your information in a form AI can read
Are your menu and prices available only as images or PDFs? AI builds its answers from the text on web pages, so putting your menu, prices, opening hours, and address as text on your website is the minimum preparation for the conversational channels to come.
Take stock of your fee structure
Lay out the per-order fees and profit for delivery apps, your own website, and in-store orders side by side. What the Square case demonstrated is that a "low-fee direct channel" can become an axis of competition. In the Philippines too, it is worth examining options that reduce dependence on high-fee channels, such as building out your own online ordering.
Part 4: Common Failure Patterns (What Not to Do)
Failure 1: Sitting back because "it's US-only"
The integration itself is limited to the US, but changes in buying behavior cross borders. The Philippines is a market with exceptionally heavy social media use, and the shift to conversational buying may be fast. A "respond when it arrives" posture means falling behind on building your presence inside AI.
Failure 2: Staying dependent on delivery apps with no ordering path of your own
Delivery apps bring customers, but their fees squeeze profits and customer data tends not to stay with your business. In the era of AI channels, the businesses with "their own ordering path" have more options. Design the balance between dependence and diversification now.
Failure 3: Leaving your information in a form AI cannot read
Even your signature dish will struggle to appear in AI answers if it exists only as photos and social media posts. Getting your text information in order is unglamorous, but it costs almost nothing and keeps paying off for a long time.
Failure 4: Skipping the payment and personal-data checks
When adopting any new ordering channel, always verify payment security and how customer information is handled. The Philippines has the Data Privacy Act (Republic Act No. 10173), so adding any system that handles customer data requires confirming where the data is stored and how it will be used.
Tips for Getting the Most Out of This (3 Tips)
- Ask the AI about your business once a month. Making a monthly habit of checking "how we look" in ChatGPT and Claude helps you catch missing or incorrect information early.
- Do the Step 4 briefing out loud. Practicing a three-minute spoken report, as if for a management meeting or your owner, builds the muscle of turning news into decisions for your own company.
- Build the foundation instead of guessing the next integration. Rather than predicting which AI will partner with which payment provider, build the foundation that lets you ride whichever combination arrives: text-based information, online ordering, and a clear picture of your fees.
Bonus: How to Use PH AI Works' Free Consultation
PH AI Works supports Japanese companies in the Philippines with the practical AI and web work of the AI era, in Japanese — from customer acquisition (getting your GEO and AI visibility in order) to building online ordering and payment flows. If you want to know "how does our business look from the AI's side?" or "what should we fix first?", feel free to reach out through our free consultation. We can start with a quick assessment of where you stand today.
Sources & References
References
About the author

Founder / AI Engineer (36+ years in IT)
- ●From Tokyo · based in Manila for 13+ years
- ●36+ years in IT (development, SEO, AI)
- ●IBM Certified Generative AI Engineer
- ●AI chatbots, RAG & AI agent development
A Japanese AI engineer with 36+ years in IT and 13+ years on the ground in the Philippines. I write from hands-on experience to help Japanese companies adopt AI that actually delivers results — chatbots, workflow automation, AI agents, and AI-driven marketing. Feel free to reach out in Japanese or English.
Free AI Consultation
Tell us your challenges and we'll propose the right AI adoption plan for your business.
Book a Free 30-Minute ConsultationRelated Articles
Government Data Now Comes With a Classification and a Location: Reading Executive Order 119 as a Vendor Checklist
The Philippines' Executive Order No. 119, effective July 2026, introduces a four-tier classification and data residency rules for government data — and it applies to private vendors handling that data. A practical readiness guide for Japanese IT and BPO companies, from cloud inventory to the three-year compliance timeline.
8/11/2026
Using AI Now Triggers a Mandatory Assessment: Reading the NPC's Draft PIA Overhaul as Your Company Checklist
The Philippines' National Privacy Commission has proposed the first full overhaul of its Privacy Impact Assessment rules since 2017, explicitly listing AI and machine learning among the mandatory categories. A practical checklist for Japanese companies in the Philippines, from the comment deadline to the 90-day compliance window.
8/11/2026

Government AI Rules Reach the Vendors Too — Reading the DICT-CSC Circular as a Procurement Condition | Case Study for Japanese Companies in the Philippines
How to read the DICT-CSC Joint Memorandum Circular No. 003 of 9 June 2026 as a procurement requirement rather than an internal governance exercise, and what Japanese companies with Philippine government work should prepare now.
8/10/2026

The Neighbour Published It First: Turning Voluntary Agentic AI Guidance Into Your Own Checklist|Case Study for Japanese Companies in the Philippines
Singapore's cyber security agency published an addendum on securing agentic AI in June 2026. It carries no legal obligation, but it works as a ready-made checklist for a Philippine site — here is what to take from it and what to rewrite.
8/7/2026

When the Product Changes Without You Choosing It: What to Decide Before Your Tool's Default Model Is Swapped|Case Study for Japanese Companies in the Philippines
The contract and the price are unchanged, but the generative AI model inside the tool is swapped in August. Using a real case from a development tool, this study sets out the validation and communication steps Japanese companies with Philippine operations should decide in advance.
8/6/2026

Choosing in an Era When Switching Takes One Line: How Do You Judge an AI That Is "Strong in Japanese"? | A Case Study for Japanese Companies in the Philippines
A Japanese-specialised LLM has launched as an API that existing code can switch to by changing a single connection line. When the cost of moving all but disappears, what should a company actually judge a model on? A free case-study module in four parts for Japanese companies in the Philippines.
8/5/2026
