What should you look for in lumber ERP software in 2026?

Look first at whether the ERP can be set up to record the transactions that make your business awkward. Then check whether those records come out cleanly when you want to analyse them. This applies to lumber dealers, distributors and manufacturers with more than one branch or unit of measure. The feature list matters, and every serious lumber ERP now claims most of it. Panorama Consulting's 2026 ERP Report found the most common cause of budget overruns was an unexpected need for more technology, and suspects much of that is reporting.

What the usual answer says

The leading buyer's guides are written by vendors and list features. A 2026 buyer's guide from GenetiQ, published in April, sets out nine criteria, from point of sale and native financials to "AI-enhanced decision-making". It promises "API, EDI, XML, and CSV integrations to connect with design tools, ecommerce, payments, and supplier systems." It also states that "45% of lumber companies are experimenting with AI-based inventory management systems". The guide attributes that figure to a statistics aggregator's page, not to a survey it names.

A feature list is a reasonable first filter. It cannot tell a buyer how the system will record a transaction that is peculiar to their business, or what the reports built on that record will say.

Where ERP projects actually overrun

Panorama's 2026 ERP Report surveyed 170 organisations that had selected or implemented ERP. Business intelligence led the initiatives deployed alongside it, with 55.3% reporting a major deployment. From its own consulting projects, Panorama adds that executives cite "ERP reporting delays" and "Inconsistent metrics" among their reasons.

More than a quarter of organisations reported going over budget. Of those, the most common reason was "the unexpected need for additional technology." In Panorama's words, "Organizations discover fatal misfits late in the project, so they turn to additional technology, scope expansion, and custom builds." Its authors suggest "it's possible that many organizations are needing additional tooling for data pipelines, governance, and reporting layers". The report is a consultancy survey across industries rather than lumber alone, and the reporting link is its authors' suspicion, not a finding. It is still a pattern a lumber buyer can test for before signing.

What a booking rule can do to a margin

From Quarri's own work with a lumber and millwork manufacturer: inter-branch transfers booked at zero revenue but full cost produced a negative margin that didn't exist.

A feature list never reveals a problem like that. Multi-branch inventory appears in every guide. How a transfer between branches is booked, and how the margin report treats it, appears in none. The same applies to lumber sold by the piece and bought by the thousand board feet, to rebates settled months after the sale, and to credits against a load.

A test to run in the demo

Scripted demos built on the buyer's own scenarios are standard selection advice, and consultancies including Panorama sell them. The useful part here is what to script. Bring three of your own awkward transactions. A transfer between branches, a sale in a different unit from its purchase, and a rebate that lands in a later month will cover most lumber businesses. Ask the vendor to enter each one. Then ask to see the booking the system makes and the margin report that includes it. Last, ask for the raw records behind that report, exported the way your analyst or an AI tool would receive them.

A demo tenant is configured by the vendor. How it books your transfer on the day tells you less than whether the booking can be set the way you need. Ask the vendor to change the transfer price or the unit conversion rule in front of you, per branch or per product, and run the transaction again. If the margin is right and the export is clean and complete after that, the system can record your business the way you run it. If it needs a workaround or a later phase, you have found a misfit before signing.

When it doesn't apply

A single-branch yard with no transfers and one unit of measure has fewer awkward transactions to test, and a well-built feature list may be enough. Businesses replacing an ERP inside a larger group often inherit the booking rules from the group's accounting policy, so the test is about reporting and export rather than configuration. And no demo shows how a system behaves at volume, so ask for a reference customer who runs the same transactions.

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.