How Net Soft Solutions Built a Smart Manufacturing ERP for Amrit Food Products, Jorhat, Assam
Project Snapshot
- Client: Amrit Food Products
- Industry: Wheat Milling & Staple Food Manufacturing
- Location: Kathkotia, Jorhat, Assam
- Solution Delivered: Custom Manufacturing ERP with Real-Time Production Tracking
- Technology Stack: ASP.NET (C#), Microsoft SQL Server, Crystal Reports
- Project Duration: 18 Weeks (Discovery to Go-Live)
- Key Outcome: 42% reduction in milling yield loss • 60% faster order dispatch • 98%+ stock accuracy • Near-instant MIS reporting for management
About the Client: Amrit Food Products, Jorhat
Amrit Food Products is an established wheat milling company based in Kathkotia, Jorhat, Assam. The company manufactures and supplies a full range of staple wheat products including organic wheat flour (atta), regular wheat flour, maida, sooji (semolina), and bran — serving distributors, retail chains, and institutional buyers across Assam and the broader Northeast Indian market.
As demand from regional buyers grew steadily, the Managing Director recognised that the company's existing manual workflows — built for a smaller scale of operation — were now creating measurable financial and operational risk. The business needed digital infrastructure to match its physical growth. The goal was clear: build a manufacturing ERP system that could track every quintal of wheat from intake to dispatch, in real time.
The Problem: Running a Multi-Crore Milling Business on Paper Registers
Before Net Soft Solutions' engagement, Amrit Food Products managed their production operations through a combination of physical ledgers, manual stock counts, verbal communication between departments, and spreadsheets maintained by individual staff members. At a smaller scale, this worked. At their current scale, it was actively damaging the business.
The Specific Operational Challenges
1. Zero Visibility into Real-Time Production Output
The production floor and the management office operated in information silos. The Managing Director had no way to know — without a physical visit or a phone call to the supervisor — what quantity of atta, maida, sooji, or bran had been produced on any given day. End-of-day figures were compiled manually and often reached management the following morning, making same-day decisions impossible.
2. Milling Yield Losses Going Undetected
In wheat milling, milling yield — the percentage of finished product extracted from raw wheat — is the single most important efficiency metric. A 1–2% drop in yield on a high-volume milling operation can represent lakhs of rupees in lost value every month. Without a batch-wise tracking system, Amrit Food Products had no mechanism to detect or investigate yield variances. Losses were invisible, and therefore impossible to correct.
3. Raw Material Stock Inaccuracies and Working Capital Waste
The procurement team relied on estimated wheat stock figures when placing purchase orders. Physical stock counts were done weekly at best. This resulted in two costly patterns: over-purchasing (blocking working capital in excess inventory) and stock-outs (halting production mid-batch when wheat ran short unexpectedly). Neither outcome was acceptable for a business trying to meet committed delivery schedules.
4. Dispatch Errors and Invoice-Delivery Mismatches
Because dispatch challans were prepared manually and billing was done separately by the accounts team, quantity mismatches between what was dispatched and what was invoiced were a recurring problem. The company experienced 12–15 invoice disputes per month with distributors — each one damaging a commercial relationship that had taken years to build.
5. No Management Information System (MIS) for Decision-Making
The Managing Director had no consolidated dashboard or report that could tell him — in real time — how much stock was available, what orders were pending, what the day's production had been, or which customers had outstanding payments. Every business decision was made on the basis of estimates, experience, and intuition rather than data. This was not sustainable at the scale the business had reached.
Amrit Food Products needed a purpose-built flour mill ERP system — not a generic accounting package, and not a costly enterprise platform built for a different industry. They needed software designed specifically for the way a wheat milling business actually works.
Our Approach: Discovery Before Development
Net Soft Solutions' engagement with Amrit Food Products began with a structured on-site process discovery at the Kathkotia plant. Our team spent time with the mill supervisor, the procurement officer, the dispatch staff, the accounts team, and the Managing Director — mapping every operational workflow from wheat intake and grading through milling, bagging, quality checking, dispatch preparation, and billing.
This discovery-first approach is foundational to how we build custom ERP software for small manufacturing companies. Rather than asking the client to adapt their operations to fit a pre-built system, we build the system around their operations. The difference in adoption rates — and in business outcomes — is dramatic.
Twenty-three distinct operational workflows were documented and reviewed. A detailed Software Requirement Specification (SRS) was prepared, reviewed, and formally signed off by the Managing Director before a single line of code was written. This alignment between business expectation and technical specification is what keeps manufacturing ERP projects on time and on budget.
The Development Workflow: Phase by Phase
Phase 1 — On-Site Discovery & Requirements Specification (Weeks 1–2)
Detailed interviews with every department. Process maps for all 23 workflows. SRS document prepared and approved. Technology stack confirmed: ASP.NET, SQL Server, Crystal Reports — chosen for their robustness, local support availability, and the client's existing server infrastructure.
Phase 2 — Database Architecture & Module Design (Weeks 3–4)
A relational SQL Server database was designed specifically for a wheat milling operation — with tables for raw material lots (wheat intake records), milling batch transactions, product-wise yield records, finished goods inventory, customer master, order management, dispatch challans, billing, and payment tracking. The schema was designed to support both real-time transactional use and date-range MIS queries without performance compromise.
Phase 3 — Core Module Development (Weeks 5–12)
Modules were developed in a logical dependency sequence: raw material → production → inventory → dispatch → billing → MIS. The production tracking engine was built first, as all other modules derive their data from production records. Weekly video review calls with the Managing Director kept the development aligned with evolving business priorities and allowed feedback to be incorporated without delays.
Phase 4 — Integration, UAT & Data Migration (Weeks 13–15)
All modules were integrated into a unified application and tested against actual operational data from the previous quarter. Historical customer, stock, and transaction data was migrated from manual records and spreadsheets into the new SQL Server database. A formal User Acceptance Testing (UAT) phase was conducted with actual plant staff operating the system against real-world scenarios before go-live approval.
Phase 5 — Go-Live, Training & Post-Launch Support (Weeks 16–18)
The system went live with a two-week parallel run — both the manual process and the ERP were operated simultaneously, allowing staff to build confidence without operational risk. Role-specific training was delivered to production supervisors, the stores manager, dispatch staff, and the accounts team. A 90-day post-launch support window was included in the engagement scope.
The Solution: What Was Built for Amrit Food Products
The delivered system is a web-based, role-specific manufacturing ERP with separate access levels for the Managing Director, production supervisor, stores manager, dispatch team, and accounts department. Every user sees only the modules and data relevant to their role. Here is a detailed breakdown of each module:
Module 1: Wheat Intake & Raw Material Management
Every consignment of wheat arriving at the Kathkotia plant is recorded with supplier name, purchase date, quantity in quintals, wheat grade, moisture percentage at intake, and purchase rate per quintal. The system maintains a live raw material ledger that deducts wheat consumed in each milling batch and raises an automated low-stock alert when silo levels fall below a configurable minimum threshold. Procurement can now make purchase decisions based on actual system stock, not guesswork.
Module 2: Real-Time Production Batch Tracking
This is the operational core of the ERP. For every milling batch, the production supervisor records: batch start and end time, wheat lot consumed (quintal-wise), shift and operator details, products produced (atta, maida, sooji, bran — each in quintals), downtime events and reasons, and any quality observations. The system instantly calculates the actual milling yield percentage for that batch and compares it against the standard expected yield configured for each product mix. Batches where yield variance exceeds the defined tolerance are automatically flagged for review.
This capability — real-time production tracking for flour mill operations — is the single most impactful feature for milling businesses. Yield loss that previously went undetected for weeks is now visible within the same shift it occurs, enabling immediate corrective action.
Module 3: Finished Goods Inventory Management
A live, product-wise inventory ledger for atta, maida, sooji, and bran is updated automatically whenever a production batch is closed (stock added) or a dispatch challan is generated (stock deducted). The stores manager and Managing Director can view current stock levels for every product at any moment from any browser within the network — without a physical warehouse visit or a phone call to the stores team.
Module 4: Customer Order Management & Dispatch
Distributor and institutional buyer orders are entered into the system and allocated against available finished goods stock. The system validates stock availability before confirming an order, preventing the commitment of stock that doesn't exist. The dispatch team generates a digital dispatch challan linked to the customer's account — automatically updating the inventory ledger and creating a billing record. The accounts team receives a dispatch-linked billing record, eliminating manual re-entry entirely.
Module 5: GST-Compliant Billing & Accounts Receivable
Tax-compliant invoices are generated directly from dispatch records — with customer details, product quantities, rates, GST calculation, and total amount computed automatically. Customer-wise outstanding balances, payment history, and ageing are maintained in the system. The accounts team now has precise, up-to-date receivables data to support follow-up on overdue payments — replacing the informal, memory-based system used previously.
Module 6: Management Dashboard & MIS Reports
For the Managing Director, a dedicated management dashboard provides a real-time daily snapshot of: total production (quintal-wise by product), current finished goods stock, pending customer orders, today's dispatch value, outstanding receivables, and yield efficiency trend over the last 30 days. Crystal Reports-based MIS reports can be generated for any custom date range with a single click — covering production summaries, product-wise yield analysis, stock movement, customer-wise sales, and financial summaries. This is the kind of management intelligence that modern flour mill software delivers, enabling data-driven decisions on pricing, production planning, and procurement.
Before vs. After: The Business Impact in Numbers
The results at Amrit Food Products were not incremental. They were transformational across every key operational dimension. Here is a structured before-vs-after comparison based on data gathered during the project and in the three months following go-live:
| Metric | Before ERP | After ERP (3-Month Average) | Improvement |
|---|---|---|---|
| Milling yield tracking | Not measured | Tracked per batch, per shift, per product | Yield losses identified & reduced by 42% |
| Raw material stock accuracy | "65% (manual weekly count) | 98%+ (real-time system-driven) | 33-point accuracy improvement |
| Order dispatch time | 4–6 hours per dispatch cycle | Under 90 minutes end-to-end | "60% reduction in dispatch time |
| Invoice-dispatch mismatches | 12–15 per month | 0–1 per month | 95%+ reduction in billing disputes |
| MIS report availability | 2–3 days (manual compilation) | Under 5 minutes (automated, on-demand) | Near-instant management visibility |
| Working capital in raw material | Over-stocked due to estimated purchasing | Procurement driven by real-time stock data | Working capital freed up by 18–22% |
| Customer payment disputes | 6–8 per month | 0–1 per month | Stronger distributor relationships |
| Production planning basis | Verbal, supervisor memory | Data-driven, batch-scheduled | Consistent daily output targets met |
For a milling operation where product margins are thin and profitability depends on volume and efficiency, a 42% reduction in yield loss alone represents a significant addition to the bottom line every single month. These are not projected savings — they are measured outcomes from actual operations.
Why This ERP Implementation Succeeded Where Others Fail
Manufacturing ERP projects — particularly for small and mid-sized Indian manufacturers — have a historically poor success rate. Software gets purchased, installed, partially used, and eventually abandoned. The Amrit Food Products engagement succeeded for reasons that are replicable, not accidental.
Industry-Specific Build, Not Generic Adaptation
The ERP was built for a wheat miller — not retrofitted from a generic manufacturing template. Milling-specific concepts such as wheat grade, moisture at intake, milling yield ratio, product-wise extraction percentage, bran recovery rate, and batch downtime classification are first-class entities in the data model. This specificity made the system immediately intuitive for plant staff, which is why adoption was high from day one. You can explore what purpose-built software solutions for manufacturing companies look like versus generic alternatives.
Managing Director Actively Involved in Every Phase
The single most common reason ERP implementations fail in SME settings is insufficient leadership involvement during development. At Amrit Food Products, the Managing Director participated in every weekly review call, signed off on every phase, and personally championed adoption with the plant and accounts teams. Leadership alignment at the top is irreplaceable.
Phased Delivery with Tangible Early Wins
By prioritising the production tracking module in Phase 3 and delivering it before billing or MIS, the plant team experienced a concrete, daily benefit — the ability to see yield variance per batch — within the first four weeks of use. This early win built confidence and motivated full adoption across all remaining modules. This phased approach is a core principle of successful ERP implementation in small manufacturing companies and is baked into every Net Soft Solutions engagement.
Training Was Treated as a Project Deliverable, Not an Afterthought
Role-specific training, the parallel run period, and 90-day post-launch support were scoped and budgeted as project deliverables — not optional add-ons. The goal was not just to install software, but to migrate the team's working habits from manual to digital. That migration takes time, structure, and patience — and it pays off in adoption rates that make the investment worthwhile.
Technology Stack Used
- Application Platform: ASP.NET (C#) — Browser-based web application accessible across the plant network
- Database: Microsoft SQL Server — Relational, transactional, and reporting-optimised
- Reporting Engine: Crystal Reports — For MIS, dispatch challans, invoices, and management summaries
- Deployment: On-premise server at the Kathkotia plant with browser-based access for all departments
- Access Control: Role-based login with separate dashboards and permissions per user role
- Audit Trail: Every transaction logged with user, timestamp, and original values for accountability
In the Managing Director's Own Words
"Earlier I would have to wait until the next morning to know how much we produced and what our stock position was. Now I can check it from my phone in the middle of a meeting. The dispatch team works faster, the accounts are cleaner, and we have stopped losing money to yield problems we did not even know existed. This has completely changed how I run this business."
Is Your Flour Mill or Food Manufacturing Business Facing Similar Challenges?
If you operate a flour mill, atta chakki, food processing unit, or staple goods manufacturer in India and you are still relying on manual registers, spreadsheets, or disconnected software to manage your production, the story of Amrit Food Products shows what is possible — and how quickly it can be achieved with the right partner.
Net Soft Solutions has been building custom ERP and manufacturing software for Indian businesses since 2001. We understand the specific demands of milling, food processing, distribution, and production-heavy SME operations across India. Our approach — discovery-first, industry-specific, phased delivery — consistently produces results that generic ERP products cannot match.
If you are ready to move your milling or manufacturing operation beyond manual processes, contact our team today for a free, no-obligation consultation. Let us show you exactly how we would approach your specific operation — before you commit a single rupee.
You can also explore our related insights on ERP software development: benefits and key features and understand the measurable ROI of custom software development for manufacturing businesses before making your decision.