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
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
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
- Refresh Items Pending Putaway. The placed unit should no longer appear in the unassigned pending list.
- 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.
- Check Recent Putaways for the operator, destination, and time. For a PO batch, check the PO’s remaining putaway count and status.
- 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 — keep Available, Ready to list, and pending receiving distinct.
- Product, inventory, listing: what each one is — see how inventory items and physical units relate.
- Ready to list and channel sellability — understand why a channel result is not the same as AIM’s Ready to list number.