WooCommerce is the ecommerce plugin for WordPress. It is free to download, it runs inside your own WordPress site, and it is the default answer to “how do I sell on WordPress”. That default status is both its strength and its trap. It can do almost anything, so you have to decide what you want it to do. This guide explains what WooCommerce is, how it is built, what it costs as listed on its own pages, and who should (and should not) pick it.
Every factual claim here is drawn from WooCommerce’s own site, its developer documentation, or its WordPress.org plugin page, and is marked with the date we read it where it matters. WPMusk has not run hands-on tests of the platform. Where we give an opinion, we say so.

What WooCommerce is
WooCommerce is an open-source ecommerce platform that runs as a plugin on WordPress. Its own homepage pitches it as a platform that offers “the freedom to sell and grow on your terms, without limits, compromises, or monthly platform fees”. The WordPress.org plugin page lists more than 7 million active installations, an author of Automattic, and a first publication date of September 27, 2011 (read November 2026).
Two things follow from that description. First, WooCommerce is not a hosted service. You supply the hosting, the domain, the updates and the backups. Second, the shop and the content site are one thing. Your product pages are WordPress content, your blog is WordPress content, and your theme, SEO plugin and page builder all apply to both.
If you are new to the WordPress side of this, start with what WordPress is and then come back. If you are still choosing between ways to sell, the WordPress ecommerce guide compares the routes at a higher level.
How WooCommerce is built
Understanding the architecture explains most of the platform’s behaviour: why it is flexible, why it needs decent hosting, and why extensions matter so much.
A plugin on top of WordPress
WooCommerce adds products, orders, coupons and customers to WordPress. Products are stored in WordPress’s own content tables. Orders used to live there as well, which brings us to the biggest architectural change of recent years.
High-Performance Order Storage
WooCommerce’s developer documentation describes High-Performance Order Storage (HPOS, formerly Custom Order Tables) as storing order data in dedicated custom database tables instead of WordPress posts and post meta. The tables it names are _wc_orders, _wc_order_addresses, _wc_order_operational_data and _wc_orders_meta. HPOS reached stable status in WooCommerce 8.2, released in October 2023, and is enabled by default on new installations. Existing stores must enable it manually.
The docs give three reasons for it. Dedicated tables and indexes reduce read and write load as order volume grows. Backing up and restoring order data on its own is easier. And order data sits in smaller tables that are simpler to work with than one large shared table.
For you, the practical point is compatibility. An extension that reads orders by querying the posts table directly can break on an HPOS store. The docs describe a compatibility mode that keeps both storage locations in sync and lets you step back to legacy storage: enable it, let synchronisation finish, then select “WordPress posts storage (legacy)”. Before you turn HPOS on for a store that already has orders, check every order-touching extension for declared support.
The Cart and Checkout blocks
WooCommerce’s documentation calls the Cart and Checkout blocks its current cart and checkout experience. Stores started after WooCommerce 8.3 (November 2023) use the blocks by default. Older stores that use the cart or checkout shortcodes must replace them manually, and you can transform the blocks back to classic shortcodes from the block toolbar if you need to.
The same page warns about extensions: check each one’s changelog or description for block support, because an incompatible extension can make checkout elements unavailable. For example, an incompatible payment gateway may not appear as a payment option, and if only incompatible gateways are active customers see a “There are no payment methods available” warning. That is a common way for a checkout to “break” after a change, so test checkout after every extension update. Our checkout optimisation guide covers the tuning side.
Two APIs
The developer documentation separates two interfaces. The Store API is a set of public REST endpoints for customer-facing cart, checkout and product features, using the wc/store/v1 namespace. It needs no API keys, returns only data for the current customer through cookie-based sessions, and uses a nonce token for write operations. The authenticated WooCommerce REST API gives broader access to store data, including settings and orders by ID, for authorised use. Which one you reach for depends on whether you are building a storefront or an integration.
Product types
WooCommerce’s product documentation lists four core product types and two designations that can be combined with them.
- Simple: a single item with no variations, such as a book. Only a name, price and description are required.
- Variable: items that come in multiple variations, such as sizes or colours. Each variation can have its own price, SKU, stock level and attributes.
- Grouped: several products shown on one page, where shoppers add each item to the cart individually.
- External or affiliate: items sold on other websites; the product links to the external page instead of selling in your store.
- Virtual: a designation, not a separate type, for intangible items such as services or memberships that need no shipping.
- Downloadable: a designation for digital files such as ebooks, software or music that customers access after payment.
The homepage also says WooCommerce supports custom products, subscriptions, wholesale and B2B solutions. Several of those come from extensions rather than core, which leads to the main design decision of the platform: core is small on purpose, and many business-model features are add-ons.
If you plan to sell files, read how to sell digital products on WordPress before you commit. For conversion work on the product page itself, see improving WooCommerce product pages.
Checkout and payments
WooCommerce does not process cards itself. It hands payment to a gateway, which is an extension or plugin. You choose the gateway, and you pay that gateway’s own fees. WooCommerce charges no platform fee on top, which is what “without monthly platform fees” on its homepage means.
WooPayments
The official gateway is WooPayments. Its product page (read November 2026) describes it as pay as you go, without setup costs or monthly fees, available in 38 countries, accepting payments in more than 135 currencies. It lists cards, Apple Pay and Google Pay, express checkout via WooPay (US only), local methods such as iDEAL, Przelewy24, EPS and Bancontact, and buy now, pay later where available. The page points to a separate fees page for per-transaction rates and does not state them itself, so check that page for current rates before you decide.
The same page lists in-person payments through the Woo mobile app, including Tap to Pay on iPhone (iPhone XS or later with iOS 16.0 or later) and Android, with card readers available depending on country.
Other gateways
WooPayments is not required. The product page lists compatible payment solutions including Stripe, Square, Braintree, PayPal, Elavon, Mollie, Eway, Authorize.net, PayFast, Viva Wallet, Mercado Pago, Opayo and Worldpay. The right gateway depends on your country and your customers, and the trade-offs are covered in the WooCommerce payment gateways guide.
Because checkout compatibility depends on the Cart and Checkout blocks, confirm that your chosen gateway declares support for them.
Subscriptions and digital products
Recurring billing is not part of WooCommerce core. It comes from the paid WooCommerce Subscriptions extension. Its product page (read November 2026) lists a one-year plan at $279 and a two-year plan at $558, shown with a 20 percent saving to $446.40, with a 30-day money-back guarantee. The page calls it a paid annual extension and does not explain renewal terms of the license itself, so read the terms before you buy.
What the page says you get: one-time or subscription purchase options per product, free trials, sign-up fees, discounts, downloadable content on subscriptions and gifting. Automatic renewals run through more than 25 gateways, including WooPayments, Stripe and PayPal, or you can use manual renewals with any WooCommerce gateway. Failed payments are retried automatically, billing dates can be aligned, and customers can switch plans, update details and suspend or cancel from My Account. Admins manage subscriptions from the WordPress dashboard, and a Subscriptions Health Check helps spot renewals that need attention.
Digital products, by contrast, are in core: the downloadable designation described above covers files that customers access after payment. Together with the virtual designation, that handles software, ebooks and memberships at a basic level. For the wider picture of recurring revenue on WordPress, including alternatives to a paid extension, read WordPress subscriptions and recurring billing.
Taxes
WooCommerce’s tax documentation describes a manual system in core. You enable taxes under WooCommerce, Settings, General (“Enable tax rates and calculations”), and the tax options then appear in a dedicated tab. The key choices, as documented:
- Prices entered with or without tax. You decide how you type your product prices.
- Calculate tax based on. The customer’s shipping address (the default), the customer’s billing address, or your shop’s base address.
- Tax classes. Standard rates always exist and cannot be removed. You can add classes such as reduced or zero rate for products that need different rates.
- Rate tables. Each class has a table with country code, state, postcode, city, rate, tax name, priority, compound and shipping fields. Only the first matching rate at each priority applies, so you use different priorities to stack rates.
- Display. Prices in the shop and in the cart and checkout can each show including or excluding tax, with an optional suffix.
The alternative is automation. The WooCommerce Tax extension automates tax calculation for supported countries and, when enabled, greys out the manual options. You can also use a third-party tax solution instead, which the homepage confirms.
Which approach you need depends on where you sell. A store that sells in one country at a small number of rates can live with the manual tables. A store selling across several jurisdictions will spend a lot of time on maintenance, and the documentation itself recommends consulting a tax professional on what to charge. Our EU and US tax setup guide walks through the common cases.
Shipping
Core shipping is built on zones. According to the shipping zones documentation, a zone is a geographic area you ship to, defined by postcodes, states or provinces, countries or continents. A customer matches only one zone: WooCommerce checks zones from the top of the list down and uses the first match, so you should order them from smallest region to largest. A “Rest of the world” zone catches everyone else and cannot be moved, renamed or deleted. If a customer’s address falls in a zone with no shipping methods, they are told that no shipping is available.
WooCommerce includes three shipping methods: Flat Rate (a fixed charge for the zone), Free Shipping and Local Pickup. Anything more, such as live carrier rates, comes from extensions. The WooCommerce Shipping extension’s page (read November 2026) mentions discounted USPS and DHL labels printed from WooCommerce, notes that Canada Post labels are not supported, and says live rates require a separate USPS or DHL extension. Check carrier coverage for your country before you plan around it. More detail is in the WooCommerce shipping setup guide.
Extensibility
This is where WooCommerce is strongest. The homepage claims more than 1,000 extensions in the WooCommerce Marketplace and lists integrations with Klaviyo, QuickBooks, ShipStation, Google, Amazon, eBay, TikTok, Instagram and Facebook, plus ERP, CRM and marketing tools. Those are the vendor’s claims, and you should read them as a catalogue size rather than a quality guarantee.
The developer documentation covers building your first extension, designing a simple extension and development best practices, as well as theme development for classic and block themes. Because WooCommerce sits on WordPress, a developer can use the full WordPress hook system, custom post types and custom fields. If you want to add structured data to products, our guide to Advanced Custom Fields shows one common route.
Extensibility has a cost that the vendor’s pages do not dwell on. Every extension is code that must be kept compatible with WooCommerce, with HPOS and with the Cart and Checkout blocks. A store with 30 extensions has 30 sources of conflict. Our opinion: keep the list short and use a vetting checklist before adding anything new. When something does break, plugin conflict troubleshooting explains the standard isolation steps.
Performance considerations
Performance is mostly a hosting and discipline question. WooCommerce’s server requirements page lists, for WooCommerce 10.8 and later, WordPress 6.9 or greater, PHP 8.3 or greater (tested up to PHP 8.4), MySQL 8.0 or greater or MariaDB 10.6 or greater, HTTPS support and a memory limit of 256 MB or greater. For older environments it says WooCommerce still works on PHP 7.4 or later, MySQL 5.6 or later and MariaDB 10.4 or later, but warns that these versions have reached end of life. The WordPress.org plugin page lists different, lower minimums, so check the requirements for the exact version you install rather than relying on a blog post, including this one.
What the documentation supports on speed:
- HPOS exists to reduce load on busy order tables as order volume grows.
- Newer PHP versions are a requirement, not an option, on current releases.
What is common knowledge in the WordPress community, and our reasoning rather than a vendor claim: cart, checkout and account pages are dynamic, so full-page caching must exclude them; and an object cache such as Redis helps repeat database work. See Redis object cache for WordPress, the WooCommerce speed checklist and the speed-up tutorial for the practical steps. Measure before and after any change with your own store data.
The homepage quotes customers who describe virtually unlimited scalability. That is a testimonial, not a benchmark. The honest summary is that WooCommerce has no built-in ceiling, and the ceiling you hit is your hosting, your database and your extensions.
SEO
WooCommerce’s homepage says built-in blogging and WordPress SEO tools are available. In practice that means your products, categories and blog posts are normal WordPress content, so any WordPress SEO plugin can manage titles, descriptions, sitemaps and structured data across all of them. There is no separate SEO system to learn.
That is a real advantage over platforms where the store and the content live in different systems. It also means the work is yours. Start with the WordPress SEO guide, add product structured data using the schema markup guide, and make sure your permalink structure is settled before you launch, because changing it later needs redirects. The title tags tutorial covers the basics for each product page.
Data ownership
The homepage says merchants “fully own your site, code, and data”. Because WooCommerce runs on your hosting, your database holds your customers, orders and products, and you can export them or move the whole site. That is a meaningful difference from hosted platforms, where the vendor holds the data and decides what exports exist.
Ownership also means responsibility. Backups, security updates and compliance with privacy law are yours. Set up a backup routine before you take your first order, and read the WordPress security guide. Store data includes personal data, so treat a restore test as part of launch, not an afterthought.
Pricing and licensing
As listed on WooCommerce’s own pages (read November 2026):
- WooCommerce core: free to download. The homepage states there are no monthly platform fees, and the WordPress.org page describes the plugin as free with optional paid upgrades and support.
- WooCommerce Subscriptions: $279 for one year, or $558 for two years shown discounted to $446.40, with a 30-day money-back guarantee.
- WooPayments: no setup costs or monthly fees, with per-transaction fees set out on a separate fees page.
- Enterprise: the homepage offers Woo Enterprise with a 30-day money-back guarantee; pricing is not stated there.
The homepage calls WooCommerce open source but does not name a licence, and neither does the plugin page text we read. Check the plugin’s own licence file if the licence matters for your project.
The costs that are not on any pricing page are the ones that matter most: hosting that suits a store, a theme, extensions for the features you need, and the time to maintain them all. Total those before you compare against a platform with a flat monthly fee.
Migration: moving in and moving out
WooCommerce’s documentation describes a built-in CSV tool for importing, exporting and bulk-updating products, found on the Products, All Products screen. Updates match rows by ID or SKU. It supports product fields such as name, SKU, prices, stock, categories, tags, attributes, images and parent and variation relationships, plus custom product metadata in columns prefixed with meta:. The page lists limits: it cannot add or update image alt text, cannot assign a specific ID to a new product, ignores unrecognised columns by default, and may need large files split into batches. It does not mention orders or customers, so for those you need a migration extension or a developer. Ask any prospective migration service exactly how it handles orders, customers, passwords and subscriptions.
Moving out follows the same pattern. Products export easily. Orders, customer accounts and active subscriptions are the hard parts, and the destination platform decides how well they import. Because you own the database, nothing stops you taking it all, but a clean mapping takes planning. If you are changing host rather than platform, the host migration guide applies, and the staging site guide shows how to rehearse the move without touching the live shop. For platform alternatives, see WooCommerce alternatives.
Who WooCommerce suits
This section is our opinion, built from the facts above.
- Stores that need unusual products or rules. Wholesale pricing, custom product types, odd shipping logic and complex integrations are where a large extension ecosystem and open code pay off.
- Content-led shops. If your blog, guides and product pages should live together, WordPress is a strong base.
- Teams with a developer or an agency. The platform rewards people who can read hooks and debug conflicts.
- Owners who want the data on their own server. The ownership argument is real.
- Stores that expect to grow into a custom build. Almost nothing is closed to you.
When not to pick WooCommerce
Be honest with yourself on these points before you commit.
- You want to sell a handful of digital products or a course with little setup. A lighter, purpose-built cart may be faster to launch and cheaper to keep running. Compare FluentCart and SureCart in our dedicated guides.
- Nobody on your team wants to maintain a WordPress site. Updates, backups, compatibility testing and hosting are yours. If that sounds like a burden, a hosted store may be the better fit.
- You need recurring billing and want to keep the cost down. Subscriptions is a paid extension. Compare the total with other routes.
- You run on weak shared hosting. The requirements page asks for PHP 8.3 or later and 256 MB of memory on current releases. A cheap plan that cannot meet them will make the store feel poor whatever you install.
- You dislike extension sprawl. Many business features are add-ons, and each one adds maintenance.
For a side-by-side view, read WooCommerce vs FluentCart vs SureCart.
How to evaluate WooCommerce in a day
Do this on a staging site or a throwaway install, never on a live shop. Set aside about a working day.
- First hour: install and check requirements. Compare your host’s PHP, database and memory limit with the requirements page for the version you are installing. If your host falls short, note it as a cost.
- Second hour: add five real products. Include one simple product, one variable product and one downloadable product if you sell files. Use the CSV importer with a ten-row file to see how your catalogue maps.
- Third hour: set up tax and shipping. Create the zones you actually sell to, add Flat Rate and Free Shipping, and enable taxes. Place test orders for three different customer addresses and check the totals against what you expect.
- Fourth hour: connect a payment gateway in test mode. Use the gateway you would really choose. Run a test purchase and a test refund. Confirm the gateway works with the Cart and Checkout blocks.
- Afternoon: list your must-have extensions. Write down every feature your store needs that core does not have. Price each extension from its own page, check it declares HPOS and block compatibility, and total the yearly cost.
- Late afternoon: test speed and mobile checkout. Run the checkout on a phone. Look at the page weight with PageSpeed Insights. Note what the extensions add.
- End of day: write the decision. Compare the total yearly cost, the hours of setup and the risks, and decide whether this beats the alternatives you tried the same way.
The same day-long plan works for any platform. Repeat it for the others on your shortlist so you compare like with like. When you are ready to launch for real, the WooCommerce checklist tutorial helps you finish the job.
Frequently asked questions
Is WooCommerce really free?
The core plugin is free to download, and the homepage states there are no monthly platform fees. You still pay for hosting, a domain, any paid extensions and payment processing fees charged by your gateway.
Do I need WooPayments?
No. The WooPayments page lists many compatible payment solutions, including Stripe, Square, PayPal, Mollie and others. Pick the gateway that works in your country and supports the Cart and Checkout blocks.
Can WooCommerce sell subscriptions?
Yes, through the paid WooCommerce Subscriptions extension, listed at $279 for one year (read November 2026). Other subscription routes exist, covered in our subscriptions guide.
Can I sell digital downloads?
Yes. Core has a downloadable designation for digital files, which you can combine with the virtual designation for items that need no shipping.
What is HPOS and do I need to turn it on?
HPOS stores orders in dedicated tables rather than in WordPress posts. It has been the default for new installs since the stable release in WooCommerce 8.2. Existing stores must enable it manually, so check extension compatibility first.
Will WooCommerce slow down my site?
It adds dynamic pages and database work, so it needs capable hosting. The documentation sets minimum server requirements, and what you add on top of core drives most of the cost. Measure your own store rather than trusting anyone’s claims, including testimonials on the vendor’s site.
How do taxes work?
You can configure tax classes and rate tables by hand, or use the WooCommerce Tax extension for automated calculation in supported countries. The documentation recommends consulting a tax professional on what you should charge.
Can I move my products to another platform later?
Products export through the built-in CSV tool. Orders, customers and subscriptions need extra work, so plan that mapping before you commit to any move.
Do I own my store data?
The homepage says merchants fully own their site, code and data. Because it lives on your hosting, that is true in practice, along with responsibility for backups and security.
Is WooCommerce good for SEO?
Products and posts are ordinary WordPress content, so standard WordPress SEO plugins and practices apply. Start with the WordPress SEO guide.
Bottom line
Whichever platform you choose, write down your reasons now. Six months from today you will want to remember why you picked it, which costs you counted, and which trade-offs you accepted knowingly.
WooCommerce is the most flexible way to sell on WordPress and the one with the largest ecosystem, as the vendor itself describes it. In exchange, you accept responsibility for hosting, updates and compatibility, and you pay for extensions as your needs grow. If your needs are unusual or your site is content-led, it is a strong choice. If your needs are simple and you want few moving parts, compare it against the lighter platforms before you decide. Also see the speed checklist and the Black Friday prep plan when you are ready to run a store seriously.