# Epicor Kinetic Update Schedule: Release Cadence, Versions and Upgrade Planning > Source: https://netray.co/erp-help/epicor-kinetic-update-schedule-release-cadence-upgrade-planning > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Epicor Kinetic ships versioned releases in a year-and-number pattern with point releases in between, and the cloud service applies updates on a vendor-managed schedule while on-premises customers choose when to upgrade. Confirm exact dates and the supported-version policy on the Epicor support site, then plan a regression-tested upgrade at a pace your customizations allow. ## Kind cio ## System epicor ## Erp Epicor Kinetic ## Module Releases / Upgrades / Cloud and On-Prem ## Query epicor kinetic update schedule ## Alternate Queries - epicor kinetic release schedule - epicor kinetic version numbering - epicor kinetic cloud vs on-prem update ## Applies To Epicor Kinetic cloud (multi-tenant and single-tenant) and on-premises; exact dates and support windows change, so verify them with Epicor before committing a project plan ## Steps ### How to plan around Kinetic updates **Items:** - Find your current version in the Kinetic client (Help, About) or the server and database information, and write down the full version string. - Read the release notes and the supported-versions policy on the Epicor support portal for the target and your current release. - Ask whether your tenancy is multi-tenant cloud, single-tenant cloud or on-premises, since this decides who controls the update date. - Inventory customizations: Application Studio layers, BPM directives, Epicor Functions, BAQs, reports and integrations. - Upgrade a test environment copied from production, and run regression tests on the processes that matter, such as job entry, receiving and invoicing. - Review changes to REST APIs, deprecated features and security or browser requirements, and adjust integrations. - Schedule the production change outside month end, train users on interface changes, and keep a rollback plan. ## Sections ### How versions are named **Body:** Kinetic uses a release name based on the year and a number, with build numbers on the end for patches. Earlier Epicor ERP 10 versions used a three-part number. The release name tells you the feature level, and the build tells you the patch level, so support cases should always quote the full string. Epicor has historically published major releases a small number of times per year, with more frequent cumulative patch releases. Because the cadence has changed over the years, treat any fixed calendar you read on a blog as dated, and check the current policy. ### Cloud versus on-premises **Body:** In a multi-tenant cloud service, Epicor schedules updates for all tenants, and customers get notice and a window to test in a pilot environment. The benefit is less upgrade work, and the cost is less control over timing and a need to keep customizations compatible with the shared platform. On-premises and some single-tenant arrangements let you pick the release and the date, but you also carry the server, SQL Server, Windows and IIS work, and you must stay within the supported window to receive fixes. Falling several versions behind turns a routine update into a project. ### What to test **Body:** Customizations are the main risk. Application Studio layers, BPM directives and Epicor Functions may reference fields or methods that change. Run every critical path with customizations enabled, and compare the output of key reports and BAQs between old and new versions. Integrations are the second risk. Check REST v2 endpoints, API keys, authentication flows, EDI, and connectors to other systems. For the cost of a few days of testing, you avoid a production incident at the first close after the update. ## Pitfalls - Taking a blog's release calendar as current; check Epicor's official policy. - Skipping the test upgrade from a recent production copy. - Not documenting customizations, so nobody knows what to retest. - Upgrading in the last week of a financial period. - Assuming cloud updates need no testing; customizations and integrations still break. ## Ai Angle An assistant grounded in your own customization inventory, BAQs and BPM definitions can list which ones touch tables or methods affected by a release note, and draft a regression checklist from your actual usage. SyteRay-style accelerators exist for SyteLine; for Epicor, ERPray reads the live system read-only and can show what is in use so testing focuses on it. ## Faq ### How often does Epicor Kinetic release updates? **Answer:** Epicor publishes major releases a few times a year and more frequent cumulative patches, but the cadence has changed over time. Check the current release policy on the Epicor support site rather than relying on third-party calendars. ### Do cloud customers control when Kinetic updates? **Answer:** In multi-tenant cloud Epicor schedules updates for the service, and customers test in a pilot environment during a notice window. On-premises and some single-tenant setups give more control over the date. ### How do I find my Kinetic version? **Answer:** Use Help and About in the Kinetic client, which shows the application and server versions. Quote the full version and build when raising support cases. ### How long can I stay on an older Kinetic release? **Answer:** Epicor defines a support window per release. Staying outside it means no fixes and harder upgrades later, so check the policy and plan upgrades within the window. ## Search terms epicor kinetic update schedule, epicor kinetic release schedule, epicor kinetic version numbering, epicor kinetic upgrade planning, epicor cloud update window, epicor kinetic on-premises upgrade, epicor kinetic regression testing, epicor kinetic supported versions --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json