Why most warehouse improvement efforts fail
Most warehouse improvement projects focus on the wrong thing. They buy a software system, or rearrange the racking, or hire a consultant who produces a report — without first understanding why the current warehouse is performing the way it is.
In most Indian manufacturing and distribution warehouses, the underlying problems are the same regardless of industry: goods are received on paper and entered into the ERP later; FIFO is written in the SOP but not enforced at the pick; nobody knows which bin anything is in without asking the person who put it there; the annual stocktake shows a variance that takes weeks to reconcile; and warehouse performance is measured by intuition rather than data.
These 8 tips address the specific problems that show up in Indian warehouse operations. Each tip is specific and actionable — the aim is that you can take one tip and implement it this week. Not all 8 need to happen at once. Start with the one that describes your biggest current pain point.
Fix the GRN process first
The Goods Receipt Note (GRN) is the most important document in any warehouse. It is the moment at which stock officially enters the system — and it is the moment at which most warehouse accuracy problems begin.
The problem in most Indian warehouses
In the typical Indian warehouse, the GRN process works like this: the truck arrives, the store man unloads and counts the goods, writes the quantities on paper, compares them informally against the challan, signs the delivery document, and lets the truck leave. The paper receipt is then handed to the accounts department, who enter it into Tally or the ERP the next morning — or sometimes later in the week.
The problems this creates are immediate and compounding. If the delivery is short or has damaged goods, the truck is already gone by the time the discrepancy appears in the system. Lot numbers and expiry dates, if captured at all, are written on a register and never make it into the inventory system. And the time lag between physical receipt and system record means there is always a period when stock exists physically but not digitally — or vice versa.
What to do instead
The result: zero time lag between physical receipt and system record. Discrepancies caught before the truck leaves. Lot numbers captured correctly at the source. And every GRN scan becomes an immutable ledger entry — traceable from receipt to dispatch.
Enforce FIFO at the scan, not just on paper
FIFO — First In, First Out — is in the SOP of almost every warehouse in India. It is followed by almost none of them consistently, because it relies on the picker making the right decision rather than the system enforcing it.
Why FIFO policy fails
In a manual warehouse, the picker goes to the bin, sees three lots of the same item, and picks from the one at the front — which is the most recently received, not the oldest. The older lots are at the back. Nobody manually checks receipt dates and sequences them before picking. FIFO policy exists on paper. FIFO practice is a different matter.
For most items, the difference between picking the February lot vs the January lot is negligible. But for items with expiry dates — food, pharma, chemicals, rubber, lubricants — picking in the wrong sequence causes real damage: expired stock dispatched to customers, recall risks, rejected deliveries, financial and reputational cost.
The right way to enforce FIFO
FIFO enforcement requires two things to work together: correct lot capture at GRN (which Tip 1 addresses) and scan enforcement at pick.
Replace annual stocktake with cycle counting
The annual physical stocktake is a fixture of Indian warehouse operations — often conducted at year-end, taking 2–3 days, halting all warehouse activity while every item is counted, reconciled, and adjusted. It is also the least efficient way to maintain inventory accuracy.
The problem with annual stocktake
By the time you discover a variance in an annual count, the cause is untraceable. Was the stock lost in July? In October? Was it a GRN error, a picking error, or a theft? A year's worth of transactions separates the count from the cause. And because the variance is discovered all at once, the adjustment is done in bulk — often with low confidence in the numbers.
Meanwhile, the 2–3 day shutdown costs both direct labour (staff counting instead of picking and dispatching) and opportunity cost (orders delayed or postponed around the count window).
Cycle counting — the better approach
Cycle counting counts a small section of the warehouse on a regular schedule — one bin group, one aisle, one product category — without stopping operations. Over a period of weeks or months, every section is counted. Discrepancies appear immediately, while the cause is still recent and traceable.
| Factor | Annual Stocktake | Cycle Counting |
|---|---|---|
| Frequency | Once a year | Continuously (daily or weekly sections) |
| Operations during count | Halted | Continues normally |
| Discrepancy discovery | 12 months after the fact | Days or weeks after the cause |
| Variance traceability | Very difficult | Traceable — recent transactions |
| High-value item coverage | Once a year | A items counted monthly |
| Adjustment confidence | Low — bulk adjustment | High — specific, recent cause |
| Staff disruption | Major (all hands for 2–3 days) | Minimal (one area at a time) |
The ABC approach to cycle counting
Not all items need to be counted with equal frequency. ABC analysis provides the framework:
A items — top 70% of inventory value
High-value items carry the greatest financial risk per unit of discrepancy. Errors here affect cash flow and financial reporting most significantly.
B items — 20–30% of value
Moderate risk, moderate frequency. Often the largest group by SKU count.
C items — remaining value
Low value per unit means low financial risk per discrepancy. Basic controls are sufficient.
Use ABC analysis to prioritise your controls
Not all inventory deserves the same level of attention. ABC analysis is the framework that makes this explicit — identifying which items account for most of the value, and directing tighter controls where the financial risk is highest.
The ABC principle
ABC analysis divides inventory into three categories based on value contribution — typically measured as total annual usage value (quantity × unit cost):
A items: typically 10–20% of SKUs, accounting for approximately 70% of total inventory value. These are your highest-value items — the ones where a counting error, a FIFO violation, or a picking mistake has the most significant financial consequence.
B items: typically 30–40% of SKUs, accounting for 20–30% of total value. Moderate controls required.
C items: the majority of SKUs by count, accounting for less than 30% of total value. Basic controls — periodic cycle counting and standard reorder triggers — are sufficient.
How to apply ABC in practice
Slot fast-movers close to dispatch
Pickers in a typical warehouse spend 50–70% of their working time walking — to the bin, back to packing, to the next bin, back again. Most of that walking is driven by where items are stored, not by how many items need to be picked. Slotting — the decision about where each item lives — directly controls how far pickers walk.
The basic slotting principle
Fast-moving items (high-velocity SKUs) belong closest to the dispatch area. Slow-moving items belong further away. This single change — moving fast-movers to the front — reduces average pick travel without changing the warehouse layout, adding staff, or buying any technology.
The calculation is simple: if a picker makes 200 picks per shift and each pick requires 30 seconds less walking because the item is in a nearby bin rather than a distant one, that is 100 minutes saved per picker per shift. Across five pickers, that is over 8 hours of productive picking time recovered every day — without hiring anyone.
How to implement basic slotting
Beyond basic slotting
Advanced slotting also considers co-picking patterns — items frequently ordered together should be stored near each other, so the picker can collect both in one pass. Wave picking in Fast WMS already optimises the pick route (shortest path across bins) — but if the items themselves are far apart, the route optimisation can only do so much. Good slotting and good pick list optimisation work together.
Standardise bin locations before anything else
If there is one prerequisite for every other tip in this guide, it is this one. Bin location standardisation is the foundation on which every warehouse efficiency improvement rests. Without a consistent, named, scannable address for every storage position, nothing else works reliably.
What a bin location system needs
A bin location address needs three properties to be useful: it must be unique (no two bins with the same code), hierarchical (the code shows where in the warehouse the bin is, not just what it is), and scannable (a barcode label on the physical bin that the WMS can validate by scan).
The recommended format for Indian warehouses follows the Fast WMS hierarchy: Plant → Warehouse → Store → Aisle → Bay → Shelf → Bin.
A typical bin code looks like: 1102A11-B1 — Plant 1102 · Aisle A · Bay 11 · Shelf B · Position 1. This code is short enough to be readable by staff but contains enough information to identify the exact location within a multi-warehouse, multi-plant operation.
How to implement bin labelling
Want to see bin location tracking live in Fast WMS?
A 30-minute demo shows bin assignment at GRN, directed put-away, scan-confirmed picking from named bin locations, and the graphical bin map — live on your warehouse layout.
Track 6 KPIs every week
Most Indian warehouses manage performance by feel — there are no numbers, only reactions to complaints. When a customer calls about a wrong delivery, that's when picking accuracy becomes visible. When the monthly Tally stock report doesn't match physical count, that's when inventory accuracy becomes a conversation. Managing this way means problems are always discovered after the damage is done.
Tracking the right KPIs weekly means problems are visible in the data before they become complaints.
The 6 KPIs that matter for Indian warehouse operations
These six KPIs are all available directly from Fast WMS reports — no additional analytics layer required. The practice of reviewing them weekly takes 30 minutes and makes every warehouse management conversation data-driven rather than anecdotal.
Fix the process before you automate it
This is the tip that runs under every other tip in this guide — and it is the principle that Improsys applies in every warehouse engagement before recommending or implementing software.
A Warehouse Management System automates what the process does. If the GRN process is inconsistent before a WMS, the WMS will make it consistently inconsistent. If pickers ignore FIFO before a WMS, the WMS will produce detailed records of FIFO being ignored. If bin locations are undefined before a WMS, the WMS will enforce an undefined bin location system.
What process fixing looks like
Improsys approaches every warehouse engagement with consulting before software — specifically, the Lean/KAIZEN/value stream mapping methodology. Before any WMS implementation, the team:
This is not a unique insight — it is the principle behind every successful ERP and WMS implementation, confirmed by decades of experience across manufacturing and logistics operations. But it is routinely skipped when the software sale is the primary objective. It is not skipped here.
The order to implement these tips
If all eight tips feel like too much at once, here is a practical sequencing based on dependency:
Set the foundation (Weeks 1–4)
Every other tip depends on knowing where things are (bins) and having accurate inbound records (GRN). These two create the data foundation everything else relies on.
Control quality (Months 1–3)
Once bins are labelled and GRN is accurate, FIFO enforcement and ABC-based counting become effective. Without accurate GRN data, FIFO cannot be enforced. Without bin locations, ABC slotting cannot be implemented.
Measure and improve (Month 3 onwards)
Slotting optimisation requires velocity data — which only exists after 8–12 weeks of WMS operation. KPI tracking becomes meaningful once the process changes of Phases 1 and 2 have stabilised. The process-first principle is ongoing — not a one-time step.
