This case study looks at a US distributor that outgrew QuickBooks and spreadsheets. The client is not named; the figures are the ones already published on our founder's profile.
The project at a glance
| Before | After | |
|---|---|---|
| Systems | QuickBooks, spreadsheets and one person's memory | One ERP for inventory, purchasing, manufacturing and accounting |
| Warehouses and catalogue | 4 warehouses, more than 3,000 SKUs | Same, with stock visible in one place |
| Stock-outs | 2–3 a week | Near zero within two months |
| Purchase orders | Raised by hand | 90% generated by reorder rules |
| Month-end close | 4 days | Half a day |
| Time to go live | – | 10 weeks |
| Payback | – | By month 4 |
The situation
The company had 4 warehouses and more than 3,000 SKUs, and its tools had not kept up:
- Accounting ran in QuickBooks.
- Stock was tracked in spreadsheets.
- Reordering depended on one person's memory.
The result: products ran out two or three times a week, and closing the books took four days every month.
What the implementation covered
The ERP implementation covered inventory, purchasing and manufacturing.
- Stock in one place. All 4 warehouses and more than 3,000 SKUs in one system, with real-time quantities instead of spreadsheets.
- Reorder rules instead of memory. Minimum and maximum stock levels and vendor lead times let the system generate purchase orders when stock runs low. Today 90% of purchase orders are generated this way.
- Small settings over custom code. A reorder rule set up in minutes can save more time than a new custom module, and it keeps future upgrades simple.
The results
- Stock-outs fell from 2–3 a week to near zero within two months.
- Reorder rules now generate 90% of purchase orders automatically.
- Month-end close went from 4 days to half a day.
- The project went live in 10 weeks and paid for itself by month 4.
What other distributors can take from this
- Start where it hurts most. Go live with the area in the most pain, make it stable, and let the team win once before adding the next part.
- Judge an ERP on your worst order, not a demo. Ask vendors to run last month's messiest order with your data.
- Replace memory with rules. If reordering depends on one person, it will fail the week they are away.
- Clean the data first. Fixing product codes, units and opening stock is cheaper before go-live than after; messy data is the most common reason ERP timelines slip (see how long an ERP implementation really takes).
- Watch month-end. If close takes days because stock values do not reconcile, the problem is the system, not the accountants.
If you are planning a similar move, our guides on planning an ERP budget and SaaS versus custom software costs help you size it.
How MFY Innovatech works with distributors
Our team implements ERP for wholesale distributors in the United States as an official Odoo partner and a US-registered company: multi-warehouse inventory, reorder rules, purchasing, lot and serial tracking, and accounting in one system. See ERP and inventory software for wholesale distributors and our ERP implementation services.
Frequently asked questions
- How long did the ERP implementation take?
- The implementation, covering inventory, purchasing and manufacturing, went live in 10 weeks. A focused scope and standard ERP flows are what make timelines like that possible.
- What results did the distributor see?
- Stock-outs fell from 2–3 a week to near zero within two months, reorder rules now generate 90% of purchase orders automatically, and month-end close went from 4 days to half a day. The project paid for itself by month 4.
- Why did QuickBooks stop being enough?
- QuickBooks handled the accounting, but stock across 4 warehouses and more than 3,000 SKUs lived in spreadsheets and in one person's memory. Without real-time stock and reorder rules, the company ran out of products every week and closing the month took days.
- Can a distributor keep QuickBooks and add inventory software instead?
- Sometimes, for a single warehouse and a small catalogue. Once you have several warehouses, many SKUs, purchasing based on reorder points and month-end close depending on stock values, one system for inventory, purchasing, sales and accounting usually removes more work than it adds.
- Why is the client not named?
- We keep client names confidential unless a client chooses to be named. The figures in this case study are the ones already published on our founder's profile.
Keep reading
Related guides
- How Long Does an ERP Implementation Really Take? Timelines by Company SizeSmall companies go live in 2 to 4 months, mid-sized in 4 to 9, large multi-company rollouts in 9 to 18. Phase-by-phase timelines and what makes them slip.
- Case Study: A 3D Product Animation Series for a US Hyperbaric Chamber CompanyHow our team produced five 3D product animations for a US hyperbaric chamber company, one film per model, and what medical equipment makers can learn.
- How to Plan an ERP Budget: What Really Drives the CostWhat actually drives ERP implementation cost: licences, scope, data, integrations, customisation, training and support. A practical way to build an ERP budget.
Talk to us directly
Prefer a quick conversation?
Message us on WhatsApp or call. You'll reach the team, not a call centre.

