ERP systems are usually presented as a list of modules: accounting, sales, inventory, purchasing, HR… making the choice feel like counting features.

That hides the more important truth: a system's value isn't in its modules but in the links between them. Ten modules that don't talk to each other are worse than three that do.

The Seven Core Modules

Module What it manages Who uses it
Accounting and finance Entries, general ledger, reports, tax The accountant
Sales and customers Quotations, invoices, collections Sales
Purchasing and suppliers Purchase orders, incoming invoices, payables Purchasing
Inventory Items, warehouses, stocktakes, costing Stores
Human resources Employees, attendance, leave, payroll HR
Point of sale Direct sales, shifts, returns The cashier
Reporting and permissions A unified dashboard and who sees what Management

The Junctions: Where the Value Lives

A module alone does something limited. The value appears where two modules meet:

  • Sales × Inventory: the invoice deducts the item immediately — you don't sell what's gone or count by hand.
  • Inventory × Accounting: every item movement produces cost of goods sold — so the profit figure is real, not estimated.
  • Sales × Accounting: the invoice generates the entry and the customer balance together — no double entry.
  • Purchasing × Inventory: receiving goods raises the balance and updates average cost.
  • HR × Accounting: the payroll run generates the expense entry — your largest line, with no manual transfer.
  • POS × Inventory × Accounting: a till sale does all three in a second.

Which is why the right question to a vendor isn't "how many modules do you have?" but: show me what happens across the rest of the system when I issue one invoice.

The Shared Elements That Don't Count as Modules

Three elements run through every module, never appear in feature lists, and still determine the system's quality:

  • Permissions. Who sees what and who can delete or discount. Without them you can't open the system to other departments at all.
  • Audit log. Who did what and when. It is what makes the system a trusted source rather than just a tool.
  • Cost centres. Charging every transaction to a branch, department, or project — the only way to see profitability below company level.

For the meaning of ERP itself see what is an ERP system, and for the finance and people modules ERP accounting and the HR module.

Which Modules to Deploy First

The proven practical order:

  • Phase one: accounting + sales + inventory together. The three interlink and separating them makes no sense — deploying sales without inventory recreates the original problem.
  • Phase two: purchasing, once inventory balances have settled.
  • Phase three: HR and payroll, at the start of a month or financial year to simplify migration.
  • Phase four: point of sale for those who need it, after items and prices are set.

Each phase settles before the next. A project deploying six modules in one day usually fails on adoption, not technology.

Modules You May Not Need

Not everything offered is necessary. Performance reviews, talent management, manufacturing, project management — all excellent for those who need them, and a training burden and complexity for those who don't.

The rule: deploy what you use weekly. What you use once a year can wait.

Frequently Asked Questions

What are the components of an ERP system?

Seven core modules: accounting and finance, sales and customers, purchasing and suppliers, inventory, human resources, point of sale, and reporting and permissions. Not every company needs all of them.

What matters most when evaluating modules?

The links between them, not their count. Ask the vendor to show what happens across the system when one invoice is issued: does stock deduct, does the customer balance update, is cost of goods sold calculated, is the entry posted?

Which modules should I deploy first?

Accounting, sales, and inventory together in one phase, because they interlink. Then purchasing, then HR at the start of a financial period, then point of sale if you need it.

Should I deploy every module at once?

No. Big-bang deployment is the most common cause of stalled ERP projects, and the cause is usually adoption difficulty rather than a technical problem. Let each phase settle before the next.

What are cost centres and why do they matter?

They charge every transaction to a branch, department, or project. They are the only way to see profitability below company level — and what most often exposes departments that look profitable and aren't.

Do I need a point-of-sale module?

You need it if you have high-volume direct sales, till hardware, or shifts requiring a close report. Invoiced sales to credit customers are served by the sales module alone.

Conclusion

Don't compare ERP systems by module count. Compare them at a single junction: issue an invoice, and watch what moves across the rest of the system.

A system where four things move from one input is an ERP. One where a single thing moves is a set of programs sharing an interface.