How to choose a manufacturing ERP for an Indian SME
By Graeon.ai · Updated
Choose a manufacturing ERP by testing it against your own document flow, not a feature list. Walk one real order from enquiry to invoice in the demo, check that GST, e-invoices and e-way bills come straight from the document, decide whether Tally stays your books, and make sure the shop floor can enter data from a phone. Then ask how the system is configured for you and how your data is kept separate and backed up.
1. Start from your document flow
Write down how one order moves through your company today: enquiry, quotation, order, purchase, goods receipt, production, packing, dispatch, invoice and payment. Note who touches each step and where it is typed twice. This list, not a vendor's module chart, is what the ERP has to fit.
2. GST and e-invoicing
- GST should be calculated on every line from the item's tax setup, with CGST + SGST or IGST decided from the two states
- e-Invoices and e-way bills should be generated from the invoice or dispatch document, not re-keyed on the portal
- If you have several GSTINs, check that each branch keeps its own registration and credentials
- Ask what the system does for returns. Reports and reconciliation are common; filing usually stays with your accountant
3. Decide what happens to Tally
Many Indian manufacturers keep Tally as their books. If you want to, ask exactly which documents move to Tally and back, what happens when a voucher is sent twice, and how stock in Tally and in the ERP is compared. If your group runs a larger ERP such as Oracle, ask whether it can stay the system of record with the new system on top.
4. The shop floor and the field
- Can production, packing and dispatch be entered from a phone, without a computer on the floor?
- How quickly do those entries reach stock and reports?
- Can the sales team see order and dispatch status on their phone?
- Is there a mobile app your staff will actually open, ideally under your own name?
5. Configured or customised?
Every factory works differently, so the ERP has to bend. The question is how. Settings, fields and approvals changed from screens are easier to live with than separate code written for one customer, which has to be maintained through every upgrade. Ask to see a field or approval being changed in the demo.
6. Data safety
- Is your data kept separate from other customers' data?
- How often is it backed up, and when was a restore last tested?
- Who can see what: access by role, approvals and an audit trail of changes
7. Questions to ask in the demo
- Walk one of our real orders from enquiry to invoice, with our item names
- Show an e-invoice and an e-way bill being generated from the document
- Send a voucher to Tally twice and show what happens
- Make a production entry on a phone and show the stock change
- Change a form field or an approval step without a developer
- Show how our existing items and parties will be imported
Where Graeon fits
Graeon ERP covers sales, purchase, stores, production and dispatch for Indian manufacturers. It generates e-invoices and e-way bills from the document with credentials held per GSTIN, works alongside TallyPrime through its own Tally add-on or alongside Oracle ERP as the system of record, and takes production and dispatch entries from the phone. Each company is configured from screens through hundreds of per-company settings, and each client's data sits in its own database schema with nightly backups.