ESSAYSNO. 114
Why ERP Won't Fix a Broken Warehouse (And Why I Paused a Project Without Permission)
An ERP implementation that would have digitised a disorganised warehouse, and why pausing it for two weeks was the right call.
The Assumption: ERP Would Solve Everything
A while back, I was leading an ERP implementation for a disability-inclusive manufacturing and assembly enterprise (NDIS Co-Packer).
Like many businesses, they believed ERP would fix inefficiencies, automate workflows, and streamline distribution.
That's what we sold them.
But there was a problem.
We sold them something that wouldn't work.
My boss sold them ERP for warehouse management.
The assumption? That it would bring order to the chaos.
The reality? The warehouse was in no state for automation.
- Stock was placed wherever there was space.
- No structured process for receiving, storing, or picking items.
- No tracking system—staff relied on memory to find stock.
ERP wasn't going to fix this. It was going to make it worse.
And I saw the risk early.
So I did something I wasn't technically allowed to do—I paused the project.
Why I Stopped the ERP Implementation (Without Permission)
We weren't waiting for go-live to see problems unfold.
It was obvious before we even started system configuration that if we pushed forward, the ERP would fail.
- The warehouse had no process discipline. Even if ERP introduced structure, employees weren't trained to follow it.
- Inventory data was completely unreliable. The system needed accurate stock locations, but none existed.
- Order fulfillment was chaotic. Staff had no standardized way of picking and packing.
If we pushed forward, the ERP would have been dead on arrival.
I made the call to stop ERP rollout for two weeks—just enough time to fix the foundation.
Not a complete overhaul.
Not a six-month transformation.
Just enough to get an MVP warehouse redesign that ERP could actually work with.
The Fix: A Quick but Effective Warehouse Overhaul
Instead of pretending we had all the answers, I admitted what we didn't know—we weren't warehouse experts.
So, we brought in a specialist to do what we couldn't.
Step 1: A Quick Warehouse Assessment (No More Guesswork)
We needed a fast but focused review of the warehouse.
- How were goods received? Were they checked before storage?
- Where was stock stored? Was there any structure, or was it random?
- How was stock picked and packed? Were there defined processes?
The answer? There was no structure at all.
At this point, ERP was still on hold.
Step 2: An MVP Warehouse Redesign (Not Perfect—Just Functional)
We hired a warehouse specialist who did a quick AutoCAD overhead redesign—but we didn't stall the project for months.
In just a couple of weeks, we:
- Re-engineered the warehouse layout to optimize storage and workflow.
- Mapped out the most efficient picking routes to reduce order fulfillment time.
- Defined key zones for receiving, storing, and packing goods.
- Implemented a basic but structured inventory system—just enough to make ERP functional.
No perfection. Just enough structure to support the system.
Step 3: Training the Warehouse Team—Before ERP Came In
Even a basic redesign wouldn't work if employees didn't follow a structured process.
So before touching the system, we:
- Ran process training on stock receiving, placement, and retrieval.
- Did manual pilot runs to ensure the new structure worked before automation.
- Had staff operate without ERP first, following the new warehouse rules.
Once the warehouse was working without the system, we knew it was finally ready for automation.
Step 4: Implementing ERP—Now the Right Way
With a functional warehouse structure and trained staff, ERP finally made sense.
- Stock locations were mapped into ERP. Every item had a fixed location, ensuring accurate tracking.
- Picking and packing followed a structured workflow. No more searching for stock.
- The system reinforced the process, instead of creating more chaos.
The Results?
- Orders were fulfilled faster.
- Inventory was accurate and reliable.
- Staff trusted the system because it now matched reality.
ERP didn't fix the warehouse.
Fixing the warehouse made ERP work.
Final Thoughts: Get Your House in Order First
Most companies rush into ERP thinking it will solve all their operational problems.
But technology doesn't fix a broken foundation.
If your warehouse is a mess, ERP will just digitize that mess.
Before you implement ERP, ask yourself:
- Is our inventory structured and accurate?
- Do we have clear stock placement rules?
- Are staff trained in a standardized process?
If not, stop and fix those first.
Get your house in order.
Then bring in ERP to scale what's already working.
I wasn't supposed to stop this project.
But it was the right thing to do.
Have you ever had to hit pause on a project because the business wasn't ready?
ALSO IN THE REGISTER
- Entry 09The operating model comes after the system (it never does)A programme cannot skip the operating model, it can only skip designing it.2 MIN
- Entry 35The system went live eight months agoWhen nobody designs how the business will run in a new system, the people at the desks decide it one workaround at a time.2 MIN
New entries, when there’s something worth saying.