Website Builder E-Commerce Features

E-commerce is not a single feature. A platform must support the complete operating cycle: product setup, payment, tax, delivery, customer communication, refunds, reporting, security and data export. Test that cycle before selecting a website builder.

Start with the product and fulfilment model

A shop selling ten simple products has different needs from one selling subscriptions, downloads, personalised items, regulated goods or thousands of variants. Document product data, stock locations, delivery regions, return rules and required integrations before comparing platforms.

Core commerce capabilities

E-commerce workflow checks
Area	Questions to test	Hidden complexity
Products and variants	Can the system represent every option and price rule?	Variant limits, bundles, personalisation and bulk updates
Checkout and payments	Are required payment methods and currencies supported?	Processor fees, platform transaction charges, failed payments and fraud checks
VAT and tax	Can the business apply, display and report the correct treatment?	Digital goods, cross-border sales and accounting integration
Shipping and collection	Can rates, zones, weights and local collection be configured?	Multiple warehouses, split orders and carrier integrations
Orders and refunds	Can staff fulfil, amend and refund safely?	Partial refunds, returns, exchanges and audit trail
Customer accounts	Are accounts necessary and can access be recovered?	Privacy, consent, account migration and deletion
Stock	Does inventory stay accurate across every sales channel?	Point-of-sale, marketplaces, bundles and overselling
Reporting	Can finance and operations obtain useful exports?	Reconciliation, tax, product margin and external reporting
Integrations	Do accounting, fulfilment and marketing connections work reliably?	App cost, data protection, support ownership and vendor changes

Understand the full fee stack

Separate the platform plan, payment-processing rate, any additional transaction charge, paid apps, premium theme, domain, email, development, support and migration cost. Use the expected order value and volume to model fees rather than comparing only monthly subscriptions.

Built-in commerce versus an app

A built-in system can be easier to support, while an app may provide specialised functions. When an app is essential, confirm who handles failures, what data it receives, how it is backed up and whether the business can export its records.

Test exceptional cases

Place a normal order and a failed-payment order.
Issue a full and partial refund.
Test an out-of-stock product and a product with several variants.
Check customer and staff notifications.
Export orders, products and customers in a usable format.
Confirm VAT, delivery and returns with the business’s adviser where needed.
Document how the shop would continue if a key app or integration failed.

When to use a specialist commerce platform

If the website is operationally a shop rather than a brochure site with a few products, give commerce depth, reporting, integrations and support more weight than page-design convenience. A simple builder can be excellent for a small catalogue but expensive to replace after processes become complex.

Customer-service operations

Test the tasks that occur after payment: address changes, cancellations, partial fulfilment, refunds, returns, exchanges and complaints. The quality of these administrative tools affects staff time and customer experience as much as the checkout design.

Permissions and fraud risk

Give staff only the access needed for their role. Confirm how the platform handles administrator security, payment-account access, suspicious orders and changes to payout details. A shop should not rely on one shared owner login.

Subscriptions and memberships

Recurring billing adds failed-payment recovery, cancellation rights, plan changes, access control and migration complexity. Verify exactly which system stores the subscription and whether the records can be exported or transferred.

Performance and catalogue growth

Test realistic product images, filters and scripts. A store that is fast with five sample products may behave differently with hundreds of items, reviews and marketing integrations. Confirm any product, variant, storage or API limits relevant to the growth scenario.

Data protection and retention

Map customer, order and marketing data across the platform, payment provider, apps and fulfilment services. Define retention, access and deletion processes and make sure the privacy information reflects the actual suppliers used.

Example: a small shop with product variants

A clothing shop may have colour and size variants, stock by variant, seasonal discounts, returns and several delivery methods. The trial should import representative products, create an out-of-stock case, issue a partial refund and export data. A platform that handles one simple product beautifully may still fail the real catalogue and after-sales process.

Sources and date checked

Platform features, plan names and commercial terms can change. The official sources below were checked on 21 July 2026. Recheck them before choosing or renewing a plan.

Practical next step: Process a realistic order from product selection through refund and data export, then calculate the full fee stack at expected order volume.

Keep the decision under your control

Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.