Shree Mahadev Tex Fab
TechUltra moved Shree Mahadev Tex Fab — an Indian textile manufacturer producing cotton and trouser fabrics for top apparel brands — off Tally and onto Odoo with native customizations for textile-mill operations.
- Duration
- 16 weeks
- Team size
- 5 (3 TechUltra + 2 client)
- Odoo version
- Odoo 17 Enterprise
- Services used
-
- Odoo Implementation
- Odoo Customization
- Odoo Migration
2008
Founding year
17+ years in Indian textiles, top-apparel-brand supplier
Tally → Odoo
Accounting platform
Replaced standalone Tally with integrated ERP
6
Modules in production
Sales, Purchase, Inventory, Manufacturing, Accounting, Quality
1
Source of truth
Stock checks, reports, and accounting unified
The challenge
Shree Mahadev Tex Fab, established in 2008, has become a leading player in the Indian textile market — known for high-quality cotton collections used by top apparel brands and a specialised trouser-fabric range. As the business scaled, four constraints in their existing software stack started costing them real money:
- Interoperability. Stock-checks, sales, and accounting were on disconnected systems. Reconciliation needed manual stock checks and produced inconsistent reports — increasing the risk of errors and missed shipments to apparel-brand customers.
- Cost. Multiple licenses for separate applications drove ongoing subscription overhead.
- Reporting. Isolated systems made it difficult to produce accurate sales-, inventory-, and accounting-period reports — especially the cross-cut analyses (e.g. profitability per fabric grade) that buying decisions depend on.
- Customization limitations. The previous Tally-led setup offered minimal customization, so adapting features to specific textile-mill workflows (lot tracking, dye-batch tracking, loom-output recording) was off the table.
The team partnered with TechUltra Solutions — an Odoo Gold Partner — to consolidate onto one ERP that could be customized to how a textile mill actually runs.
Our solution
TechUltra delivered an Odoo 17 Enterprise implementation in 16 weeks, with the standard six-module footprint customized for textile-manufacturing realities.
Sales + Purchase. Order-to-cash and procure-to-pay were configured for the textile workflow: yarn purchases tracked by lot and origin; finished-fabric sales tied to specific production runs so quality-claims can trace back to the loom that produced the fabric.
Inventory. Multi-location inventory (raw yarn warehouse, weaving floor, finishing, finished-goods) with lot tracking end-to-end. Stock movements during weaving/finishing are recorded against the work order so floor-team reports balance against accounting.
Manufacturing. Bills of Materials, work orders, and operations were modelled to mirror how the loom shop and finishing department actually operate. Yield variances are visible at the work-order level rather than rolled up into a monthly KPI.
Accounting (replaces Tally). Migrated from Tally with a re-designed chart-of-accounts and a clean cutover at fiscal-year boundary. GST returns and vendor reconciliations now run from the same platform that holds the inventory and production data — eliminating the data-entry layer between operations and finance.
Quality. Inline quality checks at receiving (yarn) and at finished-goods dispatch. Non-conformance reports + corrective-action workflows feed back into manufacturing so recurring quality issues stop recurring.
Customizations. Textile-mill-specific extensions where Odoo standard didn’t reach — lot-level dye-batch tracking, loom-shift productivity reporting, and a custom trouser-fabric grade catalogue used in both sales quotes and production planning.
The results
Single ERP for the mill. Sales, purchase, inventory, manufacturing, accounting, and quality run on one platform. The team is no longer reconciling between Tally and a parallel inventory ledger; the books and the floor reports come from the same database.
Customizations matched to textile reality. Workflow features that the legacy stack literally couldn’t deliver — dye-batch traceability, loom-shift productivity, lot-level finished-fabric tracking — are standard operating practice now.
Cost consolidation. Multiple software licenses are retired in favour of one Odoo Enterprise subscription. The line-item cost dropped, and the vendor-management overhead dropped further (one partner, one contract, one upgrade path).
Better buying + production decisions. Cross-cut reports that used to take a day to assemble are produced from the dashboard. Profitability per fabric grade, yield by loom, and reject rates by yarn supplier all live on the same Odoo BI layer.
For other textile manufacturers running on Tally + spreadsheets, this engagement maps onto the standard Odoo Implementation playbook with the textile-mill customization pack added on top.
Frequently asked questions
-
How long does an Odoo implementation take for a textile manufacturer?
Shree Mahadev Tex Fab went live in 16 weeks across six modules including Manufacturing and Quality. Manufacturing implementations run longer than distribution ones because bills of materials and routings have to be captured before anything can be tested.
-
Can Odoo replace an existing accounting package?
Shree Mahadev moved off its previous accounting platform onto Odoo 17 Enterprise. Replacing accounting is the part of a migration that has to be reconciled before cutover rather than after — the opening balances need to agree with the old system to the rupee.
-
Does Odoo handle quality control in manufacturing?
Shree Mahadev runs Odoo's Quality module alongside Manufacturing, so quality checks are recorded against production orders rather than kept in a separate spreadsheet.
-
What does 'one source of truth' mean in practice?
Sales, Purchase, Inventory, Manufacturing, Accounting and Quality on one instance, so stock, costs and orders are read from the same records. Before the move, those answers lived in more than one place and did not always agree.