---
schema_version: "1"
id: 7b7ebd0bfefef9fe5c7fa5d1feb25d4e9f8d4a2c57638aaac98926570da96e75
title: Industries Order Pricing Flow
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_industries_order_pricing_flow.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_industries_order_pricing_flow.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 658a20ac4b34a9261fd956e5dcab0039d035da302a8b59307f92e0690295b213
description: Get the list prices for the products. Apply any special pricing that exists for the customer. Determine the final price by applying relevant promotional, product-specific, geographic, bundle, or manual discounts. Calculate and apply the tax, and then save the final pricing to the order.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Industries Order Pricing Flow

Get the list prices for the products. Apply any special pricing that exists for the customer. Determine the final price by applying relevant promotional, product-specific, geographic, bundle, or manual discounts. Calculate and apply the tax, and then save the final pricing to the order.

![Industries Order Pricing Flow](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/resources-product/images/diagram_orderpricingflow.png)

Each process has several functional components:

**Process Flow**

![Process flow](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/resources-product/images/diagram_processflow.png)

- Trigger event: Initiates an interaction with the Component Object Model (COM) functional stack. A trigger event can be external or internal and can trigger an interface or implementation, or a COM class directly. Trigger events include:
    
    - CPQ UI widgets
    - Vlocity OmniScripts
    - Mobile applications
    - Communities
    - Customer self-service websites
    - Partner websites
    - Custom mobile applications
- Interface/Implementation: A trigger event runs an interface, which then calls the active interface implementation. There may be multiple implementations for one interface, but only one implementation can be active.
- Flow: An interface implementation initiates a workflow, which defines a sequence of events, including rules, process logic, and custom processing options. Flows are based on Salesforce flow features. Salesforce extends flows to support the flow of objects, such as orders and quotes, providing eligibility, compatibility, and pricing. Flows also support branching, embedding, and flow actions. Flows are reusable.
- Flow rule: You can create and implement rules for availability, eligibility, compatibility, and pricing. Build rules using natural language, so you can remember what the rule does now and six months from now.
- Entity filter: Rules use entity filters to determine which items in the order are subject to the rule action. Rules can include one or many filters, depending on the business logic the rule implements. Entity filters are reusable. For example, as part of a promotion, you might create a filter to identify premises where the service activation date is 45 days or less. Once created, that filter is available for use in any rule that needs to use it.
- Conditional action: Rule actions define the changes that a rule makes on qualified objects. A rule action can be an offering procedure, a product relationship, a calculation procedure, or another procedure, such as a call to Apex code. Different rule types use different rule actions.