Why your warehouse is still running on Excel and what actually replaces it
Most warehouses didn't replace paper with software. They replaced it with stock.xlsx, opened by three people at once and one broken VLOOKUP away from losing a month of counts. Here's what a real system looks like.
The spreadsheet didn't solve the problem - it just hid it
Paper had obvious failure modes. Clipboards went missing, handwriting got misread, picking sheets piled up in a tray nobody opened. So most warehouses moved to Excel, or to a shared Google Sheet, and decided they were digital.
But the spreadsheet didn't fix the problem. It just made the problem quieter.
Four failure modes come up every time we audit a warehouse running on spreadsheets:
Version confusion. Is stock.xlsx, stock_final.xlsx, or stock_final_v2 (copy).xlsx the current one? Someone emailed a copy on Tuesday, three people edited it, one of them overwrote Monday's count. Nobody's sure what the real number is.
Formula rot. Someone widens a column, someone else sorts the sheet without selecting the full range, and a VLOOKUP that used to pull pack sizes now returns the wrong row for half your SKUs. Nobody notices until a customer complains — or until you're forty cases short at year-end.
Point-in-time stock, pretending to be real-time. The sheet was accurate when someone exported it at 9am. By 3pm, after forty sales, it's fiction. The salesperson on the phone to the customer doesn't know that. Neither does the picker.
Adjustments that never make it in. A return gets noted in a WhatsApp group. A stock adjustment gets mentioned at the end of a meeting. A damaged pallet gets a sticky note on the monitor. None of it makes it into the sheet until someone's month-end tidy-up — if at all.
All four are quiet enough that you can run on spreadsheets for years without realising they're costing you. Then one year-end the stock valuation comes in tens of thousands under where it should be, and nobody can point to where it went.
From sales channel to picker's screen
In MAKSUD WMS there is no spreadsheet to keep in sync. An order arrives — from a phone call, a walk-in, the webshop, or an EPOS till — and lands immediately in the sales queue on the warehouse screen.
A picker opens the order, scans each item's barcode, and the system confirms the match. No line to tick on a printout. No cell to update on a sheet. If the barcode doesn't match the order line, the scan fails on the spot, and the picker knows before the item reaches the packing bench.
Stock decrements the moment the sale is confirmed — not the next morning, not at close of day. The salesperson on the other side of the building cannot promise what the picker just took off the shelf.
Selling eaches from a case without the stock drifting
This is where most warehouses discover that their spreadsheet was never really tracking stock — it was tracking one unit of measure and hoping that was enough.
Picture a 24-pack of tinned tomatoes. Some customers buy the case. Some buy a single tin. The typical Excel approach is two rows — one for the case, one for the tin — and a hope that someone remembers to adjust both when a case gets broken down on the shop floor. That hope is where the stock drifts from reality.
MAKSUD tracks both as linked products — the case as the parent, the tin as the child. The available stock of the tin is calculated as the loose tins on the shelf plus the unopened cases multiplied by the pack size. When a customer orders more tins than you have loose, the system breaks down a case automatically: the parent count drops by one, the child count rises by the pack size, and the sale completes. Every breakdown is logged.
For food wholesalers, cash-and-carries and hospitality suppliers, this is the difference between stock counts that match and stock counts that quietly drift.
When the shelf and the till agree
Most warehouse systems stop at the loading bay. Most till systems stop at the counter. If you run both — a cash-and-carry, a retail-plus-wholesale operation, a shop with a working stockroom — the seam between them is where spreadsheets usually live. Someone exports stock at 9am, someone else re-imports it at 5pm, and the middle of the day is a guess.
MAKSUD runs the warehouse and the till on the same inventory. A sale at the counter reduces warehouse stock the moment it's rung through. There is no nightly sync, no CSV export, no second sheet to keep in step. The shelf knows what the till did.
Accounting without the monthly CSV shuffle
The spreadsheet in the warehouse has a twin: the spreadsheet you send to the accountant. Invoices, credit notes, stock adjustments — exported from one system, cleaned up, reformatted, then imported into the accounting package. It's where half the errors get introduced, and the whole thing eats a day every month.
MAKSUD posts invoices and credit notes straight to Xero as they happen. If you're switching from another system, a single backfill sends your existing history across in one pass, no CSVs involved.
Customer updates follow the same rule. Order shipped, order ready for collection, order delayed — MAKSUD sends WhatsApp notifications in the moment, without anyone re-typing customer numbers into a phone.
The test worth putting to any new system
When a warehouse moves off spreadsheets, the right question isn't "is it faster?" It's "do the numbers match at the end of the month?"
If your current setup still has you chasing ghost stock, arguing with your accountant about variance, or answering customer calls about orders you thought had shipped - the spreadsheet is still winning, whether or not it looks like you've moved on from paper.
See it on your own stock. Request a 20-minute walkthrough with your actual SKUs and we'll show you where the drift is coming from.