Skip to content
Code Colonies

Solutions · Article

Warehouse management: when spreadsheets stop working

A spreadsheet can run a small godown well. The signs that you have outgrown it, what a warehouse management system really adds, and how to roll one out without stopping dispatch.

Code Colonies Technology Division · · 3 min read

Key takeaways

  • Bin locations and barcode scanning give most of the early benefit
  • Stock accuracy depends on process discipline more than on software
  • Go live in one zone or one product line before the whole warehouse

A spreadsheet is a perfectly good warehouse system for a small godown with a few hundred items and two people who know where everything is. It stops working gradually. First someone spends an hour looking for a carton that the sheet says is there. Then a customer is promised stock that was dispatched yesterday. Then the year end physical count disagrees with the books by an amount nobody can explain.

Signs you have outgrown the spreadsheet

  • Pickers rely on memory to find items, and new staff take weeks to become useful.
  • Stock in the books and stock on the shelf differ by more than you can tolerate, and you only find out at the annual count.
  • You track batches, expiry dates or serial numbers, and recalls or returns become detective work.
  • Dispatch errors, such as the wrong item, wrong quantity or wrong customer, show up as returns and complaints.
  • Several people edit the sheet at once, and versions get overwritten.
  • You run more than one warehouse, or a warehouse plus stock at a 3PL, and nobody has a combined view.

If two or more of these are true, a warehouse management system is worth a serious look.

What a WMS actually adds

At its core, a WMS does five things.

  1. Locations. Every item lives in a known bin, rack or zone. The system knows how much you have and exactly where it is.
  2. Scanning. Receiving, putaway, picking and dispatch are confirmed by scanning a barcode or QR label, usually on an Android handheld or a phone. This is where most accuracy gains come from.
  3. Tasks. The system tells each person what to pick, from where, in what order, on a handheld.
  4. Batch and expiry control. First expiry, first out for food and pharma; batch traceability for recalls.
  5. Cycle counting. Count a small set of locations every day, and the warehouse stays open all year.

Everything else, such as wave planning, slotting optimisation and labour tracking, matters for large operations. A business moving a few hundred orders a day can usually leave those for later.

Package, module or custom

ERP inventory module. Odoo, SAP Business One and similar systems include warehouse features with locations and barcode support. If you already run one of them, start here.

Dedicated WMS. Products built for warehousing go further with tasks, scanning and 3PL billing. They suit businesses where the warehouse is the operation, such as distributors and e-commerce fulfilment.

Custom application. Makes sense when your process is unusual, for example cut to length material, kitting for project sites or a mix of owned and consignment stock, and packages force awkward workarounds. Keep accounting in your ERP or Tally and let the custom app post stock movements to it.

Process first, then software

Software does not fix a warehouse where goods are received without checking, stacked wherever there is space and issued on verbal requests. Before go live:

  • Label every location. Rack, level and bin, printed and fixed in place.
  • Label every item or carton, or agree that supplier barcodes will be used and check that they are reliable.
  • Write the rule for receiving: nothing goes onto a shelf until it is checked against the purchase order and scanned.
  • Decide who can adjust stock, and require a reason for every adjustment.
  • Do a full physical count just before go live, so the system starts with the truth.

Rolling out without stopping dispatch

Pick one zone, one product line or one shift to go first. Run it for two to three weeks, fix what breaks, then extend. Keep the old spreadsheet read only for a while so people can check, but do not let anyone update it. Two systems of record are worse than one bad one.

Expect a dip in speed in the first fortnight as people learn to scan each item. It usually recovers within a month, and accuracy improves from the first week.

A rough sense of effort

For a single warehouse with a few thousand items, implementing a packaged WMS or ERP warehouse module typically takes one to two months including labelling, data clean up and training. Handhelds, label printers and Wi-Fi coverage in the racks are often forgotten in the budget, so survey the building early. Dead spots behind steel racking are common.

If your problem is mainly that sales cannot see live stock, you may not need a full WMS at all. A shared stock view fed from your ERP, plus disciplined receiving and dispatch entries, can solve that for much less.

Have a question about this guide? Write to us or ask Colony, our AI guide.

Start a conversation

Tell us what you are trying to build.

Share the problem in a short call. You leave with a clear view of the approach, the team and the cost.

Or get a ballpark proposal in two minutes

A specialist replies within one working day. The first conversation is free.

Chat with the Code Colonies team on WhatsApp