Account Watchlist
WooCommerce hosting for growing stores — The client account most likely to disturb the others
A store that is doing well is a compliment and a warning: the same growth that makes the client happy is the growth that starts showing up in everybody else's response times.
Straight answer first
A growing WooCommerce account is the one to watch on a shared reseller allotment: the checkout and account pages cannot be cached, so the client's success arrives as sustained PHP and database load rather than as bandwidth — put it on a Pro Store package at $5.59/mo of cost of goods and set the limits before it needs them.
The rest of this page is the watchlist: the three metrics that tell you the account is changing character, what per-account limits do and do not protect, the point at which moving it is cheaper than tuning it, and how to raise the client's price without the conversation being about hosting.
Written by the Hosting Seller staff · Checked 24 August 2026
Free
Migration when you move it
24/7
Cover for peak trading
Daily
Backups, four-hourly on Elite
$0
Setup on every plan
A WooCommerce checkout cannot be cached, and that is deliberate. It means a shop's load profile is fundamentally different from a brochure site's: the busiest pages are the ones that must be built fresh every time, by PHP, against a database. From a reseller's chair that is the whole story, because it is the only account type on a shared allotment whose growth is felt by its neighbours.
The Store shelves are Launch Store at $4.19/mo, Pro Store at $5.59/mo and Elite Store at $9.09/mo, the last of which takes backups every four hours and includes CloudLinux Pro with PHP X-Ray. Beyond them, a KVM VPS starts at $13.52/mo. Knowing where those steps are before a client needs one is the difference between a planned upgrade and an emergency.
Three numbers that say the account is changing
Uncached request share. On a brochure site nearly everything is served from cache; on a trading shop, basket, account and checkout pages never are. When the proportion of requests that reach PHP starts climbing week on week, the account has changed category regardless of what the client is paying you.
Database size and query volume. WooCommerce keeps orders, and order tables grow forever. A shop with two years of trading behind it is doing work on every admin page load that a new shop did not, and the client will describe that as 'the back end has got slow' without connecting it to their own success.
Concurrent logged-in sessions. Fifty simultaneous browsers on cached product pages cost almost nothing. Fifty simultaneous logged-in customers cost real resources, and this is the number that turns one client's good day into your other clients' bad one.
What per-account limits actually protect
You set the limits each client account gets, and that isolation is the reason a busy shop is manageable at all on a shared allotment — a runaway process is capped inside one account rather than being everybody's problem. That is genuinely valuable and it is not the same as headroom.
What limits protect is your other clients. What they do not do is make the shop faster; from the merchant's side, hitting a limit looks exactly like the site being slow, and they will tell you so. So the limit is a tool for containing risk, not a substitute for putting the account somewhere with more room.
Redis object caching through AccelerateWP is the thing that genuinely helps the uncacheable pages, because it takes the repeated database work out of the path even when the page itself has to be built fresh. Pair it with NVMe underneath and LiteSpeed in front, and a Pro Store account carries a good deal more trading than most resellers expect.
When moving beats tuning
The honest test is whether the next hour of your time buys more than the next ten dollars of plan. Early on, tuning wins easily: switching on object caching, trimming a bloated plugin stack and fixing an unindexed query can transform a shop for the cost of an afternoon. Later, it stops — you end up spending a day a month keeping an account inside limits it has outgrown.
The step from Pro Store at $5.59/mo to Elite Store at $9.09/mo buys 200 GB of storage, more cores and RAM, backups every four hours and PHP X-Ray for tracing slow code. That is a genuinely different account for less than four dollars, and it is the upgrade most resellers leave too late because the sum looks trivial next to the client's invoice.
Past that, a VPS from $13.52/mo gives the shop resources nobody else can touch — and gives you a sysadmin job you did not previously have. Move a client to a server when their workload requires it, not when their revenue impresses you, and reprice the management at the same moment.
Raising the price without talking about hosting
The conversation goes badly when it is framed as a cost increase and well when it is framed as a change of service. The client's shop has grown; what they need now is a shorter backup window, faster response during trading hours, and somebody watching the checkout during their peak season. Those are things to sell, and the plan upgrade is an implementation detail inside them.
Give them a number they recognise. Four-hourly backups instead of daily means the worst case is an afternoon of orders rather than a day of them — ask what a day of orders is worth and the upgrade prices itself. That is a merchant's arithmetic, not a hosting argument.
And do it before peak. A shop owner will agree to almost anything in September and to nothing at all in the third week of November, when the same conversation reads as opportunism. Diary the review for the quiet part of their year.
Containment on one side, headroom on the other
Per-account limits keep one busy client from becoming everybody's incident; the shelves above give that client somewhere to go when containment starts hurting them. You need both, and knowing which problem you have is most of the skill.
Upgrades apply to the account in place with no migration, so acting early costs you an invoice line rather than an evening.
- Limits set per client account, by you
- Redis object caching for uncacheable pages
- Four-hourly backups on the Elite Store shelf
- PHP X-Ray to trace slow code before you guess
Why Hosting Seller
On every plan, as standard
Isolation that contains the damage
Per-account limits mean a runaway shop is capped inside its own account rather than degrading your whole book.
Object caching for the uncacheable
AccelerateWP with Redis removes repeated database work from basket, account and checkout pages that page caches cannot touch.
A four-dollar step that changes everything
Pro Store at $5.59/mo to Elite Store at $9.09/mo buys 200 GB, more cores, four-hourly backups and PHP X-Ray.
PHP X-Ray instead of guessing
Trace the slow request to the actual query, which turns a speculative afternoon into a twenty-minute fix you can bill.
Upgrades in place
Moving a shop up a shelf is a change to the account with no migration, so acting early is cheap.
Cover during their peak
Round-the-clock support behind your desk is what lets you promise a merchant attention in the week that matters most.
Price Tags Compared
How we compare with the household names
Typical sign-up and renewal prices across the market, set next to ours — the second number most comparison charts leave off.
| Line item | Hosting SellerBest seller | Typical big-brand host | Typical budget host | Typical loss-leader |
|---|---|---|---|---|
| Entry price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Price at renewal / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Renewal price on the entry plan is unchanged | ||||
| SSL on every plan | ||||
| Site migration included | ||||
| The entry plan uses NVMe storage | ||||
| Entry plan gets a backup daily | ||||
| Live human support, 24/7 |
*The number in our column is the cheapest plan on our shelf, priced on an annual term and pulled live from the very catalogue that feeds the pricing page, so it cannot drift out of date. Other columns show the ranges shared hosting tends to advertise inside each bracket: introductory rates that normally ask for a one-to-four-year commitment, then climb once that term expires. Naming individual competitors and printing their prices is something we have stopped doing. A figure we cannot re-check on the day you read it has no business sitting in front of you. So compare us with whoever you are genuinely weighing up, and read the renewal line first. That line tells you more than the headline ever will.
First Steps
From choosing to live
- 1
Put the shop on your watchlist at signup
Uncached request share, database growth and concurrent logged-in sessions — three numbers checked monthly, not investigated after a complaint.
- 2
Switch on object caching before you tune anything
Redis through AccelerateWP addresses the pages that page caching cannot reach, which is where a trading shop's load actually lives.
- 3
Diary the upgrade review for their quiet season
A merchant agrees in September and refuses in November; the conversation is about backup windows and response, not about hosting.
- 4
Decide the VPS threshold in advance
Write down what would make you move this client to their own server, so the decision is made calmly rather than during an incident.
In the Box
Packed with every plan
- Object caching enabled on every trading client account
- Per-account limits set deliberately before growth arrives
- Backup cadence matched to the client's order rate
- A monthly check on database size and uncached request share
- Staging used for every plugin update on a live shop
- PHP X-Ray consulted before any speculative optimisation
- An upgrade threshold written down in advance
- The shop's peak trading season in your diary
- A test order placed after every significant change
- A separate cPanel account, never sharing with other clients
Across the Counter
Things people ask us all the time
How do I know a client's shop is affecting my other accounts?
Watch the aggregate rather than the anecdote. Per-account limits mean a single account is capped, so the honest answer is usually that it is not affecting the others — but your allotment is being consumed. Reseller 1 carries 30 GB of NVMe and 300 GB of bandwidth in total, and a trading shop with a growing order table and daily backups eats into both. Review aggregate usage monthly once you carry any shop at all.
Should I put a client's shop on my reseller plan or on its own Store account?
On your reseller plan while it is small, because the isolation, the branding and the billing all stay in one place. On its own account when the resource profile stops being shared-shaped — sustained uncached load, a large order table, or a backup window the merchant needs shortened. The Store shelves at $4.19, $5.59 and $9.09 a month exist precisely for that transition, and moving is a migration you do once.
What do I say when the merchant asks why the admin has got slow?
That their order table has grown, which is a symptom of trading rather than of hosting, and that the fixes are object caching, a leaner plugin stack and eventually more resources. Show them PHP X-Ray output if you have it — a merchant who can see which query is slow stops suspecting the host, and starts treating the fix as work worth paying for.
How much backup frequency does a shop actually justify?
Ask what an hour of orders is worth, then compare. Daily backups are the baseline; four-hourly copies come with the Elite Store shelf at $9.09/mo. At five orders a day the difference is academic. At fifty it is the entire argument, and the merchant will make it for you once the question is put in their currency rather than yours.
Can I move a busy shop without downtime?
Yes, and it is worth rehearsing rather than improvising. Free migration brings the site across, you check the copy before DNS changes hands, and the old site keeps serving customers until the new one takes the traffic. For a trading shop, add a step: put the store into a maintenance state for the final database sync so no order is placed against the copy you are about to discard.
Read next
Drupal Hosting Plans
The Composer-era client build and the deployment step it needs — a different profile from a plugin-driven shop.
Game Server VPS
The always-on client workload, and why an idle process is easier to size than a busy website.
WooCommerce Hosting
Shop-tuned accounts with Redis caching and checkout headroom, for the client whose order book is growing.
Web Hosting
cPanel accounts on NVMe with SSL, migration and year-one domain — the shelf most client packages are modelled on.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Give the busy account somewhere to go.
Store shelves from $4.19/mo, four-hourly backups on Elite, and KVM servers from $13.52/mo when a client genuinely outgrows them.
See WooCommerce Hosting plans