Operate

Record the movement while the goods are moving

Handle purchase receipts, transfers, picks and returns with visible exception ownership.

Separate the promise from the physical event

A purchase order describes what was ordered; it does not establish that the goods are now usable on your shelf. Likewise, a customer order may reserve stock without proving that someone has picked or shipped it. Before reading the movement guides, use the on-hand-versus-available prerequisite if those quantities are being treated as interchangeable. The barcode-plan prerequisite is useful when scanning enters the handoff, because identifying a label does not decide whether a receipt or transfer is complete. These cross-chapter references support the seven operating guides below; they do not turn setup work into a daily warehouse transaction.

Receive what arrived and isolate what did not match

A receiver needs enough detail to connect the delivery to its expected order without pretending that expectation is the result. Count the received quantity in the agreed unit, record the relevant date and location, and separate damage, wrong items or short quantities from normal stock. A fictional order for thirty pieces that arrives as twenty accepted pieces and two damaged ones has at least three facts: the expectation, the accepted receipt and the exception. The receiving, partial-delivery and wrong-delivery guides handle those facts separately. Purchase-order status then helps the buyer decide whether to follow up, close a remainder or arrange another action within the supported workflow.

Keep transfers and picks connected to their origin

A transfer is not merely an increase at a destination. Someone must be able to explain what left the origin, whether it is still in transit and what arrived. A pick similarly needs a connection to the item, location and customer order, particularly when several similar variants share a shelf. The transfer and picking guides suggest checks that can be applied without assuming a particular scanner or application. Test the product-specific status model before relying on it: a one-step movement and a two-step dispatch-and-receipt process expose different information. Use the model that reflects your operation rather than inventing an in-transit state in a note nobody reads.

Return goods through a decision rather than straight to stock

A returned product can be physically present and still unsuitable for sale. Record the return, inspect its condition and route it to the appropriate authorized disposition. Keep the customer-facing refund or replacement distinct from the inventory movement, while retaining a reference that makes the two understandable. If a routine operating step leaves a quantity unexplained, move to the Control chapter instead of making an undocumented adjustment to clear the screen. Assign an owner to the exception and record what remains unknown. This approach takes a little care at the handoff, but it prevents the next person from mistaking a convenient number for a verified available item.

Leave with a repeatable record for each movement and a clear route for mismatches.

9 practical guides

Choose the question closest to yours.

New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.

Start here · Practical guide

A receiving checklist that protects the stock record

Read the guide →
Guide preview

Check identity, quantities, condition and location before turning a delivery into usable inventory.

Bottom line: Receive the units you verified, in the unit and location you verified. Keep discrepancies separate until someone resolves them.

Practical guide

Plan barcodes before buying scanners

Read the guide →
Guide preview

Decide what each scan identifies, where labels belong and how unknown or duplicate codes are handled before rolling out inventory scanning.

Bottom line: Define what a scan should identify and what action follows it before buying equipment. Test actual labels in the intended workflow, including damaged labels, multipacks and unknown codes.