PVM analysis names every force that moved your gross margin from one period to the next. Done right, it separates revenue effects from cost effects and gives each driver a number. This guide covers all six: Price, Volume, Mix, Materials, Labor, and Burden.
Send us a file. We'll return a real six-driver margin bridge built on your numbers, not a sample. No cost, no commitment.
Request your analysisWhen margin moves, the instinct is to declare a cause: "prices softened" or "costs are up." PVM analysis replaces the instinct with a number. It forces an accounting of every driver so the business can respond to what actually happened, not what it felt like.
The result is a margin bridge: a structured walk from prior-period gross margin to current-period gross margin, with each contributing factor sized and signed. Revenue-side effects are separated from cost-side effects. Favorable moves are distinguished from unfavorable ones. No variance goes unexplained.
A manufacturer with $50M in revenue and a 28% gross margin has roughly $14M at stake. A one-point margin shift (entirely possible from mix alone in a quarter with unusual order patterns) is $500K. PVM analysis is the only way to know whether that $500K came from something you controlled, something that happened to you, or a combination of both.
The most common mistake is treating a volume gain as a margin gain. If the incremental volume was low-margin product, you may have grown revenue and shrunk margin at the same time. PVM catches this immediately. A simple revenue report does not.
Controllers and CFOs in manufacturing environments run PVM analysis as a close deliverable: it is the first explanation attached to any material variance from plan. For PE operating partners, it is the common language across portfolio companies with different ERPs, different product lines, and different pricing structures.
The first three drivers explain changes in gross revenue contribution. They are separated because each one has a different owner, responds to different levers, and signals a different problem or opportunity.
Standard PVM analysis covers the revenue side. The full margin bridge extends it to cost: three additional drivers that explain how changes in the cost of production affected gross margin, independent of anything that happened on the revenue side.
Separating cost drivers matters because they are not interchangeable. A materials variance has a different cause, a different owner, and a different remediation path than a labor variance or a burden absorption problem. Grouping them into a single "cost" line conceals the answer.
The six drivers combine into a waterfall: starting from prior-period gross margin, each driver adds or subtracts its contribution, and the walk lands on current-period gross margin. Every dollar of variance is accounted for. The example below shows a company that raised prices and grew volume, but margin still declined, because mix deteriorated and cost headwinds exceeded the revenue gains.
Reading this bridge, the story is clear: a $420K price gain and $185K volume gain were more than offset by a $315K mix deterioration and $380K in materials inflation, with a modest labor headwind. The business grew and raised prices and still lost $145K of gross margin. Without the bridge, the reported margin decline would have looked like an operations problem. The bridge shows it was mostly mix and materials.
PVM analysis is only as good as the data underneath it. A trustworthy six-driver bridge requires clean data in six corresponding places. Most manufacturers have at least one of these problems, often several.
Most manufacturers run PVM analysis quarterly, and most of the time is spent preparing the data rather than reading the results. Reconciling invoices across ERPs, mapping items to product families, normalizing customer accounts; the analytical work is straightforward once the data is clean. The data rarely is.
Automating PVM means solving the data problems first: a unified item master with consistent taxonomy, a customer master that resolves accounts to parent entities, current standard costs, and a consistent net revenue definition that works across every site and system. With those in place, the six-driver margin bridge can run on close, every period, without manual reconciliation.
The question the bridge should answer in five minutes: did we make or lose margin, and why? If the answer takes five days to produce, the data infrastructure is the constraint, not the analysis.
For PE-owned manufacturers with multiple portfolio companies on different ERPs, a consistent PVM methodology applied across the portfolio transforms quarterly board reviews. Instead of reconciling different formats from different companies, operating partners see one bridge per entity and one consolidated bridge for the portfolio, built from the same methodology, period over period.
Learn how Pricing IQ runs price-volume-mix analysis every period: see Pricing IQ.
The PVM Accelerator is a free, one-time analysis built on your data. We sign an NDA, you send a file, and we return a full six-driver bridge within 48 hours. No cost, no sales pitch.
Request your free PVM analysisFAQ
Questions about the six-driver margin bridge, data requirements, and how manufacturers put it into practice.
Price-volume-mix analysis is a method for attributing changes in gross margin to their underlying drivers: price, volume, mix, and when the full margin bridge is used, materials, labor, and burden. Together the six drivers account for 100% of the gross margin change between two periods.
A margin bridge is the output: a waterfall chart that walks from prior-period gross margin to current-period gross margin, with each driver labeled and sized. PVM analysis is the method that produces the bridge. When cost drivers (materials, labor, burden) are included alongside revenue drivers (price, volume, mix), the result is a full margin bridge rather than a revenue bridge only.
The revenue side requires units sold, realized selling price, and item classification by period. The cost side requires actual material cost vs. standard, actual labor hours vs. standard, and burden absorption data. All of this lives in ERP transaction tables. The challenge is normalizing it across multiple ERPs and periods before the attribution runs.
Most manufacturers run PVM analysis quarterly, aligned to financial reporting periods. Monthly is better for businesses with commodity-linked inputs or fast-moving pricing. Annual-only is generally too infrequent to catch mix drift or cost creep before it compounds into a year-end shortfall.
Yes, but it requires a data layer that normalizes transaction records from different ERP schemas before attribution runs. Multi-ERP PVM also requires a consolidated item master and consistent standard cost structure across all sites. Without that foundation, the comparison is apples to oranges and the attribution is unreliable.
Yes. The terms price-volume-mix, price-mix-volume, and PVM all refer to the same analytical framework. The order of the terms varies by industry convention but the underlying method is the same: decomposing a margin change into its price, volume, and mix components, and in the full version, its cost components as well.
Use a six-driver margin bridge that walks from last period's gross margin to this period's, with each factor sized and labeled: price, volume, mix, materials, labor, and burden. Instead of "margins were under pressure," you can say price added $2.1M and mix cost us $2.4M. The bridge replaces attribution disputes with response priorities—which is what a PE board actually needs.
The analysis itself takes a few hours once the data is clean. The time sink is usually data preparation—reconciling invoices, mapping items, resolving customer accounts—which can take days when done manually. Marquis can run a one-time PVM analysis on your data file in hours, and when Marquis IQ is connected to your ERP, the bridge runs automatically on every close.
Typically an invoice or sales transaction file covering the two periods you want to compare, including unit quantities, realized prices, and item identifiers, plus a cost file with standard costs by item. Marquis signs an NDA before you share anything.
Yes. Marquis normalizes transaction records from different ERP schemas into a single data layer before the analysis runs, so the bridge reflects a consolidated view across all your sites rather than a manual reconciliation of separate exports.
A P&L tells you what your margin was. A PVM analysis tells you why it changed—how much came from price, mix, volume, and cost movements. Each driver points to a different team and a different response, which is why the bridge is a management tool, not just a reporting tool.
Pricing IQ connects to your ERP, builds the master data layer, and runs the full six-driver margin bridge every period. Reach out to get started.