Configure Product Rules

Learning Objectives

After completing this unit, you’ll be able to:

• Explain why rules are essential for guiding insurance quoting and approvals.
  
• Distinguish between qualification, configuration, and underwriting rules.
  
• Describe how rule conditions guide quoting, configuration, and underwriting.
  
• Explain how rules work together to create a compliant, dynamic quote flow.
  

From Product Structure to Decision Logic

You’ve modeled the product. The structure is clear, the components are bundled, and attributes are ready for input. But structure alone doesn’t ensure accuracy or compliance. It doesn’t prevent invalid combinations, or route risky quotes for review. And it doesn’t know which products are even allowed in a given customer scenario.

That’s the job of rules.

Rules in Digital Insurance bring your product model to life. They decide which products can be quoted, how they behave during configuration, and whether a quote can be approved or needs further review. They help you adapt offerings dynamically to risk, regulation, and customer input, all without writing code.

In this unit, you learn how Digital Insurance uses three types of rules—Qualification, Configuration, and Underwriting—and how each contributes to a seamless, compliant quoting process.

Let’s return to our scenario with Justus Pardo, the product administrator at Cumulus Insurance. With Auto Gold modeled and bundled, it’s time for him to apply the logic that governs how the product behaves.

Define Eligibility with Qualification Rules

Justus starts with eligibility. Not every customer should be able to quote Auto Gold and surfacing ineligible products can lead to confusion, errors, and wasted effort.

To manage this, Justus uses two types of rules: qualification rules, which define conditions for eligibility, and disqualification rules, which define conditions for ineligibility. These rules work together to fine-tune product visibility during quoting.

For Auto Gold, he defines a:

• Qualification rule, in which only customers aged 25 and up are eligible.
  

• Disqualification rule, in which customers who live in Hawaii are excluded.
  

Both of these rules are product-level rules, but Digital Insurance also supports category-level logic, to filter out entire product groups—like Auto or Home—based on attributes like region, business type, or customer profile.

Justus configures these rules declaratively and organizes them into decision tables that centralize logic across products. He then links them to a qualification procedure, which runs during product discovery to evaluate each customer’s eligibility.

To make the rules work at runtime, he also extends the context definition, ensuring key fields—like customer age and state—are available when the procedure runs.

Most of this setup happens once. Reusable rules, procedures, and context definitions make it easy to manage eligibility logic centrally and scale it across the product portfolio.

When a customer or rep starts a quote, Digital Insurance runs the qualification procedure in real time, returning only products the customer is eligible for.

The result? A quoting experience that’s smoother, smarter, and more accurate. Customers and their reps only see products that customers are eligible for, nothing more, nothing less.

Customize Behavior with Configuration Rules

After defining which products are eligible with qualification rules, the next step is to determine how those products and their components should behave once they’re in scope. That’s the role of configuration rules.

These rules shape how products and attributes behave during quoting. They prevent invalid combinations, enforce business logic, and tailor the configuration experience to each customer’s profile.

Configuration rules consist of:

• Conditions, which evaluate criteria based on product or attribute values.
  
• Actions, which determine what happens when the conditions are met.
  

Let’s take a closer look at the types of actions available.

Product-Level Rule Actions

Product-level rule actions control how product specifications behave during quoting. These rules determine whether a product is added, removed, defaulted, disabled, or validated based on the quote context. Here are some examples.

Attribute-Level Rule Actions

Attribute-level rule actions target specific attributes and their values within a product. They define how attributes behave in real time based on user inputs and product context. These rules shape the finer points of quoting and often work alongside product-level actions. Here are some examples.

Apply Configuration Rules

Justus adds both product-level and configuration-level actions to the Auto Gold bundle.

One of his product-level rules enforces mandatory coverage. It applies when the selected vehicle is an SUV registered in California and valued at $25,000 or more. It also requires that Collision coverage be selected. When those conditions are met, Uninsured Motorist coverage is automatically added and locked.

Here’s how that rule appears in the rule configurator.

This rule includes:

• Conditions (1): One condition checks the vehicle’s type, registration state, and declared value. The other verifies that Collision coverage has been selected.
  
• Actions (2): If both conditions are true, Uninsured Motorist coverage is auto-added, locked, and explained to the user.
  

For Auto Gold, Justus also configures an attribute-level rule that sets the default Collision deductible to $1,000 for vehicles worth over $30,000, while keeping it editable under other conditions.

Rules like these can be scoped to individual products or shared bundles. They support compound logic, evaluate multiple attributes, and are easy to manage over time. By building rules declaratively, insurers deliver smarter quoting flows that reduce errors, streamline compliance, and guide users with confidence.

Automate Approvals with Underwriting Rules

So far, Justus has designed qualification rules to control eligibility and configuration rules to govern product and attribute behavior. The final layer of rule logic addresses risk assessment.

Underwriting rules define how quotes are evaluated against risk criteria and what should happen when those conditions are met. They don’t shape product structure or attribute values; instead, they govern approval logic. Should the quote pass automatically? Be routed to manual review? Trigger additional requirements?

By encoding this decision logic declaratively, underwriting rules let insurers adapt quickly to changing risk policies without hardcoding workflows. They evaluate risk at the quote level and then drive outcomes through stage transitions and automated actions.

In practice, this means Justus can define a small set of underwriting rules for Auto Gold to capture common risk scenarios. Here are some examples.

Each of these rules is linked to the quote’s state transition model, which defines how a record can move between stages such as Draft, In Review, and Approved. For example, the first rule advances eligible drivers directly from Draft to Approved, while the second routes higher-risk cases into the In Review stage.

Beyond stage transitions, underwriting rules can also trigger flows that handle follow-up actions. These flows extend the business logic to tasks outside the quote record itself, such as sending notifications, requesting documents, or logging compliance events.

For Auto Gold, Justus ties a flow to the vehicle value rule. When the declared vehicle value exceeds $50,000, the flow is designed to:

• Transition the quote to In Review.
  
• Send an appraisal request email to the customer.
  
• Log the event for auditing.
  

Underwriting rules automate how risk is assessed and acted on. And because they're declarative, you can adjust conditions and outcomes over time without code changes.

A Guided, Intelligent Flow

Rules don’t operate in isolation. They work together—sequenced, scoped, and evaluated in real time—to guide each quote from initial eligibility to final decision.

Let’s step back and see how they interact for the Auto Gold product.

• Qualification Rules check eligibility based on customer and product data. Ineligible products are filtered out before quoting even begins.
  
• Configuration Rules dynamically adjust what users see and can select, enforcing business logic, setting defaults, validating combinations, and tailoring options to context.
  
• Underwriting Rules evaluate the completed quote for risk. Based on defined conditions, they drive stage transitions, trigger flows, and determine whether the quote can proceed automatically or requires manual review.
  

Justus has now configured a complete rules framework for Auto Gold. The product is discoverable, customizable, and ready to support quoting across teams and channels.

But quoting isn’t just about structure and logic. It’s also about price.

In the next unit, you follow Justus as he builds an attribute-driven pricing procedure that calculates transparent, accurate premiums using formulas, rating tables, and orchestration tools built into Digital Insurance.

Ready to put a number on it? Let’s price the product.

Resources

• Salesforce Help: Product Qualification Rules for Insurance
• Salesforce Help: Product Configuration Rules for Insurance
• Salesforce Help: Product Underwriting Rules for Insurance
• Trailhead: Product Rules for Digital Insurance