Loyalty benefits are becoming part of the information available to Google's AI shopping experiences. For retailers, that makes the relationship between membership terms, product data and search presentation worth closer attention. The immediate scope is the United States, rather than every market where Merchant Center supports loyalty programs.
What Google confirms
Google's Merchant Center documentation says loyalty benefits are eligible to appear in AI Mode and Gemini Apps in the US. The wider program includes Italy, with country-specific differences; Japan is covered through separate points-program guidance. Eligible benefits include member prices, shipping and redeemable points. Organic participation is open to non-advertisers.
The Merchant API guide separately documents Loyalty Customer Match for organic personalization without an active Google Ads account. Merchants can manage customer identifiers and tier associations. Processing depends on the user's consent to Google, and a successful HTTP response can conceal an unmatched or unconsented request. This API documentation does not establish that every personalization feature applies to AI Mode or Gemini.
Why this matters for shopping discovery
A shopper's assessment of an offer can depend on more than its headline price. A membership discount or delivery benefit may change which purchase makes sense for that person. Making those terms available earlier in the journey creates an opportunity to explain an offer's value before the shopper arrives at the retailer's website.
That is the commercial implication of the documentation, not evidence of a new ranking factor. Eligibility to show a benefit is different from guaranteed exposure, a higher position or improved conversion. Search teams should avoid turning a data-submission capability into a promise about algorithmic preference.
Coordinate catalog, CRM and loyalty operations
A useful first step is to compare the loyalty program's customer-facing terms with the values maintained by catalog and CRM teams. Check which tier receives each benefit, when membership expires and what happens when someone changes status. A discount described differently at discovery and checkout creates a poor experience even when the product itself is accurately listed.
For API implementations, build an explicit mapping between internal membership tiers and the Merchant Center configuration. Google's guide ties API tier values to the order configured in Merchant Center. Teams should test that mapping after configuration changes and keep responsibility for membership updates clear.
Do not treat every accepted API request as proof that a particular customer can receive a personalized presentation. The documented response behavior means transport success and customer matching are different questions. Operational monitoring should distinguish rejected requests from accepted processing, while respecting the service's privacy boundaries.
What Italian retailers should do
Italian merchants can review the broader loyalty setup supported in their market and prepare consistent benefit data. They should separately verify eligibility for each target surface before designing an AI-shopping campaign. The US-only statement is a geographic limit that matters for forecasts and internal presentations.
For SEO and AI Search teams, the practical recommendation is to include loyalty data in commerce audits alongside product accuracy and availability. Measure observed presentation, referral traffic and purchase outcomes separately. Where membership benefits appear, investigate whether visitors understand the conditions and can redeem them successfully. The opportunity is a clearer offer throughout the shopping journey; any visibility or revenue lift remains something to demonstrate with evidence.