The most common surprise for store owners who chose WooCommerce because it was free is the monthly bill that arrives anyway. Nothing about it is hidden — every item is something you agreed to at some point — but the pieces are bought at different times from different vendors, so almost nobody has the total in one place. This is that total, written as line items you can check against your own card statement.
The point of the exercise is not to argue that WooCommerce is expensive. It is usually cheaper than the alternative once order volume is meaningful, precisely because there is no percentage-of-revenue platform fee. A store has an operating cost, and knowing it changes decisions: what to automate, what to cancel, and when paying someone to maintain the thing is cheaper than not.
Hosting: the line people under-buy
A WooCommerce store is a database-driven application with uncacheable pages — cart, checkout, my-account — and logged-in customers who bypass page caching entirely. Cheap shared hosting is priced for brochure sites and behaves like it under concurrency. The realistic range runs from budget shared plans through managed WordPress hosting to a dedicated or cloud setup for larger catalogs, and the jump usually happens for one of three reasons: checkout slows under load, the database has outgrown the plan, or an outage during a promotion made the decision for you.
- Budget shared hosting: fine for a launch, rarely fine at volume
- Managed WordPress hosting: the common middle, with staging included
- Cloud or dedicated: when concurrency, catalog size or uptime demand it
- Add backups and a CDN if the plan does not include them
Plugin licences and the renewal creep
This is the line that grows. A store starts with a theme licence and four plugins. Two years later it has a subscriptions extension, a bookings plugin nobody uses any more, two SEO tools where one would do, a page builder addon pack, a shipping integration, a reviews service and a form builder. Each renews annually at somewhere between $49 and $299, and each renewal is small enough to approve without thinking. Ten of them is a four-figure line nobody ever decided to spend. Once a year, list them, open the store's plugin screen next to the list, and cancel what is not doing measurable work. The audit takes an hour and frequently pays for itself twice over.
The second cost of an oversized plugin stack is not financial. Every active plugin is code that runs on your storefront, adds update risk and widens the surface area of any future migration. If the stack has quietly grown, WooCommerce plugin bloat covers how to work out which ones are actually costing you speed.
Payment processing: the largest variable line
For most stores this dwarfs everything else. The published online rate from the major US processors sits around 2.9% plus roughly 30 cents per transaction, with surcharges on international cards, currency conversion and some card types. At meaningful revenue it is the single biggest recurring cost of selling online, and it is the one line where WooCommerce's structural advantage shows: there is no additional platform commission stacked on top of the processor's fee. Check your processor's current schedule rather than trusting a number you remember — rates and surcharges change.
The services nobody counts as store costs
Email is the usual blind spot. Transactional order emails from WooCommerce should go through a proper sending service rather than the web server, and marketing email is a separate subscription priced by list size — which means it grows exactly as your marketing succeeds. Then there is the domain, an SSL certificate if the host does not include one, backup storage, uptime monitoring, analytics or session-recording tools, a helpdesk, and any accounting or inventory system with a WooCommerce connector.
- Transactional email sending service
- Marketing email, priced by list size — grows with success
- Domain, backups, monitoring, helpdesk
- Accounting, inventory or ERP connectors
Maintenance: paid deliberately or paid in emergencies
Every store pays for maintenance. The only choice is whether it is a predictable monthly amount or an unpredictable invoice after something breaks during a sale. Updates, backup verification, a staging environment, checkout monitoring and a security response plan are the boring work that prevents the expensive kind. If nobody in the business owns it, a plan is the cheaper structure — maintenance and support covers what that work actually consists of and what it should not be confused with. Plans of this kind start around $150 a month. Where one stops making sense: if you already have a developer on retainer who applies updates and watches checkout, you are buying the same hours twice.
Your own time is a real line item
The costs above are the ones with invoices. The one without an invoice is the hours you or your team spend re-uploading product photos, fighting a shipping plugin, checking whether last night's update broke anything, and answering "where is my order" emails that a decent order-tracking page would have prevented. Price those hours at what you would pay someone else to do them — $40 an hour is a conservative floor for anyone who can be trusted with a live store — and add them to the total. Six hours a month at that rate is $2,880 a year, which is more than most of the invoices above it.
Putting a number on your own store
Open your card statement and your PayPal or processor dashboard for the last twelve months, list every recurring charge related to the store, divide by twelve, and add an honest estimate for your own hours. Most owners find two or three subscriptions they forgot about and one that has doubled since sign-up. Then compare that monthly figure with what a fix costs: if a recurring annoyance eats four hours a month, it has a budget, and the revenue calculator turns the conversion side of the same argument into a number.
WooCommerce is free the way a kitchen is free once you own the house. The recurring bill is real, predictable and worth writing down.
When the total says something is wrong
Two patterns are worth reacting to. If plugin licences are approaching or exceeding your hosting cost, the stack has probably grown past what the store needs and is quietly buying you update risk. And if maintenance shows up only as emergency invoices, you are paying a premium for surprise. Neither is an argument for a rebuild by itself — but both are arguments for an hour with the list in front of you. The question worth asking once a year: put the total next to your revenue, and decide whether the stack is sized for the business you are running or for the one you were planning three years ago.