HELIVIQ Team · Published 18 October 2026
ERP implementations in trading and distribution businesses rarely fail because a feature is missing. They fail on data discipline, on people under pressure and on a stock module nobody trusts by the third month.
The part-number master breaks first
A trading business may carry thousands of items, often with several names for the same product: the supplier's code, the customer's code and what the counter staff call it. If the item master is loaded without removing duplicates and fixing units, stock will never reconcile and every report built on it will be questioned.
Training is treated as a one-day event
Counter and stores staff work under constant pressure. If the new system is slower than the old register for the job in front of them, they will go back to the register. Training has to cover their actual daily tasks, with screens set up for speed, and be repeated in the first weeks.
Stock trust disappears quietly
The first time the system shows stock that is not on the shelf, people stop believing it. Opening stock must be counted physically, receipts and issues recorded the same day, and differences investigated rather than adjusted away.
Too much scope in phase one
Switching on every module at once spreads attention thin. A first phase that covers enquiries, quotations, orders and stock — done well — builds more confidence than a complete system nobody uses fully.
What a workable rollout looks like
- Clean the item master before go-live: one code per product, correct units, brand and specification fields
- Count opening stock physically
- Go live with the core sales and stock flow first
- Review daily for the first month and fix the screens that slow people down
- Add purchase, job work, dispatch and reporting once the core flow is trusted