Almost every distributor we meet already has a system: an ERP, accounting software or a distribution app. Yet daily work still runs on Excel and WhatsApp. So the question is no longer "do we need a system", but whether the ERP you have should be replaced, extended with a module, or complemented by an app built for you.
Next stepOne company brain: every app reads the same dataSee how it worksWhat an ERP does well
An ERP is built to record transactions correctly and neatly: sales, purchasing, stock, receivables, payables and the accounting journal. At that, a mature ERP is hard to beat. Auditors trust its reports, its flows are proven across many companies, and its tax handling follows the rules.
That's why, for most mid-sized distributors, the existing ERP or accounting system should stay the main place where things are recorded. Replacing an ERP just because its reports are incomplete is rarely worth the cost and the risk.
Where an ERP usually stops
The trouble appears in work that isn't recording but deciding:
- Which shops to visit tomorrow, and which items to offer.
- How much to order from the factory, counting goods still in transit and import lead times.
- How to recalculate the price list when the exchange rate rises, for hundreds of items and several price tiers.
- Salesman visit reports, which are mostly free-form notes.
An ERP records what has happened. The work above needs someone to read that data and suggest what to do. Because an ERP isn't built for that, teams export data to Excel and do it by hand. That's why so many companies have an ERP but still work in Excel.
Three options, and when each fits
| Option | Fits when | Watch out for |
|---|---|---|
| An extra ERP module or customisation | The need is close to recording, and the ERP vendor has a module for it | Heavy customisation makes ERP upgrades slow and expensive |
| Ready-made software for one function | You work like most companies, for example attendance or GPS-tracked visits | Per-user fees keep running, rules are hard to change, data spreads across many apps |
| A custom app that reads your ERP data | The work sets you apart from competitors, or its rules are very specific | You need a builder who understands distribution, and a maintenance plan |
The three aren't mutually exclusive. Distributors whose systems work well usually combine them: the ERP for recording, one or two ready-made tools for common functions, and custom apps for the work that matters most.
When an ERP alone is enough
An ERP alone is enough when:
- you have few enough shops and items that manual analysis still gets done
- daily decisions are mostly made by an owner who knows every customer
- the ERP's built-in reports already answer the questions that come up
In that case, it's better to make sure the ERP is used properly than to add another system.
When you need a custom app
A custom app makes sense when:
- The work takes many hours every week, and it's done in Excel outside the ERP.
- The business rules are specific, for example price tiers with stacked discounts, or order rules that differ per factory.
- The result has to be used in the field, for example by salesmen on their phones, not on an office screen.
- The work is your edge, so you don't want to do it the same way as every competitor.
Examples are sales analysis per shop with AI, or a price list recalculated when the exchange rate rises. The data for both is in the ERP, but the work happens in a separate app that reads it.
How to combine an ERP and a custom app
The safest approach: the ERP stays the source of correct data, the custom app reads it and sends back only what needs recording.
One simple rule: if a number is recorded in two places, one day the two will differ. Decide from the start which system owns each piece of data.
In practice:
- order, stock and receivables data are pulled from the ERP regularly, for example every night or every hour
- the custom app does the analysis, recommendations and workflows
- results that need recording, such as new orders, are sent back to the ERP
This way the ERP doesn't need replacing and the finance team keeps working as usual. When several apps read the same data, your company has one brain: every department sees the same numbers.
Five questions before you decide
Before adding any system, answer these five questions with your team:
- Which work is done most in Excel, outside the ERP?
- How many hours a week, and who does it?
- Does the ERP vendor have a module that really answers it, not just an extra report?
- Who will use the result, and on which device?
- What happens if the person who knows that Excel file leaves?
If questions 1 and 2 add up to tens of hours a week and the answer to question 3 is "no", a custom app is almost certainly worth costing out.
Next steps
If the answers point to a custom app, the next decision is who builds it. We compare the options in a software house, a freelancer or an in-house IT team, and the numbers in the cost of building a custom app for a distributor.
If you're still at the beginning, start with the one job that takes the most time. Or bring your list of Excel jobs to a free consultation, and we'll help you sort which belong in the ERP and which need their own app.