A growing Canadian beauty and wellness retailer had outgrown its tools — not its ambition. A dozen stores, an online shop, and a sprawl of software that each worked alone. I gave it one connected system to run on.
This was a thriving retailer — beauty, cosmetics and wellness products, sourced both locally and imported, sold through twelve stores across several Canadian provinces and a busy Shopify storefront, with a team of more than a hundred and twenty-five behind it.
It had no shortage of software. If anything, it had too much. More than a dozen separate tools each ran a corner of the business — point of sale, online store, accounting, purchasing, payroll, HR, even a camera counting footfall — and each did its own job perfectly well. The trouble was that none of them did it together, and the gaps between them had all been filled by people.
The same information lived in several places at once. When two systems disagreed, no one could say with confidence which one was right.
Because the tools didn't talk to each other, the same data — purchases, sales, payroll, staff hours — was keyed in again and again, by hand, across systems.
With data scattered and entered manually in several places, the numbers that came out were neither real-time nor reliable — exactly when decisions needed both.
The work got done — but it got done by people holding more than a dozen disconnected systems together through sheer manual effort: re-typing, reconciling, and hoping the reports were close enough to make a decision on.
When a business is drowning in tools, the instinct is to go find a better one. That wasn't the problem here — and I said so.
The individual tools were mostly fine; each was good at its own job. The problem was that nothing connected them, so the people had become the integration layer — moving the same data between systems by hand, all day. Adding another app to the pile would have made that worse, not better.
So the decision was to stop treating the symptoms and fix the structure: give the business one central engine that every existing tool could connect into — a single place where the master data lives, and from which everything else is fed. Not to rip out what worked, but to put a spine behind it.
That engine had to be capable enough to run a multi-store, multi-channel retail operation, and open enough to connect freely to everything already in place. That pointed clearly to ERPNext — a capable open-source ERP — as the core, with the rest of the estate connected around it rather than replaced.
It's the same principle I bring to every project: connect what's already there into one system, and build something custom only where there's a genuine gap the existing tools can't close.
The same tools they already had — re-organised around one central engine, so the whole business finally works from a single source of truth.
A central engine that became the single source of truth, an operations-and-people layer around it, and the intelligence layer that finally made the whole business visible.
A capable open-source ERP, implemented as the central engine the whole business runs through — so every channel works from the same truth.
The layer that carries the rest of the operation — and connects the people side of the business into the same system.
With the data finally connected, an analytics layer turned it into insight the business had never had before.
The business can now see itself clearly — every store, product line and salesperson — as things happen, not weeks later.
If that sounds like your business, that's the conversation worth having. Tell me what's scattered or manual — I'll tell you straight whether I can help.