Perplexity and Claude as shopping surfaces

Perplexity and Claude can help customers research a purchase, but their shopping and tool integrations differ. Check the actual merchant route, browsing behavior and permissions before building for either one.

Reviewed October 1, 2026 · 6 min read

Do not assume that every assistant has a Merchant Center-style feed program. Perplexity offers shopping experiences and a merchant program; Claude can reach business information through search, browsing and supported connections. The available transaction flow depends on the product and integration.

For merchants, the practical questions are straightforward: can the application find accurate information, can it use the next step and what requires the customer to take over? Answer those before choosing a catalog connector or tool integration.

This guide compares the documented routes and the checks worth making. For related platforms, see Google AI Mode visibility and ChatGPT business visibility.

Two surfaces, two entirely different shapes#

Treat these as routes to investigate, not universal guarantees. A payment partnership can support checkout without being the only way a product is discovered. A connector can expose live data without placing a merchant in every conversation.

Perplexity: check the merchant program and partners#

Perplexity has partnered with PayPal for supported shopping and payment experiences. That is one important integration route. The Perplexity merchant page also describes a merchant program, so it is inaccurate to say there is no direct route to investigate.

PayPal's agentic commerce services distinguish catalog distribution from payment enablement. If your platform offers them, confirm which part is available to your account:

• Catalog synchronization helps participating destinations receive product information. Check item acceptance, destination coverage and refresh behavior.
• Payment enablement supports eligible transactions. Confirm the merchant, region, methods and customer flow rather than assuming a synced catalog can accept payment everywhere.

Ask your commerce provider for the current supported connection. A named partnership is not proof that your store is enrolled, configured or live. Check the account status and a real product result.

Older guidance may describe Buy with Pro or a previous merchant process. Use the current program documentation and your provider's account controls to establish what is available now. Do not infer that an earlier program disappeared solely because a newer payment partnership launched.

Maintain stable product identifiers, accurate variants, prices, availability and policy links. The product feed guide covers the data work. Map it to each destination's schema instead of assuming one exported file works everywhere.

Claude: distinguish browsing from connected tools#

For Claude, start with the specific application your customers or staff use. Search, Claude in Chrome and an MCP connector have different capabilities and permission rules. A useful integration does not have to resemble a retail product carousel.

Three routes are worth distinguishing:

1. Search and page fetching: publish readable, current information and review the relevant crawler controls.
2. Browser assistance: make forms, product selections and handoffs understandable in the actual website interface.
3. Connected tools: expose supported live information or actions through a compatible integration, with clear permissions and validation.

If you want a public connector listing, review the current submission requirements separately from basic MCP compatibility. Authentication, documentation and review may be required. A custom supported connection and a public directory listing are different distribution choices.

Crawler rules and access controls do different jobs#

Provider policies differ for indexing crawlers and user-triggered fetchers. Check the current documentation for the exact user-agent you are addressing. A robots.txt directive requests behavior; it is not an authentication or network access barrier.

Choose search, training and user-triggered access policies deliberately. Do not assume a broad 'AI bot' switch matches your commercial goals, or that every request carrying a familiar user-agent belongs to that provider.

Use logs to investigate blocked requests and apply appropriate edge controls where needed. Verify callers using the mechanisms the provider supports. The crawler guide explains the distinction between publishing preferences and enforced access.

What to actually do#

1. Inspect actual crawler and browser errors before changing your access rules.
2. For Perplexity shopping, review its merchant program and any supported commerce-provider route available to your account.
3. Test the website journey, including variant selection, forms and the customer handoff before payment.
4. Keep visible facts and relevant structured data consistent.
5. Build an MCP connection only for a useful supported task. Existing APIs or booking pages may already serve the need.

The useful common ground is accurate information and a working next step. The integrations differ, so verify each with the application that will actually use it. Avoid treating a catalog export, crawler visit or connector listing as proof of a completed customer journey.