Define pricing conditions

We need to create new pricing conditions for our core product family so order entry reflects correct discounts. Define a condition record for Customer Group LargeRetail with a 12% off list price for material group FG-Widgets, effective July 1, valid through December 31, applicable at item pricing. Test with a sample sales order for customer BrightMart (sold-to 100243) and confirm the net price calculates correctly before mass transport.

Before I publish these pricing condition records, make approval easy for commercial finance. Pull the top five customers by volume who will see price changes, show expected margin delta per customer at the top, surface any overlapping conditions that could override the new 12% rule, and flag materials with previously negotiated fixed-price contracts that would cause disputes.

I added the 12% condition for Customer Group LargeRetail and FG-Widgets, then placed a test order for BrightMart, but the net price stayed at list. I don’t know if the condition table sequence is wrong, the customer is misclassified, or the rule scope is incorrect. Sales Ops needs a fix today for a contract signing tomorrow. What is the most likely culprit and the step-by-step check to make this work now?

When we run quotes, sales reps often call about unexpected prices because condition records overlap, customer groups are misassigned, or condition validity dates are wrong. Which habit should the pricing team adopt to stop this recurring fire drill: centralizing condition records, introducing a pricing release checklist, or creating a monthly audit of high-value customers? Recommend one change, how to roll it out, and how to measure it in the next quarter.