# AI Shopping Platforms: How to Get Selected Across Engines

> The same structured signals surface you across ChatGPT, Gemini, and Perplexity, but each engine weights them differently and reaches you over a different protocol rail, so ties break per-engine.

<!-- One catalog, many agents: the shared signals that surface you across ChatGPT, Gemini, and Perplexity, plus the per-engine tie-breakers. -->
<!-- Canonical: https://agentmint.net/platforms/ · By Abdalsalaam Halawa · Published 2026-07-07 · Last verified 2026-07-07 -->
<!-- Evidence tags below are load-bearing: <Claim type="spec-fact|reported|hypothesis"> marks how each factual claim is sourced. -->

<KeyTakeaways
  items={[
    "One catalog serves every agent: the same structured signals (grid position, price, rating, endorsement, and description text) drive selection across ChatGPT, Gemini, and Perplexity.",
    "The weights are provider-specific. The strongest public evidence, the academic ACES simulation, shows the same signal moving each model by a different amount.",
    "A different protocol rail reaches each engine: ACP powers ChatGPT's checkout, and Google's own developer documentation confirms UCP is the rail enabling agentic actions on Gemini and AI Mode.",
    "There is no universal 'top rank' to chase. Optimize the shared inputs first, then break ties engine by engine.",
    "Agent behavior is a moving target (a model update can reshuffle which products win), so every claim on this page is dated.",
  ]}
/>

## The shared signal set (one catalog, many agents)

You do not maintain a separate product catalog for each AI shopping engine, and you should not optimize for one as if the others do not exist. The [selection chapter](/how-ai-agents-choose-products/) of this handbook lays out the signals agents actually read (where a product sits in the results grid, its price, its star rating, whether it carries a platform endorsement, and how its description is written), and those same categories of signal recur across ChatGPT, Gemini, and Perplexity. That is what lets a single well-structured catalog compete everywhere at once, and it is the practical core of [agent selection](/glossary/#agent-selection): the inputs are shared even when the scoring is not.

The evidence that the *categories* are shared but the *weights* are not comes from one controlled study. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">In the ACES simulation (vision-language-model agents choosing from a mock storefront in randomized trials), every selection signal (price, rating, endorsement, and description text) carried a different weight on each model tested, so no single "winning" configuration held across Claude, GPT-4.1, and Gemini</Claim>. Read that as evidence of *how* engines diverge, not as conversion math for a live store: it is a simulation across a fixed model set, not a record of real purchases. This hub is the platform overview inside the broader [agentic commerce optimization](/agentic-commerce-optimization/) guide; the per-engine playbooks below carry the specifics.

## Where engines differ (the weights)

If the signals are shared, the divergence lives in how hard each engine leans on them, and that is where per-engine work earns its keep. The [selection chapter](/how-ai-agents-choose-products/) reports the full ACES breakdown model by model; the short version is that the gaps are large enough to matter. One clear example: platform endorsement is a lever on every model, but not equally. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">A platform endorsement such as an "Overall Pick" badge lifted a baseline 10% selection probability to 24.3% for a Claude agent, 19.9% for GPT-4.1, and 42.6% for Gemini, with Gemini rewarding endorsement most strongly</Claim>.

The takeaway is directional, not a dial you set: the same honest signal buys more selection lift on some engines than others, which is exactly why there is no universal "top rank" to aim for and why a per-engine [agent win rate](/glossary/#agent-win-rate) is the number to watch rather than a single blended one. Get the shared inputs right first (feed completeness, product schema, titles, crawler access), then use the playbooks to break ties on the engine that matters most to your catalog.

## Which rail reaches which engine

Signals decide *whether* an agent prefers you; a protocol rail decides *how* that agent reaches your catalog and completes a purchase. The two rails to know sit behind different engines, and both mappings are now confirmed. <Claim type="spec-fact" source="Agentic Commerce Protocol: OpenAI + Stripe (2025-09-29)" href="https://stripe.com/newsroom/news/stripe-openai-instant-checkout">The Agentic Commerce Protocol (ACP), announced by OpenAI and Stripe on 29 September 2025, powers ChatGPT's Instant Checkout</Claim>, so for ChatGPT, ACP is the confirmed rail.

Google's side is confirmed too. <Claim type="spec-fact" source="Universal Commerce Protocol: Google, NRF 2026 (2026-01-11)" href="https://blog.google/company-news/inside-google/message-ceo/nrf-2026-remarks">Google announced the Universal Commerce Protocol (UCP) at NRF 2026 on 11 January 2026 as an open standard for agents to complete discovery, checkout, and post-purchase without leaving the AI surface</Claim>, and <Claim type="spec-fact" source="Google: Universal Commerce Protocol developer guide" href="https://developers.google.com/merchant/ucp" date="2026-07-08">Google's own UCP developer guide states that adopting UCP enables agentic actions on AI Mode in Google Search and Gemini, starting with direct buying</Claim>, naming Gemini and AI Mode as UCP's consuming surface directly. The full protocol comparison (what each rail covers, and which one to implement) lives in [UCP vs ACP: which gets you selected](/ucp-vs-acp/).

## Per-engine playbooks

The shared inputs get you eligible; these four pages break the ties on each engine.

- **[ChatGPT Shopping Optimization](/chatgpt-shopping-optimization/)**. The product-data signals ChatGPT reads over the ACP rails, and why there is no "enroll" button to flip.
- **[Why you're not in ChatGPT Shopping](/store-not-in-chatgpt-shopping/)**. The diagnostic order when your products are missing: crawler blocks, feed gaps, title mismatches.
- **[Gemini & Google AI Mode shopping ranking](/gemini-shopping-ranking/)**. How AI Mode ranks through your Merchant Center feed and the UCP rail, where feed quality is the lever.
- **[Perplexity Shopping Optimization](/perplexity-shopping-optimization/)**. The signals and sources Perplexity leans on, and how it differs from the other two.

## Behavior changes on updates

Optimizing to a single engine is fragile because the engine itself moves. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">ACES documented that a model update can drastically reshuffle market shares, as it did between Gemini 2.5 Flash Preview and Gemini 2.5 Flash</Claim>. What an agent rewards this quarter it may weight differently after the next release, which is why AgentMint.net types and dates every model-behavior claim rather than presenting it as a fixed rule.

**Agent behavior changes with every model update. Last verified: 2026-07-07.** Treat the per-engine playbooks as snapshots, re-check them against your own measured [agent win rate](/glossary/#agent-win-rate) on a cadence, and weight the shared inputs (which are stable across updates) over any single engine's current quirks.