Warehouse SOPs for an ecommerce brand: which to write and what goes in each
Updated:
A warehouse SOP (standard operating procedure) is a written, step-by-step instruction for one warehouse process, so every person on every shift does it the same way. An ecommerce warehouse in India typically needs SOPs for receiving, QC, putaway, replenishment, picking, packing, dispatch handover, returns and RTO, cycle counts, order holds and safety. Each SOP should name its owner, what starts it, the steps, the record each step leaves and what to do when something goes wrong.
The SOPs an ecommerce warehouse needs
| SOP | What it covers | Record it leaves |
|---|---|---|
| Gate entry and receiving | Logging the vehicle and documents, counting cartons and units against the ASN and purchase order, and recording batch, expiry and serial numbers | GRN with shortages, excess and damage noted |
| Inbound QC | Which receipts get a full inspection and which get a sample check, and what happens to rejected stock | QC result per receipt; quarantine record |
| Putaway | Which bin each product goes to, and the scan that confirms it | Bin location for every unit |
| Replenishment | When and how stock moves from reserve storage to the pick area | Bin-to-bin stock move |
| Picking | Pick lists, the picking method, scanning the bin and the item, and what to do when a bin is short | Pick confirmation; short-pick record |
| Packing | Scanning each piece, choosing the carton, adding the packing slip and invoice, sealing and weighing | Packed carton linked to its order |
| Dispatch handover | Staging by courier and channel, scanning cartons to the manifest, and handing over before the pickup cut-off | Manifest signed by the courier |
| Returns and RTO | Receiving returns, checking each item, deciding what happens to it and where it goes | Return record with a decision per item |
| Cycle counts and adjustments | Which bins are counted and when, how counts are taken, and who approves a stock adjustment | Count result and approved adjustment |
| Order holds and cancellations | Stopping an order before it is picked or shipped, and returning picked stock to its bin | Hold and release record |
| Safety and housekeeping | Stacking, aisles, fire exits, equipment use, protective equipment and 5S | Daily checklist |
Add SOPs for batch and expiry stock, B2B or quick-commerce purchase orders, and sale days if they apply to you. The guides on receiving and putaway, short picks, marketplace dispatch deadlines, returns processing, cycle counts, batch and expiry (FEFO), quick-commerce POs and sale days cover the steps for each.
What goes in each SOP
- Header. The SOP title, a document number, the version, the date it takes effect and the date it is next reviewed.
- Purpose and scope. A short statement of why the procedure exists and which stations, shifts or product types it covers.
- Owner and roles. Who is responsible for the SOP, who does each step and who decides exceptions.
- Trigger. What starts the procedure: a vehicle at the gate, a pick list released, a return scanned in.
- Steps. Numbered, one action per step, written as an instruction, in the order they happen on the floor.
- Records. The scan, entry or signature each step leaves, so anyone can check later that it was done.
- Exceptions. What to do when the count doesn't match, the bin is empty, the item is damaged or the system is down, and who to call.
- Measures. How you will know the SOP works, such as order accuracy or on-time dispatch, reviewed on a fixed day.
How to write warehouse SOPs that get followed
- Start from the floor. Watch the process with the person who does it, and write down what actually happens before deciding what should.
- Write the steps as instructions. "Scan the bin label", not "the bin should be scanned".
- Show it. Add photos of the station, the screen and the correct label position.
- Write in the team's language. Give floor teams the SOP in the language they read best, such as Hindi or the local language, as well as English.
- Post it at the station. A one-page version at each bench or zone gets read; a binder in the office doesn't.
- Train and sign off. Walk each new person through the SOP and record who has been trained on which version.
- Change it when the process changes. Update the SOP whenever the layout, the system or a channel's rules change, and after each peak, and withdraw the old version so only one is in use.
Example: a packing SOP for an ecommerce order
This is an outline to adapt, not a standard. Replace each step with what your own pack bench does.
- Take the next tote or pick list from the packing queue.
- Scan the order, then scan each piece and check it against the order: item, size or variant, quantity and condition.
- If a piece is missing, wrong or damaged, stop, put the order on the exceptions shelf and record why.
- Choose the carton or mailer, add protective packing, and add the packing slip or invoice the channel requires.
- Seal the carton, weigh it if your courier needs the weight, and apply the shipping label.
- Place the carton in the staging lane for its courier or channel.
- At pickup, scan each carton to the manifest and get the courier's signature on it.
Common SOP mistakes
- Writing for an auditor, not the floor. Long documents in office language get signed and then ignored.
- No exceptions section. The steps cover the normal case; errors happen in the cases the SOP is silent on.
- Several versions in use. Old printouts at the bench keep the old process alive.
- SOPs that don't match the system. If the SOP says one thing and the warehouse software asks for another, the team follows the screen.
- No owner. An SOP that nobody owns goes out of date at the first change.
- Nothing measured. Without a measure, nobody knows whether the SOP is followed until a customer complains.
How Fretron CommerceOS fits warehouse SOPs
Fretron CommerceOS is order, warehouse and shipping software for Indian D2C, retail and omnichannel consumer brands.
Scanning on the floor. Your warehouse team works the floor on a phone — fifteen scan stations from gate entry to dispatch handover. No handheld hardware required.
Receiving and QC. Inbound stock is received against the ASN with a GRN, and QC can accept or reject each piece and quarantine it.
Putaway. Putaway is directed to zone-compliant bins by product type.
Picking. Pickers scan the bin, then the item or serial.
Packing and dispatch handover. Each piece is scanned at the pack bench before the carton is closed, and cartons are scanned to the courier manifest at handover.
Returns. Returns come back through QC on the same record, with the disposition decision captured per line.
Order holds. An order on hold can't be picked, packed, labelled or dispatched until it is released.
Stock. Stock is held on one on-hand ledger, with reservations, batches and serial numbers recorded on it.
Frequently asked questions
- What is a warehouse SOP?
- A warehouse SOP (standard operating procedure) is a written, step-by-step instruction for one warehouse process, such as receiving, picking or packing. It says who does the work, what starts it, each step in order, the record each step leaves and what to do when something goes wrong, so every shift does the work the same way.
- What SOPs does an ecommerce warehouse need?
- An ecommerce warehouse typically needs SOPs for gate entry and receiving, inbound QC, putaway, replenishment, picking, packing, dispatch handover, returns and RTO, cycle counts and stock adjustments, order holds and cancellations, and safety and housekeeping. Add SOPs for batch and expiry stock, B2B purchase orders and sale days if they apply.
- What should a warehouse SOP include?
- A header with the title, number, version and dates; the purpose and scope; the owner and roles; the trigger; numbered steps; the record each step leaves; the exceptions and who decides them; and how the SOP is measured.
- What are the 5S in a warehouse?
- 5S is a housekeeping method in five steps: sort (remove what isn't needed), set in order (give everything a marked place), shine (clean and inspect), standardise (write the routine down) and sustain (check it regularly). In a warehouse it usually sits in the safety and housekeeping SOP.
- What is the difference between an SOP and a KPI?
- An SOP says how a task is done; a KPI measures how well it is done. For example, a packing SOP sets out the scan and check at the bench, and order accuracy, the share of shipped orders that left with the right items, shows whether the SOP is working.
- How often should warehouse SOPs be reviewed?
- Review an SOP whenever the process, the layout, the system or a channel's rules change, after each peak season, and on the review date set in its header. Withdraw the old version when the new one takes effect.
- How does Fretron CommerceOS fit with warehouse SOPs?
- Fretron CommerceOS is order, warehouse and shipping software for Indian D2C, retail and omnichannel consumer brands. Pickers scan the bin, then the item or serial. Each piece is scanned at the pack bench before the carton is closed, and cartons are scanned to the courier manifest at handover. An order on hold can't be picked, packed, labelled or dispatched until it is released.