E-Commerce Platforms & Shop Systems

BigCommerce

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 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

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Merchant v1.0 · The B2B Seller v1.0 · The Developer v1.0 · The Operations Lead v1.0 · The Data Protection Officer v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 5 Oct 2026

Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Data Protection Officer

Weighted verdict

The shop holds customers, addresses and buying histories, and the checkout is full of third parties. Wants the subprocessor list, consent handling that survives a complaint, deletion that executes against order history, and an answer on where the CDN and analytics sit.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Data Protection Officer

Catalogue & checkout

How this is scored

Products, variants, pricing rules and the path to payment — the part that either converts or does not.

0 — Flat product list with one price and no variants; checkout is a form and one payment method.

3 — Variants and categories with a standard checkout and two or three payment methods, but no bundles, no tiered pricing and no guest checkout worth the name.

5 — Full variant matrix, product bundles, tiered and customer-group pricing, guest checkout, and the payment methods a German shop needs including invoice and direct debit.

8 — Configurable products, per-channel pricing, promotions and vouchers with rules, a checkout that can be customised without a rebuild, and payment via the major providers plus 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.

Report an error

The Data Protection Officer

The captured checkout pages show a one-page checkout that can be forked on GitHub with full source access, BNPL, digital wallets and one-click, plus customer-group pricing, account-specific catalogs, promotions and upsells inside checkout, and abandoned-cart email recovery shipped alongside multi-currency and multi-language. We found no public information on an A/B-testable checkout or a rule-driven promotions engine, which is what keeps this off the top band. 1 3 4

Report an error

Tax & German legal correctness

How this is scored

VAT determination, OSS, B2B reverse charge, and the checkout requirements German law actually imposes — judged on what the platform does, not on a plugin someone could buy.

0 — A single VAT rate applied everywhere; no B2B handling, no country logic, no legal-text handling in checkout.

3 — Per-country VAT rates configurable by hand, net prices for B2B possible with effort, and legal texts as free-form pages.

5 — Automatic VAT by destination and customer type, VAT-ID validation with reverse charge, gross and net display per customer group, and the mandatory checkout elements (order button wording, withdrawal policy, price indications) handled.

8 — OSS thresholds tracked and reported, correct invoicing 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.

Report an error

The Data Protection Officer

The tax documentation states plainly that the Rates and Zones API configures manual taxes, with per-country, per-subdivision and per-postal-code zones, multiple rates per zone, and tax-inclusive or exclusive price display per customer group and zone. That is hand-built VAT rather than vendor-maintained correctness: we found no public information on VAT-ID validation, reverse charge, OSS reporting, e-invoicing, or the German checkout elements such as order-button wording and withdrawal policy, and cross-border automated taxes appear only via shipping partners. 5 6 9

Report an error

Extensibility & developer surface

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 — Fixed templates, no app ecosystem, no API.

3 — Theme editing within limits and a small app store; a read-mostly API and no local development story.

5 — Custom themes with a template language, an app or plugin ecosystem, a documented REST API, and webhooks for the core order events.

8 — Full storefront API for headless builds, an extension framework with its own lifecycle, staging 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.

Report an error

The Data Protection Officer

There is a genuine headless surface — REST and GraphQL APIs across storefront, admin, account and B2B, downloadable OpenAPI specs, starter apps, and a checkout a team can fork and rebuild — which sits well above a basic plugin shop. We found no public information on staging environments, on documented rate limits beyond the session-sync lockout, or on version control for themes, so this stops short of the top band. 3 7 8

Report an error

Order operations & back office

How this is scored

What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.

0 — An order list and an email; stock is a number nobody trusts, returns are manual.

3 — Order statuses and basic stock, one shipping integration, and returns handled by hand.

5 — Order workflow with partial shipments, multi-warehouse stock, named carrier integrations with label printing, and a returns process in the system.

8 — Multi-channel order intake, automated fulfilment routing, supplier and dropshipping flows, and maintained interfaces to named ERP and accounting systems.

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.

Report an error

The Data Protection Officer

Multi-channel intake is well evidenced — marketplace listings, point-of-sale sync, multi-storefront, 3PL and warehouse-system connections, and a Shipping Manager with real-time carrier quotes and location-based methods. Returns surface only as a nine-app marketplace category, and we found no public information on partial shipments or carrier label printing; from my seat, order data running through that many third-party apps also spreads customers' personal data across the chain. 1 3 9 10

Report an error

Data ownership & exit

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 — Export is a partial CSV; order history and customer records cannot leave intact, and hosting is the vendor's alone.

3 — CSV export of products and customers, order history partial, no self-hosting, no documented migration path.

5 — Complete export of catalogue, customers and orders via API or dump, documented deletion, and a stated data-return commitment.

8 — Full-fidelity export including media and order documents, 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.

Report an error

The Data Protection Officer

Moving data in is documented — 500,000 product, customer and order records via a migration app — and Data Erasure is listed as a security module heading, but we found no public information on export completeness, on deletion executing against order history, or on a data-return commitment. Hosting is on the vendor's Google Cloud platform with no alternative offered, so the pages captured do not document what leaving actually costs. 2 11 12

Report an error

European sovereignty

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.

0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.

3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — CDN, analytics, payment routing, support tooling — are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, complete subprocessor list published, 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.

Report an error

The Data Protection Officer

The vendor is BigCommerce, Inc. with copyright held by BigCommerce Pty. Ltd., hosting runs on Google Cloud Platform with no server region stated, and the subprocessor list exists only as an uncaptured document heading — so with 20+ embedded payment providers in the checkout we cannot see where a single one of them processes. Data-protection artefacts such as a DPO contact, a transfer impact summary and an international transfer whitepaper exist as headings, but we found no public information on EU hosting, an EU entity, or where CDN, analytics and payment routing sit, and the US cloud provider in the chain raises Cloud Act exposure. 1 2 4

Report an error

Pricing transparency

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 monthly headline exists, but transaction fees, mandatory apps or hosting costs are unstated — the invoice is unknowable from the page.

5 — Tier prices public with billing period stated and transaction fees given, but at least one commonly needed piece (a required app, hosting, payment gateway rate) is unpriced.

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.

Report an error

The Data Protection Officer

The only pricing facts captured are a no-credit-card free trial and the statement that there are no payment fees for orders through 20+ embedded providers, with PayPal card rates described as pre-negotiated but no figures given. We found no public plan prices, billing periods, VAT treatment or order limits, so a merchant cannot compute a real annual cost from these pages. 1 4

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built 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
Ownership	Not determined	—	uncited Report an error
Data residency	Not determined	—	uncited Report an error
Subprocessors	US CLOUD Act reach ⚠ unverified	0/2 pts	2 Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 29 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Subprocessors. Google Cloud Platform appears only as a trust-center section heading under Infrastructure rather than in the subprocessor list or DPA (both exist as document categories but their contents were not captured), and no server region is stated
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.

37 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
11 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
9 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
2 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
1 support 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

Do you know more about BigCommerce? Tell us Report an error on this page

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 29 Sep 2026 Details →
2 Security / trust page — found from the homepage security.bigcommerce.com Checked 30 Sep 2026 Details →
3 Catalogue & checkout — found from sitemap www.bigcommerce.com Checked 1 Oct 2026 Details →
4 Catalogue & checkout — found from sitemap www.bigcommerce.com Checked 1 Oct 2026 Details →
5 Tax & German legal correctness — found from sitemap docs.bigcommerce.com Checked 1 Oct 2026 Details →
6 Tax & German legal correctness — found from sitemap docs.bigcommerce.com Checked 1 Oct 2026 Details →
7 Extensibility & developer surface — found from sitemap docs.bigcommerce.com Checked 1 Oct 2026 Details →
8 Extensibility & developer surface — found from sitemap docs.bigcommerce.com Checked 1 Oct 2026 Details →
9 Order operations & back office — found from sitemap www.bigcommerce.com Checked 1 Oct 2026 Details →
10 Order operations & back office — found from sitemap www.bigcommerce.com Checked 1 Oct 2026 Details →
11 Data ownership & exit — found from sitemap www.bigcommerce.com Checked 1 Oct 2026 Details →
12 Data ownership & exit — found from sitemap www.bigcommerce.com Checked 1 Oct 2026 Details →