How to use this practical guide
This guide brings together three modules for store owners: setting up and running the store, keeping it secure and making it fast. Use it as a reference: start with the module that solves what your store needs right now.
Setting up and running the store
The foundation for a working WooCommerce store: pages, catalogue, checkout, payments, shipping and admin routines.
A compass for the day-to-day of your store
Organise operations into simple routines for orders, stock, support, open issues and tests. Record important changes to reduce errors and make follow-up easier.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
The pair that powers your store
Understand how WordPress organises content, pages and brand identity, while WooCommerce adds the catalogue, cart, checkout, orders and customers.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
The technical pillars of your store
Review your domain, hosting, theme, catalogue, payment methods, shipping and security before you launch or scale.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
More design freedom with Elementor Pro
Use the visual builder to customise the pages that decide the buying journey, while keeping the experience clear and responsive.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
The minimum structure of a store
Set up and test the essential pages: home, shop, product, cart, checkout, order confirmation and My Account.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Home page: how to create and set it up
Set the home page in WordPress and present your offer, categories, products, selling points and calls to action in an order that helps the visitor.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Shop page: how to set it up
Adjust the catalogue view, including columns, sorting, filters and the balance between browsing by category and discovering products.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Product page: how to set it up
Build complete product pages with title, images, price, description, variations, stock, lead time, delivery and the arguments that support a buying decision.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Category page: how to set it up
Create categories people understand, organise products consistently and write descriptions that guide the customer without getting in the way.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Cart page: how to edit it with Elementor
Review items, quantities, coupons, shipping and next steps. The cart should show what the customer needs without adding distractions before checkout.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Shipping rates: zones, flat rates and live carrier rates
Set your ship-from address and each product’s weight and dimensions, create shipping zones for the regions you serve, connect live rates from carriers such as USPS, UPS, DHL or Royal Mail where they are available, and test the calculation with different postcodes.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Checkout page: how to edit it with Elementor
Keep checkout focused, with only the essential fields, a reliable order summary, and payment methods and delivery information in plain view.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Payment methods: setting up Stripe, PayPal or WooPayments
Understand what a payment gateway does, connect your account correctly, add the local payment methods your customers expect, and test approvals, declines, refunds and notifications before you open for sales.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Order confirmation page: how it works
Use the confirmation to reassure the customer: order received, next steps, payment, delivery and how to track the purchase.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
My Account page: how to edit it with Elementor
Organise orders, addresses, account details, downloads and support so customers can handle common tasks without contacting you.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
General store settings: currency, units and country
Set the currency, selling countries, store location, weight and dimension units and other global settings before you add your catalogue.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Product variations: colour, size and other options
Tell attributes apart from variations, create valid combinations and keep price, stock, image and availability consistent for every option.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Customer reviews and social proof
Turn on reviews, set moderation rules and use real feedback to answer doubts and build confidence in the purchase.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Coupons and discounts: how to create and set them up
Define the amount or percentage, eligible products, usage limit, expiry date and restrictions of each coupon to protect your margin.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Automatic order emails: how to customise them
Adjust the sender, branding, content and triggers of transactional emails to keep the customer informed at every step.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Invoices and sales tax: how to handle them in your store
Decide how you will issue invoices, set up tax rates for the regions you sell to (sales tax, VAT or GST), and define how documents are generated, sent and stored.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Security, continuity and response
Routines to protect customers, orders, data and admin access, with prevention, monitoring and an organised response to incidents.
SSL certificate: what it is and how to confirm it is active
Confirm HTTPS, the certificate’s validity, the absence of mixed content and that product, cart and checkout pages load securely.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Store backups: WPvivid, UpdraftPlus and server backups
Back up both files and the database, keep off-site copies and test restores. The 3-2-1 rule is a good guide for a resilient strategy.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Passwords and users: how to protect access
Use unique passwords, two-factor authentication and the minimum role each person needs. Review access whenever your team changes.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Security plugins: Wordfence, Sucuri and alternatives
Compare firewall, scanning, blocking, alerts and reputation. Set up one security plugin instead of stacking redundant tools.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Updates and clean-up of themes and plugins
Update with a backup and a test, remove inactive extensions you do not use and keep WordPress, theme and plugins on compatible versions.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Monitoring: know when your store goes down
Set up external monitoring and alerts to detect downtime before the problem turns into a customer complaint.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Cloudflare: protection and speed
Get to know DNS, CDN, caching, bot protection and the rules that need special care on the cart, checkout and My Account pages.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
GDPR and privacy laws: the minimum your store needs
Keep a privacy policy, clear information on how data is processed, cookie consent where it is required, contact channels and practices that match what your store actually collects, whether you fall under GDPR, CCPA or another law.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Fraud prevention: how to spot suspicious orders
Recognise warning signs, review inconsistent details and use your gateway’s tools before you approve risky orders.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Incident response plan
Define the first hours of an incident: preserve evidence, limit access, restore safely, communicate and document decisions.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Activity log: know who did what
Record relevant changes in the admin to investigate failures, track access and build a useful audit trail.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Returns and refunds policy
Explain time limits, conditions, channels and refunds in plain language, in line with the consumer law of the countries you sell to.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Chargebacks: what to do when a payment is disputed
Keep proof of the order, communication, delivery and acceptance so you can respond in time and reduce avoidable losses.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
SPF and DKIM: protecting your store’s email
Set up domain authentication to improve delivery of transactional emails and reduce spoofing and spam.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Performance, experience and conversion
A practical sequence for cutting load time without breaking your e-commerce operation: server, theme, images, cache, database and measurement.
Why performance matters: speed, SEO and conversion
Connect load time to experience and sales. Use Core Web Vitals to keep an eye on LCP, INP and CLS in a practical way.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Hosting: the foundation of performance
Assess server resources, PHP version, plan limits and the signs that your store needs better infrastructure.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Lightweight theme: how to choose and why it matters
Prefer a lean, well-maintained visual base that is compatible with WooCommerce to cut unnecessary CSS, JavaScript and features.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Image optimisation: WebP and the right sizes
Resize before uploading and use modern formats and lazy loading to reduce page weight without hurting how products look.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Image optimisation plugins
Automate compression and conversion with tools such as Smush, ShortPixel or Imagify, checking quality and the images you already have.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Avoiding unnecessary plugins
Run a regular audit: every extension should have a purpose, active maintenance, compatibility and an acceptable impact on the store.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Caching with WP Rocket
Set up page caching with the right exclusions for cart, checkout and My Account, and test the purchase flow after every change.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Cloudflare for performance
Use the CDN, minification and image features with careful rules so that dynamic WooCommerce content is never cached by mistake.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Database clean-up and optimisation
Review revisions, transients, tables and accumulated data with a backup in place and clear criteria, so you do not remove data the store needs.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
How to measure performance
Compare before and after with PageSpeed Insights and GTmetrix; note the URL, device, metrics and changes applied to avoid guesswork.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Third-party scripts without slowing the store
Keep pixels, analytics, chat and external widgets under control, prioritising deferred loading, consent and the real impact of each script.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Performance in Elementor
Avoid too many widgets, animations, nested sections and global features; turn on the optimisations that suit your project.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Web fonts: how to load them without delaying the page
Limit families and weights, host fonts locally when you can and keep a clear typographic hierarchy with fewer external requests.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.
Object caching: Redis and Memcached
Understand when an object cache layer helps larger stores, and check server compatibility before turning it on.
Next step: apply this in a staging environment whenever the change could affect payments, delivery, customer data or store availability.