Skip to main content

We are trying to better understand when/how these three fields (currency, customer group, and primary price book) on a SITE come into play with pricing on orders.  We do not allow both customer/site records in our database so each customer center record is either a CUSTOMER or SITE. 

We strictly manage these three fields on CUSTOMERS, but have found that the data on SITES is not aligned/consistent.  We are tyring to determine which fields we should populate and clean up.

Hi Nick,

Pricing can be complicated especially when you have multiple price books which may be defined on the customer or contracts.

In my understanding:

  • The customer is assigned a price book
  • This price book may be a specific price book for the customer but not the complete pricing of all products as it may be a subset of products.
  • If it is a specific customer (or contract price book) and the product is not defined in that price book, the pricing is then obtained from the parent price book.
  • If the obtained price is in a different currency than the customer, there will be a currency conversion.  Example, customer price book is in EUR but the product is not in that price book, then the price is obtained from the parent price book which is in USD.  The price will be adjusted by currency exchange defined between EUR and USD.

In regards to the Customer Groups:

So the way I read this is the priority of the pricing goes this way low to high:

Main Price book

Customer or contract specific price book (site inherits pricing from Customer)

Customer Group price books

 

Appreciate it Phil, thank you.

-Nick

Reply


Terms & ConditionsCookie settings