The SOP that does not get followed is not a discipline failure. It is a writing failure. An SOP that is too long gets read once and skimmed thereafter. An SOP that is too vague produces guesswork. An SOP that covers every edge case in prose becomes the document nobody opens. The SOP that gets followed is specific, short, and structured so the key information is findable in under 30 seconds.
Ecommerce SOP writing for a VA is a different task from writing documentation for a technical audience. A VA who is handling customer service, product listings, and returns does not need comprehensive operational theory. They need to know what to do when the order arrives damaged, what to do when the customer does not know their size, and what to do when none of the standard options apply and they need to escalate.
Most Shopify sellers who write their first SOP write it too long and in the wrong format. They produce a prose document that explains everything they know about the process, with the most important information buried in paragraph three. The VA reads it once during onboarding and never opens it again because finding the answer to “what do I do about this specific situation” requires reading the whole document.
This article is for the Shopify seller who has tried writing SOPs and found that their VAs do not actually use them. The Five-Element SOP Format produces a document that gets used.
Why Most SOPs Do Not Get Used
The obvious format failure: long, dense prose. An SOP written as a series of paragraphs requires the VA to read sequentially to find the specific answer to their specific question. Under time pressure (which is when an SOP gets consulted), reading sequentially is not realistic. The VA guesses instead.
The less visible problem is the information hierarchy. Most SOPs put the process overview first and the critical decision rules last. But the most important information for a VA in the moment of handling a customer interaction is the decision rule for this specific situation, not the background context. The format should lead with what is most needed in the moment.
The deepest problem is scope creep during writing. The founder who writes an SOP naturally wants to be thorough. They add edge case after edge case, context about why the process works this way, historical notes about how it used to be done, and exceptions that apply to three situations per year. The SOP grows until it is comprehensive and unusable.
The Five-Element SOP Format
The Five-Element SOP Format organizes every SOP into five clearly separated sections. The VA can jump directly to the section they need without reading the whole document.
Element 1 is the one-line purpose statement
One sentence at the top of the document: “This SOP covers how to process a return request from a customer.”
The purpose statement tells the VA immediately whether this is the document they need. It takes five seconds to read. Every SOP starts with it.
Element 2 is the trigger and the scope
When does this SOP apply? What situations does it cover and, critically, what does it not cover?
“This SOP applies when a customer submits a return request through the Gorgias support portal. It does not apply to exchanges (see Exchange SOP) or to returns initiated by Shopify’s automatic return flow.”
Scope definition prevents the VA from applying the wrong SOP to a situation and prevents scope creep during the SOP’s use.
Element 3 is the numbered step sequence
The core of the SOP: numbered steps in order. Short. Each step is one action.
- Open the return request in Gorgias.
- Check the order date. If within 30 days, proceed to Step 3. If over 30 days, go to the Over-30-Days Exception below.
- Check the return reason.
- Apply the resolution from the Resolution Matrix below.
- Update the returns log.
- Send the confirmation response using Template A.
Before: “When a customer submits a return, begin by checking when they ordered the product in relation to our standard return window, then review the stated reason for the return, apply the appropriate resolution based on our policy, and update internal records before communicating the outcome to the customer.” After: Steps 1 through 6 above.
The numbered sequence is scannable. The prose version requires reading.
Element 4 is the decision matrix for common variations
A table or list format covering the most common variations and the correct response to each.
| Return reason | Within 30 days | Over 30 days |
|---|---|---|
| Wrong size | Full refund or replacement | Store credit only |
| Product defective | Full refund + prepaid return label | Full refund + escalate to founder |
| Changed mind | Store credit only | Deny, escalate if customer escalates |
This format makes the most common decisions findable in under 10 seconds.
Element 5 is the escalation criteria
Explicit. Numbered. Clear. “Escalate to [founder contact] when: (1) the customer mentions chargeback or dispute, (2) the product defect claim involves safety, (3) the requested resolution is not in the matrix above.”
How the Conductor Builds Your SOP From Library Records
An SOP written from memory captures the easy cases and forgets the messy ones. The messy ones are exactly where a VA gets stuck. An SOP built from the store’s actual records includes them from the start.
The Conductor is Kiluma’s context-aware AI, and it works from what actually happened, not what the founder recalls. It reads the returns records, exception logs, and escalation history in the Living Library. The Living Library is where those real cases have been recorded as they occurred.
What comes back populates the hard parts of the SOP. The decision matrix fills with variations that have genuinely come up. The escalation criteria come from situations that actually occurred. A VA following it meets fewer surprises the document never foresaw.
Rewrite One Existing SOP in the Five-Element Format
Pick the most-used SOP in the store that is currently in prose format. Rewrite it using the Five-Element SOP Format.
Measure how long it takes your VA to answer one specific “what do I do about this?” question from the original version and from the rewritten version.
That comparison tells the seller whether the format change matters. For most stores, it takes the VA one to three minutes to find an answer in prose and under 30 seconds to find the same answer in the matrix format.
An SOP That Gets Used Is Worth More Than a Comprehensive One That Doesn’t
The returns SOP that a VA opens 10 times per week because it is fast to consult is producing more operational value than the comprehensive one they read once and never return to. The Conductor helps build the decision matrix from actual past records. Try Kiluma free for 14 days at kiluma.ai.