Date: anticipated August 18, 2026
Issues: TBD
Understanding these pre-release notes
Pre-release notes describe some features and functionality Epicor is considering to make generally available (GA) as part of our next anticipated release. However, such features and functionalities are not committed and will be made GA only on an “if and when made available basis.” Epicor reserves all rights not to release, delay the release, modify the release from what is described here, and not include some or all of the entries found in these pre-release notes. Please review the formal release notes, which will replace these notes on the day of the release.
Learn how to preview some of these features in your "preview" environment before they are released.
Do you integrate Epicor CPQ with salesforce.com? Learn how to keep your integration compliant with upcoming salesforce security requirements.
![]() |
Features and improvements with this icon are based on customer suggestions submitted to Epicor Ideas. |
New Features and Improvements |
|||
![]() |
CPQ-6247 | Snap Assistant Usage UI in CPQ. |
|
![]() |
CPQ-6389 CPQ-6390 |
Improved integration with Kinetic: editable "KineticCompany" If you integrate with the Kinetic ERP system, you can now set the "KineticCompany" parameter shared between Epicor CPQ and Kinetic. Epicor CPQ now can access the list of companies defined in Kinetic, and can stamp one of those company codes on an order. This allows greater control over quotes in a multi-company Kinetic implementation. Learn more about the integration between CPQ and Kinetic by opening the Kinetic help, and searching for the Implementation Guide for integrating Epicor CPQ. |
|
|
|||
![]() |
CPQ-6309 | When viewing the Quote Header, in some situations the "Basic" tab would appear in the wrong position. This has been fixed. |
|
![]() |
CPQ-6358 | When viewing the Quote Header, some comments added to the quote were not word-wrapped and could be hard to read. This has been fixed. |
|
| CPQ-6359 | Configurator rules are organized by their type, such as the "Value" group for all value rules. These rule type headers appear in the node tree when the first rule of that type is created. When the last rule of a certain type is deleted, the header remains (even though it is empty). Previously, an empty "Pricing" header would result in a runtime error. This has been fixed. |
||
![]() |
CPQ-6395 | KB3D: When navigating through a 3D scene using an overhead viewpoint, zooming with pan enabled zooms into the wrong spot. This has been fixed. |
|
| CPQ-6397 | In some edge cases, use of the uppercase and lowercase Snap blocks could prevent the configurator from being loaded. This has been fixed. |
