Explain stock position and inventory value

Cockpit is where the stock question starts because it brings Total Stock Value, On Hand Quantity, Reserved Quantity, Available Quantity, In Transit Quantity, Low Stock Products, Negative Stock Exceptions, Open Transfers, and Open Counts into one operational read. The point is not to memorize the dashboard. The point is to choose the right investigation path from the first signal.

Teach learners to use the matching widget instead of wandering across tabs. Low Stock Queue, Reservation Queue, Stock Aging by Lot, Transfer Pipeline, Negative Stock Exceptions, and Count Variance Queue are all clues about where the explanation should go next.

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

Balances is the first place to prove what the system believes by product, warehouse, and bin. It shows On Hand, Reserved, Available, In Transit, and Last Transaction together so teams can stop arguing from a single available number with no location context.

Lot Balances is the next hop when the answer depends on a specific lot rather than the aggregate product position. That matters when shelf life, quarantine, or lot aging is the real reason the business cannot treat all stock as equally available.

For Balances turn the signal into persisted quantity, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Items, Product Profiles, Warehouses, Bins, Lots, and Serials are the master-data tabs that explain how stock is allowed to behave. If an item is configured poorly, if warehouse or bin structure is unclear, or if lot and serial controls are incomplete, later balances and transactions can look confusing even when the system is doing exactly what it was configured to do.

Teach learners to inspect master data before assuming the ledger is wrong. Many stock disputes are really setup disputes that only become visible when the team starts moving goods.

Use this section to confirm the learner understands more than the page label. They should connect Master data explains why the number behaves that way to the business state, owner, and consequence behind it.

The Transactions tab is the chronological proof surface. It is where the team confirms whether the relevant receipt, issue, reservation, reservation release, transfer dispatch, transfer receipt, adjustment, or count posting actually exists in the ledger.

That changes the quality of the conversation. Instead of saying stock looks wrong, the team can ask which movement posted, which movement never posted, and which source document created the current state.

Use this section to confirm the learner understands more than the page label. They should connect Transactions prove whether the movement actually happened to the business state, owner, and consequence behind it.

Quantity alone is not enough when finance or margin reporting disagrees with operations. Cost Layers lets the team inspect the remaining quantity, unit cost, valuation method, and layer evidence behind the stock value, then drill into audit for the selected layer when needed.

Teach learners not to split quantity and value into separate stories. If the stock position is being explained properly, both the physical quantity and the current value should become clearer together.

For Cost Layers answer the value side of the same question, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Audit is the place to move from transaction to proof. The trace path shows source document, transaction reference, balance impact rows, and cost-layer evidence, while Warehouse Reconciliation View summarizes On Hand Qty, Reserved Qty, Available Qty, Layer Stock Value, and Open Cost Layers for the chosen product and warehouse.

That is the right end state for this lesson. Before the business creates a reservation, posts a count, starts a transfer, or books an adjustment, it should be able to explain what the current stock record means and why.

Use this section to confirm the learner understands more than the page label. They should connect Audit closes the argument with trace and reconciliation to the business state, owner, and consequence behind it.

Exceptions, Rules, Events, Jobs, and Optimization are the tabs for recurring inventory intelligence. Exceptions show operational breaks that need ownership, Rules define how the system evaluates conditions, Events preserve what the system observed, Jobs show background execution, and Optimization helps teams improve movement and replenishment decisions.

Those tabs should be taught as management surfaces, not as decorative advanced screens. When a stock issue repeats, the team should look for the rule, event, job, exception, or optimization signal that explains why it keeps returning.

Use this section to confirm the learner understands more than the page label. They should connect Intelligence tabs turn repeated issues into managed work to the business state, owner, and consequence behind it.

Run the lesson as a stock-evidence investigation. Start with the practical task: start with Cockpit signals and choose the right drill-down path instead of reacting to one isolated number. 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 answer the real stock question with evidence: start from Cockpit, prove quantity in Balances and Lot Balances, confirm movement in Transactions, reconcile value in Cost Layers, and close disagreements in Audit before anyone changes the record.

Close the exercise by asking the learner to restate the objective in operational terms: start with Cockpit signals and choose the right drill-down path instead of reacting to one isolated number. 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: start with Cockpit signals and choose the right drill-down path instead of reacting to one isolated number.

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