The Indent-to-Stock Playbook: How Inventory & Store Management Works in Indian Plants (2026)
One approval-driven system for indents, POs, receipts, issues and gate passes, giving you an auditable stock ledger.
Sort String Solutions Team

Reading
9 min
Every plant store runs on the same basic chain. A department asks for material, someone approves the request, purchasing orders it, the store receives it, and the material is later issued, scrapped or returned. The trouble starts when this chain lives in WhatsApp messages, paper indent books and a spreadsheet that one person updates on Friday evenings. Inventory and store management software puts that whole chain into one approval-driven, auditable system.
This guide explains how the indent-to-stock workflow should work, who should approve what, how stock should be valued, and what to check before you pick a system. It is based on the way Sort String's Inventory & Store Management platform is built for manufacturing, dairy and FMCG plants in India.
Quick answer: Inventory and store management software is a system that records every material request (indent), purchase order, goods receipt, stock issue, scrap, return and gate pass in one stock ledger. Approvals are enforced by role, and stock value, vendor payables and reorder alerts are calculated automatically.
What is inventory and store management software?
Inventory and store management software controls how materials enter, sit in and leave a physical store. It keeps master data (items, vendors, locations, units), runs the approval workflow for indents and purchase orders, updates a live stock balance on every receipt and issue, and produces operational and financial reports. It is different from a sales-side DMS. A DMS tracks what you sell to distributors and retailers. A store management system tracks what your plant buys, holds and consumes.
Why spreadsheets and paper indents break down in plant stores
No approval trail. Nobody can prove who approved an order, or whether the person who raised it also approved it.
Stock is always out of date. Receipts and issues are entered late, so reorder decisions use last week's numbers.
Vendor payables drift. Approved POs never reach the vendor ledger, so outstanding balances are guesswork.
No stock valuation. Without a running average rate per item, finance cannot put a reliable rupee value on the store.
Material leaves the gate untracked. Tools and parts sent out for repair are not recorded, so nobody chases their return.
If you are moving off spreadsheets, read our data migration checklist first.
How does the indent-to-stock workflow work?
Raise an indent. A Store Manager or Production Manager creates a requisition with department, store location, priority (Low, Medium or High) and line items. The system shows current stock of each item so the requester does not over-order.
Approve or reject the indent. The GM Plant approves or rejects it. Only approved indents can become purchase orders.
Create the purchase order. The Purchase Executive converts the approved indent into a PO. Line items, UOM and the default vendor pre-fill, and rate, GST %, freight and insurance are added. Subtotal, tax and grand total calculate automatically.
Approve the PO. The PO is approved by an authorised role other than its creator. On approval, a debit entry is posted to the vendor ledger automatically.
Receive stock (GRN). The store receives goods against the approved PO. The received quantity cannot exceed the PO's remaining quantity. Batch and expiry dates are captured for tracked items.
Issue, scrap or return. Material is issued to an internal department, scrapped to an external party or returned. Issues can never exceed available stock.
Close the loop. Indents and POs move through Open, Approved, Partially Completed and Closed. Each line shows its remaining quantity, so one indent can be fulfilled across several POs.
Who approves what? The maker-checker rule
The most important control in a store system is simple: the person who creates a record cannot approve it. Approval rights belong to the role, not to the individual record. A typical role map looks like this:
Admin: full access. Manages users, masters and permissions.
GM Plant: approves or rejects indents. Reviews POs and stock movement.
Purchase Executive: creates POs from approved indents and approves or rejects POs.
Store Manager: raises indents, receives and issues stock, and issues gate passes.
Production Manager: raises indents and creates POs for their own department.
Permissions should be granular at module level (Create, View, Edit, Delete, Approve, Reject, Export). When a permission is missing, the menu item, the button and the back-end call should all be blocked, not just hidden on screen.
Stock movement: receiving, issuing, scrap and returns
Receiving against a purchase order
Selecting an approved PO pre-fills the vendor and items. The store adds the bill or invoice number, transaction date and attachments. On save, three things happen at once: current stock increases, a stock-movement record is written, and the vendor's payable ledger is updated.
Receiving without a purchase order
Urgent or one-off purchases still need to be recorded. The vendor is selected first, then items, quantities, rates and taxes are entered by hand. The same capture rules apply as for PO-backed receipts.
Issuing to Company, Scrap or Return
Every issue has a type. Company and Return issues go to an internal person and department. Scrap issues go to an external party. This split is what makes scrap and consumption reports reliable.
Gate passes: what is the difference between MRGP and NRGP?
An MRGP (Material Returnable Gate Pass) covers material that leaves the premises and is expected back, such as a motor sent for rewinding. It records the vehicle number, the expected return date and the destination, and returned items restore stock when they come back. An NRGP (Non-Returnable Gate Pass) covers material that leaves for good, and the issue is final.
How is weighted-average stock valuation calculated?
Weighted-average cost gives each item one running rate that reflects everything you paid for it. It is recalculated on every receipt and left unchanged on every issue.
New average rate = (existing qty × existing avg rate + received qty × received rate) ÷ total qty
Worked example: You hold 100 kg of a packing film at ₹50/kg. You receive 50 kg at ₹56/kg. The new average rate is (100 × 50 + 50 × 56) ÷ 150 = ₹52/kg. If you then issue 30 kg, the rate stays ₹52 and only the quantity drops to 120 kg. Total stock value is the sum of quantity × average rate across all items, and this becomes the Stock Value tile on the dashboard.
A vendor ledger that updates itself
In many plants the vendor ledger is filled in by hand, so it falls behind the purchase register. A good store system makes the ledger a by-product of the workflow:
PO approval automatically posts a debit for the PO grand total.
A PO revision posts only the difference as an adjustment. The original entry is never edited.
A vendor payment by cheque, NEFT, RTGS or UPI is recorded as a credit.
Outstanding per PO = PO debit − payments credited, with a running balance per vendor.
PO revisions should also keep a full snapshot of the previous version, so auditors can see exactly what changed and when.
Dashboard, reorder alerts and daily digests
The dashboard should answer "where is the pressure today?" as soon as a user logs in. Six tiles cover it: Open Indents, Open POs, Approved POs, Low Stock Items, Total Stock Items and Stock Value. A Product Below Reorder Level table then lists each item's current stock, reorder level, last stock-in and stock-out dates, and a suggested action (Urgent Reorder or Raise Indent).
Dashboards only help people who log in, so the platform also sends the alerts out:
09:00, reorder alert to the purchase team by email or Slack, with the suggested order quantity and default vendor for each item.
11:00, pending-approval nudge to the GM Plant (open indents) and the Purchase Executive (open POs). Anything older than 3 days is highlighted.
18:00, daily activity digest to leadership: indents raised, POs placed, total spend, stock movements and items below reorder level.
Which reports should store management software provide?
Every report should have a date-range filter, filters for item, category, vendor, department, location and status, and Excel export. The core set is:
Inventory Report (current quantity per item)
Stock-In and Stock-Out Reports
Scrap Report
Indent Report and PO Report
Indent vs PO Report (how much demand has been ordered)
Credit & Debit (Vendor Ledger) Report
Reorder Report
Item-wise Consumption Report
Rate Comparison Report (the same item's rate across vendors and POs)
Inventory Valuation Report (quantity, average rate and total value)
Activity Report for the last 1, 7 or 30 days, or a custom range
Standard vs Extended: do you need the advanced modules?
A single-location store usually needs only the Standard scope: masters, vendors, items, indents, POs, receipts, issues, reports and permissions. Multi-category or dairy-style facilities usually need the Extended scope, which adds:
Gate Pass module (MRGP / NRGP) with vehicle number and expected return date
Collection-Centre master
Store categories on receipt (Packing Material, Engineering, MPD, Market)
Invoice and gate-entry number and date on receipt
Weighted-average rate on current stock
Per-day consumption on items, for forecasting
Current Stock Summary Report by category, location and collection centre
Both scopes run on the same code base, so a plant can start on Standard and switch the Extended modules on later without migrating data. For multi-site operations, see our guide to multi-warehouse inventory for FMCG.
Checklist: how to evaluate store management software
Does it block a creator from approving their own indent or PO?
Can one indent be fulfilled across several POs, with remaining quantity shown per line?
Does receiving block quantities above the approved PO quantity?
Are batch and expiry tracking switchable per item?
Does PO approval post to the vendor ledger automatically?
Is stock valued at a weighted-average rate that updates on each receipt?
Does it handle returnable and non-returnable gate passes?
Can masters be bulk-imported from Excel or CSV, with an error report for rejected rows?
Is every record soft-deleted, with created, updated and deleted by and on stored?
Does it push reorder and approval alerts, or only show them on a dashboard?
How Sort String's Inventory & Store Management platform fits in
Sort String's Inventory & Store Management platform covers everything in this guide. It can run integrated with SalesPort, so staff sign in with their existing SalesPort credentials, or standalone with its own users and departments. Onboarding is quick because masters can be bulk-imported from a spreadsheet, and a one-click action fills each item's default vendor from its latest PO. An admin-only Adoption Health page tracks data quality over time: default-vendor coverage, ledger completeness and items with no movement in 90 days.
Want to see the indent-to-stock workflow on your own items? Book a demo with Sort String.
Frequently asked
Quick answers
What is an indent in inventory management?
What is the difference between MRGP and NRGP?
How is weighted average cost calculated for inventory?
Can the person who raises an indent or PO also approve it?
Can stock be received without a purchase order?
Which reports should inventory and store management software include?
Does Sort String's store management system work without SalesPort?
Written by
Sort String Solutions Team
See it in action
Run this playbook on your own data.
Book a 30-minute walkthrough — we'll demo the exact module discussed in this article on a real dairy or FMCG dataset.
Schedule a walkthroughGet a 30-min walkthrough on your data.
No deck, no fluff. Just the modules from this article running live.
Keep reading
More from the field
DairyFat / SNF Testing Software — When to Digitise and the Integrations That Matter
Manual fat/SNF entry is the single biggest source of farmer-payment disputes in Indian dairy. What to evaluate when picking software that talks to your milk analyser device.
DairyAuto-Calculated Milk Payments: How NDDB-Grade Cooperatives Pay Farmers in 24 Hours
Farmers stay loyal to the dairy that pays accurately and fast. Here's how digitised, fat/SNF-based payment calculation lets NDDB-grade cooperatives pay farmers within 24 hours — and why it's the strongest retention lever in dairy.
DairyCooperative Governance: The 6 Board Reports a Modern Dairy Co-op Can't Live Without
A dairy cooperative's board governs on data — but most still assemble board packs by hand from registers. Here are the six reports a modern co-op needs generated automatically from live data.
