Can you keep K8 and modernise everything around it?
Yes. K8 stays exactly what it already is — the system built for branch-based trade distribution — while a bespoke, real-time interface gets built on top of it. No rip-and-replace, no ERP migration, and nothing lost from the setup your business already runs on. This is what Sysgraft calls a graft: a precise join between a new intelligent layer and the systems you already own.
Should you replace K8, or build around it?
For most £1.5m–£20m+ UK distribution and wholesale businesses, the honest answer is: build around it.
K8 is usually not the problem. It's an ERP system built for distribution and wholesale trade, and it does that job well. The problem is that it was never designed to be a live, cross-business dashboard for leadership — it wasn't built to show margin, cash position and order performance together on one screen. The frustration leaders feel ("why can't I see margin in real time?", "why does month-end still take a week?") isn't a reason to tear K8 out. It's a reason to add a layer it was never meant to provide.
Ripping out a working ERP system to solve a reporting and visibility problem is one of the most expensive mistakes a mid-market distribution business can make: months of migration, retraining, data risk, and disruption — to fix something a graft would fix without any of it.
What connecting to K8 actually involves
Kerridge Commercial Systems provides open APIs and webhooks for K8, typically confirmed by working with your K8 support partner or with Kerridge directly to establish the exact data structures in play for your install. K8 is offered on both cloud and on-premise deployment, and which one you're on affects how that access is actually opened up — another detail worth settling at discovery rather than assuming.
K8 was built specifically for branch-based trade distribution — builders' merchants, timber merchants, plumbing and heating, electrical wholesale — with customer-specific trade pricing baked into how it operates. That's exactly the kind of detail a graft has to respect rather than flatten into something generic.
Common questions about modernising around K8
Can custom software sit on top of K8?
Yes. Kerridge provides open APIs and webhooks for K8, typically accessed by working with your K8 support partner or with Kerridge directly to confirm the exact data structures in play. A bespoke interface can draw live data through that route and present it alongside data from your CRM and other systems — giving leadership one real-time view without changing how K8 itself works.
Can I get a real-time dashboard from K8 without replacing it?
Yes. A dashboard built on K8 can show margin and order performance by branch, updating live, sat alongside your other systems — reflecting the trade-specific pricing K8 already manages.
Is K8 the problem, or our processes?
Often, neither is fully the culprit. K8 handles branch-based trade distribution the way it's designed to — the real issue is that margin, stock and order performance across branches don't show up on one screen, which is an integration problem, not a reason to replace a system built specifically for this sector.
Can I connect K8 to my CRM and see both in one place?
Yes. Grafting an interface across K8 and your CRM lets customer, sales and order data appear together — the single view that neither system gives you alone.
Does keeping K8 limit what AI can do later?
No. What limits AI usefulness is fragmented data, not which ERP you run — including the branch-specific, customer-priced detail K8 is genuinely built around. Join that data up and AI features have something coherent to work with. Keeping K8 doesn't hold that back.
Modernising isn't migrating
The software industry has trained businesses to believe that "modernising" means a large, disruptive replacement project. It doesn't have to. Grafting a new layer onto K8 is modernisation without the migration — you move forward on visibility and capability while K8 keeps running branch-based trade distribution exactly as it always has.
See how the whole process works, step by step →
Get your AI Exposure snapshot Find out where your real constraint is — most often it isn't AI, and it isn't K8