Skip to content

A stalled ERP rollout taken to production in one quarter

An in-house ERP implementation that had run for over a year without going live, audited, re-scoped and put into production in a single quarter.

Manufacturing · Mid-market discrete manufacturer

ERP
1 quarter
Time to production

from 12+ months stalled

100%
Manual weekly reports removed
6
Extensions shipped

all upgrade-safe

The challenge

An internal ERP project had been running for more than a year with no go-live date. Standard modules did not match the company's tiered pricing or its stock-reservation policy, so operations had reverted to spreadsheets and had stopped trusting the system entirely.

What we did

We audited the existing build and separated what was salvageable from what had to be rewritten. The universal 80% of the platform was left untouched. The three processes that genuinely differed — priority stock reservation, tiered customer pricing, and the weekly operations report — were rebuilt as upgrade-safe extensions rather than as edits to core objects. Rollout ran plant by plant so production never stopped.

More configuration was never going to get this live. What did was a small number of framework-native extensions capturing the 20% of the business that no standard product can know about, and a decision to stop customizing the other 80%.

The test we hold ourselves to on this kind of work is what happens at the next version upgrade. Because nothing in the vendor's own objects was edited, the extensions are re-tested and the upgrade proceeds. The spreadsheets went away and stayed away.

Stack

OdooPythonPostgreSQLQWeb

Have something to build?

Tell us the problem. We'll come back with a plan, a price, and who'd actually build it.

  • Free scoping call
  • Reply within 1 business day
  • No lock-in