12Hardware & Building Supplies · ERP software
Hardware wholesaler handling the same item in multiple units of measure
Cement, pipes and fittings bought by the tonne or bundle and sold by the bag or length, with stock and margin correct in both.
- Multi-unit item master
- Purchase-to-sale unit conversion
- Part-bundle sales
- Landed cost per base unit
The problem
Stock was tracked in purchase units but sold in smaller units, so the system figure never matched the shelf. Staff converted in their heads at the counter, which meant pricing errors on part-bundle sales and a margin nobody could verify.
What we built
We modelled base units with defined conversion factors, so an item can be purchased in one unit and sold in another with stock held in a single base quantity. Pricing and margin are calculated against the base unit regardless of how the line is sold.
Modules delivered
- Multi-unit item master
- Purchase-to-sale unit conversion
- Part-bundle sales
- Landed cost per base unit
- Margin by item
- Reorder in purchase units
What changed
What the delivered system does differently from the process it replaced.
- Stock quantity stays correct whichever unit a line is sold in
- Margin is calculated from landed cost rather than estimated
- Counter staff no longer convert units manually
Built with
The stack chosen for this build.
- Go
- PostgreSQL
- REST API
Why this customer is not named
Most of our customers allow the work to be described but not their name published. Where a customer has given permission, their name and testimonial appear here.
Independent accounts of our work are published by customers themselves on our Facebook reviews page.
Related case studies
Does this look like your problem?
If any of this is familiar, the first step is the same one this project started with: a free requirement study that ends in a written scope and a fixed price.