Which ERP Modules Does Your Business Actually Need?
A 40-person medical-supply distributor outside Columbus swapped QuickBooks for a mid-market ERP last year. In the first month they turned on three modules: general ledger, inventory, and order management. HR stayed dark, because an outside payroll provider already handled that. The native CRM module stayed off too, because their five-person sales team was happy with a $15-a-seat pipeline tool they already knew. Eight months later, when a second distribution center opened, they added warehouse management. That staged approach, not a big-bang rollout where every module gets switched on at once, is how most ERP module decisions should actually get made.
The modules almost every company licenses on day one
Four modules form the core of nearly every ERP deployment, regardless of industry:
- General ledger / financials: the chart of accounts, journal entries, and the source of truth for every other module's dollar figures. Nothing else works without this one.
- Accounts payable and receivable: often bundled with the GL, but worth evaluating separately if you have complex payment terms or high invoice volume.
- Inventory management: if you touch physical goods, this module owns stock levels, costing method (FIFO, LIFO, average), and reorder points.
- Order management: the pipeline from quote to sales order to fulfillment. This is usually where the most manual re-keying happens before an ERP goes in, so it's often the module that justifies the whole project.
These four cover the transactions that happen daily: someone books a sale, ships product, pays a vendor, closes a period. Everything downstream of them, reporting, forecasting, budgeting, depends on this data being clean, so implementation teams almost always sequence these first regardless of what else gets licensed.
Modules that depend on what you actually make or sell
Past the core four, the right module list splits hard by business model.
A contract manufacturer running three shifts needs a bill-of-materials engine, a shop floor control module to track work orders against machine time, and often a quality module to log inspection results against lot numbers. None of that is useful to a services firm.
A distributor with more than one warehouse usually needs a dedicated warehouse management module (bin locations, pick/pack/ship workflows, cycle counting) well before it needs advanced demand planning. A single-location distributor can often run inventory reasonably well out of the base inventory module and skip WMS entirely.
A 12-person engineering consultancy, by contrast, typically runs project accounting, time and expense entry, and billing, and skips the inventory module altogether because there's no physical stock to track. Retail and eCommerce operations lean on point-of-sale or storefront integration modules instead.
The mistake to avoid is licensing a manufacturing-grade planning module because a competitor has one, when your actual production is two SKUs assembled to order. Match the module to the transaction volume and complexity you actually have, not the one you might have in three years.
Modules worth deferring even when the salesperson bundles them
Three modules are commonly bundled into ERP quotes that most buyers should hold off on:
- Full HCM/payroll: below roughly 100 employees, the per-employee ERP HR fee frequently costs more than a dedicated payroll vendor like Gusto or ADP, and a CSV or API sync between the two systems is usually enough. HCM modules earn their cost once you need multi-state compliance tracking or benefits administration at real scale.
- Advanced planning and scheduling (APS): this only pays off once you're managing enough SKUs and enough demand volatility that a planner can't reasonably hold the constraints in a spreadsheet. Below roughly 200 active SKUs, base MRP is usually enough.
- Native CRM: most ERP CRM modules are thin compared to a dedicated tool like HubSpot or Salesforce. Turn it on only when you specifically need order history and pipeline data on the same screen for the same rep. Otherwise you're paying twice for weaker functionality.
How ERP vendors actually price modules
Module pricing typically stacks three layers: a base platform fee, a per-module fee, and a per-user fee, and each layer can move independently. As a rough sense of the range, a mid-market cloud ERP might run a base platform fee near $999 a month, with individual modules adding another $99 to $499 a month each, plus $99 to $199 per user per month on top. An open-source-adjacent platform like Odoo instead charges per app per user, often in the $20 to $30 range per app per user per month, which sounds cheaper per line item but adds up fast once you're running eight or nine apps across 30 users. On-premise platforms like SAP Business One flip the model: a larger perpetual license fee up front, plus roughly 18 to 22% of that license cost per year in maintenance.
The practical risk is that per-module and per-user fees compound quickly once headcount crosses 25 to 30 seats, which is exactly the point where a lot of implementations quietly double their original quote. Before signing anything, it's worth running the specific module list through a license cost calculator using your actual user count, not the discounted pilot-phase number the sales rep quoted.
| Module | Owns this data | Skip it if... |
|---|---|---|
| General ledger | Chart of accounts, journal entries | Never skip. This is the foundation. |
| Inventory | Stock levels, costing, reorder points | You sell services with no physical goods |
| Warehouse management | Bin locations, pick/pack workflows | You operate a single small warehouse |
| HCM/payroll | Employee records, benefits, comp | You're under ~100 employees with an outside payroll vendor |
| Project accounting | Time entry, project budgets, billing | You don't bill by project or hour |
| Native CRM | Pipeline, opportunities, contacts | Your sales team is happy with a dedicated CRM |
A worked example: pricing a 35-user rollout
Take a 35-employee distributor evaluating a mid-market cloud ERP. Say 20 users need full transactional access (warehouse, order entry, finance) and 15 need lighter reporting-only access. Most vendors price those two tiers differently, often $150 to $180 a month for a full user and $40 to $60 a month for a reporting-only user. Layer on the module fees: GL and AP/AR bundled at $299 a month, inventory at $199 a month, order management at $249 a month. Rough monthly total: (20 × $165) + (15 × $50) + $299 + $199 + $249 comes out to roughly $4,800 a month, or about $57,600 a year, before implementation services. That implementation services line is routinely 1 to 1.5 times the first year's license cost for a mid-market rollout, which is the number that catches most first-time buyers off guard when the final invoice arrives.
One more detail worth confirming before finalizing a module list: some modules have hard dependencies on others. A warehouse management module typically requires the base inventory module underneath it; an advanced planning module typically requires MRP already running. Vendors don't always volunteer this during a sales conversation, and discovering a dependency after signing a contract for just the module you thought you needed is a common source of mid-implementation scope changes.
A rule of thumb that holds up across most implementations: license the modules that touch a transaction you process daily, orders, invoices, receipts, starting on day one, and hold off on anything you touch weekly or less until the core system has been through at least two full month-end closes. By then you'll know from lived experience, not a sales deck, whether the gap is real.