Google UCP, Gemini and Shopify: preparing your e-commerce business for agentic commerce

Google UCP, Gemini and Shopify: preparing your e-commerce business for agentic commerce

Google is working to let shoppers buy certain products directly in Gemini or in AI Mode in Google Search, without visiting the retailer’s website to complete their order.

To support these purchases, Google co-developed an open standard with Shopify and other companies: the Universal Commerce Protocol, or UCP. It lets an AI assistant and a store exchange the information needed for a sale, including the chosen product, price, availability, delivery and payment.

Access depends on the merchant, products and market. A French retailer should not assume that an announcement means the channel is already available to its business.

The change is still worth preparing for: a customer could buy from you without visiting your website. Your company would remain responsible for delivery and returns, and would need to record the sale in both its accounts and its analytics.

What should you check in your store before opening this channel? That is what this article covers.

What to check before using UCP

Before starting an integration, distinguish what the UCP standard allows, what Google or Shopify supports and what your store can actually access. A documented capability is not necessarily available to your business.

Google’s January 11, 2026 announcement initially targeted eligible US retailers. The guide reviewed for this article requires approval before going live. It describes two journeys: completing the purchase within Google’s interface, or transferring the cart to the retailer’s website to finish the order.

Overview pages and detailed guides do not always describe the same rollout, particularly for Gemini mobile, carts and account linking. Confirm the capabilities approved for your store before committing to development. The selected sources do not establish automatic activation for every Shopify store, the specific October dates shared on social media or a victory for UCP over the ACP standard.

Shopify can simplify connectivity, not transfer responsibility

Shopify offers Agentic Storefronts to manage integrations with AI channels from the admin. Its announcement also describes an Agentic plan that opens Shopify Catalog to brands whose stores run on other platforms. Start by checking what your business can access: an announcement does not activate every feature.

On Shopify, check the channels in your admin, market terms, eligible products and participation settings. On WooCommerce, PrestaShop or a custom platform, first review product feeds, checkout and the data exchanged with your order systems. That will show what needs connecting before you consider a migration.

You remain the Merchant of Record, the seller responsible for the transaction. If delivery fails, the customer will turn to you, even if they bought in Gemini. You carry that responsibility without necessarily controlling offer rankings, product presentation or all browsing data on the third-party interface.

First workstream: product data that stays true down to the variant

Accepting the right order starts with identifying the right product. If the offered size is out of stock or its identifier points to a different variant, the purchase begins with an error. The catalog and checkout therefore need matching product references, prices and availability.

• Identifiers: map product, variant, SKU and the identifier received in checkout requests without ambiguity.
• Prices: account for currency, applicable promotions, taxes and the final total for the delivery destination.
• Inventory: synchronize the feed and recheck availability during the transaction. A recent feed is not a stock reservation.
• Useful information: explain materials, dimensions, compatibility, use cases and exclusions without relying on the agent to invent a sales answer.
• Exceptions: exclude unsupported products instead of forcing them through an unsuitable journey.

Google requires the product ID in Merchant Center to match the one expected by the checkout system, called the Checkout API. The merchant_item_id field can map the two when they differ. Another field, native_commerce(checkout_eligibility), indicates whether the product can be purchased through this journey. In the feed Google documents, a missing field or FALSE value disables eligibility; check your Shopify connector’s settings separately.

Matching identifiers will not make every product eligible. Google’s guide excludes categories such as certain subscriptions, personalized goods, pre-orders and special shipping from its checkout. List what you can sell by country and channel, even where the protocol allows broader possibilities.

Illustrative example, not a client case: a footwear store sells a model in several sizes. An AI presents the chosen size as available, but the last pair has just sold on the website. The system must reject the transaction cleanly or offer another permitted option. Creating an order first and cancelling it later only transfers the cost to customer service.

Second workstream: delivery and return promises that systems can execute

Once the product is chosen, the address can still prevent the sale. The system must check delivery coverage, calculate charges and provide delivery timing and return conditions. If the customer changes destination, the total and terms must be recalculated before confirmation.

Google leaves address validation and rejection of unsupported destinations to the merchant. Add return policies and support details to Merchant Center too. Customers should find the same conditions there that the warehouse and customer service will actually apply.

Illustrative example: a furniture order needs a delivery appointment and special fees. If the channel does not support that scenario, exclude those items or retain website completion where that handoff is supported. An agent must not promise free delivery that the business cannot provide.

After confirmation, check that inventory is adjusted, the payment reconciled and fulfilment triggered. Tracking must reach the customer, and a return must lead to the correct refund. Google’s guide describes creation, shipment and delivery updates, along with return, cancellation and refund adjustments. Those updates need connecting to your systems; the AI conversation does not run your entire support operation.

Third workstream: measuring a sale without the confirmation page

Many stores send purchase events to analytics from the browser when the thank-you page loads. If a customer completes checkout in an AI interface, that page may never open. The sale is confirmed in your store, yet it may remain invisible to browser-based measurement. Check what your integration already sends before concluding that conversions are being lost.

To find that sale, start with the orders recorded in your commerce system. Keep the order and checkout identifiers, observed channel, amounts and currency. Track status changes too: an authorized payment can still fail, and a confirmed order can later be cancelled or refunded. Your reports need to reflect those changes.

Matching those records to analytics requires four checks:

1. Define the event: specify exactly when a sale is recorded, using a rule consistent across commerce, finance and analytics.
2. Send only what is permitted: transmit supported events with required identifiers and parameters only when the legal basis, any required consent and platform rules allow it.
3. Deduplicate: use the same transaction identifier across browser and server paths and protect against repeated sends and retries. Each destination has its own mechanisms; matching event names alone does not solve duplication.
4. Reconcile corrections: record cancellations and refunds, including partial refunds, and reconcile net revenue against the commerce source and destination reports.

Automatic order notifications, or webhooks, may arrive late or more than once. Your system must recognize a notification it has already processed, log deliveries and retry failed sends. Compare reports with orders regularly: a retry must not add another sale, and a partial refund must not erase the whole order.

Google documents how to recognize UCP requests and transactions in exchanges between systems. That can identify an order’s channel without revealing everything that happened before purchase. Reconciling a Google/UCP sale does not guarantee complete marketing attribution. Recording a payment on the server cannot recover impressions, clicks or steps inside Gemini that you never received.

Check what GA4, Google Ads or Meta can receive and match through your integration. Keep an “unknown source” category when data is missing rather than inventing a session. Any transmission remains subject to the legal basis, required consent and platform rules: data needed for delivery does not, by itself, authorize remarketing.

Fourth workstream: make the channel profitable and reversible

Once orders and refunds are reconciled, you can assess what the channel earns. Deduct refunds, product costs, fees and customer service costs from sales, then check the remaining margin. Watch picking and inventory errors too: their cost can absorb the gain from new orders.

You still need to ask whether those customers would otherwise have bought on your website. A test or reasonable comparison helps distinguish additional sales from purchases shifted between channels. An order attributed to the channel does not, by itself, prove that the channel created the demand; a small sample also limits early conclusions about advertising returns.

Plan how to stop the pilot if orders cause problems. Assign responsibility for enabling products, changing rules, authorizing discounts and suspending the channel. Verify where requests come from and limit permissions: rephrasing a request must not let an assistant bypass a selling restriction.

How can a store start without rebuilding everything?

Establish channel access first, then choose a product family with familiar variants, reliable stock, standard shipping and clear returns. Complete an end-to-end order and test what can go wrong before expanding:

• Variant availability and price at checkout.
• Unsupported address, destination changes and recalculated totals.
• Failed payment, timeout and retry without a duplicate order.
• Shipment, partial delivery, cancellation and partial refund.
• Purchase event sent twice, replayed webhook and deduplicated measurement.
• No marketing consent and no usable acquisition source.
• Channel suspension without breaking the website checkout.

With the Say Digital Framework, we scope this first test, connect the necessary systems and check the order through delivery, any refund and reconciliation of the amounts. Expansion follows the results observed and the access approved for the channel.

If customers can find your products but orders remain difficult to handle, our e-commerce mini-case on SEO, operations and AI explores that connection between acquisition and fulfilment. If the problem starts earlier, an AI visibility audit grounded in Search Console helps examine how your offer is discovered, without assuming that it can be purchased inside Gemini.

Frequently asked questions

Does UCP automatically improve product rankings?

No. Google’s FAQ says that native integration does not influence offer ranking. It adds a direct purchase option for relevant offers. Visibility and transaction capability remain separate levers.

Can a French store immediately sell inside Gemini?

Check merchant, market, product and surface eligibility and obtain the required approval. The sources reviewed do not establish general availability in France. Product data and measurement preparation can begin before channel access.

Is moving to Shopify mandatory?

No. UCP is an open standard. Shopify offers integrations and infrastructure, but the decision depends on the existing commerce system and channels actually available. A complete migration should not precede evidence of a need.

Does server-side measurement guarantee full attribution?

No. It can help record and reconcile transactions when a journey does not load normal browser tags. Journey visibility, available identifiers, consent and each tool’s rules still limit attribution.

Prepare a buying channel, not just an AI presence

Your website continues to serve direct purchases, brand content and journeys that need more explanation. To add an AI channel, focus on what must work wherever the purchase happens: identify the product, confirm delivery, process the order and find the correct amounts in your reports.

SAY Digital helps prepare that first pilot: review the catalog and Merchant Center, clarify selling rules, connect orders to your systems and check measurement for missing or duplicate records. You can then expand, correct or stop based on orders actually delivered and the margin left.

Discuss your agentic commerce readiness with SAY Digital

Sources and verification scope

Primary sources reviewed on October 14, 2026. January announcements describe their scope at the time; technical guides were rechecked to separate documented capabilities, restrictions and approval requirements. Deployment information can change.

• UCP: open protocol overview and capabilities.
• Google: UCP on its AI surfaces and integration and approval guide.
• Google: Merchant Center, eligibility and product restrictions.
• Google: order lifecycle, adjustments and idempotency.
• Google: FAQ, responsibilities, ranking and privacy.
• Google: January 11, 2026 announcement.
• Shopify: UCP, Agentic Storefronts and Agentic plan.

Version française : Google UCP, Gemini et Shopify : préparer son e-commerce au commerce agentique