Automation Cannot Fix an Undefined Process

Consider a common purchasing process. One employee raises a requirement through WhatsApp. Another prepares a purchase order in Excel. A manager approves it over a phone call. The goods arrive, but the store team does not have the approved order. The supplier invoice goes directly to Accounts, where someone has to call three people to confirm the quantity and price.

It may be possible to reproduce every one of these steps inside an ERP. But that is not process improvement. It is only moving the same confusion into a new system.

Before configuring the software, the business needs to answer some basic questions:

Who is authorised to request a purchase?

Who approves it, and based on what limits?

Who confirms receipt of the goods?

What should happen if the received quantity or price is different?

Who owns the exception?

Once these decisions are clear, the ERP can make the process faster, more controlled and easier to track.

Do Not Confuse Flexibility with Efficiency

Many companies depend on employees who know how to “manage somehow.” One person knows which spreadsheet to check. Another remembers special customer prices. Someone in Accounts corrects the entries at month-end. A senior employee knows which exception applies to which customer.

This flexibility may keep the business running, but it also creates dependency and risk. The process works because particular people remember how to handle the exceptions — not because the organisation has a reliable process.

During an ERP implementation, businesses often ask to preserve all of these exceptions through customisation. Every special case becomes a new field, screen, workflow or report. The result may technically satisfy the requirement, but it can make the ERP harder to use, harder to maintain and more difficult to upgrade.

Customisation is valuable when it supports a genuine business advantage or industry requirement. It should not protect unnecessary steps simply because:

“This is how we have always done it.”

Simplify Before You Configure

A good ERP project should begin with process discussions, not software screens. First, document how the work happens today — including unofficial steps happening through calls, chats and spreadsheets. Then identify:

duplicate work

delays

unclear ownership

unnecessary approvals

manual dependencies

exceptions that exist only because the current system cannot handle them

Then ask one important question: what is the simplest process that can achieve the business objective with the required control?

For example, a production user should not have to understand Work Orders, Stock Entries, time logs and accounting entries just to report completed production. The user-facing process can be simple: Select the Finished Good from the Sales Order, enter the materials and consumables used, record electricity consumption and operation time, and submit. The ERP can then create the required Work Orders and Stock Entries in the background, update inventory and calculate the actual cost of the Finished Good. The controls remain strong. The accounting remains accurate. But the employee interacts only with the information relevant to the job. That is what good ERP design should do: the system handles the complexity instead of passing it to the user.

Management Must Own the Decisions

ERP implementation is not only an IT project. The implementation team can recommend best practices, suggest better workflows and configure the system. But they cannot decide how the business should operate. Management has to agree on:

approval authority

responsibilities

exception handling

ownership

required controls

expected reports and outputs

If different department heads continue giving conflicting instructions, the implementation will either keep changing or result in a process that nobody fully owns. These decisions should be agreed and documented before development begins. Otherwise, changes will continue during testing and after go-live, increasing cost and delaying adoption.

Measure Success by Simplicity and Control

An ERP implementation is not successful simply because every department has started entering transactions. A better measure is whether the business now operates with:

less duplicate data entry

faster and traceable approvals

clearer accountability

better visibility

fewer manual reports

controlled exceptions

less dependency on individual employees

Ask these questions after implementation:

Are employees entering the same information fewer times?

Are approvals faster and traceable?

Can management see reliable information without waiting for someone to prepare a report?

Is ownership clear when something is delayed?

Are exceptions visible and controlled?

If the answer is yes, the ERP is creating value.

Fix the Process, Then Let ERP Strengthen It

The best ERP implementations do not begin by asking: “How can we put our current process into the software?” They begin by asking: “Why do we follow this process, and how can it be simpler?” ERP can automate routine work, connect departments, enforce controls and provide real-time visibility. But it cannot compensate for decisions the organisation has avoided making. Before blaming the ERP, look closely at the process behind it. Simplify the workflow. Define ownership. Remove unnecessary exceptions. Then configure the system around that clarity. Your ERP may not be the problem. Your process may simply need to be redesigned.

Frequently Asked Questions

Why does my ERP implementation feel complicated?

Often because the process itself was already complicated before the ERP arrived — unclear approvals, duplicate data entry, manual dependencies and too many exceptions. ERP usually reflects the process it is configured around, so simplifying the process first often makes the system easier to use.

Does customising ERPNext solve process problems?

Not always. Customisation should support a genuine business requirement or competitive advantage. It should not preserve unnecessary steps simply because they existed in the old process.

Who should decide how business processes should change for ERP?

Management must own these decisions. The implementation team can recommend and configure, but the business must agree on approval authority, responsibilities, exceptions and expected outputs.

Should business processes be redesigned before ERP implementation?

Not every process needs to be redesigned, but existing workflows should be reviewed before configuration begins. This helps identify duplicate activities, unclear approvals, unnecessary manual steps and areas that can be simplified before they are built into the ERP.

Why Wahni?

At Wahni IT Solutions, we do more than configure ERPNext. We study how your business currently operates, identify unnecessary steps and design simpler workflows before implementing the system.

As a Frappe Certified Partner serving businesses across India, the UAE and the Middle East, our team supports ERPNext implementation, customisation, integration and ongoing support. With teams in Kochi, Bengaluru and Dubai, we work closely with manufacturing, distribution, trading and service businesses to build practical ERP systems that employees can use with minimal effort.

If your current processes depend heavily on Excel sheets, manual follow-ups or individual employees, Wahni can help you simplify them and build an ERPNext solution around a clearer and more scalable way of working.