Loading
Prepare for Email to Become the Default Login ExperienceRead More
The online Trailblazer Community becomes read-only Oct 30, 2026Read More
Important Advisory: iOS Update Impacting CG Mobile ApplicationRead More
Penny Perfect Pricing
Apply a Product's List Price

You are here:

  1. Salesforce Help
  2. Docs
  3. Penny Perfect Pricing

Apply a Product's List Price

Configure a fallback search so an order uses a customer-specific price when one exists, and the product's standard list price otherwise.

Required Editions

Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions in Manufacturing Cloud, Automotive Cloud, and Consumer Goods Cloud, with required add-ons.

Let's consider a scenario where Acme Fabrication orders Steel Bracket A100. Because Acme Fabrication has a negotiated customer-specific price, the order must use $95 per unit instead of the $120 standard list price. A different customer ordering the same product, with no negotiated price on file, must still see the $120 list price.

  1. Define the Pricing Key Types.

    See Create a Pricing Key Type for the create/activate procedure. Create two key types, as follows.

    1. "Account + Product" — Anchor Type: Account And Account Hierarchy and Product And Product Hierarchy. Click Save, then Activate.
    2. "Product" — Anchor Type: Product And Product Hierarchy. Click Save, then Activate.
  2. Define the Search Strategy.
    1. See Create a Pricing Search Strategy for the create/activate procedure.
    2. Enter a Name (for example, "Search By Account and Product"), select a Context Definition, and click Save.
    3. Add two Pricing Search Strategy Steps: step 1 with Pricing Key Type = "Account + Product" and Sort = 10 (matches Acme Fabrication's negotiated price for Steel Bracket A100); step 2 with Pricing Key Type = "Product" and Sort = 20 (matches the product's list price when no account-specific record exists).
    4. Click Save, then Activate.
  3. Define the List Price Specification.
    1. See Create a Pricing Specification for the create/activate procedure. Create a specification named "List Price."
    2. Set Meta Type to Price, Base to Value or Quantity, and Condition Level to OrderItem. Link the search strategy from the previous step. Click Save, then Activate.
  4. Define the Calculation Schema.
    1. See Create a Pricing Calculation Schema for the create/activate procedure. Create a schema named "Standard Pricing Procedure."
    2. Add a Calculation Schema Step referencing the List Price specification, with Position = 10 and Mandatory checked, so pricing fails with an error rather than silently pricing an item at zero if no price is found. Click Save, then Activate.
  5. Define the Procedure Plan.
    Note
    Note There's no meta type literally called "List Price" — Price is the correct value for a base/list price step.
    1. See Create a Procedure Plan for the create/activate procedure. Map your Sales Organization / Internal Organization Unit and Order Pricing Type to this calculation schema.
  6. Load the Pricing Data.
    1. From Setup, in Quick Find, enter Data Loader, and select it. Click Insert, select External Pricing Key Value, and import two records: one keyed by Acme Fabrication's Account + Steel Bracket A100 with a Pricing Value of 95, and one keyed by Steel Bracket A100 only with a Pricing Value of 120.
    2. Run the External Pricing Key Value Consolidation job so the imported records become available at runtime. See Load Pricing Data from a Backend ERP System for the full job procedure — every scenario in this section reuses it.
  7. Simulate the Price.
    1. Create an order for Acme Fabrication with a line item for Steel Bracket A100 (see Price an Order).
    2. Click Calculate Price.
    3. Open the Pricing Details tab for the line item. The Calculation Result for step 10 shows $95, and the Condition Found column confirms the "Account + Product" search step matched — the customer-specific price, not the list price.
    4. Create a second order for a different customer, with no negotiated price on file, for the same product. The Calculation Result shows $120, and Condition Found confirms the "Product" step matched instead.
  • Load Pricing Data from a Backend ERP System
    Export pricing condition data from an ERP system and consolidate it for runtime pricing lookups — the load-and-consolidate procedure shared by the pricing scenarios in this section.
 
Loading
Salesforce Help | Article