You can’t build a scalable e-commerce business on tribal knowledge and verbal instructions. At some point — usually around $500K to $1M in annual revenue — the things that worked when it was just you and a handful of people start breaking down. Orders get missed. Returns are handled inconsistently. New hires take months to ramp up. The fix for all of these is the same: documented standard operating procedures. Here are the 10 SOPs every e-commerce business needs, along with template outlines you can adapt immediately.
Table of Contents
- 1. Order Processing SOP
- 2. Customer Returns & Refunds SOP
- 3. Inventory Management SOP
- 4. New Product Listing SOP
- 5. 3PL Receiving & Put-Away SOP
- 6. Customer Service Escalation SOP
- 7. Supplier & Vendor Management SOP
- 8. Employee Onboarding SOP
- 9. Quality Control SOP
- 10. Peak Season Operations SOP
- How to Use These Templates
- Frequently Asked Questions
1. Order Processing SOP
Why you need it: Order processing is your highest-volume, highest-frequency process. Any inconsistency here has a direct impact on customer satisfaction and margin.
What it should cover:
- How orders flow from Shopify (or your sales channel) to your warehouse or 3PL
- Who is responsible for reviewing orders each day and at what times
- How to handle high-risk or flagged orders (fraud, address issues)
- How split shipments and backorders are handled
- Escalation path for any order that can’t be filled as placed
Template outline:
SOP: Order Processing
Owner: Operations Manager
Trigger: New order received in Shopify
Steps:
1. Review order queue in Shopify Admin each day at [TIME]
2. Flag any orders with: unverifiable address / fraud score > X / out-of-stock items
3. For flagged orders: [escalation steps]
4. For clean orders: confirm 3PL has received pick ticket (check Extensiv dashboard)
5. If pick ticket not received within 2 hours: [escalation]
6. Confirm tracking number pushes to Shopify by end of business
7. Log any exceptions in [tracking sheet/system]
Expected output: All orders confirmed in WMS within 2 hours of placement
2. Customer Returns & Refunds SOP
Why you need it: Returns are one of the most inconsistently handled processes in e-commerce. Without an SOP, different customer service reps make different decisions — creating customer frustration and margin leakage.
What it should cover:
- Eligibility criteria (how many days, condition of product, exceptions)
- How to initiate a return in Shopify
- How to issue a return shipping label
- What happens when the return is received at the warehouse
- When to issue a refund vs. exchange vs. store credit
- How to handle “item not received” claims vs. “damaged on arrival” vs. “changed my mind”
Key SOP decision point: Define explicitly what situations get a refund without requiring the item to be returned. This is a policy call, but it needs to be documented so every customer service rep applies it consistently.
3. Inventory Management SOP
Why you need it: Inventory discrepancies compound. A small error in a stock count on Monday leads to overselling by Friday. An inventory management SOP prevents this by standardizing how counts are done, recorded, and acted upon.
What it should cover:
- Cadence for cycle counts (daily for fast-movers, weekly for mid-tier, monthly for slow-movers)
- How inventory discrepancies are investigated and corrected
- Reorder point calculation and who triggers purchase orders
- How new stock receipts are logged (in Zoho Inventory, Extensiv, or your WMS)
- How damaged or unsellable inventory is tagged and disposed of
In our experience working with brands that use Zoho Inventory alongside a 3PL, the most common failure point is not the software — it’s the lack of a clear process for reconciling discrepancies between the Zoho count and the 3PL’s count. Document this explicitly.
4. New Product Listing SOP
Why you need it: Inconsistent product listings create SEO problems, customer confusion, and fulfillment errors. An SOP ensures every product goes live with the right information, images, and tags — every time.
What it should cover:
- Naming convention for product titles (brand name, descriptor, size/variant format)
- Required fields before a product can go live (description, images, SKU, weight, HS code for cross-border)
- Image specifications (resolution, background, angles required)
- SEO fields (meta title, meta description, alt text standards)
- How variants are structured in Shopify
- How to notify the 3PL of a new SKU before launch
5. 3PL Receiving & Put-Away SOP
Why you need it: Receiving errors at the 3PL are one of the most common — and most expensive — operational failures for e-commerce brands. Products get lost, mislabeled, or counted incorrectly during receiving, and you often don’t find out until months later when a customer reports a missing item or you run a cycle count.
What it should cover:
- How to send an Advance Shipping Notice (ASN) to your 3PL before a shipment arrives
- What documentation to include in every inbound shipment (packing slip format, labeling requirements)
- How to confirm receipt — who checks the 3PL dashboard, and when
- Discrepancy threshold — at what unit variance do you flag a receiving error?
- How to submit a receiving discrepancy claim to your 3PL
6. Customer Service Escalation SOP
Why you need it: Not every customer service rep knows when to escalate vs. when to resolve independently. Without a clear escalation path, either reps over-escalate (wasting management time) or under-escalate (creating liability).
What it should cover:
- Tier 1 issues: resolved by front-line CS rep (order status, simple returns, password resets)
- Tier 2 issues: requires manager approval (refund over $X, replacement order, custom resolution)
- Tier 3 issues: legal/compliance risk (fraud claims, chargebacks, social media threats)
- Response time SLAs for each tier
- How to log escalations in your helpdesk (Zoho Desk, Gorgias, etc.)
7. Supplier & Vendor Management SOP
Why you need it: Vendor relationships are often managed entirely in one person’s head — including pricing agreements, lead times, quality standards, and escalation contacts. When that person leaves, the knowledge leaves with them.
What it should cover:
- How to place a purchase order (format, approval required, lead time expectations)
- Vendor performance tracking (on-time delivery rate, defect rate)
- How to handle a late or incorrect shipment
- Contact directory for each vendor (account manager, production, finance)
- Annual vendor review process
8. Employee Onboarding SOP
Why you need it: Every hour a new hire spends confused about where to find things, who to ask, or how to do basic tasks is an hour of lost productivity. A solid onboarding SOP compresses the ramp-up period significantly.
What it should cover:
- Pre-start checklist (system access, email setup, tool logins)
- Week 1 schedule — who they meet, what they learn, what they do independently
- Probation milestones — what does “ramped up” look like at 30/60/90 days?
- Where to find SOPs, policies, and company documentation
- Who is responsible for the new hire’s onboarding (usually their direct manager)
9. Quality Control SOP
Why you need it: For product-based businesses, quality control is the last line of defence before a defective product reaches a customer. An inconsistent QC process means inconsistent product quality — and inconsistent customer trust.
What it should cover:
- Inspection protocol for incoming goods from suppliers (sample size, defect categories, pass/fail criteria)
- Who is authorized to reject a shipment
- How to document and photograph defects
- How to file a claim with a supplier for defective goods
- Pre-shipment inspection process for outbound orders (if applicable)
10. Peak Season Operations SOP
Why you need it: Peak season (Black Friday, Cyber Monday, Q4, major promotional events) breaks every process that isn’t explicitly designed for high volume. A peak season SOP documents the specific adjustments your team makes to handle 3x–10x normal order volume.
What it should cover:
- Pre-season checklist (inventory pre-position, 3PL capacity confirmation, carrier account setup)
- Customer service staffing and response time adjustments
- Order cut-off dates for pre-Christmas delivery by carrier and region
- Inventory safety stock thresholds during peak
- Escalation protocol for 3PL capacity issues
- Post-season review process (what worked, what broke, what to change next year)
How to Use These Templates
These outlines are starting points — not finished documents. To turn them into working SOPs:
- Copy the template outline into Google Docs, Notion, or your chosen SOP tool.
- Fill in the specifics for your business — your software, your thresholds, your team members’ names.
- Walk through the SOP with the person who actually does the task and make corrections.
- Test it with a team member who doesn’t yet know the process.
- Publish it somewhere everyone can find it — not buried in a folder.
- Set a review reminder for 6 months out.
The goal is not a perfect document — it’s a useful one. A good-enough SOP that gets used is worth ten perfect SOPs that sit untouched.
Frequently Asked Questions
How many SOPs does a small e-commerce business need?
Start with 5–10 for the highest-volume, highest-stakes processes. A business doing $500K–$2M/year typically needs 15–25 core SOPs to operate consistently without founder dependency.
Should SOPs be role-specific or process-specific?
Process-specific. An SOP should describe how to execute one process, not everything a particular role does. A customer service rep might use 5–6 different SOPs, each focused on a specific process (returns, escalations, order lookups, etc.).
How do I get my team to actually follow SOPs?
Three things matter: location (make SOPs easy to find), relevance (SOPs must reflect how the process actually works, not how management wishes it worked), and accountability (SOPs need to be referenced in training and performance conversations).
What’s the biggest mistake e-commerce businesses make with SOPs?
Writing them once and never reviewing them. An SOP that was accurate 18 months ago is often actively misleading today — Shopify has changed, your 3PL has changed, your team has changed. Build review cycles in from the start.
Do I need SOPs if I’m a solo operator?
Yes — especially if you plan to hire. Writing SOPs while you’re still the one doing the work is far easier than trying to document processes after you’ve handed them off to someone else. It also forces clarity on whether your current process is actually the right one.
Want Help Building Your SOP Library?
OpsStack works with e-commerce brands and Canadian SMEs to document, design, and implement the operational systems they need to scale without chaos. If building your SOP library feels like a project that keeps getting pushed to the backlog, we can help you get it done. Book a free consultation.
