The Price Book Has Two Tabs
A discounting explanation depends on an effective-dated price book that covers fewer channels than the transaction ledger. Separate observed pricing from mapping assumptions and mix.
- ROLE
- Pricing Operations Analyst
- TIMEBOX
- 90–120 minutes
- COMPLEXITY
- Advanced / 4 of 5
- ROTATION
- Brief 10 of 16
The decision has already reached your desk.
Pricing leadership believes discounting in the acquired HarborHome business explains the quarter’s commercial movement and is considering a temporary pricing-control intervention.
The transaction ledger contains four sales channels, while the effective-dated price book contains only web and branch prices. A working spreadsheet maps other channels to the branch book and describes variance from list price as realized discount.
You must determine which comparisons are directly supported, which depend on an unapproved crosswalk and whether price—not product, channel or customer mix—supports the proposed action.
Certify, qualify or reject the discounting explanation and recommend whether HarborHome needs a temporary pricing-control intervention.
Use only Q2 orders knowable by 08 Jul 2024 at 08:30 ET. Captured line economics remain the transaction fact. Do not invent a crosswalk for unsupported sales channels, and separate price, volume, product mix and customer mix.
Run the brief as a controlled assignment.
The workbench mounts only the listed source neighborhood and supplies neutral starter worksheets. It does not grade the conclusion or reveal the mechanisms planted in the larger assignment.
- Open the dedicated brief workspace and confirm the brief ID in the queue.
- Establish table grain, cutoff and control totals before joining or modeling.
- Make at least two distinct evidence moves and test a credible rival explanation.
- Leave the requested polished artifact, then export the workspace or portfolio package.
The source files are shared; the draft workspace is not. Changing to another full assignment drops brief mode deliberately.
Real tables. A deliberately bounded neighborhood.
These Parquet files already belong to Meridian’s public 96-table estate. Use the mounted schema.table names in SQL or Python; download links are provided for learners working in a local DuckDB environment.
GRAIN / One canonical Q2 order header.
CAUTION / Source identifiers can collide and warehouse availability controls the eligible order population.
GRAIN / One captured purchase line.
CAUTION / Quantity, unit price, discount, tax and total must be reconciled before constructing a realization metric.
GRAIN / One product, price-book channel and effective period.
CAUTION / Only web and branch books are present; list price is context rather than captured transaction value.
ANALYSIS CUTOFF / 08 Jul 2024 / 08:30 ET
Questions to pressure-test—not steps to copy.
These prompts define the analytical territory without prescribing an order, technique or conclusion.
- 01
Which line-level fields reproduce captured value and what does each candidate price-realization metric mean?
- 02
What share of line volume has a directly supportable effective-dated price-book match?
- 03
How do source-system differences change after controlling separately for channel, product and account mix?
- 04
Which apparent price effect comes from an unsupported mapping choice rather than observed transactions?
Leave work another analyst can review.
Artifact presence can be recorded; analytical quality remains a human judgment. A complete brief has evidence, reasoning and a decision—not merely executed code.
- 01Governed pricing fact
Build a line-level fact with arithmetic, eligibility and effective-date controls.
- 02Price-book coverage matrix
Show directly matched, unmatched and assumption-dependent volume by source and sales channel.
- 03Price-volume-mix bridge
Compare Meridian and HarborHome while keeping price, volume and observable mix effects separate.
- 04Pricing disposition
Deliver a concise certify, qualify or reject recommendation for the proposed control intervention.
Review the reasoning after a real attempt.
The debrief does not contain an official answer. It identifies defensible analytical moves, common failure modes and questions a reviewer may use to challenge the handoff.
SPOILER-GATED REVIEW / REVEAL AFTER YOUR FIRST HANDOFF
DEBRIEF REVEALED / THIS MAY CHANGE HOW YOU APPROACH THE BRIEF
A price book is a reference, not a receipt. The central judgment is how much of the commercial comparison survives effective-date and channel coverage controls.
Defensible approaches
- Begin with captured line economics, validate arithmetic and keep the canonical order cutoff visible.
- Match price history only on product, directly supported channel and transaction date while retaining unsupported rows in an explicit category.
- Compare source systems within common product, channel and customer slices before attributing a residual difference to pricing behavior.
Common traps
- Treating list price as booked revenue or every variance from list as a discount.
- Mapping all non-web transactions to the branch book without evidence or dropping unmatched lines through an inner join.
- Averaging percentages without a declared weight and attributing compositional differences to policy.
Reviewer questions
- What proportion of the conclusion is directly observed rather than supplied by a channel assumption?
- Does the source comparison survive a common product and channel mix?
- Can the bridge reconcile to captured line value without silently excluding unsupported transactions?
CHALLENGE A COLLEAGUE
Pass the Brief
The link shares this spoiler-free briefing. It never includes your work, identity, or browser progress.SUGGESTED NOTEFour transaction channels, two price-book tabs and one silent mapping assumption. I audited the commercial claim in The Price Book Has Two Tabs from The Analyst.
