Topic hub

WordPress E-Commerce

WordPress can support a small online shop, catalogue, booking flow or membership business, but the software is only one part of the operating system. A reliable store also needs product data, payments, tax and delivery…

1 published guides0 subtopicsUpdated 21 July 2026

Start here

The main guide for this topic

Comparison

WooCommerce Payment Gateways for UK Businesses

A payment gateway should be chosen as an operational and financial service, not merely as a checkout logo. A UK business needs to assess customer payment methods, fees, settlement, refunds, disputes, …

Open the complete guide →

Published guides

Articles in this section

Comparison12 August 2026

WooCommerce Payment Gateways for UK Businesses

A payment gateway should be chosen as an operational and financial service, not merely as a checkout logo. A UK business needs to …

Read guide →

About this section

Start with the business model, not the plugin

Define what is being sold, where customers are located, how fulfilment works and which events must be recorded. A shop selling ten physical products within the UK has a different risk profile from a subscription service, a digital-download business or a catalogue with quotation requests.

E-commerce requirements to settle before implementation
Decision	Questions to answer
Products	Physical, digital, variable, made-to-order, subscription or service?
Customers	Consumers, businesses or both; UK only or international?
Money	Currencies, VAT treatment, refunds, deposits and recurring payments?
Fulfilment	Shipping zones, collection, booking, access delivery or manual handling?
Operations	Who manages orders, stock, customer messages and failed payments?
Evidence	What records are required for disputes, refunds, tax and support?

Choose the smallest suitable commerce layer

WooCommerce is the usual starting point because it is the main open-source commerce platform for WordPress and keeps store data within the WordPress environment. It is not automatically the best answer for every business. A simple payment link, booking service or hosted checkout may be safer when the website does not need a full product catalogue and order-management system.

Use WooCommerce when products, orders, customer accounts and store content need to work together inside WordPress.
Use a specialist plugin when the primary need is bookings, memberships, courses or digital delivery and the specialist workflow matters more than a conventional basket.
Use a hosted payment or commerce service when low maintenance, provider support and a simpler compliance boundary matter more than deep WordPress control.

Treat extensions as part of the architecture

Each gateway, shipping integration, subscription add-on and marketing connector adds code, data flows and an update dependency. Before installing an extension, record its purpose, owner, renewal date, data processed, support route and removal plan. Do not install overlapping plugins “just in case”.

A free core plugin can still lead to ongoing costs for hosting, premium extensions, developer support, email delivery, fraud controls and monitoring. Compare the first-year and steady-state cost, not only the download price.

Build a complete test order

Create representative products, taxes and delivery rules.
Place orders using every enabled payment method in its test environment.
Confirm customer, administrator and fulfilment emails arrive and contain correct information.
Test failed, cancelled, refunded and partially refunded orders.
Check stock, coupons, guest checkout, mobile checkout and accessibility.
Export orders and confirm the business can retrieve its records without the original developer.

Do not launch after testing only the happy path. Failed callbacks, duplicate payments, address errors and refund handling are where operational weaknesses usually appear.

Protect live order data during changes

A live store changes continuously. Copying production to staging can expose personal data, while restoring an old full-site backup can overwrite new orders. Use a documented maintenance process that separates code and configuration changes from live transactional data. Before a major change, decide exactly what would be restored and how orders received during the change window would be reconciled.

Use this section as a route

Use the setup guide for the initial store configuration and acceptance test.
Use the payment-gateway guide to compare checkout, settlement, fees and operational support.
Use the maintenance guide for updates, scheduled actions, logs and order reconciliation.
Use the plugin comparison when the business may be better served by a specialist commerce tool.

Common launch mistakes

Do not launch with placeholder legal pages, untested tax rules or a single administrator owned by the developer. Avoid installing several extensions that promise the same function, and do not assume that a completed checkout proves fulfilment, refunds and accounting exports are correct.

Running live payments before email and order-status tests are complete
Restoring a full old database over new orders
Using product descriptions copied from suppliers without checking accuracy
Leaving test coupons, accounts or gateway credentials enabled

Practical next step

Write a one-page operating brief covering products, customers, payments, fulfilment, refunds, order ownership and the required records. Select software only after that brief is agreed.

Sources and date checked

This guide was checked on 21 July 2026. WordPress, plugins, hosting platforms and commercial terms change, so confirm the current documentation and licence details before making a material change.