Custom ERP for manufacturing: modules that matter

Manufacturing ERP development succeeds or fails on six modules: bill of materials, production planning, inventory, procurement, quality, and GST-compliant finance. Everything else, from HR to maintenance, can come later or come from a packaged product. The order you build them in matters as much as the features, because each module depends on master data the previous one creates. This article sets out what each module has to do for a mid-sized Indian manufacturer, how we phase them, and what a custom build costs compared with a packaged product.

Why manufacturers outgrow packaged ERP and spreadsheets

Most plants we work with run on a mix: an accounting package for finance and GST, spreadsheets for planning and stock, and a whiteboard for the shop floor. It works until volumes grow, a second unit opens, or a large customer demands traceability and on-time delivery reporting. Packaged manufacturing ERPs exist and are right for many; the fit breaks where the process is unusual, such as make-to-order with engineering changes mid-run, multi-level subcontracting, or job work under GST rules that generic products handle awkwardly.

The choice is the same one we set out in custom CRM versus off the shelf: implement a product if it fits most of the process, build custom where the process is the differentiator. For manufacturers the differentiator is usually planning and quality, so a hybrid of packaged finance plus custom operations modules is common.

Manufacturing ERP modules: what each one must do

The bill of materials is the centre of the system

Everything in a manufacturing ERP reads the BOM: planning explodes it to work out material needs, inventory consumes against it, costing rolls it up, quality attaches inspection plans to its steps. Get the BOM model wrong and every later module inherits the fault. The decisions that matter are whether BOMs are multi-level, how revisions are handled when a drawing changes mid-order, whether alternate components are allowed, and how scrap is expressed. Ask the production engineers, not the accountants; they know where the current spreadsheet lies.

Routings belong with the BOM. Each step names a work centre, standard time and any subcontractor. Without routings there is no capacity planning and no honest cost per unit.

Production planning ERP: from order to shop floor

Planning is the module that most often justifies a custom build. A packaged product's planning engine assumes a way of working; yours may be make-to-order with frequent engineering changes, or a mix of stock and order production with shared work centres. The custom version does three things well: converts confirmed orders and forecasts into production orders with dates, checks material availability against inventory and open purchase orders, and shows capacity by work centre so a planner can move work rather than discover the clash on Monday.

Resist the temptation to build finite scheduling optimisation in phase one. Most plants need a clear, trustworthy plan board and a fast way to reschedule. Optimisation can be added later, and demand forecasting can feed it once there is two years of clean order history to learn from.

The shop-floor interface

Operators will not use a desktop ERP screen. A tablet or a shared kiosk per work centre, showing the day's orders, letting an operator start, pause, complete and record quantities and rejections, is what makes production data real. Barcode scanning of job cards and batches removes the last spreadsheet, and gives quality and costing the timestamps they need.

Inventory ERP: batches, bins and valuation

Inventory is where most manufacturers feel the pain first and where a first phase usually starts. The custom build must handle multiple stores and units, batch and serial tracking where customers demand traceability, bin locations for a fast-moving raw-material store, cycle counting so year-end stock takes stop being a crisis, and a valuation method finance agrees with. Consumption should post automatically from production orders against the BOM, with variances flagged rather than silently absorbed.

Procurement follows immediately, because purchase orders and goods receipts are the main inbound movements. Indents from planning, quotes, purchase orders, receipt with a quality hold, and vendor performance close the loop. Job work and subcontracting need their own challan flow with GST-compliant documents, which packaged products from outside India often lack.

Quality and GST finance: the modules that keep you compliant

Quality is often left to paper because it is seen as a cost centre. In a custom ERP it is cheap to build because it attaches to objects that already exist: inspection plans on BOM steps and item receipts, results recorded on the shop-floor interface, non-conformance raised against a batch, rework orders created from it. Certificates of analysis for customers are then a report, not a scramble.

Finance in India means GST. E-invoice generation through the Invoice Registration Portal, e-way bills for despatches, and clean data for returns are not optional features, and we cover the integration in GST and e-invoicing in custom business software. Many manufacturers keep their existing accounting package for statutory books and integrate the ERP with it, which is a sensible phase-one choice.

Phasing: which module first

We phase in the order item master and BOM, then inventory and procurement, then production planning with the shop-floor interface, then quality, then costing and finance integration. Each phase goes live on its own, with data migrated for that module and the team trained for it. The method is described in phased ERP delivery. Never attempt a single go-live of all six modules; the data will not be ready and neither will the people.

A worked example

A components manufacturer with two units and a growing export book ran finance on a packaged accounting product and everything else on spreadsheets and printed job cards. A customer audit asked for batch traceability from raw material to shipped part, which the spreadsheets could not give. Phase one built the item master, multi-level BOM and inventory with batch tracking, going live in one unit's raw-material store first. Phase two added procurement with quality hold on receipt. Phase three put a tablet at each work centre for production orders and inspection results. The accounting package stayed for statutory books, integrated for invoices and GRNs. Traceability reports for the audit came from the system rather than from a week of reconstruction, and planners stopped maintaining the whiteboard.

Team and timeline

A manufacturing ERP build needs a product lead who has stood on a shop floor, two to three engineers, a designer for the shop-floor and planning screens, and, on the client side, a plant head or production manager who owns decisions and a finance person for costing and GST. Master data cleansing is the client's work, with our templates, and it starts on day one.

We begin with a Sprint Zero at $3,250 / ₹2,00,000 to map processes and fix the phase plan, credited to the build. ERP and CRM development then starts at $28,000 / ₹18.4L per phase; a full six-module build across several phases is priced up front and delivered at fixed price per phase, with the pricing page listing the Care Plans that support it after go-live. Clients own the code and data throughout.

Before you start: a checklist

• Confirm the item master is clean: one code per item, agreed units of measure
• Choose the first plant and first store for go-live
• Decide whether finance stays in the existing package or moves into the ERP
• Document BOM levels, revision rules and scrap handling with production engineers
• List customers who require batch or serial traceability
• Agree the shop-floor device strategy: tablets, kiosks or scanners
• Name a process owner per module who can make decisions weekly
• Plan the parallel run and reconciliation for the first module

Glossary

• BOM: bill of materials, the structured list of components and quantities for a product
• Routing: the sequence of operations, work centres and standard times to make an item
• MRP: material requirements planning, exploding demand through the BOM to purchase and production needs
• GRN: goods receipt note, recorded when purchased items arrive
• Job work: sending materials to a subcontractor for processing, with GST challan requirements
• Non-conformance: a recorded quality failure against a batch or order

Related reading

See AI in ERP: where automation removes real work, custom enterprise software, and the dispatch platform for a logistics operator for a related operations build. For e-invoicing rules the primary source is the GST e-invoice portal.

Build the BOM first, phase the rest, and let the plant's real process decide what is custom and what is packaged.