Ecommerce Business Continuity Plan: Outages and Faults
A plan that keeps sales running through a site outage, payment fault or carrier delay: ranking risks, backup routes, communication and regular drills.
rabbitclip teamPublished: 6 min read
Short answer
An ecommerce business continuity plan is a short document, written in advance, that says how sales and customer trust are protected when the site, the payment system or the delivery line fails. It holds three things: which failure would do the most harm, who does what for each one, and what the customer is told. The plan need not be long. It only has to be readable on a single page while the fault is happening.
Most businesses make a plan after the failure, not before. Picture a flooring manufacturer on the morning of a campaign: the payment page is throwing errors, nobody on the team knows who should call the provider, and customers are asking questions on social media. This article explains which risks to handle first, how to build backup routes and when a plan has grown larger than it needs to be.
Which risks should be written down first?
Trying to list every possibility makes a plan unreadable. Three questions are enough: which failure stops sales completely, which slows them, and which only annoys the customer. The ones that stop sales come first: the site will not load, payment cannot be taken, the order panel is down.
Beside each risk, add two notes: how long it can last before the damage grows, and who decides. An hour of payment downtime and half a day of carrier delay do not call for the same response. This ranking also shows which system deserves closer watching during busy periods such as campaigns.
- The site will not load or is very slow
- The payment page errors or the provider does not respond
- The order panel or stock system is down
- The carrier is not collecting parcels or is running late
- A domain, certificate or hosting subscription is expiring
What do you do in a site outage?
The first step in an outage is to find where the problem sits: your own server, the domain or DNS, or an outside service. For that, it must be clear in advance who looks at which panel. The hosting provider's support channel, the domain registrar login and a copy of the DNS settings should sit in one place, kept current.
While the outage lasts, a simple status page or a social media note is prepared for customers. Backups matter here too: a backup has value not because it was taken but because a restore has been tried. A team that has never restored one learns, at the moment of need, that it was incomplete.
What happens when the payment system fails?
A payment fault stops sales fastest and worries customers most. First establish whether the fault is yours or the provider's; most providers publish a status page, and checking it comes first. If the fault is yours, roll back the latest change. If it is the provider's, tell customers what to expect while they wait.
Where possible, keep a second payment route ready: another provider, bank transfer or cash on delivery. Not every business needs one, but in busy selling periods reliance on a single provider enlarges the risk. A customer who hit an error at checkout must be told clearly whether their card was charged. Uncertainty produces more complaints than the fault itself.
How do you talk to customers when delivery slips?
In a delivery delay the harm comes less from the lateness than from the silence. A customer who does not know where the parcel is will ask, and one who cannot wait will ask for a refund. When a delay is confirmed, list the affected orders and contact customers yourself; waiting for them to contact you damages trust.
Keep the message short and concrete: what happened, where the order stands, when the next update will come. Where possible, keep a second carrier or a local courier defined as a backup. The same route helps when a carrier has damaged deliveries or a regional shutdown.
Who writes the plan and how is it tested?
The plan needs an owner, since shared responsibility often turns into nobody's. The owner keeps the document current and coordinates when a fault occurs. The document holds names, phone numbers, access routes and decision rights; passwords do not belong in it, but in a password manager that authorised people can reach.
Test the plan once a year or before a large campaign. A test is not a real outage but a desk exercise: if the payment provider were unreachable for half a day, who would do what? The conversation usually exposes a gap, such as a missing phone number or access right.
When is a continuity plan bigger than it needs to be?
For a small shop taking a few orders a day, with one provider and able to absorb a day of downtime, a twenty-page crisis plan is unnecessary. A one-page list is enough: whom to call, where to look, what to tell customers.
A larger plan should match the size of the business and the cost of failure. A business where even an hour's downtime causes serious loss, whose campaign periods are intense or which has contracted customers should build a more detailed plan. The test is not the size of the company but how expensive an hour of stoppage would be for you.
What mistakes are common in business continuity?
The most common mistake is writing the plan and shelving it; phone numbers go stale, staff change and access lapses. The second is taking backups without ever testing a restore. The third is overlooking ordinary causes of downtime such as an expired domain, certificate or subscription, which are the most frequent failures and the easiest to prevent.
The fourth is tying all access to one person: if they are on holiday or have left, nobody can reach the panel. The fifth is telling customers nothing during a fault. Silence often does more damage to reputation than the fault itself.
A continuity plan consists of ranking the risks, writing who does what for each, preparing backup routes and settling in advance how you will speak to customers. What matters is not its length but that it can be read and followed while a fault is under way. If you would like to review the weak points of your site, payments and delivery together, we can arrange a discovery call with rabbitclip.
FAQ
What should an ecommerce business continuity plan cover?
Site outage, payment failure and delivery delay, with a responsible person, a backup route and a customer message for each. Tracking domain, certificate and subscription expiry belongs in it too.
Is taking backups enough for business continuity?
No. A backup is not a safeguard until a restore has been tried. Test a restore at regular intervals and keep the backup somewhere separate from the server.
Is relying on one payment provider risky?
The risk grows in busy selling periods, because a provider fault stops sales entirely. A second provider, bank transfer or cash on delivery acts as a small insurance.
How often should the plan be reviewed?
Once a year and before large campaigns. Phone numbers, access rights and provider details are updated then, and a desk exercise exposes what is missing.
