Release picks and dispatch outbound shipments

Outbound execution starts from a real reservation, not from a vague promise that the warehouse should somehow pick something later. In the Sales Reservations tab, the Create Pick List action is the formal handoff from protected demand into outbound execution.

That distinction matters because a released reservation and a created pick list do not mean the same thing. Releasing removes or reduces the commitment. Creating the pick list converts the commitment into warehouse work that now needs to be executed and supervised.

Evidence should come from control-tower signals, warehouse task state, receiving sessions, putaway tasks, pick lists, scan confirmation, shipment status, or exception queues. For Turn the reservation into executable work, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

The Pick Lists tab is where the business releases the outbound work. It proves that the warehouse is now allowed to act on the demand. The Warehouse Task Queue and Mobile Scan Console are where the floor proves the action was actually carried out.

Teach learners to keep those surfaces separate. A released pick list does not prove the stock was picked, and a task selected in the scan console does not replace the commercial or outbound record that created the work in the first place.

For Pick lists and warehouse tasks are two different proofs, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Mobile Scanning is the user-facing proof surface for outbound task execution. The operator selects a warehouse task, verifies the task type, origin, destination, product, and quantity, and then confirms the scan with the actual scanned value and quantity when needed.

That is stronger evidence than assuming the pick happened because the order is urgent or because someone on the floor said it was done. The lesson should make scan-backed confirmation the operational truth for outbound task completion.

Use this section to confirm the learner understands more than the page label. They should connect Scan confirmation is the real outbound execution checkpoint to the business state, owner, and consequence behind it.

Shipments are where outbound execution becomes visible to the rest of the business. Shipment number, sales order, customer, warehouse, carrier, service level, shipment date, dispatch date, tracking number, and freight amount define what is actually leaving and how it should be monitored.

Dispatch and Deliver are the critical state changes here. Dispatch means the outbound promise has moved into active movement. Deliver means the business is now asserting downstream completion. Those actions should stay tied to real execution evidence, not to a fictional dock screen that the current runtime does not expose.

Use this section to confirm the learner understands more than the page label. They should connect Shipments express the customer-facing outbound promise to the business state, owner, and consequence behind it.

Run the lesson as a warehouse execution drill. Start with the practical task: create or release pick work from active sales reservations without losing protected demand. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from control-tower signals, warehouse task state, receiving sessions, putaway tasks, pick lists, scan confirmation, shipment status, or exception queues. The practice should end with the learner connecting the action back to the lesson summary: teach WMS operators to use the outbound controls the runtime actually exposes today: convert active reservations into pick lists, release pick work, confirm warehouse execution through mobile scans, and move shipments through dispatch and delivery with real status evidence.

Close the exercise by asking the learner to restate the objective in operational terms: create or release pick work from active sales reservations without losing protected demand. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not let warehouse work become a manual promise. Task state, scan confirmation, exception ownership, and shipment status should stay visible before escalation. In this lesson, watch for that risk while learners work on this objective: create or release pick work from active sales reservations without losing protected demand.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain when to create a pick list instead of releasing a reservation 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 create a pick list instead of releasing a reservation, keep the lesson in practice mode before marking it complete.