Stock Moves Built
A stock move is a single planned movement of a product's quantity from one stock location to another. This screen is where you review every move in the system and step in when one needs to be held or stopped — it is not where moves are created.
What a stock move is
Every physical or logical movement of stock — a despatch item for an approved order, a stock transfer between warehouses, a closing-stock adjustment, a returned package coming back in — is recorded as one StockMove row: a product, a quantity, a source location, a destination location, and a state. The state tracks the move through its life, and the console's job is to let you see that history and intervene when something needs to be suspended or cancelled.
There is no Create button here. Delivery moves (despatch items) are created automatically for approved orders: every night at 01:00 the portal creates one per order line and released part still owed, already Confirmed, and moves the order to In Despatch; HO can also do it for one order at once with Create despatch items now; other moves are created behind the scenes by stock transfers, closing-stock reconciliation, goods receipts and returns processing. The one move you can raise by hand is a manual adjustment, from the New adjustment button above the list — see New adjustment below. Everything else on this page is about what your team does after a move exists — reviewing it, and, when necessary, suspending or cancelling it.
Where to find it & who can see it
Open Inventory › Stock move in the left navigation. The list is visible to anyone holding stock_move.view (or a super administrator). There is no create, edit or delete page for this resource — every column and every action described below appears on the list itself, including the New adjustment button in the page header, which needs stock_move.create.
The state machine
StockMoveState has nine cases, but a single move only ever follows one of two short paths through them, plus the exception actions this screen exposes.
In practice a move follows one of two short routes:
- Delivery moves (despatch items for an approved order): Draft → Confirmed — created together by the nightly despatch-item run or Create despatch items now — then Reserved by the daily auto-reserve job (see Schedulers), then Shipped when its picking wave is despatched (see Picking Waves), and finally Done when the package carrying it is marked Delivered (see Packages). That last step is the only route to Done for a delivery move: if its package is instead marked Returned or Lost it also closes, after a replacement move is created to re-send it; if it is split across packages and one of them has not been delivered, or if it was never packed into a package at all, it stays Shipped indefinitely.
- Transfer / closing-stock / receipt moves: Draft → Confirmed, then straight to Done — skipping Reserved and Shipped entirely — when the owning process (a stock transfer, a closing-stock statement, a goods receipt) marks it complete.
StockMoveState has nine cases, but Picked and Packed are not reached by any move today — no service, job or console action assigns them. They are shown here for completeness and because the enum's badge colours are defined for them, but you will never see a move sitting in either state.
A move can be split across several packages that leave on different days (see Packages). When that happens, each despatch decrements only the stock its own parcel carries, and the move is marked Shipped only once all of it has gone. Until then it keeps the state it already had — usually Reserved — while a separate shipped_quantity figure records how much has actually left, and the remainder stays reserved.
So a move showing Reserved may already have had part of its stock physically despatched. There is deliberately no "partly shipped" state: whether AIR wants one is still an open decision, and inventing it here would have pre-empted that call.
Columns
| Column | Shows |
|---|---|
reference | The move's identifying number, shown as a badge. Searchable and sortable. |
operation_type | Badge showing what kind of move this is — Receipt, Delivery, ReturnIn, ReturnOut, Adjustment or Internal. |
| Product | product.code — the product code being moved. Searchable. |
| Qty | product_qty — the quantity on the move. |
| From → To | A computed column reading sourceLocation.location_name and destLocation.location_name as "From → To" (an em-dash on either side stands in for a missing location). |
| State | A coloured badge — see the diagram above for the colour key. |
| Carrier | carrier.name, toggleable — the delivery carrier assigned to the move, where relevant. |
| Hold reason | suspendReason.name, toggleable, blank when the move has never been suspended. |
| Replaces New 2026-11-07 | Toggleable. On a replacement move — one created to re-send the contents of a package recorded Returned or Lost — the reference of the move it replaces. Blank otherwise. See Packages › When a package comes back or is lost. |
| Replaced by New 2026-11-07 | Toggleable. On an original move, the reference(s) of the replacement move(s) re-sending it, one per line. |
scheduled_date | The date the move is due to happen. Sortable, toggleable. |
created_at | Date and time the move was created. Sortable, hidden by default. |
Filters
Select Filters to open three drop-downs: Product (search by product code), State (all nine StockMoveState values) and Operation type (all six OperationType values). Combine them with the search box, which matches the move's reference or product code. The Stock moves link on a product's Inventory tab opens this list with the Product filter already set.
Actions
- New adjustment Form
The one button in the page header rather than on a row. Use it to correct a location's stock against a physical count outside the closing-stock cycle — books found in the back room, or written off as damaged. It posts a single
Adjustmentmove that is confirmed and completed in one step, so Stock on hand changes the moment you submit; the move appears in the list already Done and cannot be undone (post a second, opposite adjustment to correct a mistake).Field Type Required Notes Location Select Yes Only real, in-use storage locations are listed, shown as Warehouse — Location. The virtual endpoints (Suppliers, Customers, In-Transit, Inventory Loss) never appear; the adjustment picks the right one for you. Product Select Yes Searchable by code or name. Direction Radio Yes Add stock brings the quantity in from the warehouse's supplier/production endpoint; Reduce stock writes it off to Inventory Loss. Same convention closing-stock reconciliation uses for a counted discrepancy. Quantity Number Yes Always a positive number — direction decides the sign. Reason Textarea Yes Max 500 characters. Stored on the move as its notes; this is the only record of why the position changed, so write it for whoever audits the count later. A reduction that would take the location below zero is refused outright — you get an Cannot post adjustment message and nothing changes. If neither the warehouse nor the global endpoint list has a supplier/loss location configured, the adjustment is refused the same way.
- Suspend Form
Available on any move that is not already Done, Cancelled or Suspended — that covers Draft, Confirmed, Reserved and even Shipped. Selecting it opens a form rather than a plain confirmation dialog:
Field Type Required Notes Reason Select Yes Drawn from active StockMoveSuspendReasonrecords that are flagged for manual selection — the list is curated by an administrator, not free text.Remark Textarea No Max 500 characters — add context for whoever unsuspends it later. Submitting the form is the confirmation — there is no separate "are you sure?" step. If the move was Reserved, its reservation is released immediately (the reserved quantity on Stock on hand drops back to available) before the state changes to Suspended.
- Unsuspend Confirmation required
Available only on a Suspended move. It returns the move to whichever state it held immediately before it was suspended (recorded on its move log) — typically Confirmed or Reserved. If that prior state was Reserved, unsuspending re-attempts the reservation there and then; if there is no longer enough available stock to reserve, the move settles at Confirmed instead rather than failing outright.
- Cancel Confirmation required
Available on any move that is not already Done or Cancelled — notably, unlike Suspend, this includes a move that is currently Suspended; you do not need to unsuspend something before cancelling it. A confirmation dialog is all it asks for — no reason field. If the move was Reserved at the time, its reservation is released as part of cancelling.
On a part of a subscription set the dialog also shows Stop all later parts, on by default: later parts of that subscription are never created for the order, and any not yet shipped are cancelled too. The order line then shows "Stopped from part N"; Resume later parts on the line undoes it (see Sale Orders). Switch it off to cancel only this item — the next nightly run then creates it again.
- Reserve now Confirmation required
Available on an order's delivery move that is Confirmed, or held by one of the automatic holds that clear themselves. It runs the same hold checks as the nightly reservation job and reserves stock there and then — even where the carrier or warehouse is not set to auto-reserve. If a hold still applies, or the stock isn't there, you are told why and nothing changes.
- Set carrier / Change carrier Form
(November 2026) Available on a delivery move that has not left the warehouse (Draft, Confirmed, Reserved or Suspended) and is not on a picking wave yet; needs stock_move.edit. Pick the Carrier. An order line booked without a delivery mode produces a move with no carrier, and the nightly wave run skips those (they show as no_carrier on Dropped Records) — this is how you give it one so it can be waved. Each change is written to the move's log ("Carrier none → Speed Post"). To change the carrier of a move already on a wave, take it off the wave first.
- Override holds / Remove hold override Form
Available on a delivery move that is not Done or Cancelled. Asks for a Reason (required, max 500 characters). With the override on, the item skips every credit and hold check at reservation; stock still has to be there. Each change is recorded on the move's log with your name. Turning it on for an item held by an automatic hold releases it, so the next reservation run reserves it; a manual hold stays until someone unsuspends it. Remove hold override puts the checks back from the next run. To override every open item of an order line at once, use Override despatch holds on the line in Sale Orders.
Each action is only offered when the move is in a state its underlying service will actually accept — the same safety rule as everywhere else in the console (see Getting started). A Done or Cancelled move never shows any action at all; it has reached the end of its life.
Why a move is held
The Hold reason column tells you why a move stopped. A hold comes from one of two places: a colleague pressed Suspend by hand, or the nightly auto-reservation job checked the move against AIR's credit-control rules and refused to reserve stock for it. The automatic checks run strictest first and only the first failure is recorded — so the reason shown is the one thing you have to fix, not necessarily the only thing wrong.
| Hold reason | What it means | What to do |
|---|---|---|
| Delivery pincode not serviceable by the assigned carrier carrier_unserviceable | The carrier on this move is recorded as not delivering to the pincode on the order's delivery address, so sending it would only produce a return. | Either assign a carrier that serves that pincode, or correct the serviceability record if the carrier does in fact deliver there. If the customer's address is wrong, fix the address on the order. Note: when no serviceability record exists at all for that pincode and carrier, the move is not held — a missing record is never read as "unserviceable", so this reason only ever appears where someone has explicitly marked the pincode as not served. Hand delivery: the same hold is used when a hand-delivery move's warehouse doesn't serve the delivery address's region — map the region to the warehouse (its Regions list) or change the delivery mode. A Hand delivery / warehouse override on the order lifts this hold. |
| A pending return on this order line holds its further parts return_pending | An earlier part of this same order line came back in a return that is still open (not yet reconciled or cancelled). Nothing more of that line goes out until the return is settled, whatever the inspector chose. Other lines and other orders are not held. | Finish the return: reconcile or cancel it. If the inspector chose suspend further parts, reconciling puts the line's open items on a manual hold for someone to release; cancel subscription stops the line from the next part. |
| Too many unremitted COD packages already out cod_in_transit | The customer already has more cash-on-delivery packages out, with the money not yet received, than the configured limit allows — more than 5 by default. Only items of cash-on-delivery orders are held. | Chase and record the outstanding COD remittances; each one marked received brings the customer back under the limit. The limit is reservation.cod_in_transit_limit in System Configuration; 0 switches the check off. |
| Too many RBP/OLP packages already out for this customer rbp_in_transit | This item goes by a carrier marked RBP / OLP carrier, and the customer already has more than the allowed number (1 by default) of cash-on-delivery packages on such carriers out with the money not yet received. | Record the outstanding remittances. The limit is reservation.rbp_in_transit_limit; 0 switches the check off. |
| Full set not yet paid full_set_payment | This product is marked withhold until paid in full: not a single part of the set leaves until payment covers the whole order line. The customer is notified by SMS and email when this hold is applied. | Collect and allocate the remaining payment against that order line. Once the line is fully covered, the hold no longer applies. |
| Minimum payment allocation not reached min_payment_allocation | The product has a minimum payment allocation %, and the payment allocated to this order line, or to the order as a whole, is still below it. Every part of the line waits, not just this one. The customer is notified by SMS and email when this hold is applied. | Collect and allocate payment against the order line (or other lines of the order, for the overall %). Once both percentages are reached, the hold clears on the next nightly run. The percentages are on the product's Discounts & Credits tab. |
| Not enough credit left on the order line for this part credit_insufficient | The order line doesn't have enough credit left for this part. The line's credit is: payments allocated to it that have cleared + post-approval discounts on it + its parts-on-credit allowance (see Parts on credit) + its share of any credit HO approved on the order − the value of its parts already reserved or sent. Parts are let through in despatch order while the credit covers them (with ₹1 of rounding tolerance); the first one that no longer fits, and every later one, waits. Each part's value is the one fixed when its despatch item was created. Cash-on-delivery orders, free-supply and re-send order types, and items already packed are not checked. The customer is notified by SMS and email. | Collect and allocate payment against the order line; once the payment clears, the next nightly run lets the next parts through. A manager can let one item through anyway with Override holds. |
| Payment not received/allocated payment_pending | The order as a whole hasn't settled — it is no longer fully paid or credit-approved, and no payment override is in force. The customer is notified by SMS and email. | Record the payment and allocate it to the order — the hold then clears on the next nightly run. |
| Credit limit exceeded credit_limit | Credit checking is switched on for this customer, and what they would owe with this item — the value of their reserved or sent items on open orders, less cleared payments on those orders — would be above their ceiling. | Collect payment to bring the balance down, or have the customer's credit_limit reviewed on their customer record. The hold clears on the next nightly run once the balance is under the limit. |
| Order suspended order_suspended | HO suspended the sale order this part belongs to, so its waiting parts were paused. Any reserved stock was freed. The customer is not notified. | Resume the order — that releases exactly these parts and nothing else. Don't Unsuspend the move by hand: while the order is suspended the nightly job ignores its parts anyway. |
| Manually held by admin/manager manual_hold | A colleague suspended this move by hand. This is the only reason a person can pick from the Suspend dropdown — every other reason above is applied by the system. | Read the remark left on the move, resolve whatever it describes, then Unsuspend. |
Nine of the automatic holds release on their own once their cause is gone: full_set_payment, min_payment_allocation, credit_insufficient, cod_in_transit, rbp_in_transit, return_pending, carrier_unserviceable and — since November 2026 — payment_pending and credit_limit. The nightly job re-checks held moves before it does anything else, so when the payment is allocated, the credit balance comes down, the set is paid in full, the COD money comes in, the return is reconciled or the serviceability record is corrected, the move is released and reserved in that same run. Fix the cause and leave it — nobody has to press anything.
Two holds wait for a person. manual_hold was applied deliberately by a colleague, so only Unsuspend releases it. order_suspended is released only by resuming the order.
A hold on a move that is already on a picking wave stops that wave being despatched until the move is taken out with Remove suspended moves (see Picking Waves) or released.
Suspended and cancelled orders are skipped. The nightly job neither reserves nor releases any part of an order that is suspended or cancelled — even one held by a self-clearing hold. order_suspended clears only when the order is resumed; cancelling an order cancels its waiting parts outright.
Out-of-stock is not on this list, and never appears as a hold reason. A move that can't be reserved for lack of stock is simply left Confirmed and retried on the next nightly run — no suspension, nothing for you to clear.
Bulk actions and forms
There are no bulk actions on this list — every move is actioned one row at a time. This is a read-only base resource: no create page, no edit page, no delete. The only forms are the small ones opened by Suspend described above; Override holds and the Stop all later parts switch on Cancel; Unsuspend and Reserve now are single-click confirmations.
Related pages
See Stock on hand to watch qty_reserved rise and fall as moves are reserved, suspended, unsuspended or cancelled; Picking Waves for how a wave's Despatch action ships every one of its reserved moves in one cascade; and Schedulers for the daily auto-reservation job that advances Confirmed delivery moves to Reserved.