Custom ERP for Chemical and Paint Distributors (And When Off-the-Shelf Actually Wins)

A custom ERP for chemical and paint distributors is an enterprise resource planning system built around how a process-distribution business actually works — batch numbers, expiry dates, blending runs, drummed goods, tiered dealer pricing, and credit limits as native concepts rather than custom fields a consultant added. It replaces a per-user monthly licence with a one-time scoped build the business owns outright, code and database included.

Let me be honest about the thing most agency pages won't say first: for a lot of distributors, you should just buy Datacor or BatchMaster. They're mature, they've been doing this for decades, and if your process fits their model, a custom build is a slower and riskier way to arrive somewhere similar. I'd say that on a call before I'd quote you.

But "fits their model" is doing a lot of work in that sentence. Here's where it stops being true.

Why Doesn't Generic ERP Software Handle Chemical Distribution Well?

Because generic ERP assumes you sell discrete units off a shelf. A box is a box. You count them, you ship them, you reorder.

A drum is not a box. A drum has a batch number, an expiry date, a certificate of analysis, and a blend it came out of. When a customer calls about a bad batch, you need to answer two questions fast: which raw material lots went into it, and who else got product from that same run. That's forward and backward traceability, and it needs to be a property of every stock movement — not a text field someone remembered to fill in.

Then there's pricing. A walk-in customer pays list. A dealer pays a tier price, on 30-day terms, up to a credit limit, and gets put on automatic hold when they cross it. In most off-the-shelf systems that's an approval workflow bolted onto a sales order. In a distribution business it's just... Tuesday. It should be part of the order flow, not an exception to it.

The systems built specifically for this — Datacor, BatchMaster, Deacom — handle all of it properly. That's the point of them. The question isn't whether they work. It's what they cost you over ten years, and whether your process is close enough to theirs.

What Does a Custom Distribution ERP Actually Need to Do?

I'll describe this concretely, because I built one. It's running in production for an industrial lubricants and oils distributor, and the module list is the honest answer to this question:

• Batch and lot tracking with expiry, at the stock-movement level, with QC hold alerts when a batch fails or approaches its date
• Blending and production orders that consume raw material stock and produce finished goods, recording which lots went into which output
• Multi-warehouse inventory with transfers and a full movement audit trail
• Reorder-point automation that watches live stock and generates draft purchase orders on its own, rather than waiting for someone to notice a shortage on a spreadsheet
• Customer groups with tiered pricing, credit limits, and automatic credit holds
• Double-entry bookkeeping that posts journal entries automatically on every order, payment, credit note, and vendor bill
• Returns and RMA wired through to credit notes and restocking
• Dispatch and fulfillment, including in-house driver assignment and multi-carrier shipping labels
• An internal AI chatbot staff can ask about stock in plain language, answering from the live database

That last one is worth a caveat, because "AI ERP" is a phrase that's being used to sell a lot of vapor right now.

What Does an AI Chatbot in an ERP Actually Do?

It answers questions about live data. That's it, and that's genuinely useful.

Someone in the warehouse asks what's in stock of a grade across three locations, and gets a number — instead of finding the right report, filtering it, and exporting to Excel. The chatbot is scoped to read-only queries against the real database. It isn't generating an answer from a language model's general knowledge, and it isn't authorised to change anything.

I'd push back on anyone selling you an ERP chatbot that writes transactions. The value here is removing the report-pulling tax on simple questions. The moment you let a model post journal entries, you've created a very expensive debugging problem for a very small convenience gain.

Custom ERP vs SAP, NetSuite, and Odoo: What's the Real Trade-off?

The honest version, in both directions:

Off-the-shelf wins on: a vendor support desk you can call at 2am, a decade of edge cases already handled, compliance modules maintained by someone else, and no dependency on one developer. If your process is standard, this is a real and significant advantage. Don't dismiss it.

A custom build wins on: a one-time scoped fee instead of a per-user licence that grows every time you hire a warehouse hand, native modelling of your actual process instead of a consultant's approximation of it, ownership of the code and data, and no annual version migration you didn't ask for and can't defer.

The per-user thing is worth doing arithmetic on. Microsoft lists Business Central Essentials at $80 per user per month (Premium is $110), billed annually. Thirty people on Essentials is $28,800 a year, every year, before implementation or the partner fees that come with customising it. That maths changes the build-versus-buy answer somewhere between year two and year four for most mid-size distributors — and it changes it permanently, because the licence never stops.

The counterweight is real though: you're trading vendor risk for developer risk. Ask about that directly before hiring anyone, including me.

What Does a Custom ERP for a Distributor Cost?

Scoped per project, and I'd be suspicious of anyone who quotes you off a feature checklist.

What I can say concretely is that the starting point isn't a blank page. The inventory, procurement, sales, fulfillment, and finance modules already exist and already run in production. So scoping is about the delta — your product categories, your pricing rules, your approval chain, your reporting — not about rebuilding an ERP from nothing.

That's a walkthrough of the running system first, then a scoping session, then a written scope and fixed quote before any build work starts. Phased delivery after that, so the modules you need most go live first rather than everything landing at once.

Should You Build or Buy?

A rough heuristic, offered against my own commercial interest:

Buy off the shelf if your process is close to standard, you need compliance modules maintained by someone else, you want a support contract, or you're under about fifteen users where the licence maths doesn't bite yet.

Consider a custom build if you've already been told by two vendors that your pricing or blending process needs "customisation," your per-user licence is climbing past what a build would cost, you're being pushed through version migrations that break your workflows, or you want the data and code to be genuinely yours.

If you're in the second group, Distributor ERP is the product version of the system described above — built for chemical, paint, adhesive, and lubricant distribution, running in production today. The full technical write-up of the original build is in the industrial ERP case study.

And if you're in the first group, buy the off-the-shelf one. I'd rather tell you that now than six months into the wrong project.

Let's Build Something

I work remotely with clients in the United States, Canada, the United Kingdom, Germany, the Netherlands, Switzerland, Norway, and the rest of Europe, as well as Australia, New Zealand, the UAE, and Singapore.

If you're weighing a custom ERP against another year of licence renewals, get in touch and we'll talk through whether it's actually the right call for your operation. If it isn't, I'll say so.