Field Guide Operations systems
How to write SOPs for an ecommerce brand
A standard operating procedure is what turns a founder's instinct into something a team can run. Here is the format that actually gets used, which SOPs to write first, and how to keep them from going stale.
The difference between a brand that runs on a founder’s memory and one that runs on a system is written down, and it is called a standard operating procedure. An ecommerce SOP is a repeatable instruction for one recurring task: how a return is handled, how a product launches, how the weekly inventory check gets done. Get a handful of them right and the operation stops living in your head, which is the only way it ever scales past you. Standard operating procedures ecommerce brands actually use are the backbone of real ecommerce operations documentation. Here is how to write an SOP people actually follow, which ones to write first, and how to keep them alive.
Why a brand without an ecommerce SOP hits a ceiling
Growth does not break businesses; the absence of systems does. At one product and one person, you can hold the whole operation in your head. At five products and three people, you cannot, and the cracks show up as the same mistakes repeating: the return handled three different ways, the launch that forgot a step, the inventory check that happens only when you remember. SOPs are how a founder’s instinct becomes something a team can run without you in the room.
An SOP is not bureaucracy. It is the difference between training someone once and answering the same question forever.
The format that actually gets used
Most SOPs fail because they are written like a manual no one opens. A good one is one page and has four parts.
A title and an owner
Name the task plainly (“Process a customer return”) and name one person accountable for the procedure being correct. Not a team. One owner. Shared ownership is how SOPs go stale.
A trigger
State exactly when this procedure runs: “When a return request arrives in the helpdesk,” “Every Monday at 9am,” “When a new ASIN is ready to launch.” The trigger is what turns a document into a habit.
The steps, numbered
Write the actual steps in order, each one a single action a new hire could follow without asking you. Link to the exact tool or screen. If a step needs judgment, say what good judgment looks like, with an example.
A definition of done
End with what finished looks like: the return refunded and the inventory adjusted, the launch live with tracking confirmed. Without a definition of done, people stop halfway and think they finished.
Which SOPs to write first
Do not try to document the whole business. Write the high-frequency, high-risk procedures first, the ones that happen often and hurt when they go wrong.
The first SOPs an ecommerce brand needs
- Order processing and returns
- The weekly inventory and IPI check
- A product or ASIN launch, end to end
- Customer-service escalation and refunds
- The weekly tracking and reporting routine
- Restock and reorder decisions
Notice these map to the parts of the business that quietly cost the most when they are inconsistent. The weekly inventory check is the same routine that keeps a multi-brand portfolio from drifting; write it once and it runs on every brand.
Keep them alive, or do not bother
An SOP no one maintains is worse than none, because people trust it and follow it into a process that has changed. Three rules keep them honest.
Store every SOP in one place the team actually opens, not scattered across documents and chat threads. Give each one a named owner and a review date. And update the procedure the moment the process changes, not at some quarterly cleanup that never happens. The discipline is small and the payoff compounds: every SOP you keep current is a question you never answer twice and a mistake that stops recurring.
This is the quiet core of the operations-systems work, turning the way you do things into something that survives you being busy, on holiday, or scaling to the next brand. Most founders spend years learning service delivery and almost none learning to systematize it, which is exactly why the ones who do pull ahead.
If your operation still lives mostly in your head and the same fires keep starting, building the system that documents and runs it is the work I do for brands. It starts with a Growth Audit that maps where the operation depends on you and what to write down first.