Reserve stock and move or adjust inventory

Reservations are where the business protects a promise before warehouse work begins. The runtime expects source document type and id, optional sales-order-line reference, product, warehouse, bin, lot, serial, reserved quantity, and timing fields such as reserved-at and expires-at. That is the minimum evidence set for saying this stock is now committed to something real.

Teach teams not to skip that commitment step. If demand should be protected, the reservation is what stops the same stock from being promised twice while the pick decision is still unfolding.

Evidence should come from cockpit signals, balances, lots, serials, transactions, cost layers, reservations, transfers, adjustments, counts, receiving, putaway, scans, or audit history. For Protect the commitment before touching stock, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

A reservation in `active` or `partially_released` state can either be released or converted into a pick list. Those are different decisions. Release reduces or removes the commitment. Convert To Pick means the warehouse should start execution from the committed stock position.

The converted pick list becomes the controlled execution document. It carries source document type and id, warehouse, and line-level product, bin, lot, serial, planned quantity, and picked quantity. Draft pick lists can be released, and the server only allows close once the list is actually `picked`, which is why line status should move from open to partial to picked instead of being guessed.

For Turn the commitment into controlled pick work, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

When stock has to change warehouse or controlled location, the correct tool is a transfer. The runtime captures transfer number, from and to warehouse, request date, remarks, and line detail such as from-bin, to-bin, lot, serial, transfer quantity, and received quantity. That is the audit trail for physical relocation.

Teach the state sequence deliberately: draft, approved, dispatched, received, then closed. If the business uses an adjustment to solve a location problem, the total may look corrected while the location history and custody chain remain wrong.

Use this section to confirm the learner understands more than the page label. They should connect Move location with transfers, not with corrections to the business state, owner, and consequence behind it.

Adjustments are for record correction, not for workflow shortcuts. The runtime expects adjustment number, warehouse, date, header reason, and line-level product, bin, lot, serial, direction, quantity, unit cost, and reason code so the business can explain exactly what changed and why.

That is why the state gates matter. Adjustments are created in draft, then approved, then posted. If the real issue was missed picking, unreceived transfer stock, or a reservation mistake, fix that upstream process first and do not turn the symptom into a permanent correction.

Use this section to confirm the learner understands more than the page label. They should connect Use adjustments only for true stock correction to the business state, owner, and consequence behind it.

The Transactions tab is where operations prove the branch they chose actually posted. Reservations should produce reservation or reservation-release events. Transfers should produce dispatch and receipt events. Adjustments should produce adjustment-in or adjustment-out events.

That final check is what keeps this lesson grounded. The workflow is not complete because a row changed status; it is complete when the resulting transaction history explains what the warehouse and ledger now believe.

For Confirm the movement in transactions, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Run the lesson as a stock-evidence investigation. Start with the practical task: create reservations with source, product, warehouse, and quantity detail that protects demand before warehouse execution starts. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from cockpit signals, balances, lots, serials, transactions, cost layers, reservations, transfers, adjustments, counts, receiving, putaway, scans, or audit history. The practice should end with the learner connecting the action back to the lesson summary: teach inventory teams to protect demand with reservations, release warehouse execution through pick lists, move stock with transfer states when location changes, and use adjustments only when the stock record truly needs correction.

Close the exercise by asking the learner to restate the objective in operational terms: create reservations with source, product, warehouse, and quantity detail that protects demand before warehouse execution starts. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not let learners correct stock before they can explain the stock state. Quantity, location, value, movement source, and audit evidence should be checked before action. In this lesson, watch for that risk while learners work on this objective: create reservations with source, product, warehouse, and quantity detail that protects demand before warehouse execution starts.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain when to release a reservation versus convert it to a pick list and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot explain when to release a reservation versus convert it to a pick list, keep the lesson in practice mode before marking it complete.