Client Risk Notes
Ecommerce hosting for first stores — Taking on a client's first shop without inheriting the whole business
A brochure site that breaks costs your client embarrassment; a shop that breaks costs them takings, and they will call you about it at ten on a Saturday night.
Straight answer first
Take a first store on only with the scope written down: put it on a Launch Store package at $4.19/mo of cost of goods, charge for out-of-hours answerability rather than for disk, and exclude payment gateways, plugins and tax configuration explicitly.
Everything below is about the difference between hosting a shop and being responsible for one. What the merchant will believe you agreed to, where the money actually goes wrong, what an order-taking site costs you in attention, and the four exclusions worth writing into the first proposal.
Written by the Hosting Seller staff · Checked 24 August 2026
NVMe
Under every client store
Free
Domain on annual orders
99.9%
Target you can quote a merchant
Flat
Wholesale cost at renewal
First stores fail on platform fees and rigid rules chosen before the business model settled — but from a reseller's chair, that is not the interesting failure. The interesting failure is a merchant who believes that because you host the shop, you are answerable for anything that stops an order completing, including the parts you have never had access to.
The shelves underneath are Launch Store at $4.19/mo, Pro Store at $5.59/mo and Elite Store at $9.09/mo. Those figures are not the reason a first store is expensive to carry. Your evenings are.
What the merchant believes you agreed to
A first-time merchant does not have a mental model with layers in it. There is 'the shop', and you are the person who looks after the shop. When a card payment is declined, when a shipping plugin miscalculates, when VAT appears on an order it should not have, the first call is to you — and reasonably so, from where they are sitting.
So the proposal has to draw the line explicitly and in their language. You are responsible for the account being up, the certificate being valid, the backups being taken and the site being served quickly. You are not responsible for the payment gateway's decisions, the tax configuration, the plugin the merchant installed on a Friday, or the courier's API.
Write that as four sentences, not four pages. A merchant who has read four sentences before signing will accept them at eleven at night. A merchant reading a clause for the first time during an outage will not.
Where the money actually goes wrong
Not at the server. In practice the incidents that cost a first store real takings are a lapsed certificate on the checkout, a plugin update that broke the basket, and an out-of-stock sync that never ran. The first of those is solved outright by SSL that issues automatically and reissues before it lapses — which is why it should never be a manual step in anything you build.
The second is solved by staging, and staging is included rather than billed per site. Clone, update, look at the checkout with a real test order, then push. A merchant will forgive a scheduled ten minutes; they will not forgive discovering a broken basket from a customer email.
The third is a cron job, and cron is where most first-store agencies get caught out — a sync scheduled by a plugin runs on visitor traffic rather than a real timer, so on a quiet Tuesday it does not run at all. Set the real cron in the panel, and check it has fired before you say the integration is live.
What an order-taking site costs you in attention
Budget on incidents rather than hours. A brochure site produces perhaps two contacts a quarter. A trading shop produces two a month in an ordinary month, and five in December, and they arrive at the times when orders are being placed rather than the times when you are working.
The cost that surprises people is not fixing things. It is being reachable. If you have promised an evening response to a shop, you have sold an option on your own weekends, and that option should be priced. Agencies that carry shops profitably almost always charge a distinctly higher tier for them and say plainly why.
The backup cadence deserves the same thought. Daily copies are the baseline everywhere; the Elite Store shelf at $9.09/mo takes them every four hours, which narrows the window of lost orders to something you can apologise for. Losing a day of orders and losing four hours of orders are very different conversations, and the second one is cheaper than the discount you would offer to survive the first.
The four exclusions worth writing down
Payment gateways. You can help configure one; you cannot be answerable for an acquirer's risk decision, a declined card or a payout schedule. Say so.
Plugins the client installs. Offer to review anything before it goes on, make clear that anything installed without that review is fixed at your hourly rate, and keep staging available so the review is quick rather than grudging.
Tax, shipping and stock configuration. These look like website settings and behave like accountancy. Quote for setting them up if you want the work; do not let them fall inside a hosting retainer by silence.
Third-party outages. When a courier's API or a marketplace connector goes down, your client's shop is affected and your servers are fine. Agreeing in advance that you will investigate and report but not indemnify is the difference between a supportive supplier and an unpaid one.
What stays yours, and what stays theirs
The account, the branding and the support relationship stay yours — private nameservers, your own package names, your own welcome email. The shop's commercial decisions stay theirs, and the proposal should say so before the first order is taken.
HTTPS runs throughout and the free certificate reissues itself, so the single most damaging first-store failure — a browser warning at the checkout — is not something anybody has to remember.
- A written scope before the shop opens
- Staging included, so plugin updates are tested
- Real cron, not visitor-triggered scheduling
- Four-hourly backups on the Elite Store shelf
Why Hosting Seller
On every plan, as standard
Certificates that never lapse
Free SSL issues and reissues on its own, removing the failure that costs a first store the most credibility per minute.
Staging copies you do not bill for
Test the plugin update against a real test order before it meets a real customer, on every store you carry.
Backups every four hours on Elite Store
At $9.09/mo the lost-order window narrows from a day to an afternoon, which is a different apology entirely.
Proper cron in the panel
Stock and marketplace syncs run on a real timer rather than on whether somebody happened to visit the site.
PCI-friendly defaults
HTTPS throughout and hardened defaults mean the questionnaire your merchant is sent has straightforward answers.
A supplier your merchant never meets
White labelling from the nameservers down keeps the shop's supply chain entirely between you and us.
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
Write the four exclusions before the build
Gateways, client-installed plugins, tax and shipping configuration, and third-party outages — four sentences, agreed before the shop opens.
- 2
Price the evening, not the disk
A shop account should sit on a visibly higher tier than a brochure site, and the reason given should be response time rather than resources.
- 3
Wire staging into your update routine
Clone, update, place a test order, push. Make it the only way plugin updates reach a trading site you are responsible for.
- 4
Set the real cron and prove it fired
Schedule syncs from the panel rather than trusting visitor-triggered scheduling, then check the log before declaring an integration live.
In the Box
Packed with every plan
- A four-sentence scope agreed before the shop takes an order
- Free SSL issuing automatically on the checkout domain
- Staging used for every plugin update on a trading site
- A real cron entry for every stock or marketplace sync
- Backup cadence matched to the client's order rate
- A test order placed after every significant change
- The merchant's gateway credentials held by the merchant
- An out-of-hours response target you can actually meet
- Imunify360 watching the store account
- A separate cPanel account, never an addon domain
Across the Counter
Things people ask us all the time
Should I host a client's first shop at all?
Only if you want the phone call. Shops generate the highest out-of-hours contact rate of any account type, and the merchant's revenue is directly affected by anything that goes wrong, which changes the emotional temperature of every conversation. If you do take it on, take it on a higher tier with a written scope. If you do not, referring it out cleanly costs you nothing and preserves the relationship for the build work.
What backup frequency should I sell a shop client?
Match it to their order rate. Daily copies are the baseline on every plan; the Elite Store shelf at $9.09/mo runs every four hours. At five orders a day a lost day is an inconvenience, at fifty it is a serious sum, and the cost difference between the shelves is smaller than the discount you would end up offering to keep the account after losing a day of orders.
How do I keep gateway problems out of my support queue?
By never holding the credentials. Let the merchant create the gateway account in their own name and give you limited access if they want configuration help. The moment you hold the login you become the first call for every declined transaction and every payout query, none of which you can influence.
Is WooCommerce the right platform to put a first-time merchant on?
Commercially, usually yes — it costs hosting money instead of platform money and takes no slice of the takings, which matters most when margins are thin. Operationally it means the plugin stack is your problem in a way that a hosted platform's is not. Charge accordingly, keep staging in the loop, and be explicit that plugins the client adds unreviewed are billed at your hourly rate.
What happens when the shop outgrows the package I built?
You move it up in place, with no migration. The Store shelves run from Launch at $4.19/mo through Pro at $5.59/mo to Elite at $9.09/mo, and beyond that a VPS from $13.52/mo gives a busy shop resources nobody else can touch. The signal to watch is sustained order volume rather than catalogue size — a long product list is cheap to serve, and a steady queue at the checkout is not.
Read next
cPanel vs Plesk
The panel decision from a reseller's side: which one your clients will be looking at, and which one your staff can support.
Web Hosting for Beginners
The non-technical client account and the tickets it sends you in the first week.
WooCommerce Hosting
Shop-tuned accounts with Redis caching and checkout headroom, for the client whose order book is growing.
Domain Names
Search, register and transfer names — registered in whichever name you tell us to put on the record.
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.
Carry client shops on purpose.
Separate cPanel accounts, staging on every store, and backups as often as the order book deserves — under your own brand.
See WooCommerce Hosting plans