> ## Documentation Index > Fetch the complete documentation index at: https://docs.aimventory.com/llms.txt > Use this file to discover all available pages before exploring further. # Put away and locate stock > Place received stock in the right shelf or bin and verify where AIM records it. ## Goal Put received stock in the exact shelf, bin, or rack where your team will find it again. For a valid received unit, putaway records its sublocation inside its existing location. Placement keeps Available unchanged and does not mint stock, transfer ownership, change condition, or change the receiving quantity. Clearing a putaway step can change pending-workflow and derived Ready to list state; listing automation your business has set up may be triggered, but this page does not promise a listing. ## Who should use this Use this workflow when stock has finished the receiving step that creates the inventory record and you are working from the Putaway Station or a purchase-order putaway view available for your business. It covers both surfaces when they are available. ## Before you start * Confirm that the purchase order has a receiving **location**. Receiving is blocked until a location is assigned. * Confirm that the destination **sublocation** exists inside that location. A location is the building or warehouse; a sublocation is the exact shelf, bin, or rack inside it. * If receiving shows **Queued**, wait for the receiving work to finish. Queued receiving is not the same as completed receiving. * Have the destination sublocation code ready. In serial mode, have the AIM serial label for each physical unit; in aggregate mode, have the supported AIM item barcode. ## Keep these terms separate | Term | What it means here | What it does not mean | | --------------------- | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Received** | A purchase-order line or receiving event has recorded stock as received. | It does not prove the item is in its final shelf or bin. | | **Pending receiving** | A received unit is still held by a post-receive step your business has set, such as putaway. | It is not an unreceived shipment and is not the same as a physical location. | | **Physical unit** | One physical item with its own identity and, when applicable, cost and serial history. | It is not a counter value or a number of interchangeable rows. | | **Available** | The inventory pool AIM draws from when something sells. | It is not a count of everything physically sitting in the building. | | **Ready to list** | The portion of Available that remains after damaged, still-processing, and quarantined stock is held back. | It is not a promise that a marketplace listing was created. | | **Location** | The warehouse, store, or other receiving destination assigned to the stock. | It is not the exact shelf or bin. | | **Sublocation** | The exact shelf, bin, or rack inside a location. | For a valid received unit, it must belong to that unit's existing location. If the unit has no valid location, stop and escalate rather than treating the target as a transfer. | Receiving can put stock into Available while a post-receive step your business has set still holds it back from Ready to list. Completing putaway clears the putaway step for the placed unit; Available remains unchanged by that placement. The pending-workflow count and derived Ready to list state may change when putaway was the remaining hold, while other pending steps or holds can still keep it out of Ready to list. ## Fictional example Northstar Kicks receives a fictional purchase order into **Main Warehouse**. The receiving operation completes for two physical units of one size, and one unit still appears in **Items Pending Putaway**. The operator scans the fictional sublocation code **MW-A-03**, then scans that unit's fictional AIM serial label. AIM reports the unit as placed, clears that unit's pending putaway step, and records the same unit at MW-A-03. The operator checks the pending list and Recent Putaways or the item's placement context to verify the result. The example keeps Available, ownership, condition, and receiving quantity unchanged. Clearing the remaining putaway step may change pending-workflow and derived Ready to list state. The page remains scoped to scanner placement and makes no promise about label output or a marketplace listing; listing automation your business has set up may be triggered without guaranteeing a listing. ## Process | Step | Where in AIM | What you do | What you should see | | ----------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1. Confirm the starting state | Purchase order receiving | Make sure the PO has a receiving location. If receiving is queued, wait for its completion before looking for putaway work. | The stock has a receiving record, and any remaining putaway work is shown separately from the PO's received state. | | 2. Open the worklist | **Putaway Station** or the PO's putaway view | Use Putaway Station for scan-based work. Where the supported unit-ledger PO view is available, use only the candidates shown for that PO and its location. | Items or units that still need putaway, plus the sublocations available at the relevant location. PO candidates are live and attributable to that PO when that view is available. | | 3. Set the destination | Putaway Station | Scan the sublocation code first, or select the sublocation in the fallback control. Keep the destination set while you process the matching stock. For a valid received unit with an existing location, use only a sublocation inside that location; if the unit's location is missing or malformed, stop and escalate instead of placing it. | The destination is locked for the scan session and belongs to the stock's existing location when the unit has a valid location. If the unit is locationless or malformed, stop for review. | | 4. Place each unit | Putaway Station | In serial mode, scan one AIM serial label per physical unit. In aggregate mode, scan the supported item barcode once for each physical unit. | The unit is placed in the selected sublocation and its pending putaway step is cleared. Available stays unchanged; if that was the remaining workflow hold, pending-workflow and derived Ready to list state may change. Other pending steps can continue to hold that unit back. | | 5. Allocate PO candidates when applicable | PO putaway view | In a supported unit-ledger business, assign a positive amount from the displayed PO-attributable unassigned amount to a sublocation at the same location. Split across bins only when the view shows the candidates and destinations. | The source and destination remain the same inventory item; the unit placement and putaway status update while Available stays unchanged. | | 6. Resolve a placement conflict | Putaway Station | If the scan reports that the unit is already in the target, continue. If it is in another sublocation, choose **Leave it** or explicitly confirm **Move here**. | An already-here scan creates no quantity adjustment or placement-history entry, but it may clear a still-pending putaway step. An unconfirmed relocation does not move the unit. A confirmed relocation reports the new sublocation. | | 7. Verify the result | Items Pending Putaway, Recent Putaways, or item placement context | Refresh the worklist and inspect the current sublocation and recent history. For PO work, check the remaining putaway count. | The completed unit is no longer in the unassigned pending queue and the intended sublocation is shown. Actual placements identify the action in placement history; an already-here result has no placement-history entry. | ## Supported variants and boundaries ### Serial workflow When your business uses the serial workflow, process one AIM serial label per physical unit. AIM checks the business, barcode, active status, and unit identity before placing it. Serial values can be hidden in placement and history views when serial reads are disabled for the business. ### Aggregate putaway When the Putaway Station is in aggregate mode, scan the destination and then the supported item barcode once for each physical unit. This is still a physical placement workflow: it does not authorize a free-form quantity or create stock without a matching unit. If the station cannot resolve the barcode or does not show a supported aggregate worklist, stop and correct the item or use the workflow your business has enabled. ### Purchase-order putaway Where the supported unit ledger is available, the PO view works from live PO-attributable unassigned units at the PO's location. It excludes consumed, unreceived, and pre-receipt rows. A location without sublocations cannot accept PO putaway, and a destination from another location is rejected. If the PO view shows no candidates, do not invent a quantity or assign stock from another PO; use the supported scan workflow or stop for review. Placement leaves Available unchanged and does not mint stock, transfer stock between locations, change ownership or condition, or change the receiving quantity. Clearing the putaway step may change pending-workflow and derived Ready to list state. Use the separate workflow for a location transfer or an inventory correction when the evidence supports one. ### Listing automation boundary Clearing a putaway step can trigger listing automation your business has set up. That trigger does not promise that a listing will be created or succeed. This page stays scoped to the scanner/placement path and does not define listing results. ## Safe correction and restart * **Receiving is queued:** wait for the receiving operation to finish before treating the unit as pending putaway. A queued response is not a completed receipt. * **The scan is repeated at the same destination:** AIM returns an already-here result. It creates no quantity adjustment or placement-history entry, but it may clear a still-pending putaway step. Do not make a quantity adjustment for a duplicate scan. * **The destination is wrong:** for a valid received unit, leave it where it is, or explicitly confirm the move after AIM shows the current sublocation. The unconfirmed relocation path does not change placement. * **The unit has no valid location:** stop and escalate for review. Do not scan it into a destination or treat a missing location as permission to transfer it. * **The last placement was wrong:** open Recent Putaways and choose Undo while the unit is still unconsumed. Undo returns one physical unit to pending putaway, clears its current sublocation, leaves Available unchanged, and records a reverse history entry. A consumed unit cannot be reversed through this control. * **The PO allocation fails:** stop at the validation message. Do not retry with a different location or a made-up amount; confirm that the PO, inventory item, destination, and displayed unassigned amount are the ones you intend. ## Check it worked 1. Refresh **Items Pending Putaway**. The placed unit should no longer appear in the unassigned pending list. 2. Check the current placement in the item's unit or assignment context. The location should be the same location used for receiving, and the sublocation should be the destination you selected. 3. Check **Recent Putaways** for the operator, destination, and time. For a PO batch, check the PO's remaining putaway count and status. 4. Read **Available** and **Ready to list** separately. Putaway records where the physical unit lives and leaves Available unchanged. Clearing the final pending workflow hold may change pending-workflow and derived Ready to list state. Listing automation your business has set up may be triggered, but a listing is not guaranteed. ## What was recorded For an actual placement or an explicit relocation, AIM records the unit and destination in placement history and writes a zero-delta inventory history row: the before and after quantity are the same and Available remains unchanged. The record includes the actor, destination, unit reference when available, and the putaway action. A repeated already-here scan creates no quantity adjustment or placement-history entry, but it may clear a pending putaway step. Undo returns one physical unit to pending putaway with Available unchanged, writes a reverse history row, and links it to the placement it reverses. ## Related * [How the inventory numbers fit together](/concepts/inventory-numbers) — keep Available, Ready to list, and pending receiving distinct. * [Product, inventory, listing: what each one is](/understand/product-inventory-listing) — see how inventory items and physical units relate. * [Ready to list and channel sellability](/understand/channel-sellability) — understand why a channel result is not the same as AIM's Ready to list number.