The short version
Price-volume-mix analysis (referred to as PVM analysis or simply PVM) is a method for attributing changes in revenue or gross margin to three sources. When your Q1 revenue is up $2.1M over the prior year, PVM analysis tells you how much of that came from higher prices, how much from more units sold, and how much from a shift in what you sold. Each source is isolated and quantified.
For manufacturers, this matters because the three effects can run in opposite directions at the same time. Revenue can grow while margin erodes if the mix has shifted toward lower-value products. Volume can decline while margin improves if the shift is toward higher-value parts. Without attribution, the income statement only shows the net result, which can be misleading in either direction.
The key insight: revenue can grow while margin erodes. PVM analysis is the tool that separates these movements so pricing teams can respond to the right problem.
The three components of PVM analysis
Every change in revenue or gross margin between two periods decomposes into three and only three forces. Once you have the attribution, the three values sum to the total change.
The revenue impact of selling at a different price per unit than the prior period, holding volume and mix constant. This isolates whether your pricing decisions held in the market. A 5% list price increase that resulted in a 3.8% realized increase produces a measurable price effect and a measurable gap between plan and outcome.
The revenue impact of selling more or fewer units, holding price and mix constant. This separates market demand from pricing decisions. When revenue is down, the volume effect tells you whether the shortfall is a demand problem, a lost-customer problem, or something else entirely, rather than a pricing problem that a compliance review would catch.
The revenue impact of selling a different composition of products, holding both price and volume constant. If your revenue is flat but average margin improved, the mix effect explains why: you shifted toward higher-margin products even without raising prices or selling more units. The mix effect is the one that most often surprises manufacturers, and it can move significantly without anyone noticing until PVM is run.
Why the mix effect matters most for manufacturers
Manufacturing businesses tend to run wide product catalogs: thousands of SKUs across product lines, some with high margin entitlement and others that are commodity items with full price transparency. The mix effect captures what happens when the composition of what gets sold shifts across those product lines.
Consider a manufacturer that runs a blanket 5% price increase. The high-value specialty parts absorb the increase and margins hold. The commodity parts often don't, because customers can source alternatives. The net revenue number looks like the pricing initiative worked, but the mix has shifted: volume is now concentrated in lower-margin items because the high-value parts saw some demand compression.
PVM attribution catches this. The price effect shows the increase holding partially. The volume effect shows some demand compression. The mix effect shows the shift toward lower-margin items. The combination tells the real story. Without PVM, "the pricing initiative was broadly successful" becomes the default read when it shouldn't be.
Watch for this pattern: revenue growing while gross margin percentage falls. That combination almost always indicates a mix shift, not a pricing problem. PVM analysis confirms which it is before the team debates the wrong question.
A manufacturing PVM example
Here is a worked example from a specialty parts manufacturer comparing Q1 FY2025 to Q1 FY2024. Total revenue moved from $21.4M to $23.5M, a $2.1M increase. The table shows where it came from.
| Effect | Amount | What it tells you |
|---|---|---|
| Price | +$1.8M | Price increases partially held. Realized price up 2.4% on average against a 3.0% planned increase. |
| Volume | −$0.9M | Unit volume declined slightly in Q1. Demand softness concentrated in the standard catalog tier. |
| Mix | +$1.2M | Mix shifted toward high-value specialty parts. Complex assemblies grew as a share of total orders. |
| Net revenue change | +$2.1M | +9.8% YoY. Revenue growth is real but driven more by mix than price. |
Without PVM analysis, the read is: "revenue is up nearly 10%, pricing is working." With PVM, the read is more specific: volume is actually declining, pricing held but came in 0.6 points below plan, and the revenue gain is largely driven by mix, specifically a shift toward the specialty segment. That is a different conversation with a different set of follow-on questions.
The follow-on questions for the VP of Pricing look different depending on the answer. A volume problem calls for a commercial response. A pricing compliance gap calls for an exception review. A mix shift calls for examining whether it's structural (the market is changing) or a one-quarter anomaly.
What data PVM analysis requires
PVM analysis runs entirely on transaction-level data from your ERP. The inputs needed are:
This data lives in your ERP's order and invoice tables. No external benchmarks are required. No surveys. No manual data collection. The entire analysis runs on what your ERP already recorded when orders were entered and invoices were posted.
The challenge is not collecting the data. It is getting it out in a format that allows period-over-period comparison by item, by cohort, by customer, and by plant, without spending hours in Excel each reporting cycle.
Running PVM in spreadsheets vs. ERP-native tools
Most manufacturers attempt PVM analysis in Excel first. The process typically involves pulling invoice exports from the ERP, cleaning and normalizing the data, building a pivot model, and manually constructing the waterfall bridge. For a business with 2,000 active SKUs and multiple plants, this takes a full day of analyst time per reporting period.
The fragility of the spreadsheet approach compounds at scale. If your plants run different ERP systems, each system needs a separate export process, and the resulting data structures often don't align without significant manual reconciliation. Multi-ERP PVM in Excel is technically possible but practically unsustainable for a team without dedicated data engineering support.
How Marquis Pricing IQ runs PVM attribution
Pricing IQ connects to your ERP and runs price-volume-mix attribution from transaction data. The bridge updates each period as invoices post. No exports, no manual bridging, no reconciliation between systems.