Does a forest products business need a data platform, a data warehouse or a new ERP?

It depends on where your wrong numbers come from. If transactions are recorded wrongly or not at all, the fault is in the ERP. If the records are right but reports cannot reach far enough back or across enough of them, a data warehouse fixes that. If each system is right on its own terms and they disagree with each other, the fault sits between them. Checking that is what a data platform is for: a warehouse plus the written rules for how records in different systems should match. The three are often sold as stages of one purchase. They fix different faults, and a new ERP bought to fix a fault between systems costs the most and changes the least.

What the usual answer says

The pages that answer this question online are mostly forestry ERP vendors and software directories. Their answer is to start with an ERP built for the industry and add analytics later. One vendor promises "End-to-end visibility, ensuring timely transportation of harvested logs and processed products." Business intelligence and warehouses appear, where they appear at all, as add-ons.

That answer suits a business whose ERP is the problem, without asking whether it is.

What a wrong choice costs

Panorama Consulting's 2026 ERP Report surveyed 170 organisations with ERP projects. The median project timeline was 9 months, and more than a quarter went over budget. The most common cause of overruns was an unexpected need for more technology, and the report is direct about why: "Unexpected technology needs are often a result of poor system selection." The report's example is close to this question. An organisation "might need to add a governed analytics layer because they didn't realize that their chosen ERP system's native reporting won't meet executive dashboard needs at scale, especially across multiple entities and data sources." The sample skews larger than most forest products businesses. Median annual revenue was $200.5 million, and 56.5% were multinationals.

The warehouse and platform options carry their own risk. dbt Labs' 2026 survey of 363 data practitioners and leaders found that "Nearly three-quarters (71%) of data professionals are concerned about incorrect data reaching stakeholders." dbt Labs sells data transformation software, so it has an interest in the finding. A warehouse copies whatever the source systems hold, errors included. It makes history reachable without making it right.

Sort the faults before choosing

Collect the last few numbers that turned out to be wrong: a margin, a stock figure, an accrual, a delivered volume. For each, find where it went wrong.

If the transaction was never recorded, or recorded in a way the system cannot represent, the ERP is the fault. Examples are a haul rate the system has no field for, or a unit it cannot convert. Configuration may fix it. If not, that is the case for a new ERP.

If every record was right but the report could not combine them, because it only looks back two years or cannot join sales to production, the fault is reach. A warehouse, or the ERP vendor's own analytics store, fixes that without touching how transactions are recorded.

If each system was right on its own terms and the two disagreed, the fault sits between them: a scale record against a settlement, an accrual against a contract, a document against a ledger. A new ERP does not close that gap, because the other system is still there. A bare warehouse doesn't either, until someone writes and tests the rule that says how the two should match. Once those rules and checks exist, the warehouse has become what this piece calls a platform. The label matters less than whether the rules are there.

What the third kind looks like

From Quarri's own work with a forestry operation: one reconciliation cycle surfaced an over-accrual credit of $80k+.

Finding a fault between systems and fixing it are different jobs. A platform can show that a scale record and a settlement disagree. If the cause is two systems keyed differently, or a step in how entries are made, someone still has to change that process at the source.

Most businesses will find more than one kind of fault on their list, and the count of each points to the answer. Mostly the first kind points to the ERP. Mostly the second points to a warehouse or the vendor's analytics. Mostly the third points to a platform, and it can sit over the ERP you already run.

When it doesn't apply

An ERP that is out of vendor support, or that cannot record the business at all, needs replacing whatever the other faults are, and the sorting exercise only helps set the order. A business in the middle of an ERP migration should sort its faults against the new system's design rather than the old one's history. And a very small business with one system and few wrong numbers may need none of the three.

Quarri for finance and strategy teams is built for the people who close the month, explain the margin and answer the board.

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.