WooCommerce store care - what must it include so the store never stops?

TL;DR: WooCommerce store care is five recurring tasks: updates with a test of the purchase path, backups kept off the server, monitoring of the store and its payments, a pool of hours for small changes, and a response time at failure written into the contract. It differs from looking after a regular website because after every change you have to check the cart, the checkout, the payment and the order emails, and because the store database changes every minute. My care runs in three plans - Start, Store and Plus - with no minimum contract term, and plans and prices are on the support page. Below I break down every element and link to the separate articles where I covered each one in depth.

This article is a map of the subject. If what you are looking for is one answer to “does my store need care at all”, read first the piece on when WooCommerce technical maintenance pays off. Here I assume the answer is “yes” or “probably yes”, and I show what such care has to contain, how to compare offers and what to demand in writing.

How store care differs from website care

The word “care” means something different for a company website, for a blog and for a store, even though all three run on the same WordPress. The difference is not the number of clicks in the admin panel. It is what breaks and what that costs.

For a company website the worst case is a few hours of downtime and one lost contact form. I laid out the scope of that kind of care in the article on what WordPress maintenance should include. For a blog the work shifts from reacting to reviewing the archive, which I cover in the piece on looking after a company blog.

In a store each of those tasks has an extra layer:

• After an update it is not enough to check that the site opens. You have to walk through the cart, the checkout fields, the payment, the confirmation email and the hand-off of the order to the courier or to accounting.
• The store database changes all the time. A backup from yesterday is a different database from the one holding today’s orders, so the backup rhythm and the restore procedure look different from a website.
• Integrations break quietly. The payment gateway, parcel lockers, invoicing, stock sync - none of them shows an error on the home page, and each can stop sales.
• Downtime costs from the first minute. A website visitor comes back tomorrow. A customer in the middle of a sale does not.

That is why care for WooCommerce stores is priced by how much has to be tested after every change, not by the number of pages.

What WooCommerce store care must include

Good care is a list of tasks with a frequency, not a promise to “take care of everything”. Five elements without which I would not sign a contract, neither as the contractor nor as the client:

1. Updates with a test of the purchase path. WordPress, WooCommerce, the theme and the plugins get patches every week. An update without a backup and without a checkout test is a lottery where the stake is your sales. The order, the backup beforehand, the staging copy and the test order afterwards are in my safe WooCommerce updates checklist. Under care that procedure runs on a schedule, not once per rescue operation.

2. Backups that actually restore. Files and database, at a rhythm matched to the number of orders, kept off the store’s server and restored as a test from time to time. How a store backup differs from a website backup, and what to do with orders that arrived after the copy, is in the article on WooCommerce store backups. The basics - files plus database, the 3-2-1 rule and a restore drill - are in the piece on a WordPress backup that actually restores.

3. Monitoring of the store, not just the home page. Checking that the store responds is the minimum. A store can be “up” and at the same time not accept payments or not send order emails. Monitoring under care covers availability, response time, critical errors and selected points of the purchase path.

4. A pool of hours for small changes. A typo in a description, a fix in the email template, a new shipping method, a change to the free-shipping threshold. These pile up every month, and without a pool of hours each request becomes a separate job with a separate quote.

5. Priority and a response time at failure. The most important element, invisible until it is needed. A client under care has a person who knows the store, has a fresh backup at hand and steps in within an agreed time, instead of searching for anyone with a free slot on a Friday evening.

On top of that come things that are not tasks but have to be in the contract: the list of tasks with their frequency, hours beyond the pool quoted before work starts, who holds the access credentials and what happens after termination. More on that below, in the section on the contract.

Care plans: what Start, Store and Plus include

My WooCommerce store care runs in three plans. The prices are fixed and public, with no “from”, because there is no point hiding them for a recurring service, and there is no minimum contract term, because care should stand on its results, not on a clause.

How to read the table:

• Start is for a company website or a small store that simply has to keep working: it sells, it does not change every week, and the owner wants to stop thinking about updates and backups.
• Store is the main plan, for a WooCommerce store that really earns and where something happens every month: a new promotion, a change in the checkout, another integration. The pool of 6 hours pays for itself, because you would be commissioning those changes anyway, only ad hoc and without priority.
• Plus is for a store critical to the business that keeps developing. Response within 8 business hours, a critical outage within 2 h, a pool of 12 hours and a quarterly technical review, which is the role of an IT department.

The Peace of Mind Guarantee works in every plan: if the store goes down through my fault and is not back within the critical-outage time of your plan (Start 8 h, Store 4 h, Plus 2 h), you do not pay for that month of care. Unused hours carry over to the next month. The full description of the plans with an FAQ is on the ongoing support and help page.

Work beyond the pool of hours I quote separately and before it starts, never afterwards. Prices outside these plans - a store rebuild, a migration or a performance fix - I always give in writing after seeing the store.

Response time, SLA and what happens at failure

In a care contract two promises matter, and they are easy to confuse: response time and repair time. Response time is the moment someone confirms the ticket has arrived and starts working on it. Repair time depends on what happened, and an honest contract does not promise it blindly for every case. How to write both so they can be enforced is in the article on the maintenance contract, which I come back to below.

In practice WooCommerce store failures have a few recurring faces, and for each one I have a separate diagnostic article:

• The checkout does not accept orders, or the customer does not see a payment method. Most often a plugin conflict after an update, caching or an incompatible gateway. Causes and the order of checks: WooCommerce checkout not working.
• A white page or “there has been a critical error on this website”. Usually a plugin or theme after an update, the PHP memory limit or a PHP version change on the server. How to undo it without losing data: WordPress critical error.
• The store does not send order emails. Customers pay and get no confirmation, the team gets no notifications. This is a separate kind of failure, because from the outside the store works normally. Diagnosis and fix: WooCommerce not sending order emails.

Under care the difference from an ad hoc repair is that the person stepping into the failure knows the store, has a fresh backup and knows what changed in the last week.

How taking a store under care works

A store that comes under care is rarely in perfect shape. It usually has overdue updates, a backup “somewhere at the host” and a few plugins nobody remembers. That is why a takeover starts with an entry audit, not with signing up for a ready-made plan.

The entry audit is a review of what really threatens the store: the state of updates, unsupported plugins, backups and whether they restore, speed, security, the checkout and the emails. The list of points that most often hide problems is in the article on what to check in a WordPress site audit beyond SEO. For a store I add the purchase path and the integrations.

The audit produces three things: a list of critical clean-up tasks for day one, a plan recommendation and a scope in writing. Only then do we sign.

The takeover itself looks the same every time:

1. Access: the WordPress admin, hosting, domain, repository if there is one. You get a list of who has what and where it is recorded.
2. The first full backup kept off the server and a test restore on a staging copy of the store.
3. Critical clean-up: overdue security patches, unsupported plugins, conflicts found by the audit.
4. Monitoring and an update rhythm set for the store: different for a store with 10 orders a day than for one that sells at night.
5. The first report: the state on entry and what has changed.

From that point care runs in a monthly cycle, and you get a one-page report: what was updated, what was detected, how many hours from the pool were used and on what.

The maintenance contract: what has to be in writing

“We look after the site” in an email is not a contract. A store care contract has a few mandatory elements, without which on the day of the failure both sides will have a different version of what was promised. A full template with every clause explained is in the article on what a website maintenance contract must contain; here is only the checklist:

• An appendix with the task list and frequency. What exactly and how often. “Updates” is not enough; “WordPress, WooCommerce and plugin updates every week, with a backup before and a test order after” is a line that can be checked.
• Response time separate from repair time. With a note on when the clock starts and during which hours.
• The pool of hours and the rate beyond it. What is in the subscription and what is quoted separately, with the rule “quote before work starts”.
• Access and ownership. Who holds the passwords, where the code lives, what you receive when the cooperation ends. The code and the access are yours from day one, not after termination.
• Termination. Notice period, form, hand-over of backups and documentation.

In-house, an outside person or ongoing care

Store care does not have to be an external service. There are three honest models, and each has its cost.

In-house makes sense when there is someone in the company who knows the difference between staging and production, can restore a backup and can check the checkout after an update. The cost is their time and their availability at the moment of failure, which usually arrives outside working hours. How to count that cost honestly, including the risk that does not show in the budget, is in the article on WordPress maintenance in-house or outsourced.

An outside person on call is cheaper on paper until there is a failure. Then you pay an emergency rate, and the contractor learns the store from scratch at the worst possible moment.

Ongoing care costs every month, but it turns the unpredictable cost of a failure into a predictable subscription with a written response time. It pays off when a day without sales costs more than a month of care, or when in the last quarter there was at least one moment of “something broke and I did not know where to start”.

When care does not pay off: a store before sales have started, a store with a dozen products and occasional orders, a technical owner with a checklist at hand. Then your own quarterly rhythm is enough, with this article as the checklist.

How to choose a plan and where to start

The decision fits into three questions:

1. What does a day without sales cost you? If less than a month of care, start with your own rhythm and come back when the store grows. If more, care pays for itself with the first failure that did not happen.
2. How often does something change in the store? Once a quarter: Start. Every month: Store. Every week, and the store is critical for the business: Plus.
3. Does anyone today know your store from the inside? If the previous contractor has disappeared and you do not know where the backups are, start with the takeover within 48 hours and the entry audit that come with every plan, and we will pick the plan after that audit.

If you are not sure which option fits, do not guess. Send me the store address and two sentences about what worries you, and I will send back the scope, the plan and the price in writing: ongoing support and help.

Frequently asked questions

What does WooCommerce store care include? Five recurring elements: WordPress, WooCommerce and plugin updates with a test of the purchase path after every change, file and database backups kept off the server with a restore test, monitoring of uptime and the checkout, a pool of hours for small fixes, and a response time at failure written into the contract. Plus a monthly report and an entry audit when the store is taken over.

How much does WooCommerce store care cost? With me, the Start, Store and Plus plans run with no minimum contract term, and scope and prices are on the ongoing support page. A takeover within 48 hours with an entry audit is included in every plan. Work beyond the pool of hours is quoted separately, always before it starts.

How is store care different from WordPress website care? By the scope of testing after every change and by the backup rhythm. For a website it is enough to check that it opens and that the form sends emails. For a store, after every update you have to walk through the cart, the checkout, the payment and the order emails, and take backups more often, because the database changes with every order. That is why store care costs more than care for a website with the same number of pages.

How fast does someone respond when the store goes down? The response time depends on the plan: Start within 48 business hours, Store within 24 business hours, Plus within 8 business hours. A critical outage jumps the queue and has its own time: 8, 4 or 2 hours depending on the plan, covered by the Peace of Mind Guarantee: if the store went down through my fault and is not back within that time, you do not pay for that month of care. Response time and repair time are two different promises, and both belong in the contract.

Can I cancel the care at any time? Yes. The plans have no minimum term: you pay for a month and cancel by the end of the month. On exit you receive the full set of access credentials, the latest backup and the documentation of what was done, because the code and the access are yours from the first day of the cooperation.

Would rather not watch over it every month yourself? I take sites and stores under ongoing care - backups, updates, monitoring, and priority when something breaks. Tell me what you run and I will send back scope and price.