Configurator

Each SKU carries the commercial details used from quote through invoice. Product families support sales and pricing analysis, while product type distinguishes standalone items, bundles, subscriptions, services and add-ons. Billing cadence, unit of measure and revenue category follow the accepted sale into later records.

Retiring a product prevents new use under the catalog policy without breaking old quotes, contracts or invoices. A historical quote continues to show the product and configuration it actually carried.

Option groups define the decisions on a configurable product: edition, support level, capacity, term, warranty or deployment. A group can require a selection and allow one or several values. Each option carries its price effect and active definition.

Defaults give the rep a starting selection; the resulting configuration still has to pass all required-group and compatibility checks. A chosen option records its definition and price delta on the quote revision. Changing a catalog option later cannot alter the document the buyer has already received.

The rep can see recommendations without being forced to accept them. Required selections and blocking rules are different: they must be resolved before the quote can advance.

A bundle contains required and optional components, quantities per parent unit and a pricing treatment for each. Included components can carry zero separate selling price, while separately priced components contribute their own amounts. Both retain their product and quantity identity for fulfillment and billing.

Changing the parent quantity recomputes the required component quantities. Repeated saves reuse the existing rule or component origin instead of adding another accessory each time. When a condition stops matching, the recompute removes or revises only the generated work it owns and preserves deliberate rep selections where policy permits them.

Bundle nesting stays traceable through the accepted order and invoice mapping. Configured option values must also travel in the fulfillment payload; a link to a local quote line is not enough for another system to deliver the chosen configuration.

Rules combine conditions on products, quantities or selected options with actions such as requiring, adding, excluding or recommending another item. Conditions within a rule are AND-combined; alternative conditions can be represented by separate rules.

Evaluation must converge to a stable configuration. Cyclic dependencies and conflicting automatic actions stop for correction rather than repeatedly creating lines. Rule-hit evidence includes blocked attempts as well as successful additions, so Configuration Rule Hits can report the actual behavior of the configured rules.

CRM opportunity products are staged with their source identity and quantities before becoming sellable quote lines. An unmatched SKU remains an import issue until Sales Rep or the catalog owner maps it to a valid product. It cannot masquerade as a complete line with a missing required product reference.

Product Manager prepares catalog, option, component and rule changes and tests representative draft configurations. Activation follows the configured master-change review, preserving the approved revision and decision. Active Products and Configuration Rules provide the working lists; Configuration Rule Hits helps investigate inactive recommendations, recurring blocks and unexpected generated components.