An ERP is the system that holds a company's official numbers: stock, orders, purchases, production and accounts, in one place. Replacing or introducing one is among the largest changes a company makes.
Most should buy a packaged ERP. Some should not, and it helps to know which group you are in before a vendor tells you.
01Why packages suit most companies
A packaged ERP contains decades of accumulated practice in accounting, tax, purchasing and stock control. If your business runs those the usual way, you are buying a great deal of correctness that would be costly to recreate.
02Signs that a package will not fit
- Your core process, such as how you plan, price, make or deliver, is unlike your industry's norm.
- Every package you assess needs heavy customisation in the same area.
- You are small enough that a full implementation is out of proportion.
- You already run a customised package that has become impossible to upgrade.
03The sensible hybrid
Few companies should write their own general ledger. A common and sound design keeps a standard accounting package for the books and builds the operational modules around it: planning, production, job costing, field work, whatever is specific to the business.
The two are joined so that an operational event posts to the accounts automatically.
04Build it in stages
- Clean the master data first: items, customers, suppliers. Duplicates moved into a new system are still duplicates.
- Start with the module where the pain is worst.
- Run it alongside the old system and reconcile the two.
- Add the next module only when the first is trusted.
- Retire the old system last, when nothing depends on it.
A single switch-over of everything on one day is the pattern behind most failed ERP projects.
In short
- A packaged ERP is right for most companies with standard processes.
- A custom ERP suits unusual core processes and over-customised packages.
- Keeping a standard ledger and building operations around it is often the best of both.
- Clean master data and staged delivery matter more than the choice of technology.
Questions
What is master data and why does it matter for an ERP?
It is the shared reference data every transaction uses: items, materials, customers, suppliers. If the same item exists under five codes, stock, purchasing and costing are all wrong, in any ERP.
Can a custom ERP be extended later?
Yes. Since you own the code, modules can be added as the business changes, without waiting for a vendor's roadmap.
Can AI be part of an ERP?
Usefully, in specific places: detecting duplicate records and payments, classifying descriptions, forecasting demand and flagging unusual transactions. It works only as well as the data it reads.
Sounds like your problem?
Tell us about it. We'll say honestly whether the swarm can help, and what it would take.
Read next
- CRM, ERP, HRMS, CDP, PIM, WMS and the rest: thirty business systems explained in plain wordsBusiness systems
- Custom software or off-the-shelf: how to decide whether to build, buy or extendBuild or buy
- Custom CRM or off-the-shelf CRM: which does your sales team need?CRM
- CDP vs CRM vs DMP: what each one stores, and which you needCustomer data
- CMS, DAM and PIM: what each one manages, and why a catalogue needs all threeContent and product data
- OMS, WMS, SCM and ERP: how one order moves through themOrders and stock