What happened
The Channels V3 API — the plumbing BigCommerce uses to represent everywhere a store sells, from the main storefront to marketplaces — now accepts a batch of new platform values: openai, paypal, perplexity, reddit, and snapchat. Perplexity lands with both marketplace and marketing designations; Snapchat comes in as a marketing channel.
The existing amazon, pinterest, and tiktok channels were extended at the same time, so they now cover marketing use alongside what they already did.
The word that matters is channel. In BigCommerce's data model, a channel is not a referral source or an analytics label — it's a place you sell. Filing OpenAI and Perplexity under the same structure as Amazon is a statement about what BigCommerce thinks those assistants are about to become.
Why this matters
API enums ship before dashboards do. A platform doesn't add accepted values to a production API for decoration — this is groundwork, and the merchant-facing feature usually follows the plumbing. If BigCommerce wires assistants in as native channels, agentic selling arrives as a platform feature you toggle on, not a custom build you commission.
That changes the budgeting math right now. If your platform is building the assistant bridge natively, a bespoke agentic integration risks being throwaway work you pay for twice.
Honest caveat: an accepted platform value guarantees nothing about timing or final shape. There's no announcement, no marketplace app, no checkout flow to test. But marketplace-type slots are rarely reserved for services a platform doesn't intend to connect.
The bigger picture
When an AI channel does switch on, it won't browse your store the way a human does. It will read your catalog data — names, attributes, descriptions, structured data — and recommend what it can parse and trust. The merchandising layer becomes your data layer.
That work is doable today, channel or no channel. Stores that clean up their catalogs now will be sellable through an assistant on day one. Stores that wait will spend the channel's early life fixing data instead of selling.
What to do about it
Put the changelog on a weekly rotation
Assign someone — you, your developer, your agency — to skim the BigCommerce developer changelog at docs.bigcommerce.com weekly. The moment an OpenAI or Perplexity channel app appears, early movers get a clean-catalog head start before the crowd notices.
Get your catalog machine-clean now
Audit product names for clarity, fill in missing attributes, kill duplicate descriptions, and verify your Product schema is complete and accurate. Whatever an AI channel consumes, it will be some slice of this data — and it can't recommend what it can't parse.
Run your own AI visibility check
Ask ChatGPT and Perplexity the exact questions your buyers ask, and note which brands get recommended. That's your baseline for the pre-channel era. If competitors are cited and you're absent, the gap will follow you into any native channel.
Pause custom agentic-commerce builds
If you were about to fund a bespoke integration that exposes your catalog to AI assistants, hold. Re-scope after BigCommerce shows its hand — the native channel will likely cover the transport layer, and your money is better spent on the data feeding it.