Blog/How to separate price and volume in a lumberyard sales forecast

How to separate price and volume in a lumberyard sales forecast

Sep 279 min read

Separate selling-price changes from customer buying volume before revising your lumberyard sales forecast. A practical guide for LBM managers.

Data
How to separate price and volume in a lumberyard sales forecast

To separate price from buying volume in a lumberyard sales forecast, compare quantities and realized selling prices for the same products over comparable periods. Then build the next forecast from expected quantities and selling-price assumptions separately. A change in sales dollars alone cannot tell you whether a contractor bought less material, paid less for it, or changed what they bought.

Start with a manageable category whose units and product records you trust. Use it to explain the sales movement before asking reps to recover a supposedly declining account or raising their revenue targets. Expand the method only after sales and finance agree on what the numbers include.

Why sales dollars need an explanation

A framing account can generate less revenue while buying the same quantity of the same lumber at lower prices. Another account can spend the same amount while buying fewer units at higher prices. These are illustrative situations, not customer results. They show why a revenue comparison needs both price and quantity behind it.

Large building-materials suppliers make similar distinctions in their reporting. In its full-year 2025 results, Builders FirstSource separately discussed core organic sales, commodity deflation, acquisitions, and selling days. Its figures are company-specific, and core organic sales should not be treated as a pure count of units. The useful lesson is to explain the drivers rather than assign every dollar of change to sales execution.

For a yard manager, the immediate question is more local. Did the same customers buy different quantities? Did the products or realized prices change? Did a delivery move across the month-end cutoff? Those explanations lead to different conversations with the sales team.

Set a consistent comparison before calculating

Compare the same reporting periods and use the same definition of sales. A partly completed month is not directly comparable with a full prior-year month. Note differences in selling days, and review a longer period when a large delivery makes one month unusual. A daily average can help describe the difference, but it does not remove seasonality or project timing.

Keep a same-branch comparison separate from growth caused by opening or acquiring a location. At the customer level, check for renamed accounts, merged records, or purchases moved to another branch. Otherwise, administrative changes can look like lost business.

Ask finance or your reporting owner for a line-level extract with these fields where available:

  • Invoice date, customer, branch, and item identifier.
  • Product category, quantity, and unit of measure.
  • Net product sales after the discounts included in your reporting definition.
  • Returns, credits, and separately identified delivery or service charges.

These are reporting requirements to check, not a claim that every ERP makes the extract available in the same way. Reconcile its total with the sales report your managers already use. Explain any exclusions before circulating the analysis.

Normalize quantities before comparing them. Pieces, linear feet, and board feet are not interchangeable. Even within a category, different dimensions or grades can change the meaning of an average price. Do not divide all lumber revenue by a mixed quantity column and call the result a market price.

Separate the change for matched products

For an unchanged item in a consistent unit, revenue equals quantity multiplied by realized unit selling price. Calculate that price by dividing the item's net product sales by its quantity for each period. Use the same discount treatment in both periods, and do not calculate a price where the quantity is zero or the record cannot be reconciled.

One practical reconciliation starts with the earlier period and changes quantity first, then price:

  1. Calculate the quantity effect by multiplying the change in quantity by the earlier period's unit price.
  2. Calculate the price effect by multiplying the change in unit price by the current period's quantity.
  3. Add those effects. For that matched item, they should equal the change in revenue.

This order assigns the combined effect of changing both quantity and price to the price step. Other methods allocate it differently, so write down the convention and use it consistently. The calculation explains a dollar difference; it does not prove why the customer changed their buying.

Apply the calculation at a level where the comparison is meaningful. For a contractor account, that may be the same item sold to the same account. Across an entire branch, a change in average realized price can also reflect a different mix of customers or discounts, even if the product is unchanged.

When you sum the item results, label the first part a quantity-and-mix effect. Selling more of an expensive product and less of a cheaper one changes revenue at the old prices, even if a total unit count stays flat. That is not pure physical volume growth. Keep category-level quantities alongside the dollar reconciliation rather than hiding the distinction in a single percentage.

Handle unmatched items separately. A new window line has no earlier selling price for this comparison. A discontinued product may have no current sale. Returns and credit adjustments can also distort net quantities and unit prices. Show these as exceptions or separate contributions, with finance agreeing the treatment, instead of forcing them through the matched-item formula.

Do not use one market index as a shortcut for the whole yard

A published price index can provide context, but it does not tell you what an individual contractor paid for your exact mix of materials. A yard selling framing lumber, windows, and hardware does not have one uniform product price.

The U.S. Bureau of Labor Statistics explains that quantities of different retail products cannot simply be added meaningfully. For its industry measures, BLS matches product-line revenue with product-specific price indexes to estimate real sales. That is a different task from explaining one dealer's invoice history, but it reinforces the need to match the price measure to the products being measured.

Use your own realized prices for the matched-item comparison when reliable data is available. If you must use an external index for a category estimate, document what it covers, what it excludes, and why it is relevant. Label the result an estimate. Do not present it as exact customer buying volume or use it alone to judge a rep's performance.

Keep gross profit visible as well. Stable quantities do not guarantee stable gross profit dollars when selling prices and product costs change. Sales, quantities, and gross profit answer different questions, so finance should review them together before the team changes its plan.

Build the next forecast from quantities and prices separately

The historical reconciliation explains what happened. A forecast needs a separate view of what customers are likely to buy next and when the yard expects to recognize the sale.

For repeat products with dependable unit data, estimate quantities by category or matched item group. Ask reps to connect the estimate to known customer work and material needs. Then apply selling-price assumptions appropriate to those products and expected sale dates. Summing those expected quantities multiplied by expected prices gives the product-sales forecast. Keep services and other revenue on their own documented basis.

For custom packages or special orders that do not have a useful common unit, forecast the specific order value and expected timing instead. Do not pretend that a count of unlike window packages measures physical volume consistently. Record the scope and price basis so a later revision has an explanation.

Keep committed orders separate from open quotes and early project discussions. Review the remaining unfulfilled value of an order, not its original value if part has already shipped. Check for revised quotes and for jobs already included in the repeat-business estimate. The lumberyard quote follow-up guide covers the job context and status checks behind that review.

Avoid assigning a universal close probability to every quote. Use your own consistently defined outcomes if you have enough history, and show uncertainty when you do not. A contractor's expected start date is useful evidence, but it is not a guarantee that the material will be ordered or invoiced in that month.

Write down a base forecast and a downside case with explicit assumptions. For example, one case could hold quantities steady but use lower expected selling prices; another could move an unconfirmed project's deliveries into a later month. These are planning examples, not predictions. Change each assumption visibly so managers can see what would cause the forecast to move.

Use the explanation to choose the next sales action

A price-driven decline calls for checking the selling-price assumptions and gross profit outlook. A quantity decline calls for a customer conversation about project schedules, scope, and where materials are being purchased. A category-mix change calls for understanding what work the contractor is doing before concluding that the relationship is weakening.

Suppose an account's framing revenue is down but matched-item quantities are steady. Ask about upcoming starts and confirm pricing; do not begin by accusing the rep of losing volume. If quantities are down as well, ask which jobs changed and whether the next delivery is delayed. Neither finding, by itself, proves that a competitor gained the business.

The existing guide to building-materials retail analytics covers buying frequency and category coverage. Use those signals to add context after you have separated the basic revenue drivers. More dashboards will not repair an inconsistent unit definition or an unexplained credit adjustment.

SalesJack's Analytics page describes role-specific dashboards and product category mapping. Confirm the invoice fields and calculation definitions needed for this analysis with your reporting team. The method in this guide is not a claim that a ready-made price-volume forecast is included in the product.

At the next review, keep the sales total beside the explanation for its change, the assumptions behind the next period, and the customer questions still unanswered. That gives the manager a concrete basis for revising the forecast without confusing commodity-price movement with the amount of business the team is winning.

Sources