BigCommerce
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by BigCommerce, Inc. · www.bigcommerce.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
BigCommerce at a glance
- Vendor
- BigCommerce, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates BigCommerce 2.5/5, the mean of 6 judges. BigCommerce scores highest at catalog and checkout with 8-9: a one-page checkout with wallets, one-click and buy-now-pay-later that can be restyled in the control panel or forked on GitHub with full source access, plus customer-group and account-specific pricing and native purchase orders, net terms and invoice payments for B2B. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
BigCommerce scores highest at catalog and checkout with 8-9: a one-page checkout with wallets, one-click and buy-now-pay-later that can be restyled in the control panel or forked on GitHub with full source access, plus customer-group and account-specific pricing and native purchase orders, net terms and invoice payments for B2B. Extensibility follows at 7-8 on REST and GraphQL APIs, OpenAPI specifications and headless starter solutions. Tax and legal holds at 4, with no public information on VAT ID validation, reverse charge, OSS reporting or German checkout requirements. Sovereignty sits at 2-3: the captured pages give an Austin, Texas address and Google Cloud Platform infrastructure with no region stated. Pricing transparency scores 1-2 — no plan price, billing period or tier limit appears on any captured page, only a free trial with no credit card and no payment fees for 20+ embedded payment providers. Judges split on data control and exit at 3-5: some credit the documented APIs and a 27-app data-transfer category as an export route; others find no documented path out or public information on data return at cancellation.
Speaks for it
- Checkout is customizable at every level, from no-code controls in the control panel to a GitHub fork with full source access.
- REST and GraphQL APIs cover storefront, admin and B2B surfaces, with downloadable OpenAPI specifications and documented rate-limit headers.
- Purchase orders, quote-to-cart, net terms and invoice payments are documented as native to the B2B Edition.
- Order intake covers Amazon, Walmart and eBay, plus 150+ channels through Feedonomics, with BOPIS, POS sync and 3PL connections.
- Multi-currency with real-time exchange rates and multi-language selling run on one storefront.
Held against it
- We found no public plan price, billing period or tier limit on any captured page, so an annual cost is not computable from public information.
- We found no public information on VAT ID validation, reverse charge, OSS reporting, e-invoicing or German checkout requirements such as order-button wording.
- We found no public information on data residency, an EU hosting option or an EU contracting entity; the pages name Google Cloud Platform as infrastructure with no region stated.
- Migration is documented in one direction — in, up to 500,000 product, customer and order records — with no public information on data return or deletion at cancellation.
- Returns, ERP and accounting arrive through marketplace apps rather than the back office, with no public information on a maintained interface to a named system such as DATEV.
Best for
- You sell to business buyers and need account-specific pricing, purchase orders, quote-to-cart, net terms and invoice payments documented as native.
- Your team wants a headless or custom storefront build against documented REST and GraphQL APIs, or wants to fork the checkout outright.
- You sell across channels — Amazon, Walmart, eBay and 150+ more through Feedonomics — with BOPIS or 3PL fulfilment in the mix.
- You sell internationally and want multi-currency with real-time exchange rates and multi-language on one storefront.
Avoid if
- You sell into the EU and need a stated data residency, an EU contracting entity or an EU hosting option — ask the vendor: the public pages we read do not show it
- You must compute your annual platform cost before committing — no plan price, billing period or tier limit is public, and PayPal processing rates are described only as pre-negotiated rates that decrease as you grow, with no figures.
- You run a German or cross-border B2B shop that depends on VAT ID validation, reverse charge or OSS reporting — the documented tax system covers zones, rates and per-customer-group price display, and we found no public information on the rest.
- Your exit plan requires a vendor-documented migration path out or contractual data return at cancellation — the documented migration runs into the platform, and data erasure appears only as a listed security control.
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 4 of 5 |
| Tax & German legal correctness | 2 of 5 |
| Extensibility & developer surface | 4 of 5 |
| Order operations & back office | 3 of 5 |
| Data ownership & exit | 2 of 5 |
| European sovereignty | 1 of 5 |
| Pricing transparency | 1 of 5 |
Catalogue & checkout
Show reasoningHide reasoning
How this is scored
Products, variants, pricing rules and the path to payment — the part that either converts or does not.
0 — Not a shop: no product catalogue and no checkout of its own.
3 — A product catalogue with categories and a checkout that takes payment through at least one provider.
5 — Products with variants, discounts or vouchers, guest checkout, and several payment methods including those German buyers expect (PayPal, invoice or direct debit) through named providers.
8 — Tiered and customer-group pricing, bundles or configurable products, rule-based promotions, per-channel or per-market pricing, abandoned-cart recovery, a checkout customisable without a rebuild, and buy-now-pay-later where offered.
10 — Merchandising and checkout are the product: rule-driven pricing and promotions, A/B-testable checkout, multi-currency and multi-language as standard, and conversion features (abandoned cart, one-page checkout) shipped rather than bolted on.
The Merchant
This is the part they get right for a seller like me: the checkout can be forked on GitHub or adjusted in the control panel without a rebuild, abandoned carts get automated recovery emails, and one-page checkout with digital wallets, one-click and buy-now-pay-later ships out of the box. Customer-group and account-specific pricing plus promotions in checkout are documented, and multi-currency with real-time exchange rates and multi-language selling are stated. I found no public information on A/B testing the checkout or on bundles and variant handling, so I stop just below the top. 1 3 4 4
The B2B Seller
Customer-group and account-specific pricing, purchase orders, net terms and invoice payments are documented as native, and the one-page checkout can be adjusted in the control panel or forked outright with full source access. Abandoned-cart emails, buy-now-pay-later, multi-currency with real-time exchange rates and multi-language storefronts are also on the record. This is a shop that has met the trade buyer. 3 4 4 1
The Developer
The checkout pages document one-page checkout with BNPL and digital wallets, customer-group pricing, account-specific catalogs, automated abandoned-cart emails, and no-code checkout controls alongside the ability to fork the checkout on GitHub — a checkout customisable without a rebuild. Multi-currency at real-time exchange rates and multi-language on one storefront push this into the upper band; I found no public information on A/B-testable checkout, tiered pricing, bundles, or a rule-driven promotions engine. 3 4 4 1
The Operations Lead
Abandoned-cart recovery emails, a one-page checkout with wallets, one-click and buy-now-pay-later, customer-group and account-specific pricing, and a checkout that can be restyled in the control panel or forked on GitHub with full source access — that is conversion machinery, not a basic cart. We found no public information on tiered volume pricing, bundles or A/B-tested checkout variants, which keeps it off the top step. 1 3 4 1
The Data Protection Officer
Customer-group and account-specific pricing, abandoned-cart emails, buy-now-pay-later, digital wallets and a checkout restylable in the control panel or for forkable on GitHub with full source access are all documented, alongside one-page checkout and guest-checkout controls. Multi-currency with real-time exchange rates and multi-language storefronts are stated too. We found no public information on A/B testing of the checkout or bundles and configurable products, which is what separates the top level. 3 4 1 1
The Skeptic
The checkout pages document one-page checkout with digital wallets, one-click, buy-now-pay-later and guest-checkout behaviour, a checkout SDK with custom field injection and full source access, and even forking the checkout on GitHub. Customer-group and account-specific pricing, automated abandoned-cart emails, and multi-currency with real-time exchange rates plus multi-language are all documented. We found no public information on A/B-testable checkout or bundle products. 3 4 4 1
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, invoicing, and the checkout requirements German law imposes (Button-Lösung, Widerrufsrecht, Preisangabenverordnung) — judged on what the platform documents it does or ships as a maintained extension.
0 — No tax handling at all; prices carry no VAT logic and the merchant calculates tax outside the platform.
3 — VAT rates configurable per country or product, with prices shown gross or net and legal texts placed as pages in the checkout.
5 — VAT by destination country with gross and net display per customer group, B2B with VAT ID and reverse charge, and the German checkout requirements (order button wording, withdrawal policy, price indications) handled by the platform or a named official extension.
8 — VIES validation of VAT IDs, OSS thresholds tracked or OSS reporting data provided, invoices issued from orders with correct content per case including reverse-charge notes, small-business and third-country handling, and e-invoicing (XRechnung/ZUGFeRD) for B2B orders.
10 — Tax and legal correctness are maintained by the vendor rather than the merchant: rates and thresholds updated as the law moves, OSS reporting produced, every invoice case correct out of the box, and documented conformity a lawyer could review.
The Merchant
Tax zones by country, subdivision or postal code with multiple rates per tax class, and gross or net price display per zone and per customer group are documented, including whether prices on orders and invoices include tax. For a German shop the rest is on me: I found no public information on VAT ID validation or reverse charge for B2B, OSS reporting, or the German checkout requirements such as order-button wording, withdrawal policy and price indications. 5 6
The B2B Seller
Tax zones by country, subdivision and postal code are documented, with prices shown tax-inclusive or tax-exclusive per zone and per customer group — so net display for business customers is achievable — and zones apply across every storefront. The captured pages show nothing on VAT-ID validation, reverse charge, OSS or the German checkout formalities, and invoicing appears only as a price-display setting on orders and invoices. 5 6
The Developer
The developer docs show tax zones defined by country, subdivision and postal code, multiple rates per zone across taxation authorities, per-customer-group gross or net price display, and a documented fallback when a tax service is unavailable — VAT by destination with gross and net display per customer group. I found no public information on VAT ID validation, reverse charge for B2B buyers, OSS reporting, the German checkout requirements, or e-invoicing formats. 5 6
The Operations Lead
The developer documentation shows destination-based tax with zones by country, subdivision and postal code, inclusive or exclusive price display per customer group, guest geolocation, and multiple rates per zone per tax class — solid VAT plumbing. But we found no public information on VAT ID validation, reverse charge, OSS, e-invoicing or the German checkout requirements; the cross-border pages promise automated taxes and duties without detail, and accounting is left to a marketplace category rather than a named offering. 5 6 9 10
The Data Protection Officer
The developer documentation shows tax zones by country, subdivision or postal code, several rates per zone each tied to a tax class, tax-inclusive or exclusive display per customer group, and zone determination from the customer address or guest geolocation. We found no public information on VAT ID validation, B2B reverse charge, OSS reporting, e-invoicing, or the German checkout duties — order-button wording, withdrawal policy and price indication — so the merchant assembles those alone. 5 6
The Skeptic
The tax APIs document zones by country, subdivision and postal code with multiple rates per tax class and multiple taxation authorities, tax-inclusive or exclusive display per zone and per customer group, and guest-zone detection by geolocation. We found no public information on VAT ID validation, reverse charge, OSS reporting, e-invoicing, or the German checkout requirements such as order-button wording and the withdrawal policy. 5 6
Extensibility & developer surface
Show reasoningHide reasoning
How this is scored
Themes, apps, APIs and headless — whether the shop can be shaped to the business, and at what cost in lock-in.
0 — A closed shop builder: no themes to edit, no apps or plugins and no API.
3 — Themes adjustable in an editor and a set of apps or plugins to add features.
5 — Custom themes with a template language or code access, an app or plugin ecosystem, and a documented API with webhooks for order events.
8 — A storefront API for headless builds, an extension framework with its own lifecycle, staging or development environments, version control for themes, and documented rate limits.
10 — A platform a team can own: headless-first APIs, open-source or source-available core, plugin architecture with a real dependency model, local development and CI supported, and upgrade paths that do not orphan customisations.
The Merchant
The developer story is real: GraphQL and REST APIs for storefront and admin, downloadable OpenAPI specifications, documented rate limits and error codes, headless starter solutions, and a checkout whose source you can fork and rebuild. Themes are editable in HTML/CSS or a visual editor, and the app marketplace lists well over a thousand apps. I found no public information on staging environments or version control for themes. 7 8 8 4
The B2B Seller
Documented REST and GraphQL APIs cover storefront, admin and B2B surfaces with downloadable OpenAPI specs, pagination, filtering and rate-limit headers spelled out, plus a headless path with starter solutions and a checkout that can be forked on GitHub with full source. A large app marketplace and visual builders sit on top. We found no public information on staging environments or a source-available platform core. 3 7 8 8
The Developer
The API surface is the strongest part of this platform: REST and GraphQL storefront, admin and B2B APIs with downloadable OpenAPI specifications, documented rate-limit headers, a headless overview with starter apps, and a checkout you can fork on GitHub with full source access. Catalyst ships as versioned packages, which gives the storefront build a version-control story, but I found no public information on local development, staging environments for the platform itself, a plugin dependency model, or how platform upgrades treat a forked checkout — so this stops short of the top band. 3 7 8 8 2
The Operations Lead
REST and GraphQL APIs across storefront, admin and B2B, downloadable OpenAPI specifications, documented rate-limit headers, a headless path with starter apps, and full source access to the checkout give a real developer surface a team can build against. Staging appears only as third-party apps in the marketplace and we found no public information on theme version control, so the shop can be shaped but the full lifecycle is not all in the vendor's hands. 3 7 8 8 12 4
The Data Protection Officer
REST and GraphQL APIs cover storefront, admin, integrations and B2B, with downloadable OpenAPI specifications, documented rate limits and a defined response when a client exceeds them, and the checkout can be forked on GitHub with full source access. Headless storefronts, starter solutions and a WordPress plugin are documented as well. We found no public information on local development with CI, a plugin dependency model or an open platform core, which is what the top level describes. 8 7 8 3 4
The Skeptic
Headless builds are documented with REST and GraphQL storefront APIs, downloadable OpenAPI specifications, published rate-limit headers and 429 handling, and starter solutions; the checkout SDK ships full source access, can be forked on GitHub, and Catalyst packages are versioned. We found no public information on webhooks for order events, staging environments, or an open-source core. 3 7 8 8 2
Order operations & back office
Show reasoningHide reasoning
How this is scored
What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.
0 — No order handling in the product; orders leave as emails or exports to be processed elsewhere.
3 — An order list with statuses, stock counts per product, and shipping rates set up in the shop.
5 — Order management with status emails, stock tracking, named carrier integrations or label printing, and refunds or returns handled in the system.
8 — Partial shipments and partial refunds, multi-warehouse or multi-location stock, multi-channel or marketplace order intake, fulfilment routing, dropshipping, and maintained interfaces to named ERP and accounting systems (DATEV among them for German merchants).
10 — The shop is the front of an operation: real-time stock across channels and warehouses, returns and refunds fully worked including partials, ERP integration the vendor maintains, and operational reporting a merchant runs the business from.
The Merchant
The back office holds up: a shipping manager with real-time carrier quotes plus flat, weight or value-based rates, named shipping partners, buy-online-pickup-in-store tied to POS and inventory, marketplace listings on Amazon, Walmart and eBay, and 600-plus integrations across ERP, CRM, PIM and WMS. Returns appear as an app category rather than a documented native refund flow, and I found no public information on partial shipments, multi-warehouse stock, or maintained connections to named ERP and accounting systems such as DATEV. 9 9 1
The B2B Seller
Shipping Manager with real-time carrier quotes, BOPIS, point-of-sale sync, marketplace intake on Amazon, Walmart and eBay, and app categories for ERP, warehouse, 3PL and returns are all on record, with purchase orders, quote-to-cart and net terms native to the B2B edition. The pages show nothing on partial shipments, refunds or label printing handled in the system itself, and ERP and accounting links appear as marketplace categories — 41 ERP and 52 accounting apps — rather than named, vendor-maintained interfaces; we found no public information on a DATEV connection. 9 9 3 10 1
The Developer
Shipping Manager with real-time carrier quotes and weight or value-based rates, marketplace intake on Amazon, Walmart and eBay plus 150+ channels through Feedonomics, 3PL and warehouse-system connections, and BOPIS with POS inventory sync take this past the middle band. Returns appear as a marketplace category of nine apps rather than a documented in-system flow, and I found no public information on partial shipments or partial refunds. ERP, CRM, PIM and WMS integrations are claimed at 600+, but the captured pages give no named maintained systems. 9 10 9 10 1
The Operations Lead
Order intake is strong: listings on Amazon, Walmart and eBay, a shipping manager with real-time carrier quotes, named shipping partners, 3PL and warehouse-system connections, and POS/BOPIS keeping inventory and orders consistent across channels. But returns appear only as an app category, and we found no public information on partial shipments, partial refunds, label printing or a maintained interface to a named ERP or accounting system — ERP is a count of six hundred plus integrations, not a name I can wire to. 1 3 9 10 9 10 1
The Data Protection Officer
Order intake from Amazon, Walmart and eBay marketplaces, a shipping manager with real-time carrier quotes and named partners such as ShipperHQ, connections to 3PLs and warehouse systems, and app categories for returns, ERP and accounting are all documented. Returns and ERP arrive through third-party apps rather than the back office itself, and we found no public information on partial shipments, partial refunds, label printing or a maintained DATEV interface. 9 9 10 1 3
The Skeptic
Shipping Manager with real-time carrier quotes, flat-rate and weight- or value-based rates, BOPIS with POS and inventory integration, 3PL fulfilment, multi-address shipping, and marketplace intake from Amazon, Walmart and eBay are documented, with 600+ ERP, CRM, PIM and WMS integrations claimed. Returns appear only as a marketplace category of nine apps, and we found no public information on partial refunds, partial shipments, or a named accounting interface such as DATEV. 9 9 10 1
Data ownership & exit
Show reasoningHide reasoning
How this is scored
Whether the catalogue, customers and order history remain the merchant's: export completeness, hosting choice, and what leaving actually costs.
0 — The terms state that the merchant's data cannot be exported or is not returned on cancellation.
3 — CSV export of products and customers, or of orders, from the admin.
5 — Export of catalogue, customers and orders documented (CSV, API or dump), with data deletion or return on cancellation stated in the terms or help centre.
8 — Full-fidelity export including media and order documents, a documented migration path in and out, self-hosting or a choice of hosting partner, and no metering that prices a migration out of reach.
10 — Ownership is structural rather than promised: open-source or source-available platform the merchant can run anywhere, database-level access, documented migration in both directions, and contractual data return.
The Merchant
Getting in is well documented: a migration app moves up to 500,000 product, customer and order records from Shopify, WooCommerce or Magento with post-import error reporting, and a data processing agreement plus data backup and erasure controls are listed in the trust center. Leaving is the open question — I found no public information on exporting the catalogue, customers and order history back out, or on what the terms promise when you cancel. 11 2
The B2B Seller
Migration in is documented end to end — a migration app, premium services or an agency, handling up to 500,000 product, customer and order records — and the open APIs plus a 27-app data-transfer category give a documented route for catalogue, order history and platform moves. We found no public information on export of media and order documents, on self-hosting or hosting choice, or on data return on cancellation; data erasure is listed as a security control, not a contractual exit term. 11 12 8 2
The Developer
Migration in is documented in detail — from Shopify, WooCommerce and Adobe Commerce, up to 500,000 product, customer and order records, with post-import error reporting — and the documented REST and GraphQL APIs with pagination give a route to exporting catalogue, customers and orders. I found no public information on a documented migration path out, data return or deletion on cancellation in the terms, or any hosting choice beyond the vendor's own platform, which is what leaving would actually cost. 8 11 8
The Operations Lead
The migration pages document moving up to 500,000 product, customer and order records in from Shopify, WooCommerce or Adobe Commerce with post-import error reporting, and the APIs cover catalog and order retrieval. What leaving actually costs — export completeness, data return on cancellation — we found no public information on, beyond a data-erasure line in the security pages. 7 11 2
The Data Protection Officer
Migration in is documented in detail — a migration app from Shopify, WooCommerce and Adobe Commerce carrying 500,000 product, customer and order records with post-import error reporting — and catalogue and orders are retrievable through the documented APIs, with data erasure listed among the platform's security controls. We found no public information on data return or deletion on cancellation, a documented migration path out, or self-hosting, so an exit rests on APIs and third-party migration services. 11 8 2 12
The Skeptic
The documented migration runs in one direction: an app, premium services or an agency to move up to 500,000 product, customer and order records into BigCommerce from Shopify, WooCommerce or Adobe Commerce. We found no public information on export of catalogue, customers or orders out of the platform, or on data return and deletion at cancellation, beyond a Data Erasure heading in the security program. 2 11 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (CDN, analytics, payment routing, support tooling) is unstated or partly non-EU.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that puts the shop entirely under the merchant's control.
The Merchant
The evidence points away from Europe: the corporate address is in Austin, Texas under BigCommerce Holdings, Inc., the copyright sits with BigCommerce Pty. Ltd., and the stated infrastructure is Google Cloud Platform, with no EU hosting option shown. A data processing agreement, a transfer impact summary and an international data transfer whitepaper are listed in the trust center, but I found no public information on where customer and order data actually reside. 2 1 2
The B2B Seller
The contracting entity is proven to be BigCommerce Holdings, Inc. of Austin, Texas, with infrastructure on Google Cloud Platform and no EU hosting option, EU entity or EU representative documented. A data processing agreement, a transfer impact summary and a subprocessor section are offered in the trust center, alongside an International Data Transfer Whitepaper that contemplates transfers out of the region — thin comfort when selling into the EU. 1 2 2
The Developer
The captured pages give a legal name and Austin, Texas address for BigCommerce Holdings, Inc., while the copyright line reads BigCommerce Pty. Ltd. — different entity names on different pages — and hosting is stated as Google Cloud Platform with no data-residency statement. A Data Processing Agreement and transfer-impact summary are listed in the trust center, though access may require a request; I found no public information on an EU hosting option or an EU contracting entity. 2 1 2
The Operations Lead
The trust center lists a Data Processing Agreement, a Data Protection Officer, a transfer impact summary and a subprocessor list, though the downloads may sit behind an access request, and hosting is on Google Cloud with no region named. The company address is in Austin, Texas and the legal name is BigCommerce Holdings, Inc.; we found no public information on an EU hosting option or EU contracting entity, so the European elements are the compliance artifacts and the rest of the chain is unstated. 2 1 2
The Data Protection Officer
The captured pages give a company address in Austin, Texas under BigCommerce Holdings, Inc. and a copyright held by BigCommerce Pty. Ltd., with Google Cloud Platform named as infrastructure and no region stated. A data processing agreement, a transfer impact summary and a subprocessors document are listed in the trust center, though only by title — the locations of the CDN, analytics and payment routing are not shown — and we found no public information on an EU hosting option or EU contracting entity. Two 2026 security notices about third-party app providers are a live reminder of why that chain needs to be visible. 1 2 2 1
The Skeptic
The captured pages give the vendor an Austin, Texas address under BigCommerce Holdings, INC., with copyright held by BigCommerce Pty. Ltd., and name Google Cloud Platform as the infrastructure. We found no public information on data residency or an EU hosting option, and the DPA, subprocessor list and transfer-impact summary appear only as titles in a trust center that gates downloads behind an access request. 2 4 1 2
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the real annual cost — licence, transaction fees, apps, hosting — from public pages alone. The category where the headline price is least often the invoice.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier.
5 — Prices for the main tiers public with the billing period stated and the main inclusions per tier listed.
8 — Every tier priced publicly including transaction or revenue-share rates, order or GMV limits, and the cost of the extensions most shops need; VAT treatment and minimum term stated.
10 — Complete price computability: annual cost derivable for a given order volume and GMV including licence, transaction fees, hosting and typical extensions — and for open-source platforms, an honest statement that the licence is free and where the money actually goes.
The Merchant
A free trial with no credit card, and no payment fees for 20+ embedded payment providers, are public commitments, and app prices are at least browsable by free or paid. But I found no public information on plan prices, billing periods or tier limits, and the PayPal processing rates are described only as decreasing as you grow — I cannot compute what a year of selling would actually cost me. 4 12 1
The B2B Seller
The captured pages state a free trial with no credit card and no payment fees across 20+ embedded payment providers, and describe PayPal card processing rates only as pre-negotiated rates that decrease as you grow, without figures. No plan price, billing period or tier inclusions appear on any page we read, so a merchant cannot compute an annual cost from public pages. 4 1 1
The Developer
On the captured pages I found no public information on tier prices, billing periods or VAT treatment; what is public is the free trial without a credit card, the statement that 20+ embedded payment providers process without payment fees, and a free/paid filter in the app directory. The API documentation references plan limits such as a 500-product example, so volume limits exist but the captured pages do not price them, and the pre-negotiated PayPal rates are described only as decreasing as you grow, with no figures. 4 12 8 1
The Operations Lead
The captured pages state the trial is free with no credit card, that orders through 20+ embedded payment providers carry no payment fees, and that pre-negotiated PayPal card processing rates decrease as you grow — with no figures given. We found no public prices for any plan tier, no order or revenue limits, and the app marketplace offers only Free and Paid filters without amounts, so a merchant cannot compute a real annual cost from these pages. 4 12 1 1
The Data Protection Officer
What is public: a free trial without a credit card, the statement of 20+ embedded payment providers without payment fees, and a description of pre-negotiated PayPal card-processing rates that decrease with volume, without figures. We found no public plan prices, billing periods, order limits or transaction rates on any captured page, so an annual cost is not computable from public information. 4 1 12 1
The Skeptic
We found no public plan price, billing period or minimum term on any captured page; the pricing facts are a free trial with no credit card, '20+ Embedded Payment Providers without payment fees', and PayPal rates described only as pre-negotiated and declining with volume, with no figures. A plan limit surfaces only in developer documentation as an API error citing a 500-product example, so a merchant cannot compute an annual cost from these pages. 1 4 8 1
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?Only the document's title is listed in the trust center and downloads may be gated behind its access-request flow. |
1/1 pts | 2 Report an error |
| Transfer impact assessment |
Published
unverified
Why unverified?Only the summary's title appears in the trust center and access to the document may require a request. |
1/1 pts | 2 Report an error |
Questions about BigCommerce
Is BigCommerce European?
Not determined: the vendor’s pages as captured do not say where BigCommerce is based.
Where does BigCommerce store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does BigCommerce have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to BigCommerce?
As of 18 Nov 2026, the panel rates JTL-Shop (3.5/5), Saleor (3/5) and Shopware (3/5) highest among the other 28 E-Commerce Platforms & Shop Systems products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is JTL-Shop (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: BigCommerce alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. Only the document's title is listed in the trust center and downloads may be gated behind its access-request flow.
- Weak sourcing — Transfer impact assessment. Only the summary's title appears in the trust center and access to the document may require a request.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 119 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 42 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 20 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.bigcommerce.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 2 Security / trust page — found from the homepage security.bigcommerce.com Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
- 3 Catalogue & checkout — found from sitemap www.bigcommerce.com Checked 16 Nov 2026 Details →
- 4 Catalogue & checkout — found from sitemap www.bigcommerce.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 5 Tax & German legal correctness — found from sitemap docs.bigcommerce.com Checked 16 Nov 2026 Details →
- 6 Tax & German legal correctness — found from sitemap docs.bigcommerce.com Checked 16 Nov 2026 Details →
- 7 Extensibility & developer surface — found from sitemap docs.bigcommerce.com Checked 16 Nov 2026 Details →
- 8 Extensibility & developer surface — found from sitemap docs.bigcommerce.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 9 Order operations & back office — found from sitemap www.bigcommerce.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 10 Order operations & back office — found from sitemap www.bigcommerce.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 1 Oct 2026 Details →
- 11 Data ownership & exit — found from sitemap www.bigcommerce.com Checked 16 Nov 2026 Details →
- 12 Data ownership & exit — found from sitemap www.bigcommerce.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 1 Oct 2026 Details →