Pricing hierarchy refers to the way the system "gets a price" based on values that you define. It is called a hierarchy because system checks each pricing definition in sequence, starting with the most specific and working toward the most general. If the system finds a price at one level, it calculates a value based on defined pricing and quantity of the product. If the system does not find a price at one level, it checks the next level until it either finds a price or has checked all the levels. 

When developing a price for the sales order, the system checks the following sources in the sequence below.

When developing a price for Project Project Pricing, the system checks the following sources in the sequence below.

Project Pricing

Setup: Projects > Project Pricing. 

Matrix Pricing

Setup: Inventory > Pricing > Matrix Pricing > Product or Product Class

  • By Job
  • By Job Price Group
  • By Customer
  • By Customer Price Group
  • By Business Partner Category
  • By Price Sheet
    Within each of the above, the system checks for pricing:
    • By Product
    • By Product Class

Price Sheet Pricing (Customer Price Sheet)

Setup: Inventory > Pricing > Price Sheet

  • By Product

Standard Price

  • Inventory and Non-Inventory Items - By Location
    Setup: Inventory > Product > Location Settings > Standard Unit Price (per location)

Notes: 

  • For details about setting up system pricing, refer to the documentation for each of the modules listed above. 
  • Future versions of aSa.Studio will offer additional pricing options.