What Epicor’s Move to Monthly Releases Means for You

Think about how your phone updates. You don’t block out a weekend twice a year to install a giant new operating system that reshuffles everything you know. Small updates arrive quietly, most of them barely noticeable, and the big redesign comes once a year when you’re ready for it. Epicor Kinetic is now moving to that same rhythm, and if you run Kinetic in the public cloud, the way you plan for upgrades is about to change.

Epicor has shifted Kinetic from two large releases a year to a Continuous Integration / Continuous Deployment (CI/CD) model: smaller, more frequent monthly releases for eligible public cloud customers, with the bigger changes concentrated into one annual baseline release each March. Release 2026.103, available in August 2026, is the first monthly release under this model. It’s a useful release in its own right, but the more important story is the change in cadence itself.

“Why was the old model such a headache in the first place?”

For years, ERP vendors delivered value in large, semi-annual drops. Everything the product team built over six months landed at once. That approach had a hidden cost. Every big release was a big event: a large block of changes to review, test, schedule, and absorb, often all at the same time. The bigger the release, the more that could go wrong, and the more careful, and slow, you had to be about applying it.

For a mid-market manufacturer or distributor, that meant real disruption. Testing critical processes against a mountain of changes. Coordinating downtime. Holding your breath that a customisation or integration you rely on hadn’t quietly broken. The value was real, but so was the effort to get to it safely.

The CI/CD model is Epicor’s answer to that. Smaller increments mean less to review at any one time, lower upgrade risk, and faster access to new capabilities. Instead of waiting up to six months for a fix or a feature that’s already been built, you get it when it’s ready.

“I run operations. What actually changes day to day?”

Cadence and control: Monthly releases are designed to be backward-compatible, so they should not require the full regression testing you’d plan for a major upgrade. You still review the release notes each month and test anything that touches a critical process, but the day-to-day burden drops.

Timing is yours: Eligible public cloud customers can self-apply a monthly release through the Epicor Cloud Management Portal when they’re ready. If you don’t self-apply, Epicor’s CloudOps team applies it automatically within two calendar months, in line with the cloud upgrade schedule. So a release available in August that isn’t self-applied would be applied automatically in October.

The honest call: You can’t skip standard monthly releases entirely. They’re part of the managed cloud service. You choose when within the window, not whether.

“I’m in finance. Does this make month-end better or worse?”

Predictability is the win: Smaller monthly changes are easier to absorb and less likely to disrupt month-end or reporting than a large semi-annual overhaul.

Compliance still needs owning: If you operate in a regulated industry, your internal validation procedures still apply. Treat the annual March baseline release as your primary planned validation event, and review each monthly release against your own compliance requirements rather than assuming it’s irrelevant.

“I’m the decision-maker. What’s the trade-off?”

You get value faster: Upgrades stop being a twice-yearly project, and improvements arrive as they’re ready rather than after a six-month wait. Because issues surface in smaller, more frequent releases, they’re also easier for Epicor to identify and resolve quickly.

The catch: Upgrades become a continuous operating rhythm instead of a scheduled event, so someone needs to own the monthly review. If nobody does, the review won’t happen.

Continuous Track vs Maintenance Track: Where Do You Sit?

Not every Kinetic customer moves to monthly releases. Which track you’re on depends on your deployment.

The simplest way to read it: Continuous Track is annual baseline plus monthly feature releases. Maintenance Track is annual baseline plus patches. Maintenance Track customers still get every new feature, just consolidated into the next annual release rather than month by month.

What a Monthly Release Actually Looks Like

To make the model concrete, look at 2026.103, the first one. It’s deliberately focused, with a handful of practical improvements rather than a sweeping overhaul: Tool Resource Groups that let Advanced MES consider more valid scheduling combinations, visibility of Kinetic part quantities inside Field Service Management, the ability to reprint outstanding-items lists for bank statement reconciliation, and simpler part revision data entry.

None of those are dramatic on their own, and that’s the point. This is the new model working as intended: steady, useful, low-risk improvement, delivered in small pieces you can absorb without stopping the business.

Questions to Ask Before This Becomes Routine

Who owns the monthly review? Someone needs to read each release note and decide whether a change affects your users, integrations, or compliance.

Which of our processes are business-critical? Identify your key integrations, customisations, reports, and partner solutions now. That list tells you what to test when a relevant change appears, and what to validate hard at the March baseline.

Do we self-apply or let Epicor apply? Self-applying gives you control over timing within the window. Letting CloudOps apply automatically is lower effort. Neither is wrong; the point is to decide deliberately rather than by default.

Are our customisations resilient? Backward-compatible releases should leave customisations stable, but “should” isn’t “will.” If you carry heavy customisation, this is a good moment to review how exposed you are, especially heading into an annual baseline.

Frequently Asked Questions

Q: Do I have to test every monthly release?

No. Monthly releases are designed to be backward-compatible and don’t require the formal integration testing of an annual baseline. You should still review the release notes and test any change that affects a critical process.

Q: Can I skip a monthly release I don’t want?

No. Standard monthly releases can’t be skipped; they’re part of the managed cloud service. You control when within a roughly two-month window, either by self-applying or letting Epicor apply automatically.

Q: What happens if I do nothing?

Epicor’s CloudOps team automatically applies the release within two calendar months, in line with the cloud upgrade schedule. This automatic application does not apply to Flex customers.

Q: Will this affect my integrations and customisations?

Monthly releases are backward-compatible by design, which reduces risk. You should still monitor release notes and test critical integrations when a relevant change is introduced. The annual March baseline is where broader change may require fuller validation.

Q: I’m on-premises. Does this apply to me?

No. On-premises customers stay on the Maintenance Track: one annual baseline release plus maintenance patches, with you retaining control over when you apply upgrades.

The Bottom Line

The move to monthly releases is not really about any single feature. It’s about turning ERP upgrades from a twice-yearly ordeal into a steady, low-risk rhythm, with the big changes saved for one planned event each March.

That only pays off if someone’s managing it well. The right implementation partner helps you set up the review process, identify what to test, and plan your annual baseline validation so upgrades stay quiet and predictable rather than becoming a monthly scramble.