Google brings AI checkout to Canada Google brings AI checkout to Canada

Retailers keep the sale

Eligible sellers include lululemon, select Shopify merchants, Shoppers Drug Mart and Simons. Google Pay uses payment and shipping details saved in Wallet. The retailer remains the seller of record.

Two onboarding timetables

Consumer availability and merchant onboarding follow different schedules. Google’s Merchant Center documentation describes its integration hub as an early-access rollout for the United States. Canada and Australia are scheduled for early next year. The hub combines account setup, endpoint testing and a declaration that the merchant is ready to launch. It checks operations such as creating a checkout, changing shipping details and completing a transaction. Eligible product listings need a checkout-eligibility attribute to display the purchase button. The distinction matters for a Canadian shop evaluating the announcement: a shopper-facing launch does not make the self-service merchant interface available to every seller.

Checkout reaches the tax calculation

Google’s existing direct-integration guide offers two implementation paths. Native checkout completes a purchase on Google’s surfaces; the cart path transfers a shopping basket to the merchant’s website. Google approval is required before an integration goes live. The implementation contract includes Canadian tax breakdowns: individual federal and provincial amounts can appear beneath an aggregate tax line. Those components must add up to the parent total. When the shipping address changes, the merchant must recalculate taxes and shipping options. The merchant’s commerce backend therefore remains responsible for the destination-sensitive calculations that determine what the buyer actually pays.

The buyer submits the order

The native checkout design separates assembling a basket from submitting payment. A user and an optional agent can add items to a session. When checkout begins, control passes to Google’s interface. The buyer then supplies fulfillment and payment details and submits the order without the agent participating in that step. The completion API request has a ten-second latency target at the ninety-fifth percentile, measured over a rolling twenty-four-hour period. That target describes an integration requirement, not a measured result from this rollout.

Checkout is only part of the integration

After purchase, merchants must push order updates to Google so its order page reflects fulfillment. Required events cover order creation, shipment and delivery. Shipment updates include a tracking number and link, and the shipped state must precede delivered. The service rejects updates with timestamps older than the latest recorded update. Refunds, returns and cancellations use adjustment records, while packages are grouped by tracking link. Temporary server failures can be retried with exponential backoff; client errors require investigation and a modified request before retrying. Reusing an event’s idempotency key prevents duplicate processing during retries. These requirements connect the shopping interface to the merchant’s ongoing order operations.