Google announced new Connected Apps for Search and the Gemini app on 20 November 2026. In the United States, grocery integrations with Albertsons, Safeway, Shaw’s and Target can help users build orders and check out, while Experian and H&R Block support selected financial tasks. Angi and Thumbtack connections for local-service discovery are planned for the coming weeks.
The commerce experiences are powered in part by the Universal Commerce Protocol, an open standard designed to connect AI discovery with carts, checkout and order operations. Availability remains phased and many merchant features require approval, so the immediate opportunity for most businesses is readiness—not pretending every shop can switch the feature on today.
1. Separate Connected Apps from ordinary rankings
Connected Apps are integrations that let eligible users take actions with a service inside Search or Gemini. They are not a new organic ranking factor or a guarantee that a business will be recommended. Standard web pages, product listings, local profiles and ads remain separate discovery surfaces with their own requirements.
2. Understand what UCP does
Universal Commerce Protocol provides a common language for AI surfaces, merchants, payment providers and other participants across discovery, cart, checkout and post-purchase events. Google supports native checkout and cart-transfer paths. The merchant remains Merchant of Record and retains responsibility for the transaction and customer relationship.
3. Check market and account eligibility
The latest Connected Apps announcement focuses on U.S. users. Google says the Merchant Center UCP integration hub is gradually rolling out in the United States, with Australia and Canada expected to follow, and select merchant participation requires an interest form and technical validation. Do not advertise availability that your account does not show.
4. Decide whether to watch, prepare or integrate
A small business outside an eligible market may only need to improve product and service information and monitor official access. A platform or large retailer may start technical assessment. Choose the stage based on eligibility, transaction volume, engineering capacity and customer value—not fear of missing a new interface.
5. Fix Merchant Center foundations
For retail, accurate product feeds, brand assets, business contacts, shipping and return policies remain central. Reconcile identifiers, variants, price, stock and destination URLs with the website and order system. An AI-assisted checkout cannot repair a feed that sells an unavailable product or shows the wrong delivery promise.
6. Make inventory and substitutions dependable
Grocery and multi-item orders introduce real-time availability, location and substitution decisions. Define whether an alternative needs approval, how quantity and price changes are shown and when a cart must be revalidated. Preserve a clear audit trail so support teams can explain what the customer approved.
7. Choose native checkout or cart transfer
Native checkout handles the purchase within Google’s AI surfaces and requires checkout, payment and order-lifecycle integration. The cart path transfers a prepared cart to the merchant website through a continue URL. Compare conversion opportunity, implementation effort, brand needs and operational risk before choosing a path.
8. Prepare fulfilment and policy data
Shipping methods, delivery windows, pickup eligibility, taxes, discounts and returns must be represented accurately. Test edge cases such as partial stock, remote locations, restricted products and failed address validation. Customer-facing terms should match what the operations team can actually deliver.
- Keep item-level availability and delivery promises current.
- Show price, discount and fee changes before confirmation.
- Publish a reachable support contact and return process.
- Reconcile order status across every customer surface.
9. Protect payment and identity flows
Use approved payment providers, tokenisation and the authentication patterns in the current implementation guide. Do not put personal information in error messages or logs. Account linking and loyalty should be optional, consented and tested for revocation. Security teams should review endpoints, keys, signatures and rate limits before production.
10. Publish an accurate UCP profile
Participating businesses host a public profile at the well-known UCP path to declare supported protocol versions, capabilities, endpoints, payment handlers and public keys. Declare only functionality that has passed testing. A stale or exaggerated profile can break negotiation between the agent and merchant system.
11. Test the complete order lifecycle
A successful checkout is only the beginning. Test creation, payment, confirmation, shipment, delivery, cancellation, refund and return events, including retries and duplicate notifications. Compare status in the AI surface, merchant system and customer support view. Design idempotency so repeated requests do not create repeated charges or orders.
12. Prepare local-service information
The planned Angi and Thumbtack integrations show that connected actions extend beyond products. Local-service businesses should maintain service areas, categories, availability, price approach, credentials, response times and cancellation terms. Keep the website and trusted profiles consistent even when direct integration is unavailable.
13. Measure agentic commerce separately
Tag UCP requests and track cart transfers, checkout starts, completion, average order value, cancellation, refund, substitution and support contact. Compare contribution margin and customer quality with other channels. New analytics can be directional during early rollout, so avoid claiming precise incremental revenue without a valid baseline.
14. Run a controlled readiness sprint
Week one: audit eligibility, feeds and policies. Week two: map cart, checkout and order events. Week three: test inventory, payment and failure cases in a sandbox where access exists. Week four: train support, review analytics and decide whether to join, integrate, wait or improve foundations first.
15. Prepare for commerce without abandoning trust
Agentic interfaces may reduce steps, but customers still expect correct products, consent, secure payment, reliable delivery and easy support. Invest in the operational facts every channel needs. Businesses that make commerce data dependable will be better prepared for Search, Gemini and future agents without betting everything on one rollout.
Key takeaways
Put the framework into action
- Google expanded Connected Apps in Search and Gemini on 20 November 2026, beginning with selected U.S. grocery, finance and upcoming local-service integrations.
- UCP connects AI discovery with carts, checkout and order operations while the merchant remains responsible for the transaction and relationship.
- Most businesses should first verify eligibility and strengthen product data, fulfilment, policies, security and measurement.
Research sources
Sources & further reading
This article provides general business education, not legal, tax or financial advice. Adapt the framework to your market and consult qualified professionals where required.
