Build an Online Store with WordPress

Who this build fits and what the first version needs

This build fits a business selling its own products through one storefront. A first version needs a clean catalog, product pages, cart, checkout, customer emails, payment gateway, shipping or digital-delivery rules, tax configuration, policies, and an admin order process. If independent sellers need their own dashboards and earnings, you need a multi-vendor marketplace instead.

WooCommerce is the standard starting point when you want WordPress to sell physical or digital products. Its current documentation covers setup from installation through orders, while product management includes categories, inventory, shipping data, variations, and reviews. That breadth is useful, but it also means you should decide the store model before enabling every option.

What to know before you start

• Decide what you sell: physical products, digital files, services, subscriptions, or a mix. Product type changes shipping, tax, inventory, and fulfillment.
• Choose the countries you will sell to before configuring shipping and taxes.
• Write product data standards for titles, images, variations, attributes, dimensions, inventory, and categories.
• Choose a payment provider supported in your business location and target customer locations.
• Document the order lifecycle from payment to fulfillment, refund, cancellation, and customer support.

Recommended plugin stack

Plugin choices for this guide: There are several WordPress ecommerce platforms. Compare them in our best WordPress ecommerce plugins roundup. This guide uses WooCommerce. For SEO, compare the best WordPress SEO plugins; this guide uses Rank Math. For transactional email, compare the best WordPress SMTP plugins; this guide uses Bit SMTP. If you need a custom enquiry or wholesale-style request form, compare the best form builders before adding one.

How to build an online store with WordPress step by step

Follow WooCommerce in the same order customers will use the store: setup, products, payments, fulfilment, then a full test order.

Step 01: Install WooCommerce and run the setup flow

Install and activate WooCommerce. Complete the onboarding/setup checklist with the store address, currency, product type, selling locations, and basic business details.

Check: WooCommerce shows the store setup tasks and the store currency/location are correct.

Step 02: Add one complete product

Go to Products → Add New. Add a clear product name, description, price, product image, inventory/SKU, shipping data if physical, and variations only where customers actually choose an option.

Check: The product page shows the correct price, stock state, image, and Add to Cart button.

Step 03: Configure payments

Go to WooCommerce → Settings → Payments and connect the payment method you will use. Use test/sandbox mode where supported. Keep only payment methods you can actually fulfil and reconcile.

Check: A test payment can reach the expected success or failure state without exposing live credentials.

Step 04: Configure shipping

Go to WooCommerce → Settings → Shipping. Create shipping zones for the places you sell to, then add the shipping methods and rates that apply to each zone. If the store is digital-only, skip physical shipping.

Check: A test address receives the correct shipping option and rate at checkout.

Step 05: Configure tax behavior

Set the tax display and calculation method that matches your business. Use official tax guidance or professional advice for legal obligations rather than copying another store. Confirm prices are shown consistently on product, cart, and checkout pages.

Check: A test order produces the expected tax result for at least one location you sell to.

Step 06: Place a complete test order

Open the store in a private browser window, add the product to cart, complete checkout, and inspect WooCommerce → Orders. Verify the order status, customer email, payment state, stock reduction, shipping method, and tax.

Check: The customer and admin records match the test purchase from start to finish.

Step 07: Prepare the store for launch

Remove test products/orders where appropriate, switch payment gateways out of test mode only when ready, confirm policy/contact pages, check product SEO, test mobile checkout, and verify backups before accepting real orders.

Check: A real customer can browse, buy, pay, and receive confirmation without any test-mode messages or broken steps.

What to know before launch

An online store is an operational system. Updates, backups, fraud monitoring, stock accuracy, shipping cutoffs, refunds, customer support, and payment reconciliation matter as much as design. Avoid installing checkout customizers, analytics tools, upsell plugins, and payment add-ons until the core order path is stable.

Mistakes to avoid

• Adding products before defining attributes. You end up with inconsistent variations and filters.
• Testing only a successful payment. Failed and canceled payments, refunds, and out-of-stock cases expose different problems.
• Using giant uncompressed product images. Product galleries can become the heaviest part of the site.
• Letting transactional mail rely on basic PHP mail. Delivery problems can make customers think an order failed.
• Copying tax or policy settings from another store. Requirements depend on your products, business, and customer locations.

Best practices for a stronger site

• Keep the checkout path short and remove fields you truly do not need.
• Use consistent product photography ratios and image sizes.
• Write product content around buyer questions: fit, material, compatibility, dimensions, delivery, returns, and what is included.
• Create a daily or weekly process for unfulfilled orders, failed payments, low stock, refunds, and support.
• Back up before major WooCommerce, theme, payment, or checkout changes and retest checkout afterward.

Launch checklist

• A customer can add a product, change quantity, and remove it from cart.
• Checkout calculates shipping and tax as expected for target locations.
• Test payment succeeds and creates the expected order status.
• Failed/canceled payment does not create a falsely paid order.
• Order and customer emails arrive with correct content.
• Refund workflow is understood and tested where the gateway supports test refunds.
• Product, category, cart, checkout, account, and policy pages work on mobile.
• Sitemap, canonicals, robots, structured data settings, and duplicate filter URLs are reviewed.

Operational ownership and maintenance

Give one person clear responsibility for store operations: failed payments, stock discrepancies, fulfillment delays, refunds, transactional email, and extension updates. Review payment-gateway notices and WooCommerce system status after major changes. Keep a staging or test process for checkout-related updates when possible, and avoid making several payment, tax, shipping, and theme changes at the same time because troubleshooting becomes much harder.

How to confirm the first version works

Place a complete test order using the same path a customer will use. Check product selection, cart totals, shipping, tax, coupon behavior if enabled, payment, confirmation, order status, email, and the admin fulfillment view. Then deliberately test a failed or canceled payment and an out-of-stock or low-stock case. If refunds are part of normal operations, test that path too and confirm both WooCommerce and the gateway show the state you expect.

Conclusion

For a first store, resist the urge to add growth plugins before the purchase path works. A stable WooCommerce catalog, checkout, payment, fulfillment, email, and refund process gives you a foundation you can safely extend later.

FAQs