Several guides circulating online describe specific step-by-step methods for BigCommerce, including exact WebDAV upload paths and Stencil theme code. We could not verify these against BigCommerce's own developer documentation, and the pattern (oddly precise paths, invented-sounding adoption statistics) matches the same AI-generated SEO content flagged in our Adobe Commerce guide. This guide sticks to what is actually confirmed.
What is actually confirmed: an early, public endorsement
Per an official press release from Commerce (Nasdaq: CMRC), BigCommerce's parent company, the company announced its endorsement of UCP on January 11, 2026, the same day Google launched the protocol at NRF. The release describes UCP as a common language that lets agents and systems work together across the shopping journey and states Commerce's intent to offer buying directly across Google's AI surfaces.
BigCommerce's own blog reaffirmed this positioning later, framing its view directly: commerce "shouldn't be trapped inside channels or stitched together with one-off solutions," and describing UCP as the foundation for that open approach. This is a genuinely early and public commitment, on par with UCP's original launch partners rather than a later addition.
We could not find any BigCommerce documentation describing a native, merchant-facing UCP toggle in the control panel, the way Shopify has one. Multiple independent technical write-ups describe BigCommerce's approach as API and app-based rather than a first-party toggle, consistent with the forward-looking language in Commerce's own January announcement ("plans to offer," not "now offers"). If you check your BigCommerce store today and find no manifest, that is consistent with what has actually been confirmed publicly, not necessarily a misconfiguration on your end.
What this means in practice
For a merchant on BigCommerce wanting a working /.well-known/ucp manifest today, the practical path is building it yourself against BigCommerce's REST and GraphQL APIs, which are mature and well-documented, or through a third-party app from BigCommerce's App Marketplace built for this purpose. This is closer to the Adobe Commerce situation than the Shopify one: real platform-level commitment and solid underlying infrastructure to build on, but not yet a setting you can simply switch on.
BigCommerce does have a real, live AI-commerce feature today, just not a UCP one specifically. PayPal has named BigCommerce (through Commerce) as a Store Sync integration partner, live in BigCommerce's App Marketplace since April 2026, for US-based merchants already using PayPal. See our PayPal and Agentic Commerce guide for how that program actually works. It connects a merchant's catalog to AI shopping surfaces through PayPal's own infrastructure, independent of UCP.
Check what your store actually publishes
Whatever your BigCommerce setup, check directly whether it publishes a valid UCP manifest.
Frequently asked questions
BigCommerce's parent company, Commerce, publicly endorsed UCP on January 11, 2026, the same day Google launched it, earlier than most platforms. However, we could not find evidence of a native, merchant-facing UCP toggle having shipped since. A merchant wanting a live manifest today would need to build one against BigCommerce's APIs or use a third-party app.
We could not find one documented by BigCommerce itself. Independent technical sources describe BigCommerce's approach as API and app-based rather than a first-party control panel toggle, which is consistent with the forward-looking language in Commerce's original announcement.
No. PayPal's Store Sync integration with BigCommerce, live since April 2026, is a separate, protocol-agnostic AI-discoverability feature built on PayPal's own infrastructure. It does not publish a UCP manifest and is not a substitute for one if UCP compliance specifically is your goal.
Shopify has a native, self-serve toggle. Adobe Commerce has committed to UCP and shipped developer infrastructure, but no merchant-facing toggle. BigCommerce's parent made an even earlier public UCP endorsement than Adobe, on launch day itself, but similarly has no confirmed native toggle, leaving custom development as the practical path today.