How to Build an Outage Runbook for Your E-commerce Store (With Template)

An outage runbook is a one-to-two page document that tells anyone on your team exactly what to do, in order, when the store or a critical vendor goes down: how you detect problems, how you triage them, what you tell customers, when you escalate, and how you review afterward. Writing it takes about an hour on a calm afternoon and repays that hour during the first incident, when nobody thinks clearly and every minute costs revenue.

Most small stores run their first few outages from memory and group-chat panic. The runbook exists to replace that with a script. Here is each section, followed by a compact template you can copy.

Section 1: Detection. How do you find out?

Write down every signal that tells you something is wrong, in the order you trust them: monitoring alerts, vendor status page subscriptions, a checkout test failing, customer emails. Then be honest about the gap. If your only detection is "a customer tells us," your average time-to-awareness is measured in hours, and everything downstream in the runbook starts late.

The fix is independent monitoring on your storefront and your critical vendors, with alerts routed to a channel someone actually watches (SMS for severe incidents; the trade-offs are covered in which alert channel to use). Note in the runbook exactly where alerts arrive and who owns responding to them.

Section 2: Triage. Is it you or the vendor?

The first decision in any incident is whether the problem is your configuration or the vendor's platform, because the responses are opposite: your bug means roll back and fix; their outage means communicate and wait. Script the check:

1. Load the storefront and checkout from a phone on cellular data (rules out your wifi and cached sessions).
2. Check your monitoring dashboard: are other services down too? Multiple simultaneous failures usually point to shared infrastructure.
3. Check the vendor's status page and a crowd-report site, per how to know when Shopify is down.
4. Ask: did we change anything in the last hour? Theme edits, app installs, and DNS changes are the usual self-inflicted suspects.

Section 3: Immediate actions by scenario

List your store's revenue-touching scenarios and the two or three moves for each. Keep verbs concrete: "pause Meta and Google campaigns," not "assess advertising." A platform-down scenario should lean on a prepared playbook like what to do when Shopify goes down. Payment outages get a backup processor toggle; email platform outages get a hold on scheduled campaigns; shipping tool outages get a manual order export path.

Section 4: Customer communication templates

Pre-write two or three short messages so nobody drafts copy mid-crisis. Calm, specific, no blame:

• Site banner or social post: "We're aware of a technical issue affecting checkout and are on it. Your cart and orders are safe. Updates here as we have them."
• Order-delay email: "A technical issue with our shipping system is delaying label creation today. Your order is confirmed and will ship as soon as the issue resolves, and tracking will follow automatically."
• Support macro: one-paragraph explanation for reply-all use, updated with specifics during the incident.

Section 5: Escalation and roles

Even a two-person store needs this line: who is incident lead, who talks to customers, and at what point you open a vendor support ticket or call your developer. Include the vendor support URLs and your account IDs in the runbook so nobody hunts for them during the outage. Note SLA claim deadlines here too; the evidence you gather now feeds SLA credit claims later.

Section 6: Post-incident review

Within a week, spend 20 minutes on four questions: How long until we knew? What did it cost (the downtime cost calculator helps)? What worked and what did not? What one change reduces the damage next time? Update the runbook with the answer. Runbooks are living documents; the first draft is always wrong somewhere.

Example runbook table

Scenario	Detection signal	First 10 minutes	Comms	Escalate when
Storefront down	Monitor alert; checkout test fails	Triage you-vs-vendor; pause all paid ads	Site banner + social post	Down >30 min: vendor ticket
Payments failing	Monitor alert; checkout errors	Enable backup processor; pause ads	Banner: "try PayPal at checkout"	Immediately: processor support
Email platform down	Monitor alert	Hold scheduled campaigns and flows	None (internal note)	Send window at risk >2 hrs
Shipping tool down	Monitor alert; labels stall	Export orders manually; warn warehouse	Order-delay email if >1 day	Next pickup deadline at risk

Print it, pin it, and revisit it before peak season using the store monitoring checklist. A runbook plus fast detection turns an outage from a scramble into a checklist.