Supervise WMS control tower and warehouse tasks

The WMS runtime starts with Control Tower, not with a theoretical wave screen. Metrics, alerts, watchlists, and SLA policies are the first layer of truth when the team needs to know whether inbound health, putaway ageing, or blocked flow is starting to threaten service quality.

Teach learners to use that signal layer properly. Alerts should point the team toward the affected source entity and source entity id, but the alert itself is not the fix. It is only the pointer to the actual session, task, or exception that needs action.

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

Receiving Sessions are the inbound control point for GRN-backed stock that is still waiting on QC and directed putaway. Directed Putaway Tasks then move accepted stock from temporary or receiving locations into the final bin that the business can treat as allocatable.

That distinction matters because visibility is not readiness. Stock can appear in conversation before it is actually ready for downstream commitment, and this lesson should teach learners to prove that difference rather than gloss over it.

For Receiving and putaway define when stock is truly ready, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

The Mobile Scan Console is where the warehouse confirms task execution for pick and putaway work. Selecting the warehouse task, scanning a value, providing quantity when needed, and confirming the scan is stronger evidence than assuming the task completed because someone said it did.

The Warehouse Task Queue is the companion proof surface. It shows task number, task type, status, product, origin, destination, and quantity so the operator can confirm the selected task matches what is really happening on the floor.

Use this section to confirm the learner understands more than the page label. They should connect Mobile scanning is execution proof to the business state, owner, and consequence behind it.

When flow breaks because of damage, blocked stock, rejected receipts, or failed jobs, the right next stop is the Exception Queue. Assign, approve, reject, resolve, and retry actions are part of warehouse control, not cleanup after the fact.

Rollout Controls is the final disambiguator. Inbound, outbound, mobile, costing, and optimization features are enabled tenant by tenant, so the team must confirm the rollout stage before treating a missing task flow as an execution defect.

Use this section to confirm the learner understands more than the page label. They should connect Exceptions and rollout controls explain the remaining failures to the business state, owner, and consequence behind it.

Run the lesson as a warehouse execution drill. Start with the practical task: use control-tower metrics, alerts, watchlists, and SLA policies to decide which warehouse issue needs action first. 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 warehouse leads to use the real WMS control surfaces that exist today: start from control-tower metrics and alerts, confirm inbound work in receiving sessions, move accepted stock through directed putaway, validate execution in the mobile scan console, and use exceptions or rollout controls when the flow breaks.

Close the exercise by asking the learner to restate the objective in operational terms: use control-tower metrics, alerts, watchlists, and SLA policies to decide which warehouse issue needs action first. 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: use control-tower metrics, alerts, watchlists, and SLA policies to decide which warehouse issue needs action first.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain when Control Tower is enough and when the investigation must move into sessions, tasks, or exceptions 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 Control Tower is enough and when the investigation must move into sessions, tasks, or exceptions, keep the lesson in practice mode before marking it complete.