WooCommerce pricing and total store costs in 2026
Budgeting a WooCommerce store? Separate the core software from hosting, extensions and payment fees, then estimate the ongoing work your store needs.
- Published
- Last updated
WooCommerce pricing starts with free core software. Your store’s total cost comes from the hosting, extensions and services you choose, plus payment processing and the work of running it. There’s no universal WooCommerce plan that includes all those costs.
Build the budget from supplier terms and a written scope of work. Separate the first build from recurring costs so a low hosting bill doesn’t hide hours of maintenance.
What is free and what still costs money
The core WooCommerce plugin is free to download and use on WordPress, as WooCommerce’s pricing explanation confirms. Hosting companies can sell “WooCommerce plans”, but those are their own bundles of infrastructure and services.
A useful budget assigns each cost its own basis before adding a total.
| Cost category | Basis for your budget | What to record |
|---|---|---|
| Core software | Free WooCommerce plugin | Separate any paid service bundle |
| Hosting and domain | Provider quote or published renewal terms | Billing period, capacity, inclusions and tax |
| Extensions and theme | Exact product licence terms | Initial term, renewal, site allowance and currency |
| Implementation | Written project quote | Deliverables, revisions and handover |
| Payments | Gateway’s Australian fee schedule | Payment method, card origin and settlement currency |
| Ongoing labour | Hours multiplied by your labour rate | Catalogue work, maintenance and repair separately |
For a foreign-currency licence, include conversion costs in your own worksheet. Compare tax-inclusive cash outlay with tax-inclusive cash outlay. If you also track costs excluding recoverable tax, keep that as a separate total.
Hosting, domain and store performance
A trading store needs hosting sized for its checkout workload, plus secure connections, backups and a way to recover from failure. Domain registration also needs an ongoing renewal allowance.
WordPress’s hosting requirements identify the supported server software and HTTPS requirement. Meeting those requirements gets WordPress running. It doesn’t establish how many simultaneous checkouts a particular hosting package can handle.
Compare hosting approaches by who does the work and what happens during busy periods.
| Hosting approach | Workload it can suit | What the quote must explain |
|---|---|---|
| Shared hosting | A small catalogue with modest traffic | Resource limits, backup retention and support scope |
| Managed WooCommerce hosting | A retailer paying for more operational help | Staging, monitoring, restore service and excluded plugin work |
| Dedicated or cloud resources | Busy campaigns or a customised store | Capacity, scaling charges and who administers the server |
Ask for the normal renewal cost across a full year. Keep an introductory discount as a separate first-year adjustment. Check whether backups sit outside the live server, how often they run and who performs a restore.
A large image catalogue increases storage needs. Frequent stock imports and simultaneous checkout sessions add a different workload. Give the host those details when requesting a quote, including your busiest expected trading period.
Extensions, themes and implementation
Your selling model determines which extensions belong in the budget. Design preferences are a separate choice from features needed to take an order.
A simple store selling individual products can start with a standard theme and a small extension set. A recurring-delivery store needs subscription billing and a gateway that supports its renewal method. Wholesale rules or custom delivery calculations create their own requirements.
For example, WooCommerce Subscriptions is a paid annual extension with updates and support included in the licence. Its licence is separate from payment processing. Record the renewal term and number of stores covered alongside the purchase currency and applicable tax.
Price implementation against actual tasks. A quote can cover theme setup, product import mapping, shipping rules and checkout acceptance. Custom code needs its own handover and maintenance scope. Buying an extension doesn’t pay a developer to make it work with every other extension you use.
Keep a licence list with a named account owner. Remove overlapping purchases from the proposed stack before buying, and budget for compatibility checks when the theme or an extension changes.
Payment fees and checkout compatibility
Payment processing is a transaction cost separate from hosting or an extension licence. The total depends on the gateway, payment method and customer mix.
WooPayments’ Australian fee schedule lists online card payments at 1.75% plus $0.30 per transaction. International cards add 1.50%, and currency conversion adds 2.00% when applicable. The schedule states that transaction fees aren’t returned when you refund a customer.
WooPayments states that 10% goods and services tax (GST) applies to its Australian fees. It also describes reverse-charge treatment for GST-registered merchants who provide a valid GST ID. Use the treatment that applies to your account when forecasting cash deductions.
For an illustrative $100 domestic online card payment, the base processing fee is $2.05 before applicable GST. The same sales revenue split across more orders incurs more fixed transaction charges.
Any introductory processing offer needs its own eligibility, expiry and post-offer rate in your worksheet. The examples here use the ordinary fee schedule, with no promotional allowance.
Subscription checkout also creates a maintenance obligation. WooCommerce’s subscription gateway compatibility guide distinguishes automatic renewals from manual payments. WooPayments supports automatic renewals through cards and express checkout methods, but its additional payment methods don’t support automatic renewals.
Allow time to retest the payment routes your store uses after relevant updates. The WooCommerce checkout guide covers the configuration and compatibility checks behind that labour allowance.
Keep catalogue data and shopping help reliable
Catalogue upkeep is recurring work even when the store’s software bill stays flat. Assign time to variant changes, stock imports and product information, along with delivery and returns-policy updates.
A new colour needs the right variant, image and availability. An imported stock file needs a stable product identifier. Someone also needs to resolve failed imports and remove delivery claims that no longer match the store’s service.
Shopping assistance is a separate service using those inputs. shoppa is an AI shopping agent that helps customers find, compare and buy products in chat on your site. Its answers use your catalogue and store documents. Budget separately for the service and the staff time needed to keep those sources useful.
For the catalogue connection and product conversations, read about the WooCommerce AI chatbot integration. Put responsibility for catalogue corrections with the person who owns the underlying product data.
Maintenance and unexpected work
Recurring maintenance pays for planned updates and checks. A repair reserve covers work outside that routine, such as an extension conflict that prevents orders.
WooCommerce’s update guidance calls for a current backup and staging checks before updating. A staging site is a separate copy where changes can be tested before customers encounter them. The backup needs both the store database and relevant files.
Agree who acts when something breaks. The host can own server recovery, an extension vendor can support its product and a developer can investigate conflicts between them. Your agreement must name the person who coordinates the incident and confirms orders work again.
Keep response hours and included work in writing. A maintenance retainer can exclude emergency work or custom-code repairs. Paying your staff to investigate also belongs in the cost of running the store, even when no supplier invoice arrives.
Build a realistic first-year and recurring budget
Calculate first-year cost as implementation plus recurring services, operating labour and payment fees. In later years, remove the original implementation cost and add any new development you commission.
The two scenarios below are illustrative labour budgets, not vendor quotes or market price ranges. All labour uses an assumed $100 hourly rate excluding GST. They exclude hosting, domain, licences and payment fees, which must be added from your selected suppliers’ terms.
The simple store sells individual products using a standard theme and one stock-import process. The extension-heavy store adds recurring deliveries, custom shipping rules and more frequent catalogue changes. Its allowance includes work to integrate those features, not a fixed number of paid plugins.
| Labour category | Simple store | Extension-heavy store | Timing |
|---|---|---|---|
| Implementation | 20 hours / $2,000 | 80 hours / $8,000 | Once-only |
| Planned maintenance | 12 hours / $1,200 | 36 hours / $3,600 | Each year |
| Catalogue and policy upkeep | 24 hours / $2,400 | 72 hours / $7,200 | Each year |
| Occasional repair reserve | 6 hours / $600 | 18 hours / $1,800 | Each year, spend only if needed |
| First-year labour budget | $6,200 | $20,600 | Includes implementation and reserve |
| Recurring annual labour budget | $4,200 | $12,600 | Excludes new development |
These assumptions produce a first-year labour span of $6,200 to $20,600 across the two examples. They aren’t a total WooCommerce price. A retailer who does the work personally still uses those hours, even if their cash spending is lower.
For each scenario, add the annual hosting and domain quote, plus the exact extension renewal costs. Include a theme purchase in the first year if needed, then use its actual renewal terms in later years. Add any separate shopping-assistance service on its own terms.
Calculate payment costs from expected card sales multiplied by the percentage fee, plus order count multiplied by the fixed fee. Add applicable international-card charges, conversion costs and tax. Keep a separate allowance for disputes if your order history supports it.
Replace the assumed hours with a written implementation scope and your own catalogue workload. Then compare the complete first-year and recurring totals. The lower-cost option is useful only if its quote assigns the work your store actually needs.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.