Reviews
Part of Ecommerce platforms: operational checks before choosing
Shopify and WooCommerce core: contract records, no winner
A records-based ecommerce platforms product comparison: what supplier documents establish for Shopify and WooCommerce core, and why no overall winner emerges.
This ecommerce platforms product record finds no overall winner. Public documents can establish what a supplier offers and on what terms, but not fitness for an England merchant's configuration. The common case is one England seller of its own ordinary physical goods to UK adults.
What to take away
- No overall winner emerges because public documents cannot show fitness for one England merchant's configuration.
- Supplier records establish contract terms and billing, but not speed, security, accessibility or merchant results.
- Payment, product safety, privacy and accessibility each need separate specialist approval before selection.
- An option failing a mandatory gate is removed; HOLD means a document, configuration or specialist decision is missing.
- Buying on this table would be premature until whole-life cost and reversible exit evidence exists.
What the records support
The table sets three routes side by side on contract, hosting and upkeep, using only facts that supplier or public records state. Shopify and WooCommerce core differ most in who carries the technical work, which the Shopify and WooCommerce comparison covers in more depth.
| Route | Contract and billing | Hosting and upkeep | Exit | Unresolved before selection |
|---|---|---|---|---|
| Shopify | Contracting party depends on the billing address of the store; subscription fees are billed in advance every 30 days | Subscription service; the store may be hosted by Shopify or on a third party website | Terminate by contacting Support; domain matters then become the merchant's responsibility | Configured payments, app dependencies, accessible journey, full exit and recovery |
| WooCommerce core | Core software from the plugin repository; separate contracts for each supplier the merchant adds | Merchant must identify hosting and every additional supplier | No platform termination; exit follows each hosting and supplier contract | Full stack, gateway, maintenance, support, order exit and assurance evidence |
| Manual baseline | Existing contracts and internal ownership | Existing process and people | No new supplier to leave | Actual effort, error, access, continuity and customer-journey evidence |
You are contracting with the Shopify contracting party for your billing address, which for an England merchant is Shopify International Limited, incorporated in Ireland, and subscription fees are billed in 30 day intervals under the Shopify Terms of Service. For WooCommerce, the core plugin is released under the GNU General Public License by Automattic's WooCommerce project and distributed from the WordPress.org plugin repository; the merchant owns the update routine, so check that production runs a current version. Prices are outside the scope of this record because commercial structures and required components are not yet comparable.
Payment options on the records
The payment route decides who holds the money contract. Shopify names its default gateways; WooCommerce core does not bundle a gateway, so the merchant contracts one separately and the record names none.
| Route | Named payment options | Account holder |
|---|---|---|
| Shopify | PayPal Express Checkout and Shopify Payments, the default gateways | The store owner activates and maintains the accounts |
| WooCommerce core | Gateway chosen and contracted by the merchant | The merchant |
| Manual baseline | Existing bank or card arrangement | The merchant |
Apply independent pass gates
The seller identity, product evidence and customer contract must work together, as the market entry checklist sets out. Plan the cancellation journey and refund timing around the cancellation window in the rules table below.
The platform cannot decide whether one merchant's presentation satisfies the applicable rules.
Payment authorisation, capture, refund, dispute and settlement need separate state tests. If the design involves receiving money for onward transfer, use the perimeter guidance in the FCA Handbook and obtain specialist advice. Accounting records and VAT treatment need their own approvals.
Product safety, privacy and accessibility are also non-compensating. The consent journey needs its own test on each route. No platform page approves a store.
Rules to name before selection
Each regulated matter needs a named rule behind its test. Name the rule in the record, then run the test.
Rules named for this comparison
- Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013
- PECR (enforced by the Information Commissioner's Office)
- FCA Handbook perimeter guidance (PERG)
- General Product Safety Regulations 2005
- Equality Act 2010
- Shopify Data Processing Addendum
Tests to run against those rules
- Check the 14-day cancellation period for delivered goods under the Consumer Contracts Regulations 2013.
- Check that no non-essential cookie is set on the homepage before consent (ICO guidance on PECR).
- Take specialist advice if the design receives money for onward transfer.
- Hold evidence that each product is safe.
- Run a keyboard journey from basket to confirmation.
- Record who is controller and who is processor.
Turn unknowns into tests
Leave buyer weights and thresholds blank. For each route, test the same synthetic catalogue, order exceptions, product withdrawal, keyboard journey, privilege change and export restoration. Specify expected evidence before running a test, and record the UK regulations each test touches.
An option that fails a mandatory gate is removed. HOLD means a document, configuration or specialist decision is absent. If more than one option passes, compare whole-life cost and reversible exit. The manual route stays in the test as the baseline set out in the best providers guide. Until that evidence exists, buying on this table would be premature.
Before you act
- Assign a named UK ecommerce procurement reviewer.
- Confirm seller identity, product evidence and customer contract work together.
- Test payment authorisation, capture, refund, dispute and settlement states.
- Check product safety, privacy and accessibility with specialist advice.
- Run the same synthetic catalogue and order exceptions on each route.
- Specify expected evidence before running any test.
Common questions
Why does the comparison find no overall winner?
Public documents can establish what a supplier offers and on what terms, but not fitness for an England merchant's configuration. No account, purchase, checkout, payment, fulfilment, refund, support, accessibility or restore test supports the table, so no row establishes speed, availability, security, accessibility or merchant results.
What must happen before a platform is selected?
The seller identity, product evidence and customer contract must work together. Payment authorisation, capture, refund, dispute and settlement need separate state tests. Product safety, privacy and accessibility are non-compensating and need their own approvals. An option failing a mandatory gate is removed, and HOLD means a document, configuration or specialist decision is absent.
How should a reader turn the unknowns into tests?
Leave buyer weights and thresholds blank. For each route, test the same synthetic catalogue, order exceptions, product withdrawal, keyboard journey, privilege change and export restoration. Specify expected evidence before running a test. If more than one option passes, compare whole-life cost and reversible exit.
