Shopify vs BigCommerce

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to BigCommerce
   Shopify~partialprobed6/10

   Shopify has no llms.txt (confirmed 404 via probe), but it does publish agent-oriented docs in markdown form (agents.md, ai-toolkit.md, storefront-mcp.md, order-mcp.md) explicitly designed for AI agents/coding tools to consume, plus an AI Toolkit that connects agents to docs and schemas. missing for 10: a working llms.txt endpoint, and independent confirmation that agents can successfully parse/use these .md docs end-to-end.

   • [probe] “PROBE llms.txt: HTTP 404 at https://shopify.dev/llms.txt”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “The toolkit connects your agent to: Developer docs and API schemas... Code validation: validate GraphQL queries, Liquid templates, and Shopi…”
   • [claimed-docs] “Shopify AI Toolkit gives your AI coding tool a Shopify-aware starting point.”
   • [claimed-docs] “Shopify AI Toolkit connects your AI coding tools to Shopify's developer docs, API schemas, and CLI store management so they can help you bui…”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”

   proof ↗⚑ flag

   BigCommerce✓fullprobed8/10

   A direct probe confirms developer.bigcommerce.com/llms.txt returns HTTP 200 with structured content including an explicit 'Instructions for AI Agent' section, directly satisfying the story's requirement of agent-discoverable docs. Missing for 10: no independent/community confirmation of agents actually using it, and no broader agent-oriented doc ecosystem (e.g., MCP server, structured API docs for agents) beyond the single llms.txt file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to BigCommerce
   Shopify~partialprobed5/10

   Shopify CLI (shopify-docs-3,17,30,42) and GraphQL Admin/Storefront APIs (shopify-docs-18,31,32) provide command-line and programmatic access that could be scripted, and webhooks (shopify-docs-4,21,43) support event-driven automation, but there is no explicit documentation of running the CLI non-interactively or in a CI pipeline, no CI/CD guide, and no headless-mode flag mentioned. Missing for 10: explicit CI/CD documentation, non-interactive/headless CLI mode, automation pipeline examples.

   • [claimed-docs] “Initialize new apps, themes, and headless storefronts in an instant with the latest Shopify CLI.”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”
   • [claimed-docs] “A single command installs all the dependencies you need, including the CLI itself, so you can dive straight into development.”
   • [claimed-docs] “Run the second command to create a new app. Your app will be added as a new subdirectory.”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [probe] “official CLI documented at https://shopify.dev/docs/api/shopify-cli”

   proof ↗⚑ flag

   BigCommerce~partialcommunity6/10

   BigCommerce exposes REST/GraphQL APIs with OAuth-based API accounts and sandbox environments explicitly meant for scripted, non-UI automation of store management and headless storefronts, which supports CI-style programmatic use. However there's no dedicated CLI or CI/CD-native tooling, and a community report describes unreliable API connectivity/throttling that undermines confidence in dependable automation. Missing for 10: an official CLI, documented CI/CD pipeline integration, and confirmation the throttling issue is resolved.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “Sign up for a free BigCommerce trial store to test API calls and build integrations without affecting live data.”
   • [claimed-docs] “Navigate to **Settings > API Accounts** in your store control panel. Create credentials with the scopes you need.”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Shopify—none0/10

   All Shopify MCP evidence describes Shopify acting as an MCP *server* provider (Catalog, Cart, Checkout, Order MCP servers) for external AI agents to consume — the opposite direction of this story, which asks whether Shopify itself can plug in external MCP servers to gain new tools. No evidence shows Shopify's admin, Sidekick, or any Shopify-side agent acting as an MCP client that connects to third-party MCP servers. Missing for 10: any documentation of Shopify (or its AI features) consuming/plugging-in external MCP servers as a client.

   • [claimed-docs] “Connect any AI assistant to real-time commerce data from Shopify stores with Model Context Protocol (MCP) servers.”
   • [claimed-docs] “Use the Order MCP server to fetch the current state of an order placed through your agent, including line items, fulfillment events, and pos…”
   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “enables AI agents to build and iterate on a cart before the buyer commits to purchase”
   • [claimed-docs] “enables AI agents to create and manage checkout sessions, convert carts into checkouts, and refer buyers to the merchant storefront to compl…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”

   proof ↗⚑ flag

   BigCommerce—none0/10

   BigCommerce is an e-commerce SaaS platform; the evidence shows REST/GraphQL APIs, webhooks, apps marketplace, and llms.txt for AI agents reading docs, but no mention of an MCP client/host feature allowing users to plug MCP servers into BigCommerce so it can use their tools.

   ⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Shopify
   Shopify✓fullprobed8/10

   Shopify publishes multiple official MCP servers (Storefront MCP, Cart MCP, Checkout MCP, Order MCP, Catalog MCP) explicitly for connecting AI agents to real-time commerce data, with dedicated docs pages for each and a UCP framework for agentic commerce. Missing for 10: independent/hands-on verification that these MCP servers work as documented and details on setup/auth flow for external agent clients.

   • [claimed-docs] “Connect any AI assistant to real-time commerce data from Shopify stores with Model Context Protocol (MCP) servers.”
   • [claimed-docs] “Use the Order MCP server to fetch the current state of an order placed through your agent, including line items, fulfillment events, and pos…”
   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “enables AI agents to build and iterate on a cart before the buyer commits to purchase”
   • [claimed-docs] “enables AI agents to create and manage checkout sessions, convert carts into checkouts, and refer buyers to the merchant storefront to compl…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”

   proof ↗⚑ flag

   BigCommerce—none0/10

   BigCommerce is an ecommerce platform (not an agent), so the MCP-server axis applies, but no evidence shows an official MCP server; docs mention REST/GraphQL APIs, webhooks, and an llms.txt file for AI agent guidance, none of which constitute an MCP server implementation. Missing for 10: any mention of an MCP server, MCP endpoint, or MCP-compatible integration.

   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Shopify
   Shopify✓fullprobed9/10

   Shopify CLI is well documented as an official command-line tool for generating and managing apps, themes, and headless storefronts, with clear commands (init, dev, deploy) and dev-store integration; it's also positioned as AI-aware via the AI Toolkit that connects AI coding tools to CLI store management. missing for 10: independent/hands-on third-party review specifically validating CLI usability for AI-native workflows.

   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”
   • [claimed-docs] “Initialize new apps, themes, and headless storefronts in an instant with the latest Shopify CLI.”
   • [claimed-docs] “A single command installs all the dependencies you need, including the CLI itself, so you can dive straight into development.”
   • [claimed-docs] “Run the second command to create a new app. Your app will be added as a new subdirectory.”
   • [claimed-docs] “Shopify AI Toolkit connects your AI coding tools to Shopify's developer docs, API schemas, and CLI store management so they can help you bui…”
   • [claimed-docs] “Dev stores are testing environments that you own and control. They let you build and test your apps in a realistic Shopify environment witho…”
   • [probe] “official CLI documented at https://shopify.dev/docs/api/shopify-cli”

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence covers REST/GraphQL APIs, SDKs, API clients, and an llms.txt AI-agent instructions file, but there is no mention of an official BigCommerce CLI tool anywhere in the pack. missing for 10: an official CLI product/tool, its documentation, install instructions, and any command reference.

   ⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to BigCommerce
   Shopify✓fullprobed8/10

   Shopify ships extensive, well-documented public APIs (Admin GraphQL API, Storefront API, webhooks, scoped OAuth tokens, quarterly-versioned releases, GraphiQL explorer, CLI) that let any external system—including AI agents via UCP/MCP servers—drive the platform programmatically. Community threads confirm the API is usable in practice, though several complain about documentation quality and API design limitations (e.g., no refund endpoint, restrictive access scopes). Missing for 10: a standardized machine-readable OpenAPI/spec file (probe found 404s for openapi.json/llms.txt) and stronger independent hands-on corroboration of ease-of-use to offset the documented developer complaints.

   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “Your code obtains an access token scoped to the permissions it needs.”
   • [claimed-docs] “its access scopes determine what it can access”
   • [claimed-docs] “Shopify releases new API versions on a predictable quarterly schedule, giving you time to adopt changes before older versions are retired. S…”
   • [claimed-docs] “GraphiQL is an in-browser tool for writing, validating, and testing GraphQL queries. When working with Shopify's GraphQL Admin API, GraphiQL…”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”
   • [community] “Shopify is really terrible when it comes to partner support. The documentation is terrible and if you want to use their API, be prepared to …”
   • [community] “App Charges get added to clients bills, you're not getting paid right away (60+ days in some cases) vs getting paid instantly. If someone do…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://shopify.dev/openapi.json, https://shopify.dev/swagger.json, https://shopify.dev/api/openapi.…”

   proof ↗⚑ flag

   BigCommerce✓fullprobed9/10

   BigCommerce ships extensive first-party documentation for REST and GraphQL APIs, OAuth-based API accounts (store/app/account-level), webhooks, sandboxes, an in-browser Request Runner, and API client SDKs, explicitly positioned for programmatic/automated store management and headless integration. It even exposes an llms.txt with AI-agent-specific instructions, signaling deliberate AI-native accessibility. Missing for 10: independent/third-party corroboration of large-scale programmatic API reliability (one dated community comment mentions throttling/connection issues, but it's secondhand and not a definitive contradiction of documented capability).

   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”
   • [claimed-docs] “You can experiment with our REST Management APIs using the **Request Runner**, which is built in to the [API Reference]”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [claimed-docs] “GraphQL Storefront API overview”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to BigCommerce
   Shopify~partialclaimed5/10

   Shopify's general API auth model documents scoped access tokens ("access token scoped to the permissions it needs", "its access scopes determine what it can access") which would apply to any custom app/agent integration, and the agent-specific docs (UCP/MCP) reference authenticating agents, but there's no explicit documentation of an agent-specific credential-issuance flow or least-privilege scope management tailored to AI agents. Missing for 10: agent-specific scoped-credential issuance workflow, examples of narrowing scopes for autonomous agents, independent/hands-on confirmation of this working in agentic contexts.

   • [claimed-docs] “Your code obtains an access token scoped to the permissions it needs.”
   • [claimed-docs] “its access scopes determine what it can access”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”

   proof ↗⚑ flag

   BigCommerce~partialclaimed6/10

   BigCommerce docs describe OAuth-based API accounts with configurable scopes (store-level, app-level, account-level) created via Settings > API Accounts, which supports issuing least-privilege credentials, but nothing ties this explicitly to AI-agent use cases or agent-specific scoping/rotation controls. missing for 10: agent-specific credential guidance, fine-grained per-agent scope templates, independent/hands-on verification of scope enforcement.

   • [claimed-docs] “Navigate to **Settings > API Accounts** in your store control panel. Create credentials with the scopes you need.”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Shopify
   Shopify✓fullcommunity8/10

   Shopify documents official SDKs/APIs (Admin GraphQL API, Storefront API, CLI, Hydrogen) plus AI-specific tooling like the AI Toolkit and UCP/MCP servers explicitly designed for AI agents and coding tools to build against (shopify-docs-18, shopify-docs-31, shopify-docs-32, shopify-docs-39, shopify-docs-53, shopify-docs-6, shopify-docs-34). Community commentary raises complaints about API design and documentation quality (shopify-comm-8, shopify-comm-12), but doesn't concretely contradict the existence or functioning of the official SDKs. missing for 10: independent hands-on validation of SDK reliability/quality, and a clearer enumerated list of officially supported language SDKs beyond generic claims.

   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [claimed-docs] “Shopify AI Toolkit gives your AI coding tool a Shopify-aware starting point.”
   • [claimed-docs] “Shopify AI Toolkit connects your AI coding tools to Shopify's developer docs, API schemas, and CLI store management so they can help you bui…”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”
   • [community] “Shopify is really terrible when it comes to partner support. The documentation is terrible and if you want to use their API, be prepared to …”
   • [community] “Shopify is a terrible experience overall, and I wouldn't recommend it for anyone looking to start a quick ecom business online... certain ty…”

   proof ↗⚑ flag

   BigCommerce✓fullcommunity7/10

   BigCommerce documents official SDKs/tools (Checkout SDK, API Clients library, design system SDK) plus REST/GraphQL APIs, sandboxes, and API account setup, giving AI-native builders a well-documented path to build against first-party SDKs. Community reports of API throttling/incomplete ecosystem introduce some quality caveats but don't contradict SDK existence. Missing for 10: independent hands-on corroboration of SDK reliability/quality and AI-specific SDK usage examples.

   • [claimed-docs] “Accelerate your app development. Get started making API requests in the language of your choice with our API Clients.”
   • [claimed-docs] “Checkout SDK | SDK | [checkout-sdk-js]”
   • [claimed-docs] “Our open source design system. Use to build BigCommerce Apps that feel native inside the control panel.”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Shopify
   Shopify✓fullclaimed8/10

   Shopify documents webhook subscriptions explicitly, letting apps/agents subscribe to Shopify webhook topics for near-real-time event data, and explains their use for syncing and triggering actions. This is well documented first-party but lacks independent hands-on corroboration or AI-specific webhook integration examples. Missing for 10: independent/hands-on verification, explicit AI-agent-specific webhook consumption examples.

   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”

   proof ↗⚑ flag

   BigCommerce✓fullclaimed7/10

   BigCommerce has dedicated Webhooks documentation covering event subscription, including cloud pub/sub webhook delivery, confirming first-party webhook support for external event notification. Missing for 10: independent hands-on confirmation of webhook reliability, full event catalog details, and AI-specific framing of webhook consumption.

   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Google Cloud Platform Pub/Sub Webhooks”
   • [claimed-docs] “Overview | BigCommerce Docs”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Shopify—none0/10

   The evidence pack covers agentic commerce (AI agents shopping via UCP/MCP), a developer-facing AI Toolkit for code validation, and AI-assisted theme design, but contains no documentation of Shopify surfacing AI-generated insights or suggestions from a merchant's own store data (e.g., sales/inventory analytics, customer behavior suggestions) inside the admin or product itself.

   ⚑ flag

   BigCommerce—none0/10

   Evidence only shows AI-powered search/chat on the developer documentation portal (bigcommerce-docs-16, bigcommerce-docs-27), not AI-generated insights or suggestions derived from a merchant's actual store/sales data. No mention of AI analytics, product recommendations, or in-product insight generation from BigCommerce's own data.

   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog, and richer feedback tools.”
   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Shopify
   Shopify~partialclaimed5/10

   Shopify documents building blocks for autonomous behavior — webhooks that trigger actions on events, and MCP/UCP-based AI agent APIs (cart, checkout, order, catalog) that let agents act on a buyer's behalf without a human in the loop — but there is no evidence of a merchant-facing, no-code 'set up an automation that runs in the background' feature (e.g., a Flow-like rules engine) in the pack; the described capability is developer-oriented infrastructure for building agents/apps, not a turnkey automation-setup experience for an AI-native end user. missing for 10: a documented built-in automation/rules engine for non-developers, evidence of scheduling/persistent background execution, and independent confirmation these agent APIs run unattended long-term.

   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”
   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “enables AI agents to build and iterate on a cart before the buyer commits to purchase”
   • [claimed-docs] “enables AI agents to create and manage checkout sessions, convert carts into checkouts, and refer buyers to the merchant storefront to compl…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence shows BigCommerce offers webhooks and REST/GraphQL APIs for building integrations, but nothing describes a way for an AI-native user to configure autonomous background automations (e.g., scheduled agents, workflow triggers, or persistent background jobs) within the platform itself. Webhooks are reactive event hooks requiring external infrastructure to act on them, not a built-in autonomous automation feature.

   • [claimed-docs] “Webhooks”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Google Cloud Platform Pub/Sub Webhooks”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Shopify—none0/10

   The evidence pack mentions AI tangentially (e.g., 'Design fast with AI' theme design copy) and extensively covers AI *agents connecting to* Shopify via MCP/UCP for external agents, plus an AI coding toolkit for developers—but there is no evidence of a built-in AI assistant inside Shopify's own product (like an admin chat agent) that a merchant/user can delegate tasks to.

   ⚑ flag

   BigCommerce—none0/10

   Evidence only shows AI-powered search/chat on the developer docs site and an llms.txt file for AI agents crawling documentation, not a built-in AI assistant inside the BigCommerce product to which a user can delegate store-management tasks. No mention of an in-product agentic assistant capable of taking actions on behalf of the user.

   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog, and richer feedback tools.”
   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Shopify
   Shopify~partialprobed6/10

   Shopify documents an agentic/AI layer (UCP, Catalog/Cart/Checkout/Order MCP servers) that lets AI agents search products, build carts, and checkout on behalf of buyers using natural-language driven agent interactions, and an AI Toolkit that lets AI coding tools query docs/schemas. This supports natural-language-driven operation of commerce flows by AI agents, but there's no evidence of a natural-language interface for merchants to operate the admin/store itself (e.g., 'create a discount via chat'), and no independent/hands-on corroboration of these agentic flows working end-to-end. Missing for 10: evidence of NL-driven merchant/admin operation, independent verification of MCP/UCP agent flows in practice.

   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the Universal Commerce Protocol (UCP)”
   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “enables AI agents to build and iterate on a cart before the buyer commits to purchase”
   • [claimed-docs] “enables AI agents to create and manage checkout sessions, convert carts into checkouts, and refer buyers to the merchant storefront to compl…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”
   • [claimed-docs] “Connect any AI assistant to real-time commerce data from Shopify stores with Model Context Protocol (MCP) servers.”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”

   proof ↗⚑ flag

   BigCommerce~partialprobed2/10

   Docs mention 'AI-powered search and chat' and 'AI-ready page actions' on the developer portal, and an llms.txt file exists with instructions for AI agents, suggesting some agentic/NL tooling around the developer docs, but there is no evidence that a user can actually operate the storefront/store management (products, orders, settings) via natural-language commands. Missing for 10: concrete NL command interface for store operations, evidence of chat-driven catalog/order management, independent hands-on confirmation.

   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog, and richer feedback tools.”
   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to BigCommerce
   Shopify✓fullclaimed7/10

   Shopify docs describe GraphiQL, an in-browser tool for writing, validating, and executing real GraphQL queries/mutations against the Admin API, which is exactly an interactive API reference with runnable examples. Missing for 10: independent/hands-on confirmation and evidence of similar interactive runnable exploration for other APIs (Storefront, REST) beyond Admin GraphQL.

   • [claimed-docs] “GraphiQL is an in-browser tool for writing, validating, and testing GraphQL queries. When working with Shopify's GraphQL Admin API, GraphiQL…”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”

   proof ↗⚑ flag

   BigCommerce✓fullclaimed8/10

   BigCommerce's developer docs explicitly describe an interactive API Reference with an embedded 'Request Runner' letting developers experiment with REST/GraphQL calls directly in the browser, plus AI-powered search/chat and AI-ready page actions layered on the docs site. This matches the story of an interactive, runnable API reference well. Missing for 10: independent/hands-on user corroboration of the Request Runner experience and no explicit mention of GraphQL runnable examples alongside REST.

   • [claimed-docs] “You can experiment with our REST Management APIs using the **Request Runner**, which is built in to the [API Reference]”
   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog, and richer feedback tools.”
   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Shopify—none0/10

   Shopify's APIs (Admin, Storefront) are GraphQL-based, and while docs describe schemas, versioning, and a GraphiQL explorer, there is no evidence of a downloadable OpenAPI/Swagger spec — a direct probe of common spec endpoints (openapi.json, swagger.json, etc.) returned 404 across all candidates. No vendor claim exists for an OpenAPI-equivalent machine-readable spec download, so this is an unmet capability rather than a disputed claim.

   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [claimed-docs] “GraphiQL is an in-browser tool for writing, validating, and testing GraphQL queries. When working with Shopify's GraphQL Admin API, GraphiQL…”

   proof ↗⚑ flag

   BigCommerce—none0/10

   No evidence pack item mentions an OpenAPI (or equivalent machine-readable) spec file being available for download; references only cover REST/GraphQL usage, API Reference and Request Runner tools, not a downloadable spec artifact.

   ⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Shopify✓fullclaimed8/10

   Shopify docs explicitly describe dev stores as owned testing environments that let developers build and test apps/integrations 'in a realistic Shopify environment without affecting any live store,' directly connectable via `shopify app dev` from the CLI, plus GraphiQL for safely exercising queries/mutations. This directly satisfies the sandbox-without-touching-production story for AI-native/agentic development workflows. Missing for 10: no explicit mention of a dedicated sandbox for the newer agent/UCP/MCP flows specifically, and no independent hands-on confirmation of dev-store isolation.

   • [claimed-docs] “Dev stores are testing environments that you own and control. They let you build and test your apps in a realistic Shopify environment witho…”
   • [claimed-docs] “GraphiQL is an in-browser tool for writing, validating, and testing GraphQL queries. When working with Shopify's GraphQL Admin API, GraphiQL…”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”

   proof ↗⚑ flag

   BigCommerce✓fullclaimed8/10

   BigCommerce's developer docs explicitly describe creating a sandbox store ('Partner Use Sandbox') and a free trial store to 'test API calls and build integrations without affecting live data,' plus an in-browser Request Runner for experimenting with REST calls safely. This directly satisfies the story of testing without touching production data. Missing for 10: independent/hands-on community confirmation that the sandbox behaves identically to production and any AI-agent-specific sandbox tooling.

   • [claimed-docs] “Sign up for a free BigCommerce trial store to test API calls and build integrations without affecting live data.”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [claimed-docs] “You can experiment with our REST Management APIs using the **Request Runner**, which is built in to the [API Reference]”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Shopify
   Shopify✓fullclaimed7/10

   Shopify documents a quarterly versioned API release schedule with advance notice before retirement and a subscribable changelog, directly matching the story's requirement for versioned APIs with a documented deprecation policy. Missing for 10: independent/hands-on corroboration that deprecation timelines are reliably honored, and a standalone deprecation-policy doc beyond the versioning page.

   • [claimed-docs] “Shopify releases new API versions on a predictable quarterly schedule, giving you time to adopt changes before older versions are retired. S…”

   proof ↗⚑ flag

   BigCommerce—none0/10

   The evidence pack documents BigCommerce's REST/GraphQL APIs, sandboxes, and API account scopes, but nowhere mentions API versioning schemes or a documented deprecation/sunset policy for endpoints. missing for 10: explicit API version numbering scheme, deprecation notice process, sunset timelines, changelog of breaking changes.

   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”

   proof ↗⚑ flag

Agent discovery

1. ai-native userMy products are discoverable by AI agents and answer engines through a cross-merchant catalog or feed built for agents

   weight 2 · round to Shopify
   Shopify~partialprobed6/10

   Shopify documents a Global Catalog MCP server enabling AI agents to search and discover products 'across the entire Shopify ecosystem' plus UCP for agentic commerce, which directly supports cross-merchant agent discoverability. However, this is developer/agent-integration infrastructure rather than a proven, widely-adopted answer-engine feed, and there's no independent evidence of adoption by major answer engines or of an llms.txt-style universal feed (llms.txt probe returned 404). missing for 10: independent verification that answer engines/agents actually consume this catalog at scale, evidence of a standardized feed format beyond MCP/UCP, and confirmation the llms.txt or similar discovery file exists.

   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”
   • [claimed-docs] “Build agentic shopping experiences powered by Shopify merchants, from product discovery to checkout.”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”
   • [probe] “PROBE llms.txt: HTTP 404 at https://shopify.dev/llms.txt”

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence shows BigCommerce's developer docs and APIs (REST/GraphQL, headless storefronts, an llms.txt for AI agents to navigate developer docs) but nothing about a cross-merchant product catalog or feed designed to make individual merchants' products discoverable by AI agents/answer engines across the platform. The llms.txt probe is aimed at documentation discovery, not a product feed for agent commerce.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”
   • [claimed-docs] “GraphQL Storefront API overview”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”

   proof ↗⚑ flag

Agent ops

1. ai-native userAn agent can take an order through its post-purchase lifecycle — status, fulfillment, returns — via documented APIs and webhooks without a human in the admin

   weight 2 · round to BigCommerce
   Shopify!disputedcontradicted5/10

   Shopify documents an Order MCP server and Admin/webhooks stack that let an agent fetch order status and fulfillment events ('line items, fulfillment events, and post-purchase adjustments') without human intervention (shopify-docs-45/52, shopify-docs-4/21/43, shopify-docs-31), which covers the status/fulfillment portions of the story well. However, community hands-on reports specifically contradict the returns/refunds piece: 'Want to do refunds? Too bad there's no way to do it via the API' (shopify-comm-9), directly undercutting the vendor's vague 'post-purchase adjustments' claim for the returns lifecycle stage. Missing for 10: an explicit, documented Returns/Refund API or MCP action, and independent confirmation that returns can actually be completed agent-side without admin involvement.

   • [claimed-docs] “Use the Order MCP server to fetch the current state of an order placed through your agent, including line items, fulfillment events, and pos…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [community] “App Charges get added to clients bills, you're not getting paid right away (60+ days in some cases) vs getting paid instantly. If someone do…”

   proof ↗⚑ flag

   BigCommerce~partialcommunity5/10

   BigCommerce documents REST/GraphQL APIs for managing orders programmatically and a webhooks system for event-driven integrations, which supports agent-driven order status/fulfillment automation without human admin interaction. However, the evidence never specifically documents returns/RMA endpoints, order-status-change webhook topics, or a fulfillment workflow API, and one community report raises concerns about API reliability/throttling under load. Missing for 10: explicit docs on returns/RMA API, order-status webhook event list, fulfillment API detail, and independent confirmation of reliable agent-driven order lifecycle automation.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Overview | BigCommerce Docs”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

Agentic checkout

1. ai-native userA shopping agent can discover my store's products and build carts through a documented agent-commerce endpoint on the store (MCP/UCP), not by scraping

   weight 3 · round to Shopify
   Shopify✓fullprobed9/10

   Shopify has documented, first-party agent-commerce endpoints: UCP for agents to authenticate, search catalog, build carts/checkouts, and monitor orders, plus explicit MCP servers for Storefront/Catalog discovery, Cart, Checkout, and Order state — exactly matching the discover-products-and-build-carts-via-documented-endpoint story. This is corroborated by a dedicated probe confirming the official MCP server docs exist. Missing for 10: independent/hands-on third-party validation that an agent successfully used these endpoints in production (only vendor docs and a docs-existence probe, no real-world agent integration report).

   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Connect any AI assistant to real-time commerce data from Shopify stores with Model Context Protocol (MCP) servers.”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the Universal Commerce Protocol (UCP)”
   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “enables AI agents to build and iterate on a cart before the buyer commits to purchase”
   • [claimed-docs] “enables AI agents to create and manage checkout sessions, convert carts into checkouts, and refer buyers to the merchant storefront to compl…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence shows only general REST/GraphQL APIs, webhooks, Catalyst, and an llms.txt for AI-assisted docs browsing — no documented MCP/UCP agent-commerce endpoint enabling an AI shopping agent to discover products and build carts is mentioned anywhere in the pack.

   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “GraphQL Storefront API overview”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Shopify~partialclaimed3/10

   Evidence shows only a narrow bulk capability (creating up to 250 shipping labels at once) and general Admin/GraphQL APIs that could support scripted bulk edits, but there is no documentation of a dedicated bulk-operations API (e.g., bulk product/order import-export) or AI-agent-driven bulk actions across many items. Missing for 10: explicit bulk GraphQL/REST operation endpoints for products/orders/inventory, AI-agent tooling that performs multi-item batch actions, and any hands-on confirmation of bulk automation at scale.

   • [claimed-docs] “Create up to 250 labels at once to process at scale”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”

   proof ↗⚑ flag

   BigCommerce~partialcommunity3/10

   BigCommerce documents REST and GraphQL APIs for programmatically managing products, orders, and customers (bigcommerce-docs-30, bigcommerce-docs-25), which could technically enable scripted bulk operations, but there is no explicit documentation of batch/bulk endpoints, rate-limit handling, or bulk-import tooling for AI-driven workflows. One community report also notes historical API throttling/reliability issues (bigcommerce-comm-4), suggesting bulk API use may face friction, though this is anecdotal and not a concrete documented failure of a specific bulk feature. Missing for 10: dedicated bulk/batch API documentation, explicit rate-limit or pagination guidance for large-scale operations, and independent verification of reliable bulk throughput.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Shopify
   Shopify~partialclaimed5/10

   Shopify's webhook system lets developers subscribe to events and trigger custom actions ('a trigger to perform an additional action after that event has occurred'), which supports event-driven automation, but this requires writing app/webhook code rather than a declarative 'define rules' interface accessible to an AI-native (non-developer) user. Missing for 10: evidence of a native no-code rule builder (e.g., Shopify Flow) with trigger-condition-action UI, and any AI-specific mechanism for autonomously defining such rules.

   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [claimed-docs] “Your code obtains an access token scoped to the permissions it needs.”

   proof ↗⚑ flag

   BigCommerce~partialclaimed4/10

   BigCommerce provides webhooks that fire on store events, which can trigger external automation, but there's no evidence of a native rules engine allowing users to define conditional trigger-action automations within the platform itself. missing for 10: native if-this-then-that rules builder, documentation of event-to-action automation configuration, evidence of AI-native or no-code rule definition UI.

   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Google Cloud Platform Pub/Sub Webhooks”
   • [claimed-docs] “Overview | BigCommerce Docs”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Shopify—none0/10

   Shopify's evidence covers webhooks (event-driven triggers), APIs, MCP/agent tooling, and CLI, but nothing describes scheduling recurring jobs or workflows (e.g., cron-like scheduling, recurring task automation) — webhooks are reactive to events, not time-based recurring schedules. missing for 10: any documentation of a scheduler, recurring job/task API, or workflow automation with time-based triggers.

   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”

   proof ↗⚑ flag

   BigCommerce—none0/10

   No evidence of any scheduling, cron, or recurring workflow/job automation capability; evidence only covers APIs, webhooks, theming, and headless commerce features. missing for 10: any scheduler/cron API, workflow automation engine, or documented way to run recurring jobs.

   ⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Shopify—none0/10

   No evidence in the pack shows Shopify offering versioning, review workflows, or rollback capabilities for automations (e.g., Shopify Flow or similar). The evidence covers CLI, webhooks, APIs, MCP/agent tooling, and themes, but nothing addresses version history, diffing, review/approval, or reverting automation changes.

   ⚑ flag

   BigCommerce—none0/10

   No evidence of any versioning, review, or rollback mechanism for automations/workflows (e.g., webhooks, scripts, or app configs) in BigCommerce docs; evidence covers APIs, headless storefronts, and webhooks setup but nothing about version history, diffing, or reverting automation changes.

   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Google Cloud Platform Pub/Sub Webhooks”
   • [claimed-docs] “Overview | BigCommerce Docs”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”

   proof ↗⚑ flag

B2b

1. merchantSell B2B and wholesale — customer-specific price lists, volume pricing, quotes or net-terms invoicing — alongside DTC

   weight 2 · round to BigCommerce
   Shopify~partialclaimed5/10

   Shopify explicitly markets a B2B feature set ("Sell to businesses and consumers from one platform... you get all the B2B features you need") but the evidence pack gives no detail on customer-specific price lists, volume/tiered pricing, quoting, or net-terms invoicing — only high-level marketing copy. missing for 10: specifics on price lists, volume pricing tiers, quote workflows, net-terms/invoicing support, and any independent/hands-on confirmation these B2B features work as advertised.

   • [claimed-docs] “Sell to businesses and consumers from one platform. Your business buyers get modern self-serve, and you get all the B2B features you need.”
   • [claimed-docs] “Sell to businesses and consumers from one platform. Your business buyers get modern self-serve”

   proof ↗⚑ flag

   BigCommerce✓fullclaimed7/10

   BigCommerce documents a dedicated 'B2B Edition' offering company accounts, quotes, and custom pricing for wholesale/enterprise buyers alongside standard DTC storefronts, directly matching the story's core asks (customer-specific pricing, quotes, B2B accounts). Missing for 10: explicit detail on volume/tiered pricing rules, net-terms invoicing workflow specifics, and independent/hands-on corroboration of B2B Edition in practice.

   • [claimed-docs] “B2B ecommerce built for how business buyers actually buy”
   • [claimed-docs] “B2B ecommerce built for how business buyers actually buy | BigCommerce”
   • [claimed-docs] “Set up B2B Edition for wholesale and enterprise buyers with company accounts, quotes, and custom pricing.”

   proof ↗⚑ flag

Catalog

1. merchantModel products with variants, options, and custom fields/metafields that fit my catalog, not a fixed template

   weight 3 · round drawn
   Shopify—none0/10

   The evidence pack contains no mention of product variants, options, or metafields—core Shopify catalog-modeling features—despite this being a natural axis for an e-commerce platform to be judged on. Only generic API/CLI/theme references are present, none tied to flexible product data modeling.

   ⚑ flag

   BigCommerce—none0/10

   The axis clearly applies to an ecommerce platform, but the evidence pack contains no documentation or community mentions of product variants, options, custom fields, or metafields — only generic references to REST/GraphQL APIs for 'managing products' and building headless storefronts. Missing for 10: any docs on variant/option modeling, custom fields, or metafield support, and any independent confirmation of catalog flexibility beyond a fixed template.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”

   proof ↗⚑ flag

Catalog ops

1. operations leadBulk import, export, and edit the catalog — CSV or API — without touching products one at a time

   weight 2 · round to BigCommerce
   Shopify~partialcommunity4/10

   The evidence pack has no first-party documentation describing a native CSV import/export or bulk-edit catalog tool; the only support is the general-purpose Admin API (GraphQL) that could be used to build bulk operations (shopify-docs-31, shopify-docs-18) plus a community mention confirming CSV parsing exists but with account-tier restrictions and limited data (shopify-comm-12). This shows the capability likely exists but is thin/gated rather than a clearly documented, frictionless bulk tool. Missing for 10: dedicated first-party docs on native CSV import/export UI, bulk edit tooling, or a specific bulk-catalog API endpoint, and independent hands-on confirmation of smooth large-scale editing.

   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [community] “Shopify is a terrible experience overall, and I wouldn't recommend it for anyone looking to start a quick ecom business online... certain ty…”

   proof ↗⚑ flag

   BigCommerce~partialcommunity5/10

   Docs confirm REST/GraphQL APIs to programmatically manage products, orders, and store settings (bigcommerce-docs-30, bigcommerce-docs-25), which supports bulk catalog operations via API, but there is no explicit documentation of a native CSV bulk import/export tool for the catalog in this evidence pack, and one community report flags historical API reliability/throttling issues (bigcommerce-comm-4). missing for 10: explicit CSV import/export feature docs, UI walkthrough for bulk edit, independent confirmation of reliable bulk operations at scale.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Navigate to **Settings > API Accounts** in your store control panel. Create credentials with the scopes you need.”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

Inventory

1. operations leadInventory tracks across multiple locations with stock adjustments and fulfillment from the right warehouse

   weight 2 · round drawn
   Shopify—none0/10

   The evidence pack covers apps, APIs, headless storefronts, AI agents/MCP, POS, markets, tax, shipping, B2B, payments, themes and CLI, but contains no mention of multi-location inventory tracking, stock adjustments, or fulfillment routing/warehouse selection logic. Missing for 10: multi-location inventory management docs, stock adjustment workflows, fulfillment-from-nearest-warehouse logic, and any community/hands-on confirmation of these features working.

   ⚑ flag

   BigCommerce—none0/10

   Evidence covers headless storefront APIs, theming, B2B, webhooks, and general API tooling, but nothing addresses multi-location inventory tracking, stock adjustments, or location-based fulfillment routing. missing for 10: multi-location inventory API/docs, stock adjustment workflows, warehouse-based fulfillment logic, any first-party or community confirmation of these capabilities.

   ⚑ flag

Checkout

1. developerCustomize checkout — fields, branding, discounts, and validation logic — through supported extension points rather than forking checkout

   weight 3 · round drawn
   Shopify~partialclaimed5/10

   Shopify's docs confirm apps can extend checkout ('apps that integrate into...checkout') and market the checkout as 'customizable', and the AI toolkit validates 'Shopify Extensions' against schemas, implying supported checkout extension points exist. However, the evidence pack never names concrete extension mechanisms like checkout UI extensions, checkout branding API, or Shopify Functions for discounts/validation logic that a developer would actually use. Missing for 10: explicit documentation of checkout UI extension APIs, checkout branding/customization API, and Shopify Functions for discount and validation logic, plus independent hands-on confirmation these work without forking checkout.

   • [claimed-docs] “Extend Shopify's core functionality with apps that integrate into Shopify's admin, online store, checkout and more.”
   • [claimed-docs] “The world's highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”
   • [claimed-docs] “The world’s highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”
   • [claimed-docs] “validate GraphQL queries, Liquid templates, and Shopify Extensions against Shopify schemas to catch issues earlier”
   • [claimed-docs] “The toolkit connects your agent to: Developer docs and API schemas... Code validation: validate GraphQL queries, Liquid templates, and Shopi…”

   proof ↗⚑ flag

   BigCommerce~partialclaimed5/10

   BigCommerce explicitly advertises the ability to 'extend checkout' via its developer platform and provides a dedicated Checkout SDK (checkout-sdk-js) as a supported extension point rather than requiring a full checkout fork [bigcommerce-docs-3][bigcommerce-docs-36]. However, the evidence pack gives no detail on specific extension points for custom fields, branding theming, discount logic, or validation rules within checkout, nor any independent/hands-on confirmation that these specific capabilities work as described. Missing for 10: documented API/SDK methods for custom checkout fields, branding customization, discount rule injection, and validation logic, plus independent developer corroboration of these specific capabilities.

   • [claimed-docs] “Create single-click apps for the BigCommerce marketplace, build custom integrations, or extend checkout.”
   • [claimed-docs] “Checkout SDK | SDK | [checkout-sdk-js]”

   proof ↗⚑ flag

2. merchantBuyers can pay with accelerated wallets — Apple Pay, Google Pay, PayPal, platform one-click — without re-entering details

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

   Shopify Payments docs claim support for cards, wallets, installments, and crypto, and Shopify Checkout is marketed as a high-converting one-click checkout, implying accelerated wallet support, but no evidence explicitly names Apple Pay, Google Pay, or PayPal integration details or confirms seamless one-click behavior across all wallets. missing for 10: explicit documentation naming Apple Pay/Google Pay/PayPal support, evidence of no re-entry of details, independent/hands-on confirmation of accelerated checkout wallets working as advertised.

   • [claimed-docs] “Accept cards, wallets, installments, and crypto—from day one.”
   • [claimed-docs] “The world's highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”
   • [claimed-docs] “The world’s highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence pack mentions a general payments page (bigcommerce-docs-14/23) but provides no specifics about Apple Pay, Google Pay, PayPal, or one-click wallet checkout support; no documentation or community confirmation of accelerated wallet checkout flows. missing for 10: mention of specific wallet integrations (Apple Pay, Google Pay, PayPal one-click), checkout flow details, or merchant/customer confirmation of wallet usage.

   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions”
   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions | BigCommerce”

   proof ↗⚑ flag

Conversion

1. merchantAbandoned carts and checkouts trigger recovery emails or links so I can win the sale back

   weight 1 · round drawn
   Shopify—none0/10

   No evidence in the pack mentions abandoned cart/checkout recovery emails or links; the evidence covers APIs, CLI, themes, POS, tax, agents/MCP, and unrelated community complaints, none of which address this specific merchant capability.

   ⚑ flag

   BigCommerce—none0/10

   No evidence pack item mentions abandoned cart recovery, abandoned checkout emails, or cart recovery links; coverage focuses on APIs, headless architecture, webhooks, B2B, and theming, none of which address this specific merchant capability.

   ⚑ flag

App dev

1. developerBuild custom apps and extensions with official SDKs, scaffolding tooling, and a documented review/distribution path

   weight 2 · round to Shopify
   Shopify~partialcommunity7/10

   Shopify provides official SDKs (Admin/Storefront GraphQL APIs, officially supported libraries), a CLI for scaffolding apps/themes/headless storefronts, dev stores for testing, webhooks, and auth scopes — solidly documented in shopify.dev evidence. However, the evidence pack lacks explicit documentation of the app review/certification and App Store distribution process, and community reports (a developer's app being banned with vague reasons, terrible partner support/docs) raise real friction around that path. missing for 10: explicit docs on app review criteria/submission process, independent corroboration that the distribution path works smoothly.

   • [claimed-docs] “Initialize new apps, themes, and headless storefronts in an instant with the latest Shopify CLI.”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [claimed-docs] “Run the second command to create a new app. Your app will be added as a new subdirectory.”
   • [claimed-docs] “Dev stores are testing environments that you own and control. They let you build and test your apps in a realistic Shopify environment witho…”
   • [community] “For developers this is potentially even worse than it is for merchants, as many Shopify apps simply cannot be migrated to another platform. …”
   • [community] “Shopify is really terrible when it comes to partner support. The documentation is terrible and if you want to use their API, be prepared to …”

   proof ↗⚑ flag

   BigCommerce~partialcommunity6/10

   BigCommerce documents a broad developer toolkit — REST/GraphQL APIs, Checkout SDK, API Clients, Catalyst (Next.js) and Stencil (Handlebars) scaffolding, sandbox/trial stores, OAuth API accounts, and a single-click app marketplace for distribution — giving solid first-party coverage of SDKs, scaffolding, and a distribution channel. However, there's no detailed documented app review/certification workflow, and hands-on community reports describe the Stencil theming system as inconsistent and hard to work with and cite unreliable API connections/throttling, undercutting the polish of the developer experience. Missing for 10: an explicit documented app-review/certification process, a dedicated CLI scaffolding tool, and independent corroboration that the SDK/tooling experience is smooth in practice.

   • [claimed-docs] “Create single-click apps for the BigCommerce marketplace, build custom integrations, or extend checkout.”
   • [claimed-docs] “Accelerate your app development. Get started making API requests in the language of your choice with our API Clients.”
   • [claimed-docs] “Checkout SDK | SDK | [checkout-sdk-js]”
   • [claimed-docs] “Our open source design system. Use to build BigCommerce Apps that feel native inside the control panel.”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”
   • [claimed-docs] “BigCommerce's Handlebars-based theme engine for building hosted storefronts.”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”
   • [community] “I've never had a worse webdev experience than attempting to create a BigCommerce theme. There are hundreds of theme files, and a maddeningly…”

   proof ↗⚑ flag

Apps

1. merchantExtend my store from a marketplace of vetted apps and extensions covering the long tail of features

   weight 3 · round to Shopify
   Shopify~partialcommunity7/10

   Shopify documents a robust apps ecosystem (apps.shopify.dev integrating admin/storefront/checkout) and a separate themes marketplace (themes.shopify.com) covering long-tail customization, giving merchants a clear path to extend functionality without custom dev. However, independent community reports raise real friction in this ecosystem — poor partner/API documentation, apps being banned/unmigratable, and API limitations affecting third-party app reliability (shopify-comm-7, shopify-comm-8, shopify-comm-12) — which tempers the 'vetted, frictionless' framing of the story. Missing for 10: first-party data on app review/vetting process, quantified app store size/quality, and independent merchant reviews of app marketplace satisfaction (vs partner-side complaints).

   • [claimed-docs] “Extend Shopify's core functionality with apps that integrate into Shopify's admin, online store, checkout and more.”
   • [claimed-docs] “Fully flexible and regularly updated with Shopify’s latest features”
   • [claimed-docs] “Look for a design with the features you need most, then customize from there”
   • [claimed-docs] “All the essentials —product recommendations, reviews, discounts, and much more”
   • [community] “For developers this is potentially even worse than it is for merchants, as many Shopify apps simply cannot be migrated to another platform. …”
   • [community] “Shopify is really terrible when it comes to partner support. The documentation is terrible and if you want to use their API, be prepared to …”
   • [community] “Shopify is a terrible experience overall, and I wouldn't recommend it for anyone looking to start a quick ecom business online... certain ty…”

   proof ↗⚑ flag

   BigCommerce~partialcommunity5/10

   BigCommerce documents an app marketplace ('Over 1,200 apps to help you grow') and developer APIs to build single-click marketplace apps, but there's no detail on vetting/curation processes, and a hands-on community report describes the app ecosystem as 'rather incomplete' with API reliability issues. missing for 10: vetting/curation details, marketplace category breadth evidence, more recent independent corroboration of app quality/coverage.

   • [claimed-docs] “Over 1,200 apps to help you grow.”
   • [claimed-docs] “Create single-click apps for the BigCommerce marketplace, build custom integrations, or extend checkout.”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

Functions

1. developerInject custom backend logic — discounts, shipping rules, validation — as serverless functions or hooks that run inside the platform

   weight 2 · round drawn
   Shopify—none0/10

   The evidence pack covers Shopify's general app/extension platform (Admin & Storefront APIs, webhooks, extensions validation, UCP/MCP agent tooling) but never mentions Shopify Functions or any serverless-function/hook mechanism specifically for injecting custom discount, shipping, or validation logic that runs inline within checkout or platform processing — webhooks here are explicitly async/near-real-time, not synchronous business-logic hooks. Missing for 10: any documentation of Shopify Functions, function extension points for discounts/shipping/validation, or evidence of in-platform serverless logic execution.

   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [claimed-docs] “validate GraphQL queries, Liquid templates, and Shopify Extensions against Shopify schemas to catch issues earlier”
   • [claimed-docs] “validate GraphQL queries, Liquid templates, and Shopify Extensions against Shopify schemas to catch issues earlier.”
   • [claimed-docs] “The toolkit connects your agent to: Developer docs and API schemas... Code validation: validate GraphQL queries, Liquid templates, and Shopi…”

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence shows only webhooks (event notifications), REST/GraphQL APIs, and third-party app integrations — none of which are serverless functions or hooks that execute custom backend logic (discounts, shipping, validation) inside the platform itself. Missing for 10: any documentation of a functions/hooks runtime, script execution environment, or in-platform custom logic injection comparable to Shopify Functions.

   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Google Cloud Platform Pub/Sub Webhooks”
   • [claimed-docs] “Overview | BigCommerce Docs”
   • [claimed-docs] “Create single-click apps for the BigCommerce marketplace, build custom integrations, or extend checkout.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”

   proof ↗⚑ flag

Admin api

1. developerManage the full commerce lifecycle programmatically — create products, edit orders, issue refunds, trigger fulfillments — through the admin API

   weight 3 · round to BigCommerce
   Shopify!disputedcontradicted4/10

   Shopify's Admin API is documented as the mechanism for apps to 'extend and enhance the Shopify admin' with scoped access tokens and webhook triggers for order/fulfillment events (shopify-docs-31, shopify-docs-5, shopify-docs-48, shopify-docs-43), suggesting broad programmatic control over products, orders, and fulfillments. However, a specific hands-on developer report states 'Want to do refunds? Too bad there's no way to do it via the API' (shopify-comm-9), directly contradicting the refund-issuance claim in this story, and other community reports describe partner/API friction and poor documentation (shopify-comm-8, shopify-comm-12). Missing for 10: explicit documentation citing product-creation, order-editing, refund, and fulfillment-trigger endpoints, and independent confirmation resolving the refund-API contradiction.

   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Your code obtains an access token scoped to the permissions it needs.”
   • [claimed-docs] “its access scopes determine what it can access”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [community] “App Charges get added to clients bills, you're not getting paid right away (60+ days in some cases) vs getting paid instantly. If someone do…”
   • [community] “Shopify is really terrible when it comes to partner support. The documentation is terrible and if you want to use their API, be prepared to …”

   proof ↗⚑ flag

   BigCommerce~partialcommunity6/10

   First-party docs confirm REST/GraphQL Admin APIs for managing products, orders, customers and store settings, with scoped API-account credentials and a sandbox for testing (bigcommerce-docs-30, docs-32, docs-38, docs-39) plus webhooks for event-driven workflows (bigcommerce-docs-5). However, the evidence never explicitly names refund or fulfillment-triggering endpoints, and one hands-on account reports the API was unreliable, suffering throttling/dropped connections (bigcommerce-comm-4), which tempers confidence in full lifecycle reliability. Missing for 10: explicit refund/fulfillment API documentation, independent verification of stable high-volume API usage, and third-party confirmation of full CRUD lifecycle beyond vendor docs.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “Navigate to **Settings > API Accounts** in your store control panel. Create credentials with the scopes you need.”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”
   • [claimed-docs] “Webhooks”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

Headless

1. developerBuild a fully custom headless storefront on a documented storefront API or first-party frontend framework

   weight 3 · round to Shopify
   Shopify✓fullclaimed9/10

   Shopify offers a documented Storefront GraphQL API for building custom experiences on any platform (web, apps, games) plus Hydrogen, a first-party React-based headless commerce framework with hosting via Oxygen, and CLI tooling to scaffold headless storefronts. This is well-documented first-party capability with quarterly-versioned APIs and dev-store testing support. Missing for 10: independent hands-on developer report specifically validating headless/Hydrogen storefront build experience (community evidence present is about general API/app dev friction, not headless storefronts specifically).

   • [claimed-docs] “Get all the power of Shopify under the hood, with complete control over the frontend. Start building quickly with Hydrogen”
   • [claimed-docs] “The API offers a full range of commerce options making it possible for customers to view products and collections, add products to a cart, a…”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [claimed-docs] “Build fast with Shopify's all-in-one solution for custom commerce. Hosting included.”
   • [claimed-docs] “Help merchants express their unique brand by building a custom theme or Hydrogen storefront.”
   • [claimed-docs] “Shopify releases new API versions on a predictable quarterly schedule, giving you time to adopt changes before older versions are retired. S…”
   • [claimed-docs] “Dev stores are testing environments that you own and control. They let you build and test your apps in a realistic Shopify environment witho…”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”

   proof ↗⚑ flag

   BigCommerce✓fullcommunity8/10

   BigCommerce provides well-documented GraphQL Storefront API and a first-party headless frontend framework (Catalyst, built on Next.js), plus REST/GraphQL management APIs, SDKs, and sandbox tooling for developers to build fully custom storefronts (bigcommerce-docs-1, -2, -7, -18, -25, -29, -36). Community evidence corroborates decent API/dev experience for local development with live data (bigcommerce-comm-1), though older complaints exist about API reliability and Stencil theme complexity that are tangential to the modern headless stack. Missing for 10: recent independent hands-on validation specifically of Catalyst/GraphQL Storefront API at production scale, and clearer confirmation the API throttling issues (from older community reports) have been resolved.

   • [claimed-docs] “go fully headless with the GraphQL Storefront API”
   • [claimed-docs] “Build with Catalyst (Next.js), customize Stencil themes, or go fully headless”
   • [claimed-docs] “Catalyst: Headless Storefronts Made Easy”
   • [claimed-docs] “GraphQL Storefront API overview”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “or go fully headless with the GraphQL Storefront API.”
   • [claimed-docs] “Checkout SDK | SDK | [checkout-sdk-js]”
   • [community] “I actually helped my previous company migrate from Magento to BigCommerce, and found their offering incredibly compelling compared to Shopif…”

   proof ↗⚑ flag

Channels

1. merchantList and sync products to external channels — marketplaces, social commerce, shopping feeds — from one catalog

   weight 2 · round drawn
   Shopify~partialclaimed3/10

   Evidence only hints at multi-channel capability ('Orders from all your sales channels in one place', 'Sell online, in person, and in AI chats') without explicitly documenting catalog sync to marketplaces, social commerce platforms, or shopping feeds. Missing for 10: explicit docs on Facebook/Instagram/TikTok/Google Shopping/Amazon channel apps, product feed sync mechanics, and any independent confirmation of catalog consistency across channels.

   • [claimed-docs] “Orders from all your sales channels in one place”
   • [claimed-docs] “Sell online, in person, and in AI chats”

   proof ↗⚑ flag

   BigCommerce~partialclaimed3/10

   BigCommerce's marketing pages reference an 'Omnichannel Ecommerce Software Solution' and a large app marketplace (1,200+ apps) that could include channel-sync apps, but the evidence pack contains no concrete documentation of specific marketplace/social/shopping-feed integrations (e.g., Amazon, Google Shopping, Facebook/Instagram) or a dedicated channel-manager feature. Missing for 10: explicit docs on channel listing/sync workflows, named integrations (Amazon, eBay, Google Shopping, TikTok, Instagram), and any first-party or independent confirmation these work reliably.

   • [claimed-docs] “Omnichannel Ecommerce Software Solution”
   • [claimed-docs] “Omnichannel Ecommerce Software Solution | BigCommerce”
   • [claimed-docs] “Over 1,200 apps to help you grow.”

   proof ↗⚑ flag

Global

1. merchantSell internationally with localized storefronts, multi-currency pricing, translations, and duties handled

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

   Shopify Markets docs explicitly support selling to multiple markets from one store, market-specific pricing previews, and automated tax/duty-style compliance (sales tax automation, filing) plus shipping label bulk creation, all first-party. However, the evidence pack never explicitly mentions storefront translation tooling or international duties/customs handling by name, only tax automation for US sales tax. missing for 10: explicit evidence of translation/localization tooling, explicit duties/customs handling documentation, independent/hands-on confirmation of multi-currency and localized storefront experience.

   • [claimed-docs] “Sell to multiple markets, all from a single store”
   • [claimed-docs] “Preview what people in your different markets see and confirm they're getting the right products and pricing.”
   • [claimed-docs] “Get a holistic overview of all your markets, zoom in for details, and make updates—all in one place.”
   • [claimed-docs] ““View as” customers in each market - Preview what people in your different markets see and confirm they're getting the right products and pr…”
   • [claimed-docs] “Take the stress out of sales tax in the United States with automated calculations, liability insights, and filing—right in your admin.”
   • [claimed-docs] “Automate filing and remittance in just a few steps”
   • [claimed-docs] “automated calculations, liability insights, and filing—right in your admin”
   • [claimed-docs] “Create up to 250 labels at once to process at scale”
   • [claimed-docs] “Orders from all your sales channels in one place”

   proof ↗⚑ flag

   BigCommerce~partialclaimed2/10

   BigCommerce's 'Multi-Site' solution promotes 'Multiple Brands and Regions' which gestures at localized storefronts, but the evidence pack contains no explicit documentation of multi-currency pricing, storefront translations, or duty/tax handling for international sales. Missing for 10: explicit multi-currency pricing docs, translation/localization tooling, duties/customs handling, and any independent confirmation these features work end-to-end.

   • [claimed-docs] “Multi-Site: One Platform, Multiple Brands and Regions”
   • [claimed-docs] “Multi-Site: One Platform, Multiple Brands and Regions | BigCommerce”

   proof ↗⚑ flag

Pos

1. merchantSell in person with a point-of-sale that shares the same catalog, inventory, and customers as my online store

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

   Shopify explicitly markets POS (shopify-docs-9, shopify-docs-26) as unifying sales channels, backed by 'Sell online, in person, and in AI chats' (shopify-docs-55) and 'orders from all your sales channels in one place' (shopify-docs-57), implying a shared catalog/order backend across online and in-person selling. However, there's no specific evidence detailing shared inventory sync mechanics, shared customer profiles across channels, or hands-on/independent confirmation that POS and online store data stay unified in practice. Missing for 10: explicit documentation of shared inventory sync, unified customer records across POS and online store, and independent/hands-on verification of this multi-channel consistency.

   • [claimed-docs] “From first sale to full scale, today’s best brands run on Shopify’s POS system.”
   • [claimed-docs] “From first sale to full scale, today's best brands run on Shopify's POS system.”
   • [claimed-docs] “Sell online, in person, and in AI chats”
   • [claimed-docs] “Orders from all your sales channels in one place”

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence covers headless APIs, theming, B2B, multi-store, payments, and webhooks, but there is no mention of a native point-of-sale product or integration that syncs catalog/inventory/customers with a physical retail POS system. Omnichannel page is referenced but no details show POS capability.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to BigCommerce
   Shopify!disputedcontradicted4/10

   Shopify's docs describe broad Admin/Storefront/GraphQL APIs claimed to cover apps, storefronts, checkout, and even agentic commerce (UCP/MCP) — suggesting near-full UI parity via API. However, concrete hands-on community reports contradict full parity: one developer states 'Want to do refunds? Too bad there's no way to do it via the API,' and another reports that 'certain types of accounts are required to access certain parts of the API,' forcing merchants into limited CSV workarounds, plus reports that Shopify has killed features 'with no alternative way to achieve the removed functionality' via API. missing for 10: independent verification of full UI-API parity, resolution of the refund-API gap, and confirmation that account-tier API restrictions have been lifted.

   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “The API offers a full range of commerce options making it possible for customers to view products and collections, add products to a cart, a…”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [community] “App Charges get added to clients bills, you're not getting paid right away (60+ days in some cases) vs getting paid instantly. If someone do…”
   • [community] “Shopify is a terrible experience overall, and I wouldn't recommend it for anyone looking to start a quick ecom business online... certain ty…”
   • [community] “If you're not American, you will be forced to hand over 3% of your 80% revenue cut to PayPal (unless your MRR cut is >$30k). Sometimes Shopi…”

   proof ↗⚑ flag

   BigCommerce~partialcommunity6/10

   BigCommerce documents broad REST and GraphQL API coverage for products, orders, customers, store settings, checkout, webhooks, B2B, and multi-store management, suggesting most UI operations have API equivalents, and even provides sandbox/trial environments and an API Request Runner for testing. However, there is no explicit vendor statement guaranteeing 100% UI-to-API parity, and a community report notes historical issues with reliably connecting to the API without throttling. Missing for 10: an explicit parity guarantee/documentation mapping every control-panel action to an API endpoint, and independent hands-on confirmation that all admin UI actions (e.g., full theme/store configuration) are API-accessible without gaps.

   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “Navigate to **Settings > API Accounts** in your store control panel. Create credentials with the scopes you need.”
   • [claimed-docs] “You can experiment with our REST Management APIs using the **Request Runner**, which is built in to the [API Reference]”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to BigCommerce
   Shopify—none0/10

   Shopify's evidence pack contains no documentation of a comprehensive data-export feature in open/standard formats, and community reports (shopify-comm-7, shopify-comm-12) describe migration friction — apps that can't be ported to other platforms and merchants limited to CSV exports 'with limited amount of information.' There is no first-party claim of full open-format export, so the axis applies but is unmet.

   • [community] “For developers this is potentially even worse than it is for merchants, as many Shopify apps simply cannot be migrated to another platform. …”
   • [community] “Shopify is a terrible experience overall, and I wouldn't recommend it for anyone looking to start a quick ecom business online... certain ty…”

   proof ↗⚑ flag

   BigCommerce~partialclaimed4/10

   BigCommerce exposes REST and GraphQL APIs that can be used to pull products, orders, customers, and settings programmatically (bigcommerce-docs-30, bigcommerce-docs-25), which gives a technical path to extract data in open JSON formats, but there is no documented bulk 'export all my data' feature, data-portability guarantee, or migration-out tooling. missing for 10: explicit full-account data export/download feature, documented data portability/GDPR-style export policy, and evidence of successful full data migration away from BigCommerce.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Use REST and Gra”

   proof ↗⚑ flag

Processing

1. merchantChoose among third-party payment gateways and charge in multiple currencies when the built-in option doesn't fit

   weight 2 · round to BigCommerce
   Shopify!disputedcontradicted4/10

   Shopify docs confirm multi-currency selling via Markets (shopify-docs-10, shopify-docs-16, shopify-docs-37) and payment flexibility (shopify-docs-14), implying third-party gateway support exists, but concrete community evidence shows real friction: Shopify charges an extra 1% fee for using third-party payment gateways instead of Shopify Payments (shopify-comm-6), and merchants report Shopify's own Payment module overrides and disables standalone third-party integrations like Stripe without clear warning (shopify-comm-11), directly undercutting the 'freely choose a third-party gateway' promise. missing for 10: first-party documentation of specific supported third-party gateways and fee structure, independent confirmation that third-party gateways work without penalty on standard plans.

   • [claimed-docs] “Accept cards, wallets, installments, and crypto—from day one.”
   • [claimed-docs] “Sell to multiple markets, all from a single store”
   • [claimed-docs] “Preview what people in your different markets see and confirm they're getting the right products and pricing.”
   • [claimed-docs] “Get a holistic overview of all your markets, zoom in for details, and make updates—all in one place.”
   • [community] “Shopify charges additional 1% per transaction for 3rd party payment integrations. Weird.”
   • [community] “Worth mentioning Shopify uses Stripe. A few months back they introduced their Shopify Payment Module which runs on Stripe, which then overri…”

   proof ↗⚑ flag

   BigCommerce~partialclaimed3/10

   BigCommerce has a dedicated payments page referencing multiple payment providers/credit card solutions, implying support for third-party gateways, but there is no explicit documentation confirming a marketplace of alternative gateways or multi-currency charging capability. missing for 10: explicit list/count of supported third-party payment gateways, documentation of multi-currency checkout/settlement support, and independent confirmation of gateway flexibility.

   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions”
   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions | BigCommerce”

   proof ↗⚑ flag

2. merchantTake payments with the platform's integrated processing — published card rates, payouts, and fraud tooling — without wiring a third-party gateway

   weight 3 · round to Shopify
   Shopify~partialcommunity6/10

   Shopify Payments is documented as the native, no-third-party-gateway option ('Accept cards, wallets, installments, and crypto—from day one' — shopify-docs-14) and the checkout it powers is highlighted as high-converting (shopify-docs-25/40), but the evidence pack contains no first-party page on published card-processing rates or dedicated fraud-tooling (e.g. Shopify Fraud Filter) documentation. Community reports also surface real friction with the payouts side of the integrated system (random payout freezes over address verification — shopify-comm-4; extra 1% fee if you opt for a 3rd-party gateway instead — shopify-comm-6), which are caveats rather than proof the native processing doesn't work. Missing for 10: explicit published rate-card documentation, dedicated fraud-detection tooling docs, and independent corroboration of payout reliability.

   • [claimed-docs] “Accept cards, wallets, installments, and crypto—from day one.”
   • [claimed-docs] “The world's highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”
   • [claimed-docs] “The world’s highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”
   • [community] “Shopify would randomly stop payouts every 3-4 months or so because they needed to re-verify our owner address information. Apparently, most …”
   • [community] “Shopify charges additional 1% per transaction for 3rd party payment integrations. Weird.”

   proof ↗⚑ flag

   BigCommerce~partialclaimed3/10

   Evidence only shows a page title 'Ecommerce Payment Providers & Credit Card Solutions' (BigCommerce Payments) exists, confirming some integrated payments offering, but there is no detail on published card rates, payout schedules, or fraud tooling specifics, nor any independent confirmation it works without a third-party gateway. Missing for 10: documented rate sheet, payout timing details, fraud/chargeback tooling specifics, and hands-on/community corroboration of using it without a third-party gateway.

   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions”
   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions | BigCommerce”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Shopify—none0/10

   No evidence in the pack addresses data residency, regional storage choice, or data sovereignty controls for merchant/store data; the 'markets' features refer to selling regions, not data storage location. Missing for 10: any documentation of data center/region selection, residency guarantees, or compliance controls (e.g. GDPR data localization) for AI-native users.

   ⚑ flag

   BigCommerce—none0/10

   No evidence of data residency/region selection controls anywhere in the pack; docs only cover APIs, theming, headless commerce, and multi-store branding, none of which address data storage location choice.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Shopify—none0/10

   No evidence pack item addresses AI-training data opt-out or data-privacy controls for merchant/customer data; all citations concern APIs, CLI, agents/MCP, commerce features, or unrelated community complaints.

   ⚑ flag

   BigCommerce—none0/10

   No evidence in the pack addresses AI-training data opt-out or privacy controls preventing BigCommerce data from being used to train AI models; all evidence concerns APIs, headless commerce, themes, and developer tooling. Missing for 10: any privacy policy, data-use opt-out setting, or AI training exclusion documentation.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Shopify—none0/10

   No evidence in the pack addresses data retention or deletion controls for merchants, developers, or AI agents interacting with Shopify data; the documentation excerpts focus on APIs, commerce features, and agent/MCP integrations but never mention data retention policies, deletion requests, or privacy controls.

   ⚑ flag

   BigCommerce—none0/10

   No evidence addresses AI-native data retention/deletion controls—nothing about data lifecycle policies, deletion APIs, or retention settings for AI agents or data processed by AI tools; evidence only covers commerce APIs, theming, and app ecosystem.

   ⚑ flag

Content

1. merchantManage content — pages, blogs, media — alongside my products from the same admin

   weight 1 · round drawn
   Shopify—none0/10

   The evidence pack covers apps, APIs, headless storefronts, themes, POS, tax, shipping, B2B, payments, and AI/MCP tooling, but contains no mention of built-in admin features for managing pages, blog posts, or media content alongside products. No citation supports this specific content-management-in-admin capability.

   ⚑ flag

   BigCommerce—none0/10

   The evidence pack covers storefront theming (Stencil), headless APIs, webhooks, and apps, but contains no mention of an admin-side content/blog/pages/media management module for merchants; the only content-adjacent evidence is about theme file structure and API-driven storefront building, not admin content authoring.

   ⚑ flag

Theme dev

1. developerCustomize storefront code with a documented templating layer, local preview, and version-controlled theme deploys

   weight 2 · round to Shopify
   Shopify~partialclaimed5/10

   Shopify's CLI documentation confirms it can initialize and work with themes (shopify-docs-3, shopify-docs-17, shopify-docs-30) and Liquid is referenced as the templating layer validated by tooling (shopify-docs-8, shopify-docs-22, shopify-docs-35), plus a theme marketplace for customization (shopify-docs-15, shopify-docs-23). However, the evidence never explicitly documents a 'theme dev' local preview server, git-based/version-controlled theme deploy workflow, or push/pull staging process — dev-store evidence (shopify-docs-x2) only covers app dev, not theme dev specifically. Missing for 10: explicit local theme preview command documentation, explicit version-controlled/staged theme deployment workflow, and independent hands-on confirmation of the theme dev loop.

   • [claimed-docs] “Initialize new apps, themes, and headless storefronts in an instant with the latest Shopify CLI.”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”
   • [claimed-docs] “Fully flexible and regularly updated with Shopify’s latest features”
   • [claimed-docs] “Look for a design with the features you need most, then customize from there”
   • [claimed-docs] “validate GraphQL queries, Liquid templates, and Shopify Extensions against Shopify schemas to catch issues earlier”
   • [claimed-docs] “validate GraphQL queries, Liquid templates, and Shopify Extensions against Shopify schemas to catch issues earlier.”
   • [claimed-docs] “Dev stores are testing environments that you own and control. They let you build and test your apps in a realistic Shopify environment witho…”

   proof ↗⚑ flag

   BigCommerce!disputedcontradicted5/10

   BigCommerce documents a Handlebars-based theme engine (Stencil) as its templating layer, and a hands-on HN comment confirms local development with live product data. However another hands-on account describes the same theme system as having 'hundreds of theme files' and a 'maddeningly incomplete and inconsistent templating tag system,' directly contradicting the claim that customization is well-documented and smooth. Missing for 10: no dedicated docs on Stencil CLI local preview workflow, no explicit version-controlled/git-based theme deploy pipeline evidence, and no independent corroboration resolving the conflicting community reports.

   • [claimed-docs] “BigCommerce's Handlebars-based theme engine for building hosted storefronts.”
   • [claimed-docs] “BigCommerce’s Handlebars-based theme engine for building hosted storefronts.”
   • [community] “I actually helped my previous company migrate from Magento to BigCommerce, and found their offering incredibly compelling compared to Shopif…”
   • [community] “I've never had a worse webdev experience than attempting to create a BigCommerce theme. There are hundreds of theme files, and a maddeningly…”

   proof ↗⚑ flag

Themes

1. merchantLaunch a polished storefront from professionally designed themes and customize layout, sections, and branding without code

   weight 3 · round to Shopify
   Shopify✓fullcommunity8/10

   Shopify provides a theme store with professionally designed, customizable themes (docs-15, docs-23, docs-24, docs-54) explicitly aimed at no-code branding/layout customization ('Design fast with AI. Pick a prebuilt theme... customize from there'), backed by scale-tested credibility from long-time users (shopify-comm-3). missing for 10: hands-on/independent review specifically validating the theme editor's no-code UX (customizer drag-drop experience), and some community commentary criticizes overall dev experience/documentation quality which slightly tempers confidence.

   • [claimed-docs] “Fully flexible and regularly updated with Shopify’s latest features”
   • [claimed-docs] “Look for a design with the features you need most, then customize from there”
   • [claimed-docs] “Design fast with AI. Pick a prebuilt theme. Or go totally custom.”
   • [claimed-docs] “All the essentials —product recommendations, reviews, discounts, and much more”
   • [community] “We've been running e-commerce for six years, and have tried everything (woocommerce, open commerce, bigcommerce, magento, prestashop). They …”

   proof ↗⚑ flag

   BigCommerce~partialcommunity6/10

   BigCommerce docs confirm a Stencil theme engine for hosted storefronts and marketing copy stating stores can be built 'with or without code,' implying pre-designed themes plus customization options, alongside marketplace apps for extending functionality (bigcommerce-docs-6, bigcommerce-docs-8, bigcommerce-docs-10). However, a hands-on community account explicitly describes BigCommerce theme customization as one of the worst web-dev experiences due to 'hundreds of theme files' and an 'inconsistent templating tag system' (bigcommerce-comm-6), undercutting the no-code simplicity claim for anything beyond basic use. Missing for 10: explicit documentation of a visual drag-and-drop page builder/section editor for non-technical merchants, a gallery of professionally designed themes, and independent praise confirming ease of no-code branding/layout changes.

   • [claimed-docs] “BigCommerce's Handlebars-based theme engine for building hosted storefronts.”
   • [claimed-docs] “Build your store with or without code.”
   • [claimed-docs] “Over 1,200 apps to help you grow.”
   • [community] “I've never had a worse webdev experience than attempting to create a BigCommerce theme. There are hundreds of theme files, and a maddeningly…”

   proof ↗⚑ flag

Shipping

1. operations leadCheckout shows live carrier rates and I can buy labels and track shipments from the platform

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

   Shopify Shipping docs confirm label creation at scale (up to 250 labels) and order aggregation across sales channels, which implies carrier rate access and label purchasing, but the evidence doesn't explicitly confirm live carrier rate display at checkout or in-platform shipment tracking. Missing for 10: explicit documentation of live carrier rate calculation shown at checkout, and dedicated tracking/label-purchase workflow details beyond marketing copy.

   • [claimed-docs] “Create up to 250 labels at once to process at scale”
   • [claimed-docs] “Orders from all your sales channels in one place”

   proof ↗⚑ flag

   BigCommerce—none0/10

   No evidence pack items reference live carrier rate shopping, label purchasing, or shipment tracking within BigCommerce checkout; the evidence focuses on APIs, theming, headless commerce, and marketplace apps, not shipping/carrier integration. This is a fair axis for an ecommerce platform (shipping apps and carrier integrations are common in the category), but nothing shows BigCommerce natively delivers it.

   ⚑ flag

Taxes

1. merchantSales tax and VAT are calculated automatically per jurisdiction, with rates kept current and reports I can file from

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

   Shopify Tax provides automated sales tax calculations, liability insights, and automated filing/remittance, explicitly for the United States, positioned as a first-party admin feature. However, evidence does not confirm VAT handling or international jurisdiction coverage, nor independent corroboration of accuracy/reliability of filing. missing for 10: VAT/international tax calculation and filing evidence, rate-currency guarantees, third-party/independent validation of accuracy, and any hands-on confirmation of the filing workflow.

   • [claimed-docs] “Take the stress out of sales tax in the United States with automated calculations, liability insights, and filing—right in your admin.”
   • [claimed-docs] “Automate filing and remittance in just a few steps”
   • [claimed-docs] “automated calculations, liability insights, and filing—right in your admin”

   proof ↗⚑ flag

   BigCommerce—none0/10

   No evidence pack items mention tax/VAT calculation, jurisdiction-based rates, rate updates, or tax filing/reporting features; the evidence covers APIs, theming, headless commerce, and B2B/webhooks instead.

   ⚑ flag