---
schema_version: "1"
id: f917cbb838b8137ea73d59255b6a6825bb31eb389f2262e8b274cba59bb3766d
title: Product Configurator
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/264-0-0/rn_product_configurator.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_product_configurator.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 941a8c88c0aa46d9342fde17887bf0f94124d498e11a59917505e661d7ac3500
description: Prevent Constraint Rules Engine from altering specified attributes or relations when it satisfies a constraint. Calculate the quantity of child products per instance of the parent product, rather than the quantity of child products across all bundles.
products:
  - Cross Cloud
release: "264"
---
# Product Configurator

Prevent Constraint Rules Engine from altering specified attributes or relations when it satisfies a constraint. Calculate the quantity of child products per instance of the parent product, rather than the quantity of child products across all bundles.

- **[Prevent Constraint Conflicts When Sharing Attributes and Relations](https://help.salesforce.com/s/articleView?id=release-notes.rn_product_configurator_guardrails_annotation.htm&release=264.0.0&type=5)**  
    Prevent the constraint engine from altering specified attributes or relations when it satisfies a constraint. Use the guardrails annotation in a constraint to define protections at the constraint level, instead of on individual attributes and relations. Annotating the constraint prevents conflicts with other constraints that share the same elements.
- **[Enforce Per-Bundle Product Requirements Regardless of Order Size](https://help.salesforce.com/s/articleView?id=release-notes.rn_product_configurator_instance_quantity.htm&release=264.0.0&type=5)**  
    Write constraint rules that validate child product quantities per bundle instance. Previously, when a customer ordered multiple bundles, the constraint engine validated against the total end quantity of child products across all bundles. When you turn on Instance Quantity in Revenue Settings, the engine validates against the per-bundle quantity, so rules that enforce per-bundle quantities succeed.
- **[Optimize Performance for Revenue Management (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_product_configurator_optimize_performance.htm&release=264.0.0&type=5)**  
    This update optimizes the Configuration API to speed up processing times in Product Configurator. Enable the test run in a sandbox environment to confirm that the optimizations work with your setup. This update is available starting in Winter ’27.
- **[Updates in Default Product Configurator Flow](https://help.salesforce.com/s/articleView?id=release-notes.rn_product_configurator_flow_updates.htm&release=264.0.0&type=5)**  
    The Default Product Configurator flow has new attributes. If you cloned the Default Product Configurator flow before Winter ’27, manually map the new attributes in your customized flow, or clone the default flow and apply your customizations again.
- **[Changed Object in Product Configurator](https://help.salesforce.com/s/articleView?id=release-notes.rn_product_configurator_changed_object.htm&release=264.0.0&type=5)**  
    Do more with the updated ProductConfigurationFlow object in Product Configurator.
- **[Changed Connect REST API in Product Configurator](https://help.salesforce.com/s/articleView?id=release-notes.rn_product_configurator_changed_connect_rest_api_request_body.htm&release=264.0.0&type=5)**  
    Control what the Configuration API returns by specifying only the fields that your Configurator screen needs. The Configuration API now returns a targeted set of fields in the configurator response.