Pricing and Margin Governance Case
Business Scenario
Commercial leadership is reviewing why realized pricing differs from list price across customers, segments, collections, and style families. The company prices through formal price lists, promotions, customer-specific pricing, and rare override approvals. Those choices shape billed revenue before the result reaches the statements.
The central question is not whether realized price fell below list price. The central question is why it happened. Some dilution reflects deliberate pricing policy. Some reflects promotion strategy. Some reflects customer-specific commercial design. Some reflects negotiation pressure that shows up through overrides and price-floor tension. Leadership needs to separate those causes before it decides whether pricing governance needs attention.
Your job is to explain the pricing policy stack first, then show how that stack changes realized revenue and gross margin, and finally identify where the commercial story should move into governance follow-up.
The Problem to Solve
You need to prove where price realization falls below base list pricing, how much of that result comes from promotions, customer-specific pricing, and override behavior, which customers, collections, and sales teams depend most on non-standard pricing paths, and when pricing pressure starts changing realized margin materially.
What You Need to Develop
- A pricing-policy narrative from list price through promotions, customer-specific pricing, and overrides.
- A realized-pricing explanation by customer and portfolio segment.
- A promotion-effect explanation tied to revenue and gross margin.
- An override and price-floor pressure explanation tied to commercial concentration rather than audit exception testing.
- A short management-facing conclusion on where pricing governance deserves follow-up first.
Before You Start
- Main tables:
PriceList,PriceListLine,PromotionProgram,PriceOverrideApproval,SalesOrder,SalesOrderLine,SalesInvoice,SalesInvoiceLine,Customer,Item - Related guides: Financial Queries, Managerial Queries, Commercial and Working Capital
- Related process page: Order-to-Cash Process
- Supporting references: Schema Reference, GLEntry Posting Reference, Dataset Guide
- This case starts from realized pricing outcomes, then explains the policy layers beneath them rather than tracing one operational document chain. Use the pricing audit case when you need full control-exception review.
Step-by-Step Walkthrough
Step 1. Define realized pricing against list price
Start with realized pricing. Before you explain the policy stack, you need to know where billed revenue already diverges from base list revenue and which parts of the commercial book carry the biggest dilution.
What we are trying to achieve
Establish where realized revenue differs from base list revenue across customers, segments, regions, collections, and style families.
Why this step changes the diagnosis
This step gives you the commercial outcome first. It shows where pricing pressure exists before you decide whether promotions, customer-specific pricing, or override behavior explain it.
Suggested query
Use this first to compare realized billed revenue with base list revenue across the commercial book.
What this query does
It summarizes invoiced quantity, base list revenue, net revenue, average discount, and price-realization percentage by month, customer segment, customer, region, collection, and style family.
How it works
The query starts from SalesInvoiceLine, joins the billed lines back to SalesInvoice, Customer, and Item, and compares BaseListPrice against actual billed line totals.
What to look for in the result
- customers or segments with the lowest price realization
- collections or style families showing consistent dilution
- whether the biggest realization gaps sit in a few accounts or across the full book
- where the commercial story clearly needs a policy explanation
Step 2. Explain the promotion effect on revenue and gross margin
Once realized pricing is visible, separate deliberate promotion strategy from the rest of the pricing picture.
What we are trying to achieve
Show how promotions reduce revenue and change gross margin by month and collection.
Why this step changes the diagnosis
Promotion strategy is a deliberate commercial choice. This step shows when lower realized pricing reflects planned promotional activity rather than uncontrolled discounting.
Suggested query
Use this first to compare promoted versus non-promoted revenue and gross margin.
Use this follow-through query to isolate the revenue and gross-margin effect of promotions by collection.
What this query does
The first query compares promoted and non-promoted sales by month and collection. The second isolates the revenue reduction from promotions and shows the collection-level margin result after that reduction.
How it works
These queries group billed sales by promotion flag and collection, compare revenue before and after promotion effect, and tie net revenue to standard shipment cost through ShipmentLine.
What to look for in the result
- collections relying most on promotions
- where promotion activity reduces revenue materially
- whether promotion-heavy collections still preserve healthy gross margin
- whether promotional pricing explains the low realization seen in Step 1
Step 3. Show where customer-specific pricing is concentrated
Promotions are only one policy path. Next, isolate customer-specific pricing and see where realized pricing depends on a narrower set of negotiated relationships.
What we are trying to achieve
Identify which customers depend most on customer-specific pricing instead of standard segment pricing.
Why this step changes the diagnosis
Customer-specific pricing can be commercially justified, but concentration changes negotiation complexity and makes realized pricing more dependent on a narrower set of accounts.
Suggested query
Use this to identify which customers rely most on customer-specific price lists.
What this query does
It measures how much of each customer's sales-order-line population uses Customer Price List pricing and how much order value sits behind that dependence.
How it works
The query starts from SalesOrderLine, joins back to SalesOrder and Customer, filters the PricingMethod, and computes customer-specific pricing share and net order value by customer.
What to look for in the result
- customers with the highest customer-specific pricing share
- whether those customers are also commercially important by order value
- whether pricing concentration appears strategic or administratively heavy
- which customer relationships deserve deeper commercial review
Step 4. Measure override concentration and price-floor pressure
Now isolate override behavior. This is where negotiation pressure becomes visible before it turns into a formal control issue.
What we are trying to achieve
Show where override behavior and floor pressure concentrate by sales rep, customer segment, and month.
Why this step changes the diagnosis
Override pressure reveals negotiation intensity and pricing discipline. This step stays on commercial concentration and pressure rather than formal exception testing.
Suggested query
Use this first to compare override concentration and discount dispersion by sales rep and customer segment.
Use this follow-through query to compare monthly floor pressure with override usage.
What this query does
The first query measures override concentration by sales rep and customer segment. The second shows how often order lines sit at or below the price floor and how often overrides are used by month.
How it works
These queries start from SalesOrderLine, join to SalesOrder, Employee, Customer, and PriceListLine, and compare override usage, discount dispersion, and price-floor proximity over time and by selling context.
What to look for in the result
- sales reps with the highest override concentration
- customer segments showing heavier override pressure
- months where price-floor pressure spikes
- whether override activity looks concentrated and explainable or broad and unstable
Step 5. Extend the case into governance follow-up
Finish by taking one controlled step into governance risk. This is the handoff point where commercial interpretation becomes control follow-up.
What we are trying to achieve
Identify where the pricing story moves from commercial interpretation into governance follow-up.
Why this step changes the diagnosis
The case should end with a decision about where leadership needs stronger review. It does not turn this page into the audit case, but it should show when governance attention becomes necessary.
Suggested query
Use this to identify missing or incomplete override approvals when override pressure has already been established commercially.
What this query does
It isolates incomplete override approval records and missing override links on below-floor sales lines.
How it works
The query reads PriceOverrideApproval, SalesOrderLine, SalesOrder, Customer, Item, and PriceListLine, then separates incomplete approval records from missing linked approvals on below-floor lines.
What to look for in the result
- override-priced lines with incomplete approval support
- below-floor lines with no linked approval
- whether the governance issue is isolated or recurring
- which patterns should move into the full Pricing Governance Audit Case
Required Student Output
Submit a short case memo or notebook note with these four artifacts:
- Evidence summary: identify the key result rows, metrics, timing patterns, or exception families that changed your diagnosis.
- Accounting or business interpretation: explain what the evidence means for the process, accounting treatment, managerial decision, or control risk.
- Database explanation: name the source tables, row grain, join keys, or trace path that make the evidence defensible.
- Management or audit conclusion: state which driver, document path, or exception family should be followed up first and why.
Optional Excel Follow-Through
- Start with one customer segment or one collection and compare
BaseListRevenue,NetRevenue, and realized price. - Add a promotion tab that shows the revenue and gross-margin effect before and after promotions.
- Build one customer-specific pricing pivot that shows dependency by customer and order value.
- Add a narrower override tab with sales-rep concentration, price-floor pressure, and monthly spikes.
- Keep a final governance tab for only the approval gaps that deserve handoff into the audit case.
Wrap-Up Questions
- Accounting/process: Which pricing layer most changes realized margin: list realization, promotion, customer-specific pricing, or override behavior?
- Database/source evidence: Which customer, segment, collection, sales-order, or price-list grain supports the margin explanation?
- Analytics judgment: Where does discounting look commercially justified, and where does it look like governance pressure?
- Escalation/next step: Which pattern should stay in commercial follow-up, and which should move into the pricing audit case?
Next Steps
- Use Pricing Governance Audit Case when you want the full control-focused follow-through.
- Use Commercial and Working Capital when you want the broader commercial perspective above the case.
- Use Financial Queries and Managerial Queries for the broader pricing and margin query sets.