Manufacturing ERP Selection Checklist for Indian SMEs

Manufacturing ERP Selection Checklist for Indian SMEs

A practical manufacturing ERP selection checklist for Indian SMEs should test five things first: production fit, inventory control, accounting and GST workflows, implementation effort, and vendor support. The right manufacturing ERP is not the one with the longest feature list; it is the one your team can use accurately every day without creating more work than it removes.

For a small or mid-sized manufacturer, ERP selection is an operational decision, not only an IT purchase. A system affects purchasing, stores, production planning, quality checks, dispatch, invoicing, finance and management reporting. Choosing poorly can lead to incomplete data, workarounds in spreadsheets, delayed implementation and recurring support problems.

This checklist is designed for Indian SMEs evaluating ERP software for discrete manufacturing, process manufacturing, job work, assembly, fabrication, packaging, engineering products or related operations.

1. Define the Manufacturing Problem Before Comparing ERP Products

Many ERP purchases start with a product demonstration. A salesperson shows dashboards, mobile apps and menus, and the business begins comparing screens. This is usually too early.

Start by documenting how work currently moves through the business. Include the actual process, not only the process described in an internal procedure document.

Map the current workflow

Write down the steps from customer enquiry to payment collection:

1. Enquiry or sales order
2. Production feasibility check
3. Bill of materials confirmation
4. Material availability review
5. Purchase or subcontracting
6. Production planning
7. Material issue to the shop floor
8. In-process quality checks
9. Finished goods receipt
10. Packing and dispatch
11. Sales invoice and e-way bill
12. Payment follow-up
13. Cost and profitability review

Then map the purchasing, stores and finance processes separately. Note where staff use paper registers, Excel files, WhatsApp messages, Tally or other disconnected systems.

The purpose is not to eliminate every existing tool immediately. It is to identify where duplicate entry, missing information or delayed decisions are affecting the business.

Identify the decision you want the ERP to improve

An ERP project should solve specific operational problems. Examples include:

• The business cannot confirm whether a new order can be produced on time.
• Raw material stock in the system does not match physical stock.
• Production supervisors do not have current job priorities.
• Management cannot calculate product-wise or order-wise cost reliably.
• Purchase teams reorder materials without considering open purchase orders.
• Rejections and rework are recorded inconsistently.
• GST invoices, e-invoices or e-way bills require repeated manual entry.
• Subcontracting material sent outside is difficult to track.
• Receivables and dispatch information are not connected.

Rank these problems. If the main issue is inventory accuracy, a sophisticated production-planning module may not help until item masters, units of measure and stores processes are cleaned up.

Separate must-have features from preferences

Create three categories:

• Mandatory: The business cannot operate effectively without it.
• Important: It provides meaningful value but can be introduced after the first phase.
• Optional: It is useful but should not decide the purchase.

For example, batch tracking may be mandatory for a food or chemical manufacturer, while a customer portal may be optional. Multi-level bills of materials may be mandatory for an engineering assembly business but unnecessary for a simple trading operation.

This prevents the selection committee from choosing an ERP based on attractive but low-priority features.

2. Use This Manufacturing ERP Selection Checklist

The following checklist can be used during product demonstrations, vendor meetings and reference calls. Ask the vendor to demonstrate your process using your own sample data, not only a prepared example.

Business and company structure

Check whether the ERP can support:

• One company or multiple legal entities
• Multiple plants, branches or warehouses
• Different stock locations within a plant
• Inter-branch transfers
• Separate books of accounts where required
• Approval levels based on role, department or value
• Multiple users with controlled access
• Indian date, currency, tax and invoice requirements
• Marathi, Hindi or other local-language needs where relevant to the shop floor

Do not assume that “multi-company” means the system will handle your actual structure correctly. Ask how reports, stock transfers, taxation, user permissions and consolidated management information work across locations.

Item master and inventory

The item master is the foundation of a manufacturing ERP. Check whether it supports:

• Raw materials, consumables, semi-finished goods and finished goods
• Item codes and alternate codes
• Multiple units of measure and conversion rules
• Batch numbers, serial numbers or heat numbers
• Expiry dates where applicable
• Minimum, maximum and reorder levels
• Multiple grades, sizes, colours or specifications
• Drawing numbers and revision control
• Approved substitutes
• Location-wise stock
• Stock reserved for specific orders
• Stock under inspection, rejected or blocked
• Opening stock upload from existing records

Ask how the system prevents duplicate item creation. A business may have “MS Sheet 2 mm,” “Mild Steel Sheet 2MM” and “MS2” treated as three different materials. ERP software cannot correct poor master data automatically.

Bill of materials and routing

For manufacturing, a bill of materials is only part of the product definition. Check support for:

• Single-level and multi-level bills of materials
• Quantity, scrap and yield assumptions
• By-products and co-products
• Alternate bills of materials
• Effective dates
• Version and revision control
• Operation-wise routing
• Machine, labour and subcontracting operations
• Setup and run time
• Tooling or consumable requirements
• Work-in-progress tracking
• Material substitution with approval
• Engineering change control

Ask the vendor to demonstrate a product that has a sub-assembly, a revised drawing and a process step performed by a subcontractor. This will reveal more than a basic finished-goods example.

Planning and production control

A manufacturing ERP should help the team decide what to make, when to make it and what is needed. Evaluate:

• Sales-order-driven production
• Make-to-stock and make-to-order workflows
• Material requirements planning
• Production forecasts
• Production plans and work orders
• Capacity planning
• Machine and work-centre calendars
• Material availability checks
• Shortage reports
• Work-order priority changes
• Partial production and split batches
• Rework and repair orders
• Production against a sample or prototype
• Shop-floor reporting through desktop, tablet or mobile devices

Ask whether planning is genuinely automated or whether users must manually prepare spreadsheets after reading ERP reports. Some systems call a basic reorder report “MRP”; your team should understand the actual capability.

Purchasing and supplier management

Purchasing controls both cost and production continuity. Check support for:

• Purchase requisitions
• Vendor quotations and comparisons
• Purchase orders
• Rate contracts
• Approved supplier lists
• Material receipt and inspection
• Partial receipts
• Purchase returns
• Landed cost allocation
• Supplier lead times
• Supplier performance
• Job-work or subcontract purchase orders
• GST details on supplier records
• TDS or other applicable accounting workflows

The ERP should show open purchase orders, expected delivery dates, received quantities and pending quantities together. Without this visibility, buyers may place duplicate orders or fail to follow up on urgent material.

Quality management

Quality requirements vary significantly by industry, so this area needs detailed discussion. Check for:

• Incoming inspection
• In-process inspection
• Final inspection
• Inspection plans
• Sampling rules
• Measured and pass/fail parameters
• Non-conformance records
• Rejection and rework
• Corrective and preventive actions
• Supplier quality records
• Certificates of analysis or conformity
• Batch traceability
• Customer complaint tracking
• Calibration reminders for instruments

Ask if quality records can be linked to the material batch, work order, operator, machine and customer dispatch. A separate spreadsheet may be acceptable for a small operation initially, but it should not be treated as a permanent substitute for traceability where customers or regulations require it.

Sales, dispatch and after-sales

Check whether the ERP connects sales with production and inventory. It should support, as relevant:

• Quotations and sales orders
• Customer-specific pricing
• Delivery schedules
• Credit limits
• Partial dispatches
• Packing lists
• Dispatch documents
• Transporter and vehicle information
• E-invoice integration where applicable
• E-way bill workflows where applicable
• Export documentation if the company exports
• Returns and replacement
• Warranty or service records

Indian tax and e-invoicing requirements can change based on turnover, transaction type and government notifications. The vendor should explain how updates are handled and who is responsible for configuration and compliance review. Software support does not replace advice from the company’s chartered accountant or tax professional.

3. Compare ERP Options on Practical Fit

An SME may evaluate a local ERP provider, an India-focused product, a large international platform, a custom-built system or a combination of tools. Each option has trade-offs.

The category matters less than how the product handles your processes. A local application can be a good choice if it has reliable support and sufficient controls. A globally known product can still fail if the implementation partner does not understand Indian manufacturing operations.

Ask for a process-based demonstration

Prepare five to ten real scenarios, such as:

• A customer orders a product with a revised specification.
• One raw material is available in two grades, but only one is approved.
• A work order needs partial completion and rework.
• A component is sent to a job worker and later returned.
• The finished batch fails inspection and must be held.
• A dispatch requires a partial invoice and an e-way bill.
• Management needs order-wise material, labour and subcontracting cost.

Ask the vendor to complete these scenarios live. Note how many screens are required, which fields are mandatory, and what happens when the transaction does not follow the “happy path”.

Do not accept “this can be customised” as a complete answer. Ask whether the feature is already available, configurable, requires development, or needs a third-party integration. These have different costs, risks and maintenance implications.

Review integration requirements

Common integrations for Indian SMEs include:

• Tally or other accounting software
• Payment gateways or bank feeds
• GST and e-invoice systems
• E-commerce platforms
• Shopify, WooCommerce or marketplace channels for D2C operations
• Barcode scanners and label printers
• Weighing scales
• CRM systems
• Payroll or attendance systems
• CAD, product lifecycle or document systems
• Shipping and logistics platforms

For every integration, ask which system is the source of truth. If the same customer, item or invoice can be edited in two systems, errors become difficult to trace.

4. Check Indian Compliance and Controls

An ERP for India should support compliance without turning the finance team into a manual data-entry department. The exact setup depends on the business structure, states of operation, products and tax advice.

GST and invoicing

Check support for:

• CGST, SGST, IGST and applicable cess
• Intra-state and inter-state transactions
• Place-of-supply logic
• HSN or SAC details
• Tax-inclusive and tax-exclusive pricing
• Credit notes and debit notes
• Export or zero-rated transactions where relevant
• GST reports and data export for filing processes
• E-invoice generation where applicable
• E-way bill information where applicable
• Reverse-charge workflows where applicable

Ask how the ERP handles changes in GST rates or tax rules. Do not rely on a promise that updates are “automatic” without understanding who tests them, when they are released and how prior transactions are protected.

Audit trail and approvals

An ERP should provide suitable controls over sensitive transactions, including:

• Changes to item masters
• Changes to bills of materials
• Changes to purchase rates
• Sales price overrides
• Stock adjustments
• Backdated entries
• Invoice cancellation
• Credit notes
• User access changes
• Approval history

Ask whether the audit trail records the user, date, time, old value and new value. Also check whether administrators can delete or alter records without leaving an audit record.

Data protection and security

Indian businesses should review how the vendor protects personal and business data. Consider:

• Role-based access
• Two-factor authentication
• Encryption in transit and at rest
• Secure backups
• Disaster recovery
• Data retention
• Vendor and subcontractor access
• Data export on termination
• Incident notification
• Log monitoring
• Compliance responsibilities under applicable Indian data protection requirements

The Digital Personal Data Protection framework may be relevant where the ERP processes personal data, such as employee, customer or supplier contact information. Your legal or compliance adviser can determine the exact obligations for your organisation.

5. Evaluate Implementation, Migration and User Adoption

ERP software does not create accurate information merely because it has been installed. Implementation is where processes, data, permissions and user habits are brought together.

Build an implementation plan

The vendor should provide a written plan covering:

• Business process workshops
• Configuration
• Customisation, if any
• Data preparation
• Data migration
• Integration development
• User acceptance testing
• Training
• Go-live support
• Issue resolution
• Post-go-live review

The plan should identify responsibilities on both sides. Your company will need internal owners for finance, stores, production, purchase, sales and management. A vendor cannot make all process decisions for you.

Treat master data as a project

Prepare and clean:

• Item masters
• Units of measure
• Opening stock
• Warehouses and locations
• Bills of materials
• Routings
• Customers and suppliers
• Tax details
• Price lists
• Outstanding receivables and payables
• Open purchase and sales orders
• Machines and work centres
• User roles

Decide what historical data should be migrated. Migrating every old transaction may not be necessary and can delay the project. Many SMEs migrate opening balances and selected current records, then retain older information in a controlled archive.

Plan for user adoption

Different users need different training. A storekeeper needs to receive, issue and transfer stock. A production supervisor needs to create or update work orders. An accountant needs to validate tax and ledger postings. Management needs reports and exception alerts.

Training should use your item codes, production routes and invoice formats. Generic training is easier to deliver but less useful on the shop floor.

Create simple operating rules:

• When must a receipt be entered?
• Who can adjust stock?
• When is a work order closed?
• How are rejected materials handled?
• Who approves a BOM change?
• How quickly must production be reported?
• Which report is used for daily review?

If these rules are unclear, employees will create their own workarounds.

Choose between phased and full rollout

A phased rollout may begin with finance, purchasing, inventory and basic sales, followed by production planning, quality and advanced costing. This can reduce the initial change load but may leave gaps between departments.

A full rollout connects more functions earlier but requires stronger preparation and internal availability. There is no universal right answer. The choice depends on process maturity, number of sites, data quality, team capacity and the complexity of the manufacturing operation.

6. Check Cost, Contract and Vendor Support

Do not compare ERP proposals only by the initial licence amount. Consider the total cost of ownership over the period you expect to use the system.

Potential cost components include:

• Licence or subscription
• Number of users
• Number of plants or companies
• Implementation and configuration
• Data migration
• Custom development
• Integrations
• Hardware, scanners and printers
• Hosting
• Training
• Support
• Travel and onsite assistance
• Future upgrades
• Additional storage
• Backup or disaster recovery services
• Exit and data extraction

Cloud subscriptions are often easier for SMEs to start with because they reduce the need to maintain a local server. However, recurring payments, internet dependence, user growth and storage limits should be understood before signing.

For on-premise software, clarify responsibility for servers, operating systems, antivirus, backups, database maintenance, security patches and remote support.

Read the commercial terms carefully

Ask these questions:

• Is GST charged separately?
• What is included in implementation?
• How are additional change requests priced?
• Are support hours or tickets limited?
• What is the support response process?
• Are updates included?
• Can the vendor increase subscription rates?
• What happens if the project is delayed?
• Who owns custom code and documentation?
• Can the business export all data in a usable format?
• What happens when the contract ends?
• Is there a transition or handover process?

Govindani Infotech’s own pricing is confirmed by the team on WhatsApp after understanding the project scope, integrations and implementation needs. For any vendor, request a written proposal that separates software, implementation, customisation, support and taxes.

Assess the implementation partner, not just the product

The partner’s experience can be as important as the software. Ask:

• How many manufacturing implementations has the team handled?
• Which industries and production models do they understand?
• Who will conduct the workshops?
• Who will configure and test the system?
• Is the implementation team the same team that demonstrated the product?
• How are bugs distinguished from change requests?
• Is onsite support available in Pune or your operating region if required?
• Can the vendor provide relevant customer references?

Reference calls should focus on operational realities. Ask the customer how long it took to become comfortable, which processes required workarounds, how support tickets are handled and whether reports are trusted by management.

7. Run a Structured ERP Selection and Pilot

A disciplined selection process reduces the chance of choosing the most persuasive presenter rather than the best fit.

Score vendors consistently

Create a scorecard with weighted categories such as:

• Manufacturing process fit
• Inventory and traceability
• GST and finance
• Ease of use
• Reporting
• Integration capability
• Security and controls
• Implementation approach
• Support quality
• Total cost
• Vendor stability

Use a scoring scale agreed by the selection team. Record evidence for each score. “Looks easy” is not sufficient evidence; note the process demonstrated, number of steps and unresolved limitations.

Test with realistic data

A pilot or proof of concept should use a limited but representative process. For example:

• A few raw materials
• One multi-level finished product
• One subcontracting operation
• One quality inspection
• One partial dispatch
• One purchase return
• One rework transaction
• One GST invoice workflow

The pilot should answer practical questions:

• Can a new user complete the process?
• Does the stock ledger remain correct?
• Can finance reconcile the output?
• Are reports available without exporting everything to Excel?
• Can the system handle an exception?
• Does the process work at the shop floor?
• Is the response acceptable on your internet connection?

Do not make a pilot unnecessarily broad. The aim is to validate the highest-risk processes, not to implement the entire ERP before selection.

Keep an exit option

Before committing to a long contract, agree on acceptance criteria and a process for unresolved gaps. An ERP cannot be expected to meet every preference, but mandatory requirements should be clearly documented.

Keep independent copies of business data during implementation. Confirm how backups and exports work before the system becomes the only place where operational information exists.

Frequently Asked Questions

What is the most important feature in a manufacturing ERP for an Indian SME?

There is no single feature that suits every manufacturer. Accurate item masters, inventory transactions, bills of materials, production reporting and finance integration are usually the foundation. The priority should match the business problem: a job-work manufacturer may prioritise material traceability, while a make-to-order engineering company may need stronger production planning and costing.

Should a small manufacturer replace Tally when implementing an ERP?

Not necessarily. Some businesses keep Tally for accounting and connect it to a manufacturing ERP, while others move finance into one integrated system. The decision depends on transaction volume, existing accounting controls, reporting needs, GST workflows and the quality of the proposed integration. Avoid maintaining the same invoice, stock or ledger data manually in both systems.

Is cloud ERP suitable for manufacturing companies in India?

Cloud ERP can suit Indian SMEs when the factory has dependable internet access and the vendor provides appropriate offline or recovery procedures. It allows authorised staff to access information from offices, warehouses and other locations without maintaining a local server. Verify data export, backups, security, downtime handling, subscription terms and support before selecting it.

How long does manufacturing ERP implementation take?

Implementation duration depends on the number of locations, process complexity, data quality, customisation, integrations and the availability of your internal team. A basic inventory and finance setup may require less work than a multi-stage production, quality, subcontracting and costing implementation. Ask for a phase-wise plan rather than accepting an unqualified timeline.

Can ERP software calculate accurate product costing?

It can support costing, but the result depends on the quality of bills of materials, routing times, material rates, labour assumptions, subcontracting charges, overhead rules and production reporting. If scrap, rework or machine time is not recorded consistently, the calculated cost may be misleading. Test actual and standard costing with a representative product before relying on management reports.

What should an SME do if employees continue using spreadsheets after ERP go-live?

First identify why they use spreadsheets. The ERP may lack a required report, be slow, have unclear permissions or require too many entries. Fix the process or provide an approved export rather than banning spreadsheets without understanding the reason. At the same time, define which records must be maintained in the ERP so that stock, production and financial information does not split across unofficial files.

Where to Start

Form a small selection team with representatives from production, stores, purchase, finance and management. Document five current workflows, list mandatory requirements, clean a sample of your master data and invite vendors to demonstrate those exact scenarios.

Use a weighted scorecard, test integrations and review support and data-export terms before signing. Start with the operational problem that is costing the business the most, and choose a rollout that your team can support consistently.

If you want help assessing ERP requirements, integrations or a custom manufacturing system, talk to the Govindani Infotech team on WhatsApp.