We've placed two Epicor roles in the last quarter, and both shortlists had fewer than five people
That's not a quiet market. It's a structural gap. Epicor consultant jobs UK-wide are sitting open longer than they did six months ago, and the reason isn't salary — though we'll get to that. It's that Kinetic moved to monthly releases in May with the 2026.100 update, and the people who can handle continuous change are already working.
Four months in, the hiring impact is clearer than it was in spring. Partners are screening differently. Internal teams are either bringing in someone senior or staying stuck. And the skills you could get away with a year ago won't land an offer today. Here's what changed and what it means if you're hiring into the UK partner channel or building an internal Epicor team.
Monthly updates collapsed the old hiring model for Epicor consultant jobs UK partners rely on
Under the twice-yearly release schedule, you could hire deep module specialists. Someone brilliant at advanced planning didn't need to know finance. A production consultant could spend three months getting comfortable in supply chain and still deliver value. Partners staffed projects knowing which version would be live at go-live and exactly what features would be available.
Monthly updates killed that model. Cloud customers now get continuous improvements — planning flexibility, workflow refinements, browser UX changes — without waiting half a year. That's operationally useful, but it changes what UK partners need on their benches.
Version awareness is now table stakes. When updates landed twice a year, you could know Kinetic 2024.1 in depth and coast for six months. When they arrive every four weeks, you need to know what landed in the last three releases and what's scheduled for the next two. The partners we work with on Epicor consultant jobs UK-wide are explicitly asking candidates to walk them through recent release notes in interviews. Not trivia. A proxy for whether you'll stay ahead of client expectations when the platform moves every month.
Adaptability beats depth. A consultant who's competent across finance, supply chain and production and can pick up new capabilities in a sprint is more valuable now than someone brilliant in one module who takes three months to get comfortable elsewhere. Interview questions have shifted from "Walk me through your most complex MRP configuration" to "How do you approach a module you haven't worked in before?"
The technical bar is rising. Epicor Functions now run in the browser, the classic desktop client was fully removed in 2026.100, and browser-based administration is the default. The line between functional and technical work is blurring. Partners tell us they're hiring fewer pure functional specialists and more people who can configure, script, troubleshoot integration and interpret API behaviour without escalating every question.
Salary data backs that up. Mid-level Kinetic consultants earn £48,000–£65,000 in the UK according to our 2026 Epicor salary guide. Consultants who handle both functional and technical briefs land offers 8–12% above that band. Do the maths.
UK partners are building release teams — and paying them well
Larger UK partners are now staffing small internal teams whose entire job is to review monthly releases, test functionality, document changes and brief delivery consultants. That's a new role shape in the market. It didn't exist a year ago.
These aren't support roles. They're strategic positions that sit between Epicor's product team and the partner's client-facing consultants. The people doing this work need to read release notes, understand what changed under the hood, test it in a sandbox, figure out which clients will care, and translate technical updates into commercial recommendations.
We're seeing £60,000–£75,000 for mid-level people in those positions. Leads who can train consulting teams and advise on which features to adopt earn £90,000+. That's higher than many delivery roles because the leverage is different — one good release analyst can keep twenty consultants current.
Not every partner has built this function yet. Smaller firms are handling release reviews ad hoc or pushing the responsibility onto senior consultants who are already stretched. But the partners who've invested in dedicated resource are shortlisting faster and closing candidates more reliably because their consultants aren't scrambling to stay current on their own time.
Internal teams are stuck between monthly updates and static headcount
End-user manufacturers running Kinetic internally face a different version of the same problem. Your platform improves every month, but unless someone's reviewing those updates, configuring new features and training users, you're leaving value on the table.
Most UK internal Epicor teams are one to three people. Adding a review-and-deploy cycle for monthly releases on top of support, user requests and periodic projects is unrealistic without changing how the team operates.
We're seeing two patterns work. Some manufacturers bring in a senior Epicor consultant — often someone with partner-side experience — and give them ownership of the platform roadmap, not just support. That person tracks releases, decides which features to adopt, configures them and manages internal communication. It's broader than the traditional administrator role. It pays £55,000–£70,000 mid-career and £80,000–£100,000+ for a lead who can also manage vendor relationships. Check our interactive salary checker for current benchmarks.
Others contract partner resource on a retained basis — a day or two per month — to handle release reviews and advise on which updates matter. That's less expensive than a permanent hire. But it only works if you have enough internal capability to implement the recommendations. Adding a consultancy retainer without adding headcount just creates a backlog of good ideas no one has time to execute.
IR35 and monthly releases don't play nicely together
When updates arrived twice a year, you could bring in a contractor for a defined upgrade project, scope it tightly and structure the engagement outside IR35. Monthly updates blur that line. Ongoing support to review, test and deploy continuous releases starts to look like business-as-usual work — exactly the pattern HMRC challenges.
Partners are handling this two ways. Some move Epicor contractors onto their own payroll and supply them as part of a managed service. That's inside IR35, but the admin sits with the partner. Others scope release-review work as a separately contracted project — distinct from implementation or support — and document why the contractor provides specialist knowledge the client doesn't have in-house.
The second approach is defensible. But it requires careful contract drafting and genuine separation between release work and day-to-day support. Get IR35 advice early. The structure matters more now than it did under twice-yearly releases, and getting it wrong is expensive.
The skills gap widened because the platform moved faster than the talent pool
Epicor has always been tight in the UK. The installed base is smaller than SAP or Microsoft, concentrated in the Midlands and the North, and the consultant pool is correspondingly small. Experienced Epicor people effectively name their salary band when they move. Prophet 21 and BisTrack specialists stay open on our desk months longer than Kinetic roles.
Monthly releases made that worse. The number of people in the UK who know Kinetic well, stay current with the platform, work across functional and technical boundaries and have the adaptability to handle continuous change is smaller than the number of open roles. We've placed Epicor Kinetic consultants in the West Midlands and pre-sales professionals in Glasgow recently. Both shortlists were under five.
That's structural, not temporary. Epicor doesn't run the graduate programmes or training pipelines the larger vendors do. The only way into the market is to learn on the job, which means someone has to take a chance on you. Most partners can't afford to. The result is a small, experienced, expensive talent pool and very little new supply.
Speed matters. The people who meet the brief are usually in work, not actively looking. They'll consider a move when the role is interesting and the money is right. But they won't wait three months for a decision. We see strong candidates interview, get an offer elsewhere and accept before the original employer finishes internal approvals. In a monthly-release environment where staying current is half the job, you can't afford to lose good people to slow process.
What we're telling clients hiring Epicor consultant jobs UK-wide in Q4
Define the role around adaptability, not module depth. Screen for evidence candidates follow releases, test new features and adjust how they work as the platform evolves. That means asking about recent updates in interviews — the honest read, anyway — and listening for whether they engage with the platform actively or treat it as something they learned three years ago.
Budget for the upper end of the band. Under-offering an Epicor role in the UK buys you three months of empty desk and a higher price second time round. The people who can handle monthly releases know what they're worth.
Move quickly. The shortlist is small. The people who meet the brief won't wait.
We're working on several Epicor consultant jobs UK partners and internal teams are trying to fill right now. Building an Epicor practice, scaling an internal team or replacing someone who left? We'd be glad to talk. Get in touch and we'll walk you through what's working in the market and where the talent actually is.