SOPs People Actually Follow: An India Ops Guide

Most ecommerce operations have SOPs. Very few have SOPs anyone follows. The document sits in a shared drive folder, eleven pages long, written in English by somebody who has never packed a carton, last edited two years ago.

An SOP is not a compliance artefact. It is a tool for making the correct action the easy action for a person on their fourth day.

Choose which processes deserve one

Writing 200 SOPs guarantees that none of them are current. A mid-size Indian fulfilment operation needs somewhere between 25 and 40 live documents. Score each candidate process on four questions:

• Is it done at least weekly? A rare task needs a checklist at the moment of use, not a standing document.
• Does getting it wrong cost money, break a compliance rule or hurt somebody? Legal metrology labelling, FEFO on dated stock, hazmat handling, high-value SKU custody, GST-relevant documentation.
• Is there more than one plausible way to do it? If the equipment enforces a single method, you do not need a document.
• Has it already gone wrong at least once? Real incidents are the best selection filter available to you.

Three yeses means write it. Two means fold it into a checklist inside an existing SOP. One means leave it alone. Review the whole list once a year and retire anything nobody has referenced.

The format that survives a shop floor

The SOP that works on an Indian warehouse floor is one side of A4, laminated, mounted at the place the work happens. Not in a binder. Not on a server that requires a login the operator does not have.

Use a fixed structure every time:

• Title, owner name, version number and effective date, at the top.
• Trigger: the one line stating when this SOP applies.
• Seven to twelve numbered steps. If you need more than twelve, you have two SOPs pretending to be one.
• Exceptions: the three or four things that commonly go wrong, and the correct response to each.
• Escalation: a name and a phone number, not a designation.

Write it in the language the floor speaks, with English alongside if you need it for auditors. Hindi, Marathi, Tamil, Kannada, Bengali, whatever the site actually runs on. Target a read time under ninety seconds and then test it. Hand the draft to the newest person on the floor and ask them to perform the task from it, with nobody helping. Every place they hesitate is a defect in the document.

Photographs beat paragraphs

The fastest way to halve the length of an SOP is to replace description with a photograph. Shoot on your own floor, with your own cartons, in your own lighting. Stock images teach nothing and quietly signal that the document is decorative.

• Show the correct outcome as a photograph: the packed carton, the label at the right position, the pallet at the right height.
• Put the wrong version beside it, clearly marked. People recognise a mistake faster than they parse an instruction.
• Use arrows and circles drawn on the image rather than a caption explaining where to look.
• Reshoot when packaging changes. A photo of last season’s box is worse than no photo, because it teaches the wrong thing with authority.

A carton packing SOP that ran to 400 words usually fits into six photographs and forty words of caption. The compression is the point, not a side effect.

Version control and who owns updates

One SOP, one named owner, one source file. The owner is the person who runs the process, not the quality manager and not a consultant. Anyone on the floor can raise a change request, and the owner either approves it or explains why not, within a week. A request that sits for a month teaches everyone that the document is fiction.

Mechanics that hold up in practice:

• Version number in the filename and on the printed sheet. Something like v3.2, effective 12 May 2026.
• A single-line change log at the bottom of the document. What changed, and why.
• Print each quarter’s revision with a different coloured border. A stale copy then becomes visible from across the floor without anyone reading it.
• When you post a new version, physically collect and destroy the old one. Uncollected old copies are the most common reason two people do the same job differently.
• Quarterly review of every SOP touched by an incident, and an annual sweep of the rest.

How SOP quality shows up in audits and error rates

Marketplace audits, 3PL onboarding audits, FSSAI inspections and brand quality audits all follow the same pattern. The auditor asks for the document, then walks the floor and watches. The finding is never the document itself. The finding is the gap between the document and the practice.

That is precisely why an eleven-page SOP is a liability. It hands an auditor eleven pages of claims to compare against reality. A one-page SOP that the operator can genuinely perform gives them very little to catch, because the document and the floor agree.

The error link is more direct still. Mis-pick and mis-pack incidents cluster on tasks where the current instruction is not present at the point of work. Before your next quality review, do one thing. Take your top five error types from the last quarter and check whether a current, legible, correctly located SOP exists for each. In most Indian operations at least two will be missing, out of date or pinned somewhere nobody stands. Fix those two before you write anything new.