A warehouse management system doesn't just record warehouse operations — it controls them. This guide explains exactly how, step by step: from the moment a truck arrives at the dock to the moment the delivery challan is signed and your ERP is updated.
11 min readUpdated June 2026Foundations
3 ways a WMS controls — not just records
RulesFIFO/FEFO, slotting priority, bin capacity — enforced automatically at every scan
Directed tasksStaff told exactly where to go, which bin, in what order — not left to decide
Scan confirmationEvery action confirmed by scan — wrong item rejected before it can proceed
Without all 3: a recording system. With all 3: a control system.
Recording vs controlling — what's the real difference?
Most people think of software as something that records what happened. You make a sale — the software records it. A truck arrives — someone enters the GRN. Stock is picked — someone updates the spreadsheet. This is a recording system. It creates an audit trail. It tells you what happened after the fact.
A recording system tells you what happened. A controlling system determines what can happen. A WMS is a controlling system — and that distinction changes everything about how a warehouse operates.
A warehouse management system works differently. When a WMS controls picking, it doesn't just record that the wrong item was taken — it prevents the scan from being confirmed if the wrong item is scanned. When a WMS controls put-away, it doesn't just note where goods were placed — it directs staff to a specific bin and refuses to confirm unless the scan at that bin matches. When a WMS controls dispatch, it doesn't just generate a challan — it validates every loaded item before the truck can be cleared.
This difference — between recording and controlling — is the reason a WMS reduces errors to near zero rather than just creating better records of them. The system intervenes at the point of action, not after.
The 3 mechanisms a WMS uses to control operations
Every control action in a WMS works through one of three mechanisms — or a combination of all three. Understanding these makes every step that follows easier to understand.
Rules — the system decides
Rules determine what should happen without staff needing to decide. FIFO rules determine which pallet is offered first. Slotting rules determine which bin type suits each item. Capacity rules prevent a bin from being overloaded. The WMS enforces these rules automatically — staff don't choose, the system does.
Example: FIFO rule selects the lot received on 14 March before the lot received on 22 April — automatically.
Directed tasks — the system instructs
The system doesn't leave staff to figure out where to go. It generates an instruction: go to Bay C, Shelf 04, Bin B2. Pick 60 units of GI Pipe. Scan to confirm. The picker's job is execution, not decision-making. This eliminates the reliance on institutional knowledge and makes every staff member as effective as your most experienced one.
Example: Pick list shows A11-B1 → E17-B1 in the most efficient route — staff walk directly, no searching.
Scan confirmation — the system validates
Every step is only completed when confirmed by a barcode scan. The scan is the physical link between the instruction and the reality. Scan the wrong item and the system rejects it — the action cannot be confirmed until the correct item is scanned. This is the enforcement mechanism that makes rules and directed tasks effective rather than advisory.
Example: Picking scan rejects a lot received on 22 April if the FIFO rule requires the 14 March lot first.
Step 1 — Gate entry: before unloading starts
In a well-run warehouse, control begins before a single item is unloaded. When a supplier's truck arrives at the dock, the first action is a Gate Entry — logging the vehicle number, transporter details, challan number, and invoice reference before unloading begins. This creates an inward gate pass that becomes the anchor document for everything that follows.
Gate entry serves three purposes. It creates an official record that the vehicle arrived and at what time — useful for resolving supplier disputes about delivery. It flags whether the delivery was expected (matched against an open purchase order or ASN) or unexpected (no PO, urgent receipt). And it begins the chain of document traceability that runs from gate pass → GRN → put-away → stock → dispatch.
🚛
Indian warehouse context: Gate entry is especially important in Indian warehouses because the transporter carries both the supplier challan and the e-way bill. The gate pass records both documents against the vehicle, creating a complete inbound trail — useful when supplier deliveries and Tally purchase orders need to be reconciled later.
Step 2 — GRN and receiving: goods arrive
After the gate entry, goods are unloaded and the formal Goods Receipt Note (GRN) process begins. This is the first point at which the WMS exercises real control — and the first point where a manual process creates risk.
What happens at GRN in a WMS
1Open purchase order pulledThe WMS loads the open PO. The receiver selects the supplier and PO number — quantity pending against that PO is shown. The system knows what was ordered and will flag any discrepancy.Expected vs actual
2Item scanned against PO lineEach item is scanned by barcode. The scan matches against the open PO line. Quantity delivered is entered or confirmed. If the item scanned doesn't match the PO, it's flagged immediately.Discrepancy flagged
3Lot number and expiry date capturedFor items with batch traceability — food, pharma, metals, chemicals — the lot number (batch number) and expiry date are captured at GRN. This is mandatory for FEFO to work later. If lot number is not captured now, FEFO cannot be enforced at dispatch.Required field
4GRN Tag / pallet label printedA barcode label is printed for the received goods — showing item code, description, supplier, lot number, GRN date, and a scannable barcode. This label stays with the goods through put-away, storage, and picking. It is the physical identifier that links the goods to the system record.Barcode label
5Receiving source recordedGoods can arrive from a supplier (normal purchase), from another branch (inter-branch transfer), from a customer (sales return or job-work material), or from a third party. Each source type has a different accounting treatment — the WMS records the source and routes it to the correct workflow.4 source types
6ERP updatedWhen the GRN is confirmed, the corresponding voucher is posted to your ERP automatically — purchase receipt, stock journal, or returns credit note, depending on the source type. No manual re-entry in accounts.ERP auto-sync
Manual GRN
Paper receipt written at dock — Tally entry done next day
Quantity discrepancy discovered weeks later at stock count
Lot numbers not captured — FEFO impossible to enforce
No record of which items arrived from which source
WMS-controlled GRN
Scan against PO — discrepancy flagged while truck is at dock
Lot and expiry captured as a required field — not optional
ERP updated at confirmation — no re-entry, no lag
Source type recorded — correct workflow triggered automatically
Step 3 — Inspection: the quality gate
After GRN, the goods move to a holding location (sometimes called Open Store or Receiving Store) where they wait for inspection before entering main stock. Inspection is the quality gate — the point where accepted goods and rejected goods are formally separated, and only accepted goods become available for use or dispatch.
In a WMS, inspection is not a side note. The system maintains a queue of pending inspections — every GRN that has not yet been inspected appears on the inspection queue. Inspectors see exactly what is waiting, when it arrived, and from which supplier.
The two-path inspection split
Goods received — awaiting inspection
OK quantity → Main StoreAvailable for allocation, picking, and dispatch
Not OK quantity → Rejection StoreHeld for disposition: return to supplier, rework, or scrap
Rejection reason recorded against each line. NCR (Non-Conformance Report) generated for every rejection.
The rejection store is not a bin to forget things in. In a WMS, rejected goods have a bin location, a lot number, and a recorded reason for rejection. The rejection analysis report tracks which suppliers are generating rejection, at what rate, and for what reasons — giving procurement a data-driven basis for supplier performance conversations.
🔍
Manufacturing scenario: An automotive components manufacturer receives a delivery of raw material. During inspection, 15 of 120 units fail dimensional checks. The WMS creates a GRN for 105 accepted units into main store, moves 15 to rejection store with reason 'Dimension out of tolerance', generates an NCR, and alerts the procurement team. The supplier is contacted before the truck leaves — not three weeks later when someone finds the paper rejection note.
Step 4 — Put-away: stock finds its bin
Put-away is the process of moving accepted goods from the inspection or staging area to their designated bin location in the warehouse. In a manual warehouse, the store man decides where to put things — typically wherever there's space. This is the root cause of lost stock, FIFO violations, and overcrowded bins.
In a WMS, put-away is directed. The system assigns a bin based on rules — item type, storage zone, supplier priority, bin capacity, and item-specific restrictions. The put-away instruction tells the store man exactly which bin to go to.
The two-step put-away model
One of the most important — and least-understood — aspects of how a WMS controls put-away is the two-step model:
1. Put-away instruction created
System assigns the bin. Store man directed to take the goods from staging to the designated bin. The transfer is recorded as 'in progress'.
Stock is NOT yet updated
2. Put-away confirmation
Store man scans the bin barcode at the destination to confirm arrival. The system validates the scan matches the assigned bin. Only now is the stock balance updated.
Stock IS now updated — this is the real commit
This two-step model is important because it ensures the system never shows stock in a location until the goods have physically arrived and been confirmed there. Without confirmation, a put-away instruction is just a plan — not a fact. The confirmation scan is what makes the WMS's bin-level stock accurate.
Put-away confirmation is not a formality. It is the moment the system's record becomes a fact — because the store man's scan proves the goods are physically there.
Step 5 — Storage and the live bin map
Once goods are confirmed in their bin, the WMS maintains a live record of every bin in the warehouse — what's in it, how much, which lot, and when it expires. This is the storage layer that makes every subsequent operation possible.
What the WMS tracks in storage
Item and lot in every binExact item code, lot number, quantity, and receipt date per bin — updated at every scan
Expiry dates by lotFor FEFO-managed items, each lot's expiry date tracked from GRN — visible in the Lot Expiry Dashboard across 9 time bands
Pallet / LPN statusEach pallet has a status: available (R), on hold (H), damaged (D). Only available pallets appear in pick lists — held and damaged pallets are excluded automatically
Bin capacity and utilizationEach bin has a defined capacity in kg and cubic metres. The Warehouse Utilization Report shows actual vs capacity per bin — preventing overloading
Stock ledger — every movement loggedEvery receipt, transfer, pick, and dispatch creates an immutable ledger entry — full movement history for any item at any location
Visual bin mapA graphical grid view showing pallet contents per bin, colour-coded by status — a literal visual map of the warehouse state at any moment
❄️
Cold storage scenario: A cold storage operator uses the Lot Expiry Dashboard to see exactly which lots are expiring today, this week, this month, and up to one year ahead — across all bins and temperature zones. Near-expiry lots are automatically prioritised in pick lists. Stock in 'Hold' status (e.g., lots pending quality clearance) is excluded from pick lists — it cannot be dispatched until explicitly released.
Step 6 — Order picking: directed and enforced
Picking is where the WMS's control mechanisms have the most visible impact. In a manual warehouse, a picker reads a paper list, finds the items, and loads the trolley. The process depends entirely on the picker's knowledge of where things are, their discipline in following FIFO, and their accuracy in reading the order.
In a WMS, picking is directed and enforced. The pick list tells the picker exactly which bin to go to, which lot to take, and in what sequence. Every item is confirmed by scan. Wrong lot scans are rejected. The system controls the outcome — not the individual.
Pick list modes — the WMS adapts to your operation
A WMS doesn't generate just one type of pick list. Different operations need different picking strategies:
FIFO / FEFO picking
Oldest stock (FIFO) or soonest-to-expire stock (FEFO) picked first. Applied per item or per item category. FEFO essential for food, pharma, cold chain.
Wave picking
Multiple orders batched into one warehouse walk. Picker collects items for 4-6 orders in a single pass, sorted by bin location. Reduces travel time significantly on high-volume dispatch days.
Route-wise picking
Orders grouped by delivery route. Picker collects all items going to Route 1 customers in a single pass — ready to load in delivery sequence.
What happens when a picker scans the wrong item
This is the key control moment — and it's worth explaining precisely. When a picker scans an item barcode that doesn't match the pick list, the WMS rejects the scan. The screen shows an error. The picker cannot confirm the pick until they scan the correct item. There is no override available to a picker — only a supervisor with appropriate access can investigate and take corrective action.
This is what separates scan enforcement from scan recording. A recording system would note that the wrong item was picked. A controlling system prevents the wrong item from being confirmed — and therefore from reaching packing, loading, and dispatch.
🏭
Manufacturing store-room scenario: A production floor raises a material requisition for 60 GI Pipes (Grade A, Heat Code K-2204). The pick list directs the store man to Bay C, Shelf 04, Bin B2 — the bin holding the oldest Grade A lot. The store man scans the bin barcode, then scans each pipe's pallet barcode to confirm pick. If they accidentally scan from Bay D (a different heat code), the scan is rejected. The correct lot reaches production — traceability is maintained from supplier delivery to production use.
Want to see scan enforcement in action?
We demonstrate FIFO rejection, pick list direction, and dock validation in every Fast WMS demo.
Dispatch is the last control point — and one of the most important. In a manual warehouse, goods are loaded based on a handwritten pick list and a driver's urgency. Nobody checks whether the right items, quantities, and lots are actually on the truck before it leaves. Wrong items are discovered at the customer's site — after the cost of return, replacement, and apology has already been incurred.
In a WMS, dispatch is controlled at the dock. Every item is scanned against the confirmed pick list and delivery challan before the truck can be cleared. Any mismatch — wrong item, wrong quantity, wrong lot — is flagged immediately. The loader cannot clear the dispatch until every scan matches.
What dispatch control generates automatically
Delivery Challan
GST-compliant dispatch advice cum challan — generated from confirmed dispatch data, not typed manually
Packing Slip
Item-wise packing slip with buyer/sender address, quantities, and net weight — printed at dispatch
E-way bill data
Dispatch details passed to your ERP or e-way bill system — consignment value, vehicle number, route
ERP sync
Sales or dispatch voucher posted to your ERP automatically — no manual re-entry after dispatch
The audit trail created at dispatch is complete: which items left, in what quantity, from which bin and lot, on which vehicle, at what time, against which sales order, confirmed by which scan. Every link in that chain is available in the WMS reports — traceable from the supplier delivery that created the stock all the way to the customer delivery that consumed it.
What a WMS controls that manual processes cannot
A useful way to understand what a WMS adds is to look at each step and ask: what can go wrong in a manual process here, and what does the WMS do differently?
Step
What can go wrong manually
How WMS controls it
Gate entry
Delivery logged on paper, not linked to PO
Gate pass linked to PO/ASN before unloading
GRN receiving
Wrong quantity entered, lot not captured
Scan against PO, lot required field, discrepancy flagged at dock
Inspection
Rejected goods mixed back with accepted goods
System routes to rejection store, tracks reason and lot
Put-away
Staff put goods wherever there's space
System assigns bin by rules, confirmation required to commit
Storage
Location known only to the person who put it away
Every bin tracked in real time, any user can search and find
Picking
Picker takes wrong item or wrong lot
Pick list directed to correct bin/lot, wrong scan rejected
FIFO/FEFO
Newest stock picked because it's more accessible
Only correct lot offered in pick list, wrong lot scan rejected
Dispatch
Wrong items loaded, no check before truck leaves
Dock scan validates every item, dispatch cannot be cleared until all scans match
ERP update
Manual entry, often hours or days later
Auto-posted at each step — GRN, adjustment, dispatch
Part of the Warehouse Management GuideA series of in-depth guides covering every aspect of warehouse management for Indian businesses.
How does a warehouse management system control warehouse operations?
A WMS controls warehouse operations through three mechanisms working together: rules (FIFO/FEFO rules that determine which item is picked, slotting rules that determine where goods are stored), directed tasks (the system tells staff exactly where to go and what to do — which bin to put goods in, which location to pick from, in what sequence), and scan confirmation (every action is only completed when confirmed by a barcode scan — the wrong item scan is rejected, not just flagged). The result is that the WMS doesn't just record what happened — it controls what can happen.
What is the step-by-step process in a warehouse management system?
The core WMS process has 8 steps: (1) Gate entry — the arriving vehicle is logged before unloading begins; (2) GRN/receiving — goods are scanned against the purchase order, lot numbers and expiry dates captured; (3) Inspection — accepted goods go to the main store, rejected goods go to a rejection store pending disposition; (4) Put-away — the WMS assigns a specific bin and directs staff to it; (5) Put-away confirmation — the physical commit that actually updates stock balances in the system; (6) Order picking — a FIFO or FEFO pick list directs staff to the exact bin in the correct sequence; (7) Pick confirmation — each item scanned to confirm; wrong items physically rejected by the system; (8) Dispatch — load validated at the dock, delivery challan and documents generated, ERP updated automatically.
What is the difference between a WMS recording and a WMS controlling?
A recording system writes down what happened after the fact. A controlling system determines what can happen in the first place. When a WMS controls picking, it doesn't just record that the wrong item was taken — it prevents the wrong item from being confirmed by rejecting the scan. When a WMS controls put-away, it doesn't just note where goods were placed — it directs staff to the correct bin and refuses to confirm unless the scan matches. This distinction between recording and controlling is the difference between a system that creates an audit trail and a system that prevents errors from occurring.
What is put-away confirmation in a WMS and why does it matter?
Put-away confirmation is the step that actually commits stock to a bin location in the WMS. In many WMS implementations, the put-away step creates a transfer instruction (directing staff to take goods to a bin), but the stock balance is not updated until put-away confirmation happens — a separate scan at the destination bin that tells the system the goods have physically arrived there. This two-step model ensures the system always reflects the actual physical location of stock, not just the intended location.
How does a WMS enforce FIFO and FEFO picking?
A WMS enforces FIFO (First In First Out) and FEFO (First Expired First Out) at the barcode scan level. The pick list shows only the correct pallet or lot — the one with the earliest receipt date (FIFO) or earliest expiry date (FEFO). If a picker scans any other pallet, the scan is rejected before the item can be confirmed. This is a physical enforcement mechanism, not a recommendation — the wrong pallet cannot be confirmed regardless of what the picker does. This is the fundamental difference between a business having a FIFO policy and a business actually enforcing FIFO.
How does a WMS control dispatch and prevent wrong items leaving the warehouse?
A WMS controls dispatch through dock validation — every item loaded onto a truck is scanned against the confirmed pick list and delivery challan before the vehicle can be cleared to leave. Any item that doesn't match is rejected immediately. The loader cannot clear the dispatch until every scan matches the order. This makes it physically impossible for wrong items, wrong quantities, or wrong lots to leave the warehouse without being detected — at the point of loading, not after the truck has left.
What happens in a WMS when an item fails quality inspection at receiving?
When goods fail inspection at receiving, a WMS splits the received quantity into two streams: accepted quantity moves to the main store and is available for allocation and picking; rejected quantity moves to a rejection store, where it is held pending a disposition decision (return to supplier, rework, or scrap). Critically, rejected goods are tracked in the system — they have a bin location in the rejection store, a lot number, and a reason for rejection — so they can be managed, not just set aside and forgotten. A Non-Conformance Report (NCR) is generated for each rejection.
See exactly how a WMS controls every step — live
A 30-minute Fast WMS demo walks through every control point: GRN scan against PO, FIFO pick list enforcement, dock validation, and automatic ERP sync. Live on your items and your warehouse.