Distribution ERP Development

Building or extending an ERP system for a business that buys, blends, stores, and sells drummed and packaged goods — chemicals, paints and coatings, adhesives, and lubricants. That means inventory with batch and expiry at the stock-movement level, blending and production orders, procurement, dealer pricing tiers, credit control, fulfillment, and double-entry accounting in one system rather than across four tools and a spreadsheet.

Generic ERP assumes discrete units sold off a shelf. A drum carries a batch number, an expiry date, a certificate of analysis, and a blend it came out of — and a recall means answering which raw material lots went into a batch and which customers received product from that run. Dealer pricing has the same problem: a tier price on terms up to a credit limit is the normal case in distribution, not an exception that belongs in an approval workflow.

NestJS backend with role-based access control, Next.js admin dashboard and storefront, PostgreSQL with Prisma, and OpenAI for the read-only internal assistant. Strict TypeScript throughout, Sentry monitoring, GitHub Actions CI. Deployed on your infrastructure or managed hosting, your choice.

A codebase audit if you have an existing system, a scoping session covering your products, pricing rules, warehouses, and finance process, then a written scope and fixed quote before build work starts. Delivery is phased so the modules you need most go live first. You own the code and the database at the end of it.

Distributors whose process does not fit off-the-shelf ERP, who have been told twice that their pricing or blending workflow needs customisation, or whose per-user licence costs have outgrown what a one-time build would cost. Not for businesses whose process is close to standard — an off-the-shelf system from a specialist vendor is genuinely the better call there, and I will say so rather than sell you a build.