A dispatch clerk in Rajkot described his job to us as phone calls and guessing. He wasn't complaining about Tally. Tally was doing exactly what it's for. He just had no way to answer the one question customers rang him about, which was where their order had reached.
That gap is what this page is about. Tally runs your books. Excel and WhatsApp got recruited to run your floor, because nothing else was going to.
Should a manufacturer replace Tally with an ERP?
Where the Excel layer came from
Nobody sat down and decided to run a factory on spreadsheets. It accumulated. A production planner built a sheet because the register kept going missing. Stores built a second one because the first had no batch numbers. Sales built a third to quote from. Then someone made a WhatsApp group so the three could talk to each other.
Each of those was a sensible fix on the day it was made. Together they're a system nobody designed, with no single version of the truth and no way to ask it a question.
BMI Cables, a wire and cable plant in Bhiwadi, had accumulated more than 150 of these files before they moved. That number surprised them considerably more than it surprised us.
Those figures come from two named rollouts we've published in full: BMI Cables and Karm Machine Tools. Both of them kept Tally.
The Tally integration, specifically
Every Tally user asks this, so here's the direct answer rather than the word "seamless."
Facto syncs with Tally in both directions. Masters flow across. Transactions that belong in the books post to Tally instead of being re-keyed: invoices raised from dispatch, purchase entries against a GRN, payment receipts. What stays in Facto is everything that never belonged in Tally in the first place, meaning work orders, routings, machine time, quality checkpoints, material issued to the floor and dispatch status.
The practical test is whether anyone is typing the same number twice. After go-live, they shouldn't be.
The cost nobody puts in the comparison
Tally's licence is cheap, and that's genuinely an advantage. The cost of your current setup sits somewhere else and it never appears on an invoice.
It's the two days a month somebody spends reconciling what production says it made against what stores says it received. It's the order quoted off a costing sheet that was three weeks stale. It's the material bought twice because the first lot was sitting in a corner of the godown with nothing recorded against it.
None of that shows up in a cost comparison, which is why the current setup always looks cheaper than it is. We're not going to put a number on it for you, because the honest number depends on your plant. Counting the hours before you decide is worth doing, and our breakdown of what drives manufacturing software cost in India is a reasonable place to start.
We wanted real-time visibility on production and QC. Facto gave us a system our teams could actually use on the floor without complexity.Kumar Goyal, MD, BMI Cables
What the first eight weeks look like
Your Tally data stays where it is. Nothing gets migrated out of it.
Weeks one and two, we set up masters, items, BOMs and routings from what you already have, mostly out of your existing Excel files rather than from a blank form. Week three onwards, one module goes live on the floor. Usually production job tracking, because that's where the missing information is. Twelve modules at once is how these things die.
Our own engineers do this. There's no implementation partner, no separate statement of work, and no third party to blame if the floor doesn't use it. We've set out why that structure matters in whether SMEs really need an ERP implementation partner.
Tally keeps running throughout. Most plants keep their critical Excel sheets going in parallel for the first month too, and that's fine. They stop on their own.
For the wider question of when a plant genuinely outgrows this setup, Tally vs ERP for manufacturing covers the thresholds. This page is only about what sits on top of it.
