What does lumber yard ERP software need to handle?

Units of measure, stored in the right place. A yard buys by the thousand board feet, stocks by the unit or the piece, and sells by the piece, the lineal foot or the board foot. Every lumber ERP on a shortlist says it handles this. The difference that matters is where the conversions live. If they are held once on each item, from its dimensions, every module agrees. If they are keyed on each transaction, they drift. Inventory value and margin drift with them. A buyer can test for that in a demo, and an existing yard can test for it in its own transaction history.

What the usual answer says

The vendor guides that rank for this question already name units as the hard part. One ERP vendor's guide says that "Lumber items can be purchased in one unit, stocked in another, and sold in a third". It warns that "If your ERP cannot convert between those three unit types cleanly and in real time, every transaction introduces error". Others add random-length tallies and pricing by the thousand board feet. That is the right list. What the guides don't say is how to tell whether a system does it well, or how to find out whether yours has been doing it badly.

What the sales rules add

In at least one large market the law adds a requirement. That country's national model rules for the method of sale, in their 2026 edition, require softwood lumber at retail to be represented by "the number of pieces", by width and thickness, and by "either the length of individual pieces or the lineal footage". Nominal sizes are allowed only if "the term 'nominal' or 'nom' is also used" and the actual sizes are shown "either by means of a table or label". An undated trade body's guidance says the rules had been adopted by "about 46" of that country's states at its last count. Other markets have their own rules. For the system, the point is that nominal and actual dimensions both have to be on the item, because the label, the invoice and the board-foot figure all come from them. The rules note that a dry "2 × 4" is surfaced to "1 1/2 in × 3 1/2 in (38 mm × 89 mm)", so its actual cross-section is about 66% of the nominal one. They also define a representation as "any advertisement, offering, invoice, or the like", which puts the invoice an ERP prints within scope. A system that computes board feet from one set of dimensions and prints labels from the other will disagree with itself by a third.

Where the conversions should live

An ERP that handles units well stores four things per item. The first is one stocking unit, with every other unit derived from it. The second is nominal and actual dimensions, green and dry where both apply. The third is length, and for random-length stock the tally itself: how many pieces at each length, as well as the total. The fourth is a price unit held separately from the stock unit, so a price per thousand board feet is never applied to a count of pieces.

In our view, the failure to watch for is a conversion factor stored on each transaction instead of on the item. One receipt is keyed in board feet and the next in pieces, each with its own factor, and nothing forces them to agree.

A check on your own data

This is where data work helps most. For each item, take every receipt and sale over a year and compute the conversion each one implies: board feet per piece, pieces per bundle, price per unit against price per thousand. Compare each with the item record. Transactions whose implied conversion is out of line are the ones to look at first. A cluster of them on one item, one supplier or one clerk may point to a single cause. An AI tool can read supplier invoices and tally sheets whose units differ from the yard's into the same form, so the check covers purchases as well as sales.

When it doesn't apply

Yards selling mainly sheet goods, packaged products and hardware by the each have fewer conversions to manage. Wholesale yards selling only by the thousand board feet face retail labelling rules less directly, though conversions still matter for costing. And the difference between shortlisted systems may lie elsewhere, in commodity pricing, contractor credit or dispatch, once units are handled on the item.

Quarri for wood products is built around how a wood products plant runs, where the order book meets real capacity.

Quarri is an AI-native data platform for the timber supply chain. It connects buying, production, sales and inventory for forest management, sawmill, wood products and pulp, paper and packaging operators.