Getting an ERP system live is a significant undertaking for any small or mid-sized company. Once accounting, sales, and purchasing modules are up and running, management tends to exhale — and advanced planning, quality management, maintenance tracking, and detailed cost accounting modules get pushed to a so-called second phase. This deferral decision is usually deliberate and reasonable; the problem is that the second phase rarely arrives on its own. The company sinks back into daily operations, consultants move on to other projects, and users drift back toward familiar workarounds. A year after go-live, those deferred modules may still be sitting untouched.
Second-phase optimization is how an ERP investment moves from baseline functionality to genuine operational value. The central question is straightforward: which module, when activated, delivers the highest benefit for the lowest additional effort? Answering that question requires an honest look at where the company is still losing time or money despite having an ERP in place. For manufacturers, the gap is often between actual production costs and what the accounting system reports. For trading companies, it tends to be inventory accuracy and supplier performance visibility. Without identifying the specific leak, module sequencing becomes guesswork.
The cost accounting module is the most commonly recommended starting point for a second phase, and the reasoning holds up well in practice. Because purchasing and accounting data were captured during the first phase, the cost module finds the raw material it needs already in the system. Rather than calculating unit costs manually on spreadsheets, the system can pull together production orders, material consumption, and labor records to produce a real cost figure. In industries where raw material prices fluctuate, this shift from estimated to actual cost gives management a concrete basis for pricing decisions — something that is hard to overstate in competitive markets.
The quality management module is a strong second-phase candidate for manufacturers, but it comes with prerequisites. If production orders and bill-of-materials records were entered accurately during the first phase, quality control checkpoints and rejection logs can be connected to that foundation. If those records are incomplete, the quality module ends up floating without an anchor, and users quickly start treating it as just another form to fill in. Before committing to quality module activation, it is worth auditing how thoroughly the production module is actually being used. Gaps in production data should be closed first; otherwise the quality module will not deliver what it promises.
Maintenance and breakdown management is a meaningful tool for manufacturers with significant machinery, but its value depends almost entirely on consistent data entry by the maintenance team. When periodic maintenance schedules are entered into the system, breakdown history is recorded, and spare parts inventory is linked to maintenance records, the true cost of unplanned downtime becomes visible. The difficulty is that activating this module is less a technical project and more a user adoption project. If the maintenance team does not log activity consistently, the module produces nothing useful. Resource planning for a maintenance module rollout should reflect that reality from the start.
The most common obstacle in second-phase projects is the data quality left over from the first phase. Inventory balances entered hastily at go-live, incomplete product recipes, or inconsistent customer records all interfere with new modules trying to process that data. When consultants return for the second phase, a significant portion of the engagement budget goes toward cleaning up this legacy before any new functionality can be configured. Companies that invested in data quality at the close of the first phase find that the second phase starts faster and costs less. The connection is direct, even if it is not always obvious until the second project is underway.
An SME manager considering a second-phase ERP project should be able to answer three questions clearly before committing resources. First, which operational process is still being managed manually or through spreadsheets despite the ERP being live? Second, is the existing data in the system accurate and complete enough to support a new module? Third, is there someone inside the company who will own this project, keep users accountable, and carry it through to completion? If all three answers are solid, a second phase can succeed. If any of them is uncertain, addressing that uncertainty first will do more for the outcome than rushing to activate another module.
This article was originally written in Turkish by Gökhan MERCANOĞLU on May 2, 2005 and has been automatically translated into English and other languages using machine translation.