Hi,

If you have defined a customer agreement for the parent, prices agreed for the parent of the hierarchy could be used for the child (unless there is a applicable agreement with the child customer). This is the same when using pricing from sales campaigns and price lists. When fetching price for a customer order line following is the order of places looked at by IFS pricing logic

Price on Customer Order Line

The price on customer order line is selected depending on the data entered. Given below is a prioritized order of how the price will be fetched in a customer order

 1.     From a customer agreement set to be excluded from autopricing, manually defined on the customer order header

1.1.    Price per part

1.2.    Price on assortment node from a customer agreement set to be excluded from autopricing, manually defined on the customer order header.

2.     From a campaign

2.1.    Price per part

    2.1.1.    Price per part, from a campaign valid for customer.

        2.1.1.1.    Price per part, from a campaign valid for customer in customer hierarchy. (Hierarchy level upwards)

    2.1.2.    Price per part, from a campaign valid for customer price group.

        2.1.2.1.    Price per part, from a campaign valid for customer price group of a customer in customer hierarchy. (Hierarchy level upwards)

2.2.    Price on assortment node from campaign.

    2.2.1.    Price on assortment node, from a campaign valid for customer.

        2.2.1.1.    Price on assortment node, from a campaign valid for customer in customer hierarchy. (Hierarchy level upwards)

    2.2.2.    Price on assortment node, from a campaign valid for customer price group.

        2.2.2.1.    Price on assortment node, from a campaign valid for customer price group of a customer in customer hierarchy. (Hierarchy level upwards)

3.     From agreement.

3.1.    Price per part

3.1.1.        Price per part from customer agreement in customer hierarchy. (Hierarchy level upwards)

3.2.    Price on assortment node from the automatic price fetching customer agreement.

3.2.1.        Price on assortment node from customer agreement in customer hierarchy. (Hierarchy level upwards)

4.     From Price lists

4.1.    Part-based or unit-based price from price lists

4.1.1.        Price from price lists on Customer/Sales/Pricelist per Price Group

4.1.1.1        Price from price lists connected to a customer in customer hierarchy. (Hierarchy level upwards)

4.1.2        Price from price lists per customer price group

4.1.2.1        Price from price lists (unit-based or part-based) per customer price group in customer hierarchy. (Hierarchy level upwards)

4.2.        Deal per assortment node in sales price list

4.2.1        Price from price lists on Customer/Sales/Pricelist per Price Group

4.2.1.1        Price from price lists connected to a customer in customer hierarchy. (Hierarchy level upwards)

4.2.2        Price from price lists per customer price group

4.2.2.1        Price from price lists (unit-based or part-based) per customer price group in customer hierarchy. (Hierarchy level upwards)

5.     Price from sales part

 When searching for price in assortment structure it looks for the price on the assortment node closest to the part.

(see more info in your About Pricing help page, this is in XXX/ifsdoc/documentation/en/Sales/AboutPricing.htm. XXX is your IFS link)

Hope this helps

Asanka