Back to Blog
Case Studies

From 3 Warehouses to 1 Dashboard: A Textile Manufacturer's ERP Journey

16 June 2026 13 min read Case Studies
From 3 Warehouses to 1 Dashboard: A Textile Manufacturer's ERP Journey
Case Studies

Company Background

Kapoor Textiles & Weaving Mills Pvt. Ltd. is a family-run textile manufacturing company based in Ludhiana, Punjab — one of India's largest centres for hosiery and knitwear production. Established in 1997 by the Kapoor family, the company has grown from a single power loom unit to a diversified operation spanning yarn dyeing, weaving, knitting, and fabric finishing. With an annual turnover of approximately INR 58 crore, Kapoor Textiles supplies fabric to garment manufacturers across North India and exports greige (unfinished) fabric to Bangladesh and Sri Lanka.

The company operates from three separate locations across Ludhiana:

  • Unit 1 (Focal Point): Yarn godown and dyeing unit — receives raw yarn from suppliers, dyes it in-house, and supplies dyed yarn to the other two units
  • Unit 2 (Industrial Area-A): Weaving unit with 48 rapier looms producing woven fabrics
  • Unit 3 (Gill Road): Knitting and finishing unit with 22 circular knitting machines and a fabric finishing line (calendering, sanforising, and packing)

In addition, Kapoor Textiles relies on 14 external job workers for specialised processes — embroidery, printing, bleaching, and mercerising — that they do not perform in-house. At any given time, fabric worth INR 1.5-2 crore is circulating across these 14 job worker locations.

Before the ERP implementation, each unit maintained its own inventory records. Unit 1 used Tally with a local inventory module. Unit 2 relied on a physical stock register updated daily by the store supervisor. Unit 3 used an Excel-based tracking system built by the finishing department head. Jobwork was tracked through handwritten challans and a quarterly manual reconciliation exercise.

The Challenge

From 3 Warehouses to 1 Dashboard: A Textile Manufacturer's ERP Journey

The fundamental problem at Kapoor Textiles was deceptively simple: nobody knew the complete inventory picture at any given moment. Each unit knew its own stock. Nobody knew the total.

This lack of unified visibility created cascading problems:

  • Duplicate ordering was routine — the purchasing team at Unit 1 would order yarn based on their local stock records, unaware that Unit 2 had surplus yarn of the same count sitting unused. The company estimated annual losses of INR 12-15 lakh from unnecessary purchases and subsequent excess inventory carrying costs
  • Inter-unit material transfers were invisible — when yarn was moved from Unit 1 to Unit 2, the sending unit deducted it from their records (eventually), but the receiving unit often took 2-3 days to add it to theirs. During this lag, the material was effectively unaccounted for
  • Jobwork reconciliation losses averaged INR 35 lakh annually — the quarterly manual reconciliation exercise consistently revealed variances of 3-5% between what was sent to job workers and what was returned. Some variance was legitimate (processing wastage), but a significant portion was attributed to pilferage, over-claimed wastage, and reconciliation errors in the paper-based system
  • Production planning was reactive — because the weaving and knitting units could not see yarn availability at Unit 1 in real time, they planned production based on physical visits to the yarn godown or phone calls. Orders were frequently delayed because production was planned against stock that had already been committed elsewhere
  • Fabric wastage across all processes averaged 8.5% — well above the industry benchmark of 5-6% for comparable operations. Without process-level wastage tracking, the company could not identify where the excess waste was occurring
  • Costing was approximate at best — because material costs, dyeing costs, weaving/knitting costs, finishing costs, and jobwork costs were tracked in different systems, the actual cost of producing a specific fabric variety was estimated rather than calculated. Pricing decisions were based on market rates and gut feel rather than cost data
  • Month-end inventory valuation took 8-10 days — the accounts team physically visited all three units, compiled stock data, reconciled against the respective systems, and then valued the inventory. The exercise regularly extended past the month-end closing deadline

"I would ask my production manager a simple question — how much 40-count dyed yarn do we have across all locations? He would need half a day to find out. In a business where yarn prices fluctuate daily and customer orders have 7-day delivery expectations, half a day is half a lifetime."

Sandeep Kapoor, Managing Partner, Kapoor Textiles

The Solution

Indivar Software Solutions implemented SAP Business One with the Jobwork Addon as a unified platform across all three units and the 14 job worker locations.

Phase 1: Unified Inventory Architecture (Weeks 1-8)

The foundation was a single SAP B1 instance serving all three units, accessed via a secure VPN connection between locations. The warehouse structure was designed to provide granular visibility:

  • Each physical unit became a warehouse group in SAP B1, with sub-warehouses for raw materials, work-in-progress, and finished goods within each unit
  • Each of the 14 job workers was assigned a virtual warehouse — when material is dispatched to a job worker, it transfers from the sending unit's warehouse to the job worker's virtual warehouse, maintaining complete visibility
  • Inter-unit transfers became documented SAP B1 inventory transfer transactions — with immediate reflection in both the sending and receiving warehouses
  • All transactions across all locations update the same central database in real time — eliminating the 2-3 day lag that existed with disconnected systems

Phase 2: Production and Wastage Tracking (Weeks 9-14)

Production orders were configured for every stage of the textile manufacturing process:

  • Dyeing: Raw yarn is issued against a production order specifying the colour, shade, and lot size. The system records input quantity, output quantity, and wastage — automatically calculating dye-lot-level wastage percentages
  • Weaving/Knitting: Dyed yarn is issued to weaving or knitting production orders. Output is measured in metres, and the system tracks metres produced per kg of yarn consumed — a critical efficiency metric for textile operations
  • Finishing: Greige fabric is issued to finishing production orders. Shrinkage during finishing (calendering, sanforising) is tracked per lot, building a historical database of process-level shrinkage factors

Standard wastage norms were configured per process based on historical data. Any production order where actual wastage exceeds the standard by more than 10% triggers an automatic alert to the production manager and the managing partner.

Phase 3: Jobwork Integration (Weeks 15-20)

The Indivar Jobwork Addon replaced the paper challan system entirely:

  • GST-compliant delivery challans generated from SAP B1 for every dispatch to a job worker, with item details (fabric type, metres, weight), expected return dates, and agreed processing charges
  • Receipt against challan with automatic variance calculation — the system compares issued quantity to returned quantity, flags excess wastage claims, and generates a reconciliation report per job worker per month
  • Ageing dashboard showing all open challans, their age, and overdue items. Automatic email alerts to job workers for challans approaching the GST one-year return deadline
  • Job worker performance scorecards ranking all 14 processors on processing time, wastage percentage, return punctuality, and quality rejection rate

Phase 4: Costing and MIS (Weeks 21-24)

With material, production, and jobwork data flowing through a single system, accurate product costing became possible for the first time:

  • Fabric-variety-level costing incorporating raw yarn cost, dyeing cost per kg, weaving/knitting cost per metre, finishing cost per metre, and jobwork charges — all calculated automatically from actual transaction data
  • Real-time margin analysis per fabric variety and per customer order
  • Dashboard showing inventory value across all three units and all job worker locations on a single screen — the "one dashboard" that the MD had been asking for

Results

Results were tracked over the first six months post go-live and compared against the same period in the previous year:

  • Complete inventory visibility achieved across all three units and 14 job worker locations — the MD's question about 40-count dyed yarn availability now takes 10 seconds to answer, not half a day
  • Duplicate ordering eliminated — estimated annual saving of INR 12-15 lakh from avoided unnecessary purchases and reduced excess inventory. Total inventory value reduced by 18% without any impact on production continuity
  • Jobwork reconciliation losses reduced from INR 35 lakh to INR 8 lakh annually — a 77% reduction. The remaining variance is within legitimate processing wastage norms. Real-time tracking and automatic variance alerts made pilferage and over-claimed wastage virtually impossible to conceal
  • Fabric wastage reduced from 8.5% to 6.6% — a 22% reduction achieved by identifying the specific processes and specific shifts where excess wastage was occurring. The dyeing unit accounted for 60% of the previous excess wastage, and targeted corrective actions brought it within norms
  • Production planning cycle reduced from 2 days to 4 hours — real-time yarn availability and loom/machine scheduling in SAP B1 enabled same-day production planning against confirmed orders
  • Month-end inventory valuation reduced from 8-10 days to 1 day — because all transactions are recorded in real time across all locations, the inventory valuation report is generated automatically. The accounts team now reviews and validates rather than compiles
  • Accurate product costing enabled strategic pricing decisions — the company discovered that three fabric varieties were being sold below actual cost (including jobwork charges that were previously not allocated to product cost). These products were repriced, improving overall margins by approximately 2.8 percentage points
  • Inter-unit material transfer lag reduced from 2-3 days to zero — real-time transactions mean that material is accounted for at both ends simultaneously

"The dashboard changed everything. I open SAP B1 on my phone in the morning and I know exactly what we have, where it is, and what it is worth — across all three units and every job worker. That used to require a full day and three phone calls. Now it takes 30 seconds."

Sandeep Kapoor, Managing Partner

Key Learnings

  • Multi-location visibility requires a single database. Syncing data between separate systems at separate locations will always have lag and reconciliation issues. A single SAP B1 instance accessible from all locations via VPN is the only architecture that delivers true real-time visibility
  • Jobwork tracking must be continuous, not periodic. Quarterly reconciliation is a post-mortem — it tells you what you lost, not how to prevent losses. Real-time challan tracking through the Jobwork Addon prevents losses as they occur
  • Process-level wastage tracking exposes hidden costs. Kapoor Textiles was losing 2.5% more material than the industry benchmark, but without process-level tracking, the excess was invisible. Once you can see where waste occurs — by process, by shift, by operator — you can act on it
  • Accurate costing changes pricing decisions. The discovery that three fabric varieties were loss-making was a wake-up call. Without product-level costing that includes jobwork and finishing charges, pricing is guesswork. Many textile companies are unknowingly subsidising unprofitable products with profitable ones
  • User adoption across multiple locations requires dedicated on-site training. We conducted separate training sessions at each unit, tailored to the workflows specific to that location. A one-size-fits-all training approach would not have achieved the same adoption rate

Managing Multiple Manufacturing Locations?

If your textile, garment, or multi-unit manufacturing business is struggling with fragmented inventory visibility, jobwork losses, or inconsistent costing, a unified ERP implementation can transform your operations. At Indivar Software Solutions, we specialise in SAP Business One for multi-location manufacturers across North India. Reach out to us for a free operational assessment tailored to your business.

Indivar Software Solutions

SAP Business One consulting and custom software development since 2009. Offices in India, New Zealand, and the USA.

Related Articles

More on Case Studies

Need Help with SAP Business One?

Whether you need implementation support, custom add-ons, or strategic ERP advice, our team is ready to help. over 17 years of SAP B1 experience across India, New Zealand, and the USA.