Perplexity Merchant Program: What It Actually Gets You

What the Perplexity Merchant Program actually is

It is a free data-sharing program. You give Perplexity structured, live product data; Perplexity uses it to build the product cards that appear inside shopping answers. That is the whole mechanism.

Perplexity launched it on 18 November 2024, the same day as Buy with Pro (in-app checkout) and Snap to Shop (photo-based product search). In Perplexity's own Merchant Program announcement, the stated benefits are four, and they are worth reading literally:

• Higher chance of being a recommended product — because your items are in the index with richer detail, not because enrollment buys ranking.
• Payment integrations — eligibility for the one-click checkout flow rather than a plain click-out to your site.
• Free API access — you can build Perplexity-powered search on your own site, scoped to your own catalog.
• A trends dashboard — search and shopping demand signals around your products.

Four things it is not, each of which gets misrepresented in roundup posts:

• Not an ad product. Perplexity states the program is distinct from and unrelated to its sponsored-questions advertising, and that product cards are unsponsored. There is no bid, no budget, no placement to buy.
• Not a marketplace. You stay the seller and keep the customer relationship. Perplexity is a discovery surface, not a channel that resells your inventory.
• Not a ranking lever. Enrollment makes your data legible. Whether a model picks your SKU over a competitor's still comes down to price, reviews, specs and how your product page reads.
• Not a documented platform. There is no public feed spec, no published approval SLA, no status page. That matters for planning, and section four covers what to build against instead.

Who can join, and what enrollment really looks like

Perplexity's own wording invites "large retailers" to apply, and the entry point is a short form linked from the announcement above — business name, vertical, site URL, contact. It asks nothing about revenue, and it is not a dashboard you log into afterwards. You submit, and Perplexity comes back to you.

Two consequences that catch small and mid-size merchants out:

• Applying is not onboarding. Feed format and delivery details arrive after acceptance, not before. You cannot pre-build to a published spec the way you can with Google.
• Enrollment is not the only route in. Perplexity's shopping discovery is also powered by platform integrations including Shopify, covering Shopify-powered businesses that sell and ship to the US. If you are on Shopify and ship to the US, some of your catalog may already be visible without any application.

If you are not a US merchant

The shopping experience launched US-first and the checkout side is built around US buyers. For a merchant in the EU, the UK or the UAE, the practical question is not "can I fill in the form" — it is do I ship to the US, priced in USD, with US shipping and returns stated on the page. If the answer is no, enrollment changes very little, and your effort is better spent on the open-web path in section five.

What it costs, and where the money actually moves

Perplexity states the program is free for merchants. There is no listing fee and no placement fee described anywhere in its own materials.

The checkout side changed materially a year after launch. In November 2025 Perplexity opened the checkout experience — previously limited to Pro subscribers — to US users generally, and brought in PayPal as the checkout partner, with PayPal's buyer protection extended to purchases completed inside Perplexity. A PayPal-backed Instant Buy flow followed. The brand stays the merchant of record and keeps the customer relationship.

So "free" is accurate about platform fees and misleading about total cost. The real cost is feed operations: someone has to keep price, stock and shipping correct across the feed, the product page, the structured data and the checkout, forever. That is the line item to budget, and it is the same line item that Google Merchant Center, Meta catalogs and every agentic checkout protocol will each bill you in engineering time.

One more thing worth naming plainly: several agency and SaaS posts quote precise uplift figures — "40–60% more product card appearances within 30 days" and similar. Those numbers come from companies selling feed management, with no published methodology, no sample size and no control. Perplexity publishes no impression or recommendation-share metric at all. Treat any such figure as marketing until someone shows the data.

The feed: build to Google's spec, because Perplexity publishes none

Perplexity has never published a product feed specification. The practical answer, and what feed vendors have quietly standardised on, is that the catalog you already serve to Google Merchant Center is the catalog that travels. Build that one correctly and the Perplexity question largely answers itself.

These are the attributes from Google's product data specification that decide whether any machine reader can use your item at all:

Two gotchas with dates on them

• Image size. Google has announced a minimum of 500 × 500 pixels for all product images, with enforcement beginning 31 January 2027. Legacy catalogs are full of 300px thumbnails that pass today and will not pass then. Audit this now, not in December 2026.
• Price parity. The spec requires the submitted price to match the landing page, the structured data and the checkout. A feed at $49 against a page at $59 is not a cosmetic mismatch; it is the condition every shopping surface checks first, and the one an AI answer engine has the strongest reason to penalise, because quoting a wrong price in an answer is its worst failure mode.

Do not build and maintain a Perplexity-specific feed. Two feeds from one catalog drift apart within a quarter, and the drift is invisible until a card quotes a stale price. One canonical feed, many destinations — that is the whole discipline of product feed management across Google, Meta and AI shopping channels.

Getting into Perplexity without the Merchant Program

Product candidates reach Perplexity's shopping answers from two directions: the catalogs it ingests, and the open web it crawls. The second path is open to everyone today, needs no application, and is where a non-US or non-enrolled merchant should spend first.

What that path rewards, in rough order of leverage:

1. Complete Product and Offer structured data on every product page — price, currency, availability, SKU, brand, GTIN. The same values as the feed, which is the point.
2. Specifications as text, not as an image. Dimensions, materials, compatibility and power ratings baked into a spec sheet JPEG are invisible. A parser reads a table; it does not read your graphic.
3. Real review data marked up honestly. aggregateRating that reflects reviews actually shown on the page.
4. Crawler access. Check that your robots.txt is not blocking the AI crawlers you want reading you, and that it is not blocking your image paths.
5. Third-party corroboration. Answer engines assemble from many sources. If every independent roundup in your category omits you, a clean feed will not fix that on its own.

The visible difference between the two paths is at the end of the card: enrolled merchants can carry the in-app checkout affordance, while everyone else gets a click-out link to the product page. For many merchants the click-out is fine — it is the discovery that was missing, not the checkout.

Perplexity Merchant Program vs Google Merchant Center

They look alike and behave differently. The table below is the comparison that decides how much effort each deserves.

Read it this way: Google is a system you can debug, and Perplexity is a system you can only feed well. OpenAI's Instant Checkout, built on the Agentic Commerce Protocol, is a third shape again — a checkout standard rather than a catalog program. The common denominator across all three is the same clean, identifier-complete, parity-correct catalog. Build that once; the channel-specific work after it is small.

Worth holding in view while you plan: the rules of agentic shopping are still being litigated. Amazon sued Perplexity in late 2025 over its Comet browser shopping autonomously on Amazon.com, and the dispute ran on through 2026. What an AI agent may do on someone else's storefront is unsettled. What you publish on your own storefront is not — which is a good argument for investing in the data you control.

The order to do this in, and how to tell if it worked

Sequence matters, because applying before the catalog is clean just means your first impression is a feed full of mismatches.

1. Fix parity first. Price, sale price and availability identical across feed, product page, structured data and checkout. Nothing else matters until this is true.
2. Fill the identifiers. Correct GTINs where they exist, MPN plus brand where they do not, item_group_id on every variant family. Never guess a GTIN.
3. Rewrite thin descriptions for the top SKUs by margin, not by traffic. These are what a model paraphrases when it recommends you.
4. Audit image dimensions against the 500 × 500 minimum ahead of the 2027 enforcement date.
5. Ship Product and Offer schema on every product page, matching the feed exactly.
6. Confirm the US path — shipping, duties, returns, USD pricing — if you are outside the US.
7. Then apply, and connect the feed when onboarding details arrive.

Measuring it honestly

There is no impression-share report, so measurement is indirect and partly manual:

• Referral traffic from perplexity.ai in your analytics, segmented and tracked against its own conversion rate rather than lumped into "other".
• Prompt checks. Ask twenty category-level buying questions a real customer would ask, record which SKUs and which merchants appear, and repeat monthly. Tedious, and still the most reliable signal available.
• Assisted conversions. Discovery on an answer engine frequently converts later through brand search. Watch branded search volume, not just last-click.

If the prompt checks keep surfacing competitors and you cannot tell whether the cause is your feed, your product pages or your lack of third-party coverage, that diagnosis is exactly what our $20 Audit + Roadmap is for — a prioritised list of what to fix, in order, delivered in 24–48 hours.