Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

If your e-commerce store is growing, your store will eventually hit a hard limit: your brain. Every time something breaks—an order ships late, a refund needs approval, an email goes out wrong, a promo code misbehaves—you scramble because the steps only live in your head.

That’s what Standard Operating Procedures (SOPs) fix. SOPs are the step-by-step instructions that keep your store running the same way every day, even when you’re not online. Think of SOPs like your store’s “operating playbook.” If you do product fulfillment and customer support in a consistent way, customers get consistent experiences—fewer mistakes, faster replies, and fewer angry tickets.

The goal in an online store is simple: make sure a VA, support agent, or ops person can handle the task 80% correctly on day one by following your SOPs. That “80% on day one” standard matters because it speeds up onboarding and cuts the chaos when volume spikes (like after a paid ad launch or a weekend sale).

The Importance of Brain-Dumping

Brain-dumping is transferring what you know into a format other people can use. In e-commerce, that usually means capturing everything you do when you’re:
- Checking orders and payment status
- Handling refunds and exchanges
- Responding to “Where is my order?” messages
- Creating discount codes
- Fixing shipping label or address issues
- Troubleshooting why a product isn’t showing correctly

If you keep those steps only inside your head, your business can’t scale beyond your personal attention. You’ll end up with a store that performs well only when you’re awake and available.

E-commerce example: You know the exact steps to deal with a “paid but not fulfilled” order (sometimes it’s a Shopify order status issue, sometimes it’s a fulfillment app sync problem). If that knowledge isn’t documented, the next time it happens, you’ll be the only one who can untangle it.

Creating Effective SOPs

Good SOPs are built the same way every time:

1. Why: Start with why the task matters. In e-commerce, this ties to customer experience and money.
- Example: “Refunds must be processed within policy because delays increase ticket volume and hurt customer trust.”

2. What: Detail the exact steps to complete the task. Be specific about the screens, fields, and tools.
- Example: “In Shopify Admin → Orders → search by order number → confirm payment status → check fulfillment status → apply refund in the correct way → post tracking update if needed.”

3. Outcome: Describe what success looks like. This is how you prevent “almost done” work.
- Example: “Customer receives confirmation email within 5 minutes, refund is recorded correctly, and the order status updates to ‘Refunded’ in Shopify.”

E-commerce example: If you write an SOP for abandoned cart follow-up, define the success outcome clearly:
- Segment trigger works
- Email/SMS sends within the right time window
- Exclusions are correct (no email if the customer already purchased)
- Message matches your brand offer terms

Organizing Your SOPs

SOPs should live in one centralized place, easy to search and easy to access. For an online store, you want a system that works across devices, because your operations don’t happen only on one computer.

E-commerce example: Create an “Ops Vault” in Notion or Google Drive with sections like:
- Orders & Fulfillment
- Returns & Refunds
- Customer Support (common ticket templates)
- Email/SMS Campaign Operations
- Discounts & Promotions
- Ads & Landing Page Launch Checklist

When a VA gets a question like “How do we handle a partial refund for missing items?”, they should be able to find the correct SOP in under 60 seconds.

The Loom-First Approach

Writing long documents is slow. A fast, effective approach is recording. Use Loom to capture your screen while you do the task, then turn that video into a clear SOP.

E-commerce example: Record yourself doing a “refund review” process—show the Shopify Admin steps, what you check, what triggers approval, and what you document for compliance.

Then your SOP becomes a combination:
- A short written checklist (for speed)
- A Loom video (for visual clarity)

This is especially helpful for tasks tied to specific platform behavior, like Shopify order states, shipping label workflows, and Klaviyo campaign settings.

Building a Culture of Self-Reliance

In e-commerce, your team shouldn’t guess. They should follow your store’s process.

Train your team to check the SOP vault before asking you. Your message becomes standard:
“Before you message me, check the vault. If it’s not there, then we add it.”

That rule builds momentum. Every time something new happens, you turn it into a reusable SOP. Over time, fewer issues reach you directly—and you free up your attention for growth levers like CAC reduction, AOV improvements, LTV strategy, and conversion rate optimization.

If you do this right, your store stops being a person-dependent operation and becomes a system-dependent business.