A 25-person fabrication unit in an MIDC area does not need the ERP a 2,000-person company runs. It needs to know what stock is in the godown, which job is on which machine, what the customer was quoted, and whether the GST invoice went out. This guide is about that kind of ERP: what it should contain, what to buy versus build, and how to roll it out without stopping production.
What an MSME actually needs
Most small manufacturers we talk to are running on some mix of Tally, Excel, a register at the gate and the owner's memory. The ERP's job is to replace the Excel and the memory, not Tally. The core is usually this:
- Inventory: raw material, work in progress and finished goods, by godown and often by batch or heat number. Minimum levels and alerts.
- Purchase: indents from the shop floor, purchase orders, goods receipt with quality check, supplier bills and rate history.
- Production and job cards: bill of materials, job cards per order, which operator and machine, quantities produced and rejected, time taken.
- Sales and GST invoicing: quotations, sales orders, delivery challans, e-invoices and e-way bills with correct HSN codes, credit notes.
- Payroll and attendance: shifts, overtime, contract labour, PF and ESI, and a salary sheet that matches the attendance register.
- Accounts: usually kept in Tally, with the ERP pushing invoices and receipts to it rather than replacing it.
- Reports: stock on hand, pending orders, jobs behind schedule, outstanding receivables, daily production, ideally delivered on WhatsApp every morning.
What an MSME usually does not need on day one: finite capacity scheduling, multi-currency, multi-company consolidation, or a shop-floor kiosk on every machine. These can come later if the business grows into them. Paying for them at the start is the most common way to overspend.
Signs you have outgrown Excel and Tally
- Stock counts at the year end never match what the sheet says, and nobody knows which is right.
- A customer asks where their order is and it takes three phone calls to find out.
- Quotations are made from memory of the last price, not from actual material and labour cost.
- The owner cannot leave for a week without the factory's information leaving with them.
- Two people maintain two versions of the same Excel, and both are wrong in different places.
If three of these sound familiar, the problem is not the people. It is that the tools were never built to hold production data.
Mapping departments to modules
| Department | Modules it lives in | First reports it needs |
|---|---|---|
| Stores and godown | Inventory, purchase receipts | Stock on hand, below minimum, slow-moving items |
| Purchase | Purchase orders, supplier master | Pending POs, rate comparison, supplier delays |
| Production | Job cards, bill of materials, WIP | Jobs in progress, rejections, output per shift |
| Sales and dispatch | Quotations, orders, challans, GST invoicing | Pending orders, dispatched today, overdue deliveries |
| Accounts | Tally sync, receivables, payables | Outstanding by customer, GST summary |
| HR and admin | Attendance, payroll | Attendance summary, salary sheet, overtime |
| Owner | All of the above, read-only | One WhatsApp message a day with cash, stock, orders and jobs |
The owner's row matters most. If the system cannot answer the owner's daily questions in one glance, it will not be used, and an unused ERP is expensive furniture.
Ready-made products versus custom
Tally and Busy do accounting and GST compliance well and are used by almost every accountant in the country. Cloud products such as Zoho and various industry-specific ERPs cover a lot of ground for a monthly subscription. Custom software makes sense where your process is the product: the way you plan jobs, track heat numbers, cost a die or handle rework is what customers pay you for.
| Option | Fits when | Watch out for |
|---|---|---|
| Tally or Busy alone | Trading businesses, simple manufacturing, accountant-driven | Production and job tracking end up back in Excel |
| Cloud subscription ERP | Standard processes, small team, want to start in weeks | Per-user fees grow; workflows that do not match your floor |
| Industry-specific ERP | Your industry has a mature product (textiles, pharma, foundry) | Customisation limits; vendor may be far away |
| Custom ERP with Tally sync | Unusual process, many users, long horizon | Higher upfront cost; needs a clear scope and a committed owner |
The hybrid we see work most often for manufacturers is custom software for inventory, purchase, production and sales, with accounting left in Tally and synced. We compare the buy-versus-build trade-offs in more detail in custom ERP vs off-the-shelf, and the related decision on stock systems in inventory management systems.
Roll it out in phases
Trying to switch every department on the same Monday is how ERP projects die. A phased rollout is slower on paper and much faster in practice.
- Phase one: item master, inventory and purchase. Six to ten weeks. Clean the item list, set units and minimum levels, start recording receipts and issues. This alone removes most stock surprises.
- Phase two: production and job cards. Bill of materials, job cards per order, production entry per shift. Supervisors start logging here.
- Phase three: sales, dispatch and GST invoicing. Quotations to e-invoice, with Tally sync for accounts.
- Phase four: payroll, attendance and management reports. Once the transactional data is reliable, the reports are worth reading.
Each phase ends with training on the floor, in Marathi or Hindi if that is what the team speaks, and a couple of weeks of running before the next phase starts. Plan on three to nine months for the whole thing, depending on size.
What goes wrong in ERP projects
- A dirty item master. The same bolt entered five ways means stock reports are fiction. Cleaning the master is unglamorous and non-negotiable.
- Nobody asked the shop floor. If supervisors were not in the requirements meetings, they will not use job cards, and production data will be entered from memory on Friday.
- The owner as the only user. An ERP works when data is entered where work happens, by the person doing it.
- Running old and new in parallel forever. Two months of parallel running is prudent; twelve means the new system never became the truth.
- Over-scoping. Every feature anyone mentioned in a meeting ends up in phase one.
- No source code or data access. If the vendor disappears, you should still be able to run and extend the system.
- Training treated as a demo. One two-hour session is not training. People need to enter real transactions with someone watching.
- No one owns it internally. A named person on your side who chases data quality and decisions makes more difference than any feature.
Cost and what to budget
As a rough guide, an MSME ERP built to order costs ₹3 to 12 lakh, delivered in phases, with the real figure depending on modules, users and integrations. On top of that budget for hosting (roughly ₹1,000 to ₹10,000 a month), e-invoice and e-way bill API charges, WhatsApp report delivery, and maintenance of about 15 to 20 percent of the build cost per year. Hardware such as barcode printers, handheld scanners for the godown and a couple of tablets or PCs on the floor is extra. For a broader view of costs, see custom software development cost in India.
If you already collect data in the ERP, automation and forecasting become possible later; our note on AI and automation in ERP covers what that looks like.
Where SailRight fits
We build phased, custom ERPs for small manufacturers and MSMEs, keeping Tally where it belongs and writing the inventory, purchase, production and sales modules around how your unit actually runs. Our custom software development page explains the approach, and you can contact us to walk through your departments and decide what phase one should contain.
- ERP
- MSME
- manufacturing
- Tally
- inventory
- GST