WooCommerce vs BigCommerce

Agent access

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

   weight 2 · round to WooCommerce
   WooCommerce✓fullprobed9/10

   A direct probe confirms an llms.txt file is live at developer.woocommerce.com/llms.txt returning HTTP 200 with structured documentation listing, and there's an official MCP server for AI agent interaction with WooCommerce stores, directly supporting agent-oriented discovery. Missing for 10: no independent/community corroboration of agents actually using llms.txt successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.woocommerce.com/llms.txt # WooCommerce Documentation This file contains a list of all documen…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   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
   WooCommerce~partialprobed4/10

   WooCommerce ships WC-CLI for command-line store management and a REST API for scripted automation, which supports some headless/CI-style operations, but there is no evidence of a documented headless runtime mode, containerized CI test harness, or official guidance for running WooCommerce end-to-end in a CI pipeline. missing for 10: documented headless/CI deployment pattern, official CI/testing pipeline integration, evidence of automated store provisioning without a GUI.

   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [github] “Once you've installed all prerequisites, the following will prepare all of the build outputs necessary for development”

   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
   WooCommerce—none0/10

   Evidence only shows WooCommerce exposing itself as an MCP *server* so external AI assistants can call its tools (docs-14/29/probe-3), not WooCommerce acting as an MCP *client* that plugs in and consumes tools from other MCP servers. No documentation or feature describes WooCommerce connecting outward to third-party MCP servers.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   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 WooCommerce
   WooCommerce✓fullprobed7/10

   WooCommerce documents native MCP support enabling AI assistants to interact directly with stores via a standardized protocol, confirmed by both docs and a probe of the dedicated MCP feature page. Missing for 10: independent/hands-on corroboration of the MCP server working in practice, and details on setup/configuration depth.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   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 WooCommerce
   WooCommerce✓fullprobed8/10

   WooCommerce documents an official WC-CLI for managing stores via command line (woocommerce-docs-13, woocommerce-probe-4), and separately ships native MCP support enabling AI assistants to interact with stores (woocommerce-docs-14/29/probe-3), which together satisfy the 'official CLI for AI-native workflows' story. Missing for 10: independent/hands-on verification of CLI usage in AI-agent workflows, and no explicit documentation tying the CLI itself to AI-native tooling (MCP is separate from CLI).

   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   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 drawn
   WooCommerce✓fullprobed9/10

   WooCommerce documents a full REST API (v3) with authenticated CRUD access to store data, official client libraries in multiple languages, a customer-facing Store API, a CLI, webhooks, and even a native MCP server enabling AI assistants to interact directly with stores — together this is a well-documented public API surface highly suited to AI-native/agentic use. Missing for 10: no published OpenAPI/Swagger spec (probe found 404s) and no independent hands-on developer report confirming ease of programmatic use.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “The Store API provides public Rest API endpoints for the development of customer-facing cart, checkout, and product functionality.”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.woocommerce.com/openapi.json, https://developer.woocommerce.com/swagger.json, http…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”

   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 drawn
   WooCommerce~partialclaimed6/10

   WooCommerce's REST API key generation lets admins choose an access level (Read, Write, or Read/Write) per user, and API access conforms to that WordPress user's roles/capabilities — enabling coarse-grained least-privilege credential issuance for an agent. However, this is role/permission-level scoping, not fine-grained resource- or action-specific scoping, and there's no documented agent-specific provisioning flow, key expiration/rotation, or scope granularity beyond the three access levels. Missing for 10: granular per-resource/per-endpoint scoping, dedicated agent-credential workflow, expiration/rotation controls, and independent corroboration of least-privilege usage in agentic contexts.

   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”

   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 WooCommerce
   WooCommerce✓fullclaimed8/10

   WooCommerce documents official REST API client libraries in multiple languages (JavaScript, PHP, Python, Ruby), plus a documented REST/Store API and CLI, giving AI-native developers official SDK-level building blocks. Missing for 10: independent/hands-on corroboration of SDK quality and completeness, and no unified 'official SDK' branding beyond the library list.

   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”

   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 WooCommerce
   WooCommerce✓fullclaimed9/10

   WooCommerce has native, well-documented webhook support that lets a store send automatic event notifications to any configurable URL, letting an AI-native agent subscribe to store events like order created/updated. Missing for 10: independent hands-on corroboration or examples of AI agents actually consuming these webhooks.

   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “A webhook is an event notification sent to a URL of your choice. You (or your developer) can configure a webhook that is triggered by events…”

   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
   WooCommerce—none0/10

   The evidence shows WooCommerce exposes data via REST API, MCP, and CLI for external AI tools to interact with the store, but there is no evidence of native AI-generated insights or suggestions surfaced inside the WooCommerce product itself (e.g., an AI-powered analytics/insights dashboard). MCP support enables external agents to query data but does not itself constitute in-product AI-generated insights.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   proof ↗⚑ 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 WooCommerce
   WooCommerce~partialprobed5/10

   WooCommerce documents webhooks that automatically fire event notifications in the background (docs-8, docs-26) and now ships native MCP support so AI assistants can programmatically interact with store data (docs-14, docs-29, probe-3), which together provide building blocks for background automation. However there's no evidence of a built-in 'set up an autonomous agent/workflow' feature for AI-native users beyond these primitives — automations still require external tooling or custom code via the REST API/CLI. Missing for 10: a first-party autonomous agent/automation-builder UI, documentation of persistent background AI-driven workflows, and independent confirmation that MCP-driven automations actually run unattended in production.

   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “A webhook is an event notification sent to a URL of your choice. You (or your developer) can configure a webhook that is triggered by events…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”

   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
   WooCommerce—none0/10

   Evidence shows WooCommerce supports the Model Context Protocol so external AI assistants/tools can connect to and interact with a store (docs-14, docs-29, probe-3), but this is the reverse of the story — it makes WooCommerce a target for external agents, not a built-in AI assistant inside the product that a user can delegate tasks to. No dashboard-embedded assistant, chat interface, or agentic feature is documented anywhere in the evidence pack.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   proof ↗⚑ 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 WooCommerce
   WooCommerce~partialprobed6/10

   WooCommerce documents native MCP support enabling AI assistants to interact with stores via a standardized protocol, which is the concrete mechanism for natural-language/agentic operation, and a CLI exists for scripted control. However, evidence is limited to first-party docs with no independent hands-on verification of natural-language command execution in practice. Missing for 10: independent/community validation that MCP-driven natural language commands actually work end-to-end, breadth of supported operations via MCP, and any real-world usage reports.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”

   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
   WooCommerce—none0/10

   WooCommerce publishes REST API reference documentation (docs-11, docs-27, docs-44, docs-x1/x2) but there is no evidence of an interactive, runnable API console (e.g., Swagger/OpenAPI explorer); a direct probe for OpenAPI/Swagger specs on the developer site returned 404 on all candidate paths (woocommerce-probe-2), indicating no interactive reference exists.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.woocommerce.com/openapi.json, https://developer.woocommerce.com/swagger.json, http…”

   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
   WooCommerce—none0/10

   WooCommerce documents a REST API extensively (woocommerce-docs-11, -27, -44, -x1, -x2) but a direct probe for machine-readable OpenAPI/Swagger specs at expected paths returned 404 across all candidates (woocommerce-probe-2), and no evidence pack item links to a downloadable OpenAPI/Swagger JSON/YAML file. The REST API docs site appears to be human-readable documentation, not a published machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.woocommerce.com/openapi.json, https://developer.woocommerce.com/swagger.json, http…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”

   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 to BigCommerce
   WooCommerce—none0/10

   No evidence pack item describes a sandbox/staging environment, test-mode API keys, or any mechanism for testing WooCommerce (including its REST API or MCP integration) without affecting production data. The REST API and MCP docs describe live store interaction only, with no mention of a sandbox mode.

   ⚑ 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 WooCommerce
   WooCommerce~partialclaimed4/10

   WooCommerce's REST API is explicitly versioned (v1/v2/v3 under /wp-json/wc/v3/), satisfying the 'versioned APIs' half of the story, but the evidence pack directly states 'no deprecation-timeline policy is published' for these APIs. Missing for 10: a documented deprecation/sunset timeline or migration guide between API versions, and any changelog specifying when older versions (v1/v2/legacy) will be retired.

   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”

   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 drawn
   WooCommerce—none0/10

   Evidence shows only single-store integrations (REST API, MCP server, llms.txt for developer docs) that let an agent interact with one WooCommerce store's own data — there is no evidence of a cross-merchant catalog, aggregated product feed, or answer-engine-oriented discovery layer spanning multiple WooCommerce merchants.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.woocommerce.com/llms.txt # WooCommerce Documentation This file contains a list of all documen…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”

   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
   WooCommerce~partialclaimed4/10

   WooCommerce's REST API (v3) documents CRUD access to WC data and webhooks for automatic event notifications, which could plausibly cover order status changes, and the Managing Money guide mentions issuing refunds — giving a technical path for agent-driven order lifecycle actions. However, there is no explicit documentation of an orders/returns endpoint, no RMA/returns workflow, and fulfillment is described only via the human-facing dashboard/shipping-label workflow, not an API a fully autonomous agent could drive end-to-end. Missing for 10: explicit order-status/fulfillment REST endpoints, a documented returns/RMA API, and evidence that refunds/fulfillment can be completed via API+webhooks without any admin UI step.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “A webhook is an event notification sent to a URL of your choice. You (or your developer) can configure a webhook that is triggered by events…”
   • [claimed-docs] “This includes topics such as listing transactions, viewing your payouts, issuing refunds to customers, and so on.”
   • [claimed-docs] “our Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing y…”
   • [claimed-docs] “our Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing y…”
   • [claimed-docs] “Carriers verify shipment information during the delivery process and compare the cost paid for the shipping label to the actual cost to ship…”
   • [claimed-docs] “If the amount paid for the label is incorrect, it can result in an adjustment.”

   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 WooCommerce
   WooCommerce✓fullprobed7/10

   WooCommerce documents native MCP support enabling AI assistants/tools to interact directly with stores via a standardized protocol, and separately exposes Store API endpoints for product listing, search, and cart-to-order conversion — together matching the story of a documented agent-commerce endpoint rather than scraping. Missing for 10: explicit documentation of which MCP tools/endpoints cover product discovery and cart-building specifically, no UCP mention, and no independent/hands-on validation that the MCP server works as described.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [claimed-docs] “The Store API provides public Rest API endpoints for the development of customer-facing cart, checkout, and product functionality.”
   • [claimed-docs] “Obtaining a list of products to display that can be searched or filtered... Converting a customer’s cart to an Order, collecting addresses, …”

   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 to WooCommerce
   WooCommerce~partialprobed5/10

   WooCommerce exposes a REST API (CRUD via JSON), a CLI (WC-CLI) for command-line store management, and a native MCP server for AI assistants — all of which could be scripted to perform bulk operations across many items — but no evidence explicitly documents batch/bulk endpoints or bulk-processing workflows for AI-native automation. missing for 10: explicit batch/bulk API endpoint documentation, evidence of MCP or CLI actually performing multi-item bulk actions, and any hands-on confirmation of bulk operation performance at scale.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”

   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 drawn
   WooCommerce~partialclaimed4/10

   WooCommerce documents webhooks that fire automatic event notifications to a URL when store events occur, which is a form of event-triggered automation, but there is no native in-product rules engine to define conditional actions (if X then Y) — the actual 'action' logic must live in an external receiver, not within WooCommerce itself. missing for 10: a built-in rules/automation engine for defining conditional actions, first-party workflow/automation tooling beyond webhooks, and independent confirmation of AI-driven rule creation.

   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “A webhook is an event notification sent to a URL of your choice. You (or your developer) can configure a webhook that is triggered by events…”

   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
   WooCommerce—none0/10

   WooCommerce offers webhooks, REST API, subscriptions/renewals, and a CLI, but there is no evidence of a scheduler or job orchestration feature for recurring automated workflows in an AI-native sense; nothing in the docs describes cron-like job scheduling or workflow automation.

   ⚑ 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
   WooCommerce—none0/10

   The evidence pack shows WooCommerce's REST API, webhooks, and MCP server integration for AI assistants to interact with store data, but nothing about versioning, reviewing, or rolling back automations or workflows. There's no changelog, audit trail, or rollback mechanism described for any automation actions taken via MCP, API, or webhooks.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “A webhook is an event notification sent to a URL of your choice. You (or your developer) can configure a webhook that is triggered by events…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”

   proof ↗⚑ 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
   WooCommerce—none0/10

   The evidence pack has no mention of B2B-specific capabilities like customer-specific price lists, volume/tiered pricing, quote requests, or net-terms invoicing; only generic marketplace/extension mentions and general product variation features are cited, none of which address wholesale/B2B commerce specifically.

   ⚑ 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 to WooCommerce
   WooCommerce~partialclaimed6/10

   WooCommerce docs confirm product variations/attributes (e.g., variable products with color/size attributes), subscriptions, bundles, and simple products with just name/price, plus recent 'variation galleries' improvements, supporting flexible catalog modeling. However, evidence lacks explicit mention of custom fields/metafields support (WooCommerce does support custom product meta natively via WordPress custom fields, but no doc here confirms this) or detail on how flexible/extensible attribute schemas are beyond basic variations. Missing for 10: explicit metafields/custom-fields documentation, evidence of unlimited custom attribute sets beyond simple variations, and independent/hands-on confirmation of complex catalog modeling in practice.

   • [claimed-docs] “Let customers choose from endless product variations, subscription options, single items, or bundles.”
   • [claimed-docs] “In WooCommerce, you can add a product with just a name and a price.”
   • [claimed-docs] “You’ll need to decide which categories to use for organizing and displaying your products... How will you handle products with variations, l…”
   • [claimed-docs] “How will you handle products with variations, like a shirt that comes in different colors? What attributes will you need for these products?”
   • [claimed-docs] “you can sell anything with Woo. Let customers choose from endless product variations, subscription options, single items, or bundles”
   • [claimed-docs] “you can sell anything with Woo. Let customers choose from endless product variations, subscription options, single items, or bundles.”
   • [claimed-docs] “Variation galleries now on for every store, product collection grids alignment improvements, virtual orders drop shipping…”
   • [claimed-docs] “WooCommerce 11.1 is here! Variation galleries now on for every store”
   • [claimed-docs] “WooCommerce 11.1 is here! Variation galleries now on for every store, product collection grids alignment improvements, virtual orders drop s…”

   proof ↗⚑ 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 drawn
   WooCommerce~partialprobed5/10

   WooCommerce's REST API (docs-11, docs-27, docs-44) supports bulk create/read/update/delete of product data via JSON, and WC-CLI (docs-13, probe-4) lets operations staff manage the store from the command line — both enabling bulk catalog operations without per-product UI clicks. However, the evidence pack never cites WooCommerce's native CSV product importer/exporter (a well-known core feature) or any documentation of CSV-based bulk edit workflows, so the 'CSV' half of the story is unevidenced here. Missing for 10: explicit CSV import/export documentation, evidence of bulk-edit UI/tools beyond API/CLI, and independent confirmation of large-catalog performance.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”

   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
   WooCommerce—none0/10

   The evidence pack covers products, payments, shipping labels, taxes, APIs, and marketplace extensions, but contains no mention of multi-location/warehouse inventory tracking, per-location stock adjustments, or fulfillment routing logic. WooCommerce's core inventory model (docs-4, docs-23, docs-50) is single-stock-count per product/variation with no multi-warehouse concept documented.

   • [claimed-docs] “In WooCommerce, you can add a product with just a name and a price.”
   • [claimed-docs] “You’ll need to decide which categories to use for organizing and displaying your products... How will you handle products with variations, l…”
   • [claimed-docs] “How will you handle products with variations, like a shirt that comes in different colors? What attributes will you need for these products?”

   proof ↗⚑ 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 to WooCommerce
   WooCommerce~partialclaimed6/10

   WooCommerce documents a general hook system (add_action/filter extension points for templates) and a dedicated Store API for building customer-facing cart/checkout functionality, plus a REST API and marketplace of extensions, all of which support extending checkout without forking core code. However, the evidence pack lacks specifics on checkout-field-level hooks (e.g., field customization/validation filters), discount/coupon extension points, or branding customization guidance specific to checkout — missing for 10: checkout field customization hooks, discount/validation extension documentation, and independent developer corroboration that these extension points suffice for real-world checkout customization.

   • [claimed-docs] “The Store API provides public Rest API endpoints for the development of customer-facing cart, checkout, and product functionality.”
   • [claimed-docs] “Obtaining a list of products to display that can be searched or filtered... Converting a customer’s cart to an Order, collecting addresses, …”
   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “Storefront has a lot of `add_action()` functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core …”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “Grow your business with hundreds of free and paid extensions”

   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 WooCommerce
   WooCommerce~partialclaimed4/10

   Docs confirm WooCommerce integrates with 140 region-specific gateways including WooPayments, Stripe, PayPal, Square, and Amazon Pay, which in practice enable wallet-based accelerated checkouts, but no evidence explicitly names Apple Pay or Google Pay support or describes a one-click/no-re-entry checkout experience. missing for 10: explicit documentation of Apple Pay/Google Pay support, description of accelerated/one-click checkout UX, and any hands-on confirmation that details aren't re-entered.

   • [claimed-docs] “there are 140 region-specific gateways to choose from and integrate with, including WooPayments, Stripe, PayPal, Square, and Amazon Pay”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery... there are 140 region…”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery. Beyond the basics, the…”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery. Beyond the basics, the…”

   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
   WooCommerce—none0/10

   No evidence pack item mentions abandoned cart recovery, cart abandonment tracking, or automated recovery emails/links; core WooCommerce docs cover payments, shipping, taxes, APIs, and product management but nothing about cart-abandonment recovery workflows (this is typically only available via third-party plugins/extensions not evidenced here).

   ⚑ 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 drawn
   WooCommerce~partialprobed6/10

   WooCommerce provides official developer resources: a REST API with official JS/PHP/Python/Ruby libraries, a WC-CLI tool, Storefront theme hook system, Storybook integration for UX development, and a public GitHub repo for building extensions, plus a Marketplace for distributing extensions (docs-11, docs-40, docs-13, docs-9, docs-55, woocommerce-gh-1, docs-10). However, there is no documented formal extension review/approval process or dedicated scaffolding/generator tool (e.g., a 'create-extension' CLI) beyond WC-CLI for store management, so the 'scaffolding' and 'review' parts of the story are only thinly evidenced. Missing for 10: explicit extension review/approval criteria, a dedicated project scaffolding generator, and independent developer corroboration of the distribution pipeline.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “The WooCommerce repository also includes Storybook integration that allows testing and developing in a WooCommerce-agnostic context.”
   • [github] “Once you've installed all prerequisites, the following will prepare all of the build outputs necessary for development”
   • [claimed-docs] “Grow your business with hundreds of free and paid extensions”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”

   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 WooCommerce
   WooCommerce✓fullcommunity9/10

   WooCommerce's official marketplace explicitly offers 'hundreds of free and paid extensions' plus 140 region-specific payment gateways, covering long-tail feature needs, and this is corroborated by hands-on positive community sentiment. Missing for 10: independent third-party vetting/curation quality analysis and marketplace app review/rating transparency details.

   • [claimed-docs] “Grow your business with hundreds of free and paid extensions”
   • [claimed-docs] “The Woo Marketplace has hundreds of free and paid extensions that add features and functionality to your store”
   • [claimed-docs] “The Woo Marketplace has hundreds of free and paid extensions that add features and functionality to your store.”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery... there are 140 region…”
   • [community] “I have had a lot of fun using woo and I look forward to using it more.”

   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 to WooCommerce
   WooCommerce~partialclaimed5/10

   WooCommerce's architecture is documented as extensible via PHP hooks (add_action/add_filter) that plugins/extensions use to insert custom logic into templates and core flows, and the Marketplace/extensions ecosystem confirms third-party logic can run inside the platform. However, the evidence pack only shows generic Storefront theme hooks and marketplace extension mentions — it does not document WooCommerce's core action/filter hooks specifically for discounts, shipping rules, or validation, nor any serverless/function-as-a-service execution model. Missing for 10: concrete documentation of cart/checkout/shipping filter hooks (e.g., woocommerce_calculate_totals, woocommerce_package_rates) or a serverless functions feature, and independent developer corroboration of using hooks for discount/shipping/validation logic.

   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “Storefront has a lot of `add_action()` functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core …”
   • [claimed-docs] “Storefront has a lot of add_action() functions ... These allow you to insert sections of content using HTML, PHP, Javascript into its core t…”
   • [claimed-docs] “Grow your business with hundreds of free and paid extensions”
   • [claimed-docs] “The Woo Marketplace has hundreds of free and paid extensions that add features and functionality to your store”

   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 WooCommerce
   WooCommerce✓fullprobed9/10

   WooCommerce's REST API (v3, versioned under /wp-json/wc/v3/) supports full CRUD on products, orders, and refunds via standard HTTP verbs and JSON, with official client libraries in multiple languages and role-based key scoping; docs explicitly cover refunds and order/fulfillment management, and webhooks allow event-driven triggering. Missing for 10: no independent/hands-on developer corroboration of complex workflows (e.g., fulfillment triggers) beyond vendor docs, and no published OpenAPI spec or deprecation policy for versioning.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [claimed-docs] “our Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing y…”
   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.woocommerce.com/openapi.json, https://developer.woocommerce.com/swagger.json, http…”

   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 drawn
   WooCommerce✓fullprobed8/10

   WooCommerce documents both a full REST API (v3, with official JS/PHP/Python/Ruby libraries) and a dedicated Store API purpose-built for headless cart/checkout/product frontends, enabling a fully custom headless storefront to be built against documented, versioned endpoints. Missing for 10: no first-party official headless frontend framework/starter kit evidenced, and no independent hands-on report confirming a production headless build.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “The Store API provides public Rest API endpoints for the development of customer-facing cart, checkout, and product functionality.”
   • [claimed-docs] “Obtaining a list of products to display that can be searched or filtered... Converting a customer’s cart to an Order, collecting addresses, …”
   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.woocommerce.com/openapi.json, https://developer.woocommerce.com/swagger.json, http…”

   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 to BigCommerce
   WooCommerce—none0/10

   The evidence pack mentions a general extensions marketplace and REST/Store APIs, but nothing documents native or extension-based syncing of a single catalog to external marketplaces, social commerce channels, or shopping feeds (e.g., Google Shopping, Facebook/Instagram, Amazon). Missing for 10: any documentation of channel-sync extensions or feed integrations, evidence of catalog export/sync workflows, or hands-on confirmation of multi-channel listing.

   • [claimed-docs] “Grow your business with hundreds of free and paid extensions”
   • [claimed-docs] “The Woo Marketplace has hundreds of free and paid extensions that add features and functionality to your store”
   • [claimed-docs] “The Woo Marketplace has hundreds of free and paid extensions that add features and functionality to your store.”

   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 BigCommerce
   WooCommerce—none0/10

   The evidence pack shows tax setup, shipping, and payment gateway docs, but contains no mention of multi-currency pricing, localized/translated storefronts, or international duties/customs handling — the core elements of this story are absent. This is a fair question for an e-commerce platform (many competitors ship native multi-currency/localization), so it applies, but no supporting evidence exists.

   ⚑ 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 drawn
   WooCommerce—none0/10

   The evidence pack contains no mention of a point-of-sale product, in-person selling, or POS-catalog sync capability for WooCommerce; all evidence covers online store features (payments, shipping, taxes, APIs, mobile app for managing the online store). This is a fair axis for an ecommerce platform, but no evidence shows WooCommerce delivers it, so it is 'none' rather than 'na'.

   ⚑ 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 WooCommerce
   WooCommerce~partialprobed7/10

   WooCommerce documents a broad, versioned REST API (products, orders, customers, refunds, webhooks, coupons), a separate Store API for cart/checkout, an official WC-CLI, and even native MCP support for AI agents — strong evidence of API-driven parity with the UI. However, the docs don't confirm 1:1 coverage for every admin UI action (e.g., full store-setup wizard, extension marketplace management, granular tax/shipping configuration screens), and there's no independent hands-on test confirming complete UI/API parity. Missing for 10: explicit documentation or independent verification that every admin-UI setting/workflow (not just core commerce objects) is exposed via API, and confirmation of parity for extension-specific UI features.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “The Store API provides public Rest API endpoints for the development of customer-facing cart, checkout, and product functionality.”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”

   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 WooCommerce
   WooCommerce~partialclaimed6/10

   WooCommerce is self-hosted and open-source, with explicit messaging about 'full control of your data' and a REST API (JSON, versioned, documented) that allows programmatic export of products, orders, and customer data. However, evidence shows migration guides only for moving data *into* WooCommerce, not exporting/leaving, and no explicit CSV/data-portability export tool or 'leave the platform' guide is documented. Missing for 10: explicit data-export/portability documentation for leaving the platform, evidence of built-in CSV/data dump tools, and independent confirmation that a full data export actually works in open non-proprietary formats.

   • [claimed-docs] “WooCommerce is the open-source commerce platform for WordPress that gives you full control: of your checkout, your data, your costs.”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “Ready to switch platforms? Our migration guides help you confidently move your store to WooCommerce... transfer your data, and unlock the fl…”
   • [claimed-docs] “Ready to switch platforms? Our migration guides help you confidently move your store to WooCommerce.”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”

   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

3. ai-native userRead the product's source under an open license

   weight 2 · round to WooCommerce
   WooCommerce✓fullclaimed9/10

   WooCommerce is explicitly open-source (GPL-licensed WordPress plugin) with its source publicly hosted on GitHub, and its own site states it 'gives you full control: of your checkout, your data, your costs' as an open-source commerce platform. missing for 10: no explicit citation of the license file/terms text itself, only general open-source claims and the GitHub repo link.

   • [claimed-docs] “WooCommerce is the open-source commerce platform for WordPress that gives you full control: of your checkout, your data, your costs.”
   • [github] “Once you've installed all prerequisites, the following will prepare all of the build outputs necessary for development”

   proof ↗⚑ flag

   BigCommerce—none0/10

   BigCommerce is a proprietary SaaS platform; no evidence indicates its core source code is published under an open license (only design system and SDKs like the Checkout SDK/design system are noted as open source, not the platform itself). missing for 10: any statement that BigCommerce's core product source is open-licensed or publicly viewable.

   • [claimed-docs] “Our open source design system. Use to build BigCommerce Apps that feel native inside the control panel.”

   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 WooCommerce
   WooCommerce~partialclaimed6/10

   Docs confirm WooCommerce bundles basic payment methods (cards, BACS, checks, COD) plus access to 140 region-specific third-party gateways (WooPayments, Stripe, PayPal, Square, Amazon Pay), showing strong third-party gateway choice. However, evidence does not explicitly document multi-currency charging/checkout support (this typically requires separate extensions), so the 'charge in multiple currencies' half of the story is unevidenced. Missing for 10: explicit multi-currency checkout/gateway documentation, independent/hands-on confirmation of gateway switching working smoothly.

   • [claimed-docs] “there are 140 region-specific gateways to choose from and integrate with, including WooPayments, Stripe, PayPal, Square, and Amazon Pay”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery... there are 140 region…”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery. Beyond the basics, the…”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery. Beyond the basics, the…”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery.”

   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 WooCommerce
   WooCommerce~partialclaimed5/10

   WooPayments is documented as Woo's own integrated payment solution with transaction listing, payouts, and refunds handled directly in the dashboard (woocommerce-docs-5/24/37/43/52), which supports the 'no third-party gateway' framing. However, the evidence never publishes concrete card processing rates or documents dedicated fraud-prevention/chargeback tooling — the docs only gesture at 'managing money' generally, and WooCommerce's broader payments story explicitly leans on 140 external gateways (docs-1/18/41/47) rather than emphasizing WooPayments exclusivity. Missing for 10: published card rate sheet, explicit fraud/dispute tooling documentation, and confirmation WooPayments avoids third-party processor plumbing entirely.

   • [claimed-docs] “This includes topics such as listing transactions, viewing your payouts, issuing refunds to customers, and so on.”
   • [claimed-docs] “our Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing y…”
   • [claimed-docs] “our Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing y…”
   • [claimed-docs] “Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing your …”
   • [claimed-docs] “Once WooPayments is up and running, our Managing Money guide explains how money can flow into and out of your site.”
   • [claimed-docs] “there are 140 region-specific gateways to choose from and integrate with, including WooPayments, Stripe, PayPal, Square, and Amazon Pay”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery... there are 140 region…”

   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 to WooCommerce
   WooCommerce~partialclaimed4/10

   WooCommerce is self-hosted on WordPress, so by nature the store owner controls the hosting infrastructure and therefore the physical location of data — docs-16 states WooCommerce gives 'full control of your data.' However, there is no explicit first-party documentation of region-selection controls, data-residency settings, or compliance tooling addressing where data is stored. missing for 10: explicit data-residency/region-selection documentation, compliance certifications (e.g., GDPR data location controls), and any admin-facing region config feature.

   • [claimed-docs] “WooCommerce is the open-source commerce platform for WordPress that gives you full control: of your checkout, your data, your costs.”

   proof ↗⚑ 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 userControl data retention and deletion

   weight 2 · round drawn
   WooCommerce—none0/10

   No evidence pack items address data retention policies, deletion controls, GDPR-style export/erasure tools, or AI-specific data lifecycle controls; REST API docs describe generic CRUD capability but not a data retention/deletion governance feature. This axis applies to an e-commerce platform handling customer PII, but no documentation demonstrates such 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 to WooCommerce
   WooCommerce~partialclaimed5/10

   WooCommerce is built as a plugin on top of WordPress, and docs confirm this tight integration ("open-source commerce platform for WordPress," "If you have a WordPress site, adding Woo takes just minutes"), which implies the WordPress admin (with its native Pages, Posts/blog, and Media Library) is shared with product management. Storefront theme docs also show content can be inserted into store templates via hooks. However, no evidence explicitly describes a unified admin workflow for managing blog posts, pages, and media alongside products, or shows this in a hands-on merchant walkthrough. Missing for 10: explicit documentation or screenshots of managing WordPress pages/posts/media from the same dashboard as products, and independent confirmation of this workflow.

   • [claimed-docs] “WooCommerce is the open-source commerce platform for WordPress that gives you full control: of your checkout, your data, your costs.”
   • [claimed-docs] “If you have a WordPress site, adding Woo takes just minutes!”
   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “Storefront has a lot of `add_action()` functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core …”

   proof ↗⚑ 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 WooCommerce
   WooCommerce~partialclaimed6/10

   WooCommerce/Storefront documents a genuine templating layer (add_action hooks for HTML/PHP/JS insertion into core templates) and the GitHub repo shows a local build process plus Storybook integration for developing/testing in isolation, giving developers a documented customization and local-preview path. However there is no explicit documentation of a version-controlled theme deployment workflow (e.g., CI/CD, staging-to-production theme push) — that relies on generic WordPress/Git practices not directly evidenced here. Missing for 10: documented deployment/versioning workflow for themes, explicit local preview tooling beyond Storybook, end-to-end example of a version-controlled theme release.

   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “Storefront has a lot of `add_action()` functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core …”
   • [claimed-docs] “Storefront has a lot of add_action() functions ... These allow you to insert sections of content using HTML, PHP, Javascript into its core t…”
   • [claimed-docs] “The WooCommerce repository also includes Storybook integration that allows testing and developing in a WooCommerce-agnostic context.”
   • [github] “Once you've installed all prerequisites, the following will prepare all of the build outputs necessary for development”
   • [claimed-docs] “WooCommerce introduces Purple, its first official block theme for beta testing, offering extensive customization options and modern template…”

   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 BigCommerce
   WooCommerce~partialclaimed5/10

   WooCommerce offers designed themes (Storefront, and the new block theme 'Purple' with 'extensive customization options and modern templates') and initial setup guidance around homepage design, menus, and site structure, suggesting a storefront can be launched and styled. However, the core documented customization mechanism for Storefront explicitly requires inserting HTML/PHP/JavaScript via add_action() hooks, which is code-based rather than no-code, and evidence for genuine no-code block-editor customization (drag-and-drop sections, branding controls) is thin and limited to a single beta announcement. Missing for 10: detailed no-code section/layout editor documentation, evidence of drag-and-drop branding tools, and independent hands-on confirmation that non-developers can fully customize without code.

   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “Storefront has a lot of `add_action()` functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core …”
   • [claimed-docs] “Storefront has a lot of add_action() functions ... These allow you to insert sections of content using HTML, PHP, Javascript into its core t…”
   • [claimed-docs] “WooCommerce introduces Purple, its first official block theme for beta testing, offering extensive customization options and modern template…”
   • [claimed-docs] “The first decisions you need to make when setting up a store are about homepage design, menus, site structure... If you have a WordPress sit…”
   • [claimed-docs] “The first decisions you need to make when setting up a store are about homepage design, menus, site structure, and payment and shipping opti…”

   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 WooCommerce
   WooCommerce~partialclaimed5/10

   WooCommerce marketing docs claim 'live shipping rates from leading carriers' and 'options to print labels at home' bundled with the platform, but the shipping doc itself only discusses label cost verification, not a live-rate/checkout integration or tracking dashboard, and label printing/live rates in practice typically require third-party extensions (e.g., WooCommerce Shipping) not detailed here. Missing for 10: concrete documentation of the checkout carrier-rate integration flow, label purchase workflow details, and shipment tracking UI, plus independent/hands-on confirmation this works out-of-the-box.

   • [claimed-docs] “Save time with automated tax calculations, live shipping rates from leading carriers, options to print labels at home”
   • [claimed-docs] “Save time with automated tax calculations, live shipping rates from leading carriers, options to print labels at home, and the mobile app fo…”
   • [claimed-docs] “options to print labels at home, and the mobile app for iOS and Android”
   • [claimed-docs] “Carriers verify shipment information during the delivery process and compare the cost paid for the shipping label to the actual cost to ship…”
   • [claimed-docs] “If the amount paid for the label is incorrect, it can result in an adjustment.”

   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 WooCommerce
   WooCommerce~partialclaimed4/10

   WooCommerce docs mention 'automated tax calculations' as a marketing feature and a core guide for enabling/configuring taxes and adding tax rates, but the evidence pack shows only manual tax-rate table setup, not per-jurisdiction automatic rate updates, VAT-specific handling, or built-in filing-ready tax reports. Missing for 10: evidence of automatic jurisdiction rate updates (e.g. via a tax service integration), VAT-specific compliance handling, and generation of filing-ready tax reports.

   • [claimed-docs] “This guide explains how to enable and configure taxes in WooCommerce, add tax rates, and understand each available setting.”
   • [claimed-docs] “Save time with automated tax calculations, live shipping rates from leading carriers, options to print labels at home”
   • [claimed-docs] “Save time with automated tax calculations, live shipping rates from leading carriers, options to print labels at home, and the mobile app fo…”

   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