Stock in three places and one number you can trust.
Distribution is not retail with bigger boxes. The hard part is that the same item sits in several locations at several costs, moves between them, and is owed for by customers who pay on terms.
We have not delivered to a distributor yet. We have built and run the machinery a distributor needs — multi-location stock, an approved transfer workflow, purchase orders and receiving, supplier ledgers and a double-entry general ledger — in production, for optical retail. Two things a distributor usually wants are genuinely missing today: customer credit limits and receivables ageing. We would be building those, and we would rather you knew that before the first meeting than after it.
Sound familiar?
A week in this business.
If three or more of these are true, the problem is usually not the tools. It is that none of them talk to each other.
- The stock figure on the system and the stock on the floor are two different numbers
- A branch runs out while another branch is overstocked on the same item
- Nobody can say what a customer owes without opening a spreadsheet
- Goods arrive and the paperwork catches up days later, at a guessed cost
- The same product has three prices and no one is sure which is current
What we’d build
The parts that matter here.
Which route
Configure something proven, or build it?
Most vendors answer this the way that suits them. Here is how it usually goes in this sector — and we will tell you plainly which side you are on.
Open-source ERP
Usually faster and cheaper
Often the right answer. Distribution is the use case open-source ERP was built for, and Odoo brings credit control, ageing and delivery documents out of the box — the exact gaps in our own platform. We implement and then operate it.
How we do thisCustom build
When the standard parts run out
Worth it when the way you price, allocate or settle between branches is genuinely yours and a package would force you to abandon it.
How we do thisQuestions
- You said you have not done distribution. Why should we talk to you?
- Because the parts most likely to sink the project — stock accuracy across locations, transfers that reconcile, and accounts that balance — are the parts we already run in production. The domain-specific layer on top is the smaller risk, and we would rather be honest about which half is which.
- Can you handle expiry dates and lot tracking?
- Not today. We track receiving batches with their own cost and price, and serials at unit level, but there is no expiry or shelf-life model. If you move perishables, say so early — it changes the answer to the Odoo-versus-custom question.
Other sectors
Tell us what isn’t working.
Thirty minutes, no deck. We’ll tell you what we would do — and say so plainly if software isn’t the answer.
Book a call