The minimum SOP set for fulfillment covers six processes: receiving, putaway, picking, packing, shipping and returns, plus cycle counts and quality checkpoints layered across all of them.
If you’re starting from zero, build one versioned SOP template first, then pilot it on receiving for a small set of SKUs before rolling it out warehouse-wide. Shiporo, for example, builds every client onboarding around exactly this sequence.
TL;DR:
- SOPs should be tested on a small SKU set before full warehouse rollout to identify gaps and ensure compliance under pressure.
- Version control, clear KPIs, and evidence of steps are critical for maintaining effective SOPs and diagnosing errors.
- Peak-season SOPs must be activated four to six weeks in advance to allow staff training, capacity adjustments, and contingency planning.
- Most fulfillment failures occur due to last-minute SOP changes and lack of pilot testing, not from the SOPs’ written quality.
- Implementing SOPs with a dedicated system like Shiporo can reduce onboarding time to four or five days and improve fulfillment reliability.
Table of Contents
- What SOPs does a fulfillment operation actually need?
- What should a reusable SOP template actually include?
- Core fulfillment SOPs from receiving to returns
- How do you turn SOPs into a governed, working system?
- When do peak-season SOPs need to kick in?
- How Shiporo puts fulfillment SOPs into practice
- Why most fulfillment SOPs fail before they’re even tested
- Ready to stop writing SOPs and start running them?
- Sources
- FAQ
What SOPs does a fulfillment operation actually need?
Standard operating procedures for fulfillment aren’t a compliance formality. They’re the difference between an order that ships correctly in four hours and one that gets lost in a bin for three days. Every fulfillment operation, whether it’s a single warehouse or a network of 3PL sites, needs the same core checklist. What varies is how detailed each one gets.
- Receiving SOP: matches inbound shipments against purchase orders and flags damage before stock touches a shelf.
- Putaway SOP: gets inventory into the right slot based on how fast it sells, not just where there’s empty space.
- Picking SOP: defines the method (zone, batch, or wave) and how pickers confirm they grabbed the right item.
- Packing SOP: sets box size, weight tolerance, and insert rules so every parcel ships the same way twice.
- Shipping SOP: governs carrier selection, manifest cutoffs, and label accuracy.
- Returns SOP: dictates how an item gets inspected and routed back to stock, refurbishment, or the scrap pile.
Each one needs a measurable outcome attached, not just a description. Reasonable starting targets include dock-to-stock times that are rapid, high pick accuracy rates, and high on-time shipment rates. Before you sign off on any SOP, run a completeness check: does it list the required inputs, the expected output, and what to do when something goes wrong? If an exception path is missing, the SOP isn’t finished.
What should a reusable SOP template actually include?
A good SOP template works the same way whether it’s covering receiving, picking, or returns. The fields don’t change. Only the content inside them does.
- Purpose: one sentence stating what the SOP accomplishes and why it exists.
- Scope: which SKUs, locations, or order types the SOP applies to.
- Roles: who executes the step and who signs off on exceptions.
- Prerequisites: what needs to be true before the process starts (PO issued, dock door assigned, scanner charged).
- Steps: numbered, single-action instructions, written the way you’d say them out loud to a new hire.
- Exceptions: the specific “if this, then that” branches, not a vague “escalate as needed.”
- KPIs: the formula, not just the metric name (pick accuracy = correct picks ÷ total picks × 100).
- Evidence: what gets photographed, scanned, or logged as proof the step happened.
- Revision history: version number, effective date, and who approved the change.
For a receiving SOP, step five might read: “Scan PO barcode, confirm carton count against packing slip, photograph any damaged units before opening cartons, log lot number into WMS.” That level of specificity is what separates a real SOP from a training memo.
Pro Tip: Write every step as a device prompt, not a paragraph. If a picker or receiver has to stop and think about what a sentence means, the SOP has already failed on the floor.
Version control matters more than most operations managers treat it. Every SOP needs an effective date, a named approver, and a place to log what changed and why. Without that, you can’t tell whether a picking error came from a bad process or from someone following last month’s outdated instructions.
Core fulfillment SOPs from receiving to returns
Receiving starts with PO matching: scan or key the purchase order number and reconcile it against the packing slip before a single carton opens. Inspect for damage immediately and photograph anything questionable. This is the step legal and compliance reviewers flag most often. Written checklists and photo evidence protect both the warehouse and the brand when a dispute arises later, a point The Edu Law’s compliance checklist makes directly. Target dock-to-stock under four hours for standard SKUs.
Putaway and slotting should follow velocity data, not convenience. Fast-moving SKUs belong near the pack stations; slow movers can sit farther out. A warehouse management system gives real-time location data, which removes the manual cross-referencing that slows this step down and causes mis-slots.
Picking methods vary by order volume. Single-order picking runs 60 to 80 picks per hour, batch picking pushes 120 to 200, and zone or conveyor setups can hit 200 to 400, according to WorkProcedures’ fulfillment SOP guide. Choose the method based on order density, then build scan verification into every pick so accuracy doesn’t depend on memory. Shiporo’s breakdown of picking and packing in warehousing covers how zone, batch, and wave picking trade off against each other in practice.
Packing needs a standard for box size, weight checks, and insert placement, with separate rules for fragile items. External primers like Sara West’s kitting and case-packing guide cover quality-control checkpoints worth borrowing for multi-item orders.
Shipping SOPs govern carrier selection logic, dimensional weight checks, and manifest cutoffs, so nothing misses the truck because someone didn’t know the deadline.
Returns need a clear RMA intake process and a disposition workflow: inspect, then route to restock, refurbish, or scrap, with the decision criteria written down instead of left to judgment calls.
How do you turn SOPs into a governed, working system?
Writing an SOP is the easy part. Making sure it’s followed on a warehouse floor, by a rotating shift of workers, is where most operations fall apart. That takes governance, not good intentions.
- Intake through one channel. Every SOP request, whether it’s a new client requirement or an internal fix, should funnel through a single submission channel with a completeness checklist attached, so nothing gets implemented half-documented.
- Pilot before scaling. Test a new or revised SOP on a small SKU set before it touches the full warehouse. This is exactly how Cleverence recommends implementing client-specific SOPs in a 3PL setting, moving from documented process to process map to device workflow.
- Build device prompts, not manuals. Convert each SOP step into a short, screen-based instruction inside your WMS or warehouse execution system. Workers should never have to guess the next step or flip through a binder.
- Track KPIs with defined formulas. Pick accuracy, on-time-ship, and dock-to-stock need exact formulas and a reporting cadence, not vague monthly summaries.
- Audit on a schedule. In-line checks, sampling plans, and photo evidence catch drift before it becomes a pattern.
An order management system sitting above the WMS handles the routing and carrier-selection logic that SOPs alone can’t, applying pick priorities and carrier rules automatically instead of leaving it to manual judgment. On the billing side, every extra step a client requires should map to a specific tariff line. Skip that mapping and the SOP quietly erodes your margin every time it runs.
When do peak-season SOPs need to kick in?
Activate peak SOPs four to six weeks before forecast volume hits, not the week of. That gives time to train seasonal staff on simplified steps, add packing capacity, line up carrier contingencies for cutoff changes, and set clear escalation triggers before volume actually spikes.
- Simplify job steps for temporary hires and check comprehension before peak week, not during it.
- Shift picking methods (batch or wave) to handle higher order density.
- Pre-negotiate carrier contingencies in case a primary carrier hits capacity limits.
- Set fallback routing rules so escalations don’t stall an entire shift.
How Shiporo puts fulfillment SOPs into practice
Shiporo runs its floor operations on Shiphero, a WMS built specifically for direct-to-consumer order fulfillment, paired with real-time rate comparison across Canada Post, FedEx, UPS, Purolator, and regional carriers like Intelcom. New clients typically onboard in four to five days, not weeks, because SOP intake and pilot testing happen before go-live, not after.
Why most fulfillment SOPs fail before they’re even tested
Most operations managers over-invest in writing SOPs and under-invest in testing whether anyone can actually follow them under pressure. A twelve-page receiving procedure that nobody reads during a Monday rush isn’t a process. It’s a liability with good intentions attached.
The conventional advice, document everything, then train once, gets the sequence backwards. Pilot first. Pick one SKU category, run the SOP for two weeks, and count the exceptions that weren’t in the original document. Those gaps are the real SOP. Everything else is theory.
What gets underrated is version control. Warehouses obsess over KPIs like pick accuracy and dock-to-stock but rarely track which SOP version was active when an error occurred. Without that link, you’re guessing at root cause instead of diagnosing it.
If you take one thing from this, prioritize the pilot over the polish. A rough SOP tested on real orders beats a perfect one that’s never touched a scanner. Peak-season failures almost always trace back to last-minute changes nobody rehearsed, which is really the same lesson wearing a different hat.
— Felix Berns
Ready to stop writing SOPs and start running them?
If you’re building fulfillment SOPs from scratch, you already know the gap between a document and a working floor process. Shiporo closes that gap for eCommerce brands selling on Shopify and WooCommerce by running the SOPs for you, on a WMS built for it, with carrier rate comparison already baked in.
Shiporo fits DTC brands that need order accuracy without hiring an ops team to babysit it. Onboarding typically takes four to five days, not weeks, because the SOP intake and pilot testing described above happen before your first order ships. If receiving, picking, and packing procedures are eating your week, check Shiporo’s pricing calculator to see what handing off fulfillment would actually cost, and request a quote to get a pilot started.
Sources
- Warehouse operations: a complete guide | Epicor
- E-Commerce fulfilment SOPs: pick, pack, ship & returns procedures (2026) | WorkProcedures
- How to implement client-specific SOPs in 3PL operations | Cleverence
- Warehouse operations: the 6-stage ecommerce process | OmniOrders
- Legal compliance checklist for third-party prep and fulfilment services | The Edu Law
FAQ
What are some common SOPs in fulfillment?
The most common are receiving, putaway, picking, packing, shipping, and returns, each paired with a defined KPI like pick accuracy or dock-to-stock time.
What are the SOPs for a warehouse?
Warehouse SOPs typically cover inbound receiving and inspection, slotting and putaway, order picking, packing standards, outbound shipping and manifesting, returns disposition, and cycle counting for inventory accuracy.
What are the key processes in warehouse operations?
The core processes are receiving, putaway, inventory control, order picking, packing, and shipping, with a fulfillment centre specifically focused on picking individual eCommerce orders rather than bulk stock movement.
What are the main warehouse processes for eCommerce?
For eCommerce specifically, the essential five are receiving, putaway, picking, packing, and shipping, with returns processing and cycle counts layered on top to protect inventory accuracy over time.
How fast can a 3PL implement new SOPs?
A pilot rollout on a small SKU set can go live in days rather than weeks. Shiporo, for example, typically onboards new clients in four to five days by piloting SOPs before full-scale implementation.
