All resources

Use caseOperations

Stock Is Available. Why Are Orders Shipping Late?

Investigate late orders in AIREA with original promises, historical stock readiness and a reviewable handoff.

Late orders do not always mean a stock shortage. In the checked reference case for this guide, East has six late lines among ten eligible October order lines and West has four among ten. Four of East's six late lines had sufficient usable stock allocated and no release blocking hold at the agreed cutoff. Three of those four were released by 08:00 the following morning. These are checked reference figures, not an observed AIREA output or a customer result. They point to a release process worth reviewing; they do not establish why the orders waited.

Download the operations practice pack

Use the guide during an AIREA demo or pilot. The workbook records what you observe; the reference pack holds a separate checked case. Confirm an approved source for your product run. The CSVs are not an AIREA upload instruction.

  • AIREA product walkthrough

    Investigate late orders, inspect generated outputs and lineage, then review and share an Analysis Result.

    PDF · 8 pages
    Download PDF guide
  • Practice workbook

    Compare observed AIREA answers with the checked reference and record discrepancies, owners and the handoff decision.

    Excel · 6 worksheets
    Download Excel workbook
  • Reference records

    Review the example source tables, counting rules and expected results used in the walkthrough.

    ZIP · 8 CSVs and instructions
    Download reference pack

The walkthrough shows how to test this investigation in AIREA during a demo or pilot and record what the product actually returns.

Prepare the source and counting rules

The reference case has 22 original order lines across two warehouses, with dispatch events and historical allocation and release records. For a product run, confirm that an approved source with the necessary fields is available to AIREA. This guide does not assume a particular import or connector setup.

Count each original order line once, combining partial dispatches. An eligible line is late when its full required quantity was not dispatched by the end of its original promised local day. The comparison uses original promises in October 2026, dispatch records through November 5 local day end and America/Toronto time. Keep eligible open lines, exclude full cancellations on or before the original promise and leave a missing original promise unresolved.

Explore: ask which warehouse needs attention

Start an analysis in Ask AIREA:

Compare East and West order lines originally promised for dispatch in October 2026. Count each original line once, combining partial dispatches. Use the original promised local day and dispatches through November 5. Keep eligible open lines, exclude full cancellations on or before the promise and show missing original promises separately. Give eligible lines, late lines and the late rate by warehouse.

The checked reference has 20 eligible lines: East has 6 late of 10, or 60%, and West has 4 late of 10, or 40%. One line was cancelled before its promise and one lacks an original promise. East is the first group to inspect in this small case because it has more late lines at equal volume. This is a review priority, not an explanation of cause.

Ask a further question for the six East late line IDs and their status. The reference IDs are E01, E03, E04, E06, E08 and E10. Four completed late, E06 remains open and E10 was cancelled after its promise. Compare the IDs and counts with the Generated Outputs you actually see. A matching total can still conceal a different line classification.

Analyze: inspect the answer and its source

Open a Generated Output in full view and switch from Output to Lineage. Review How It Was Made and Process Steps in Lineage View, then compare the output with source records. These steps make the work inspectable; they do not prove it is correct.

E03 is a useful check. Four of its ten units were dispatched on the promised day and six followed later, so it is one late line. C01 was cancelled before its promise and is excluded. M01 has no original promise, so its October eligibility is unresolved. If AIREA classifies one differently, check the source record, rule and generated analysis before relying on the answer.

Explore further: what was ready to move?

Today's stock balance cannot show what an order line could use at its release cutoff. Ask AIREA to compare the six East late lines with usable allocated units and active holds at 17:00 on each original promised day. Show which lines were ready, not ready or unresolved, then ask when the ready lines were released.

In the checked reference, E01, E03, E04 and E08 were ready; E10 was not ready and E06 has no historical snapshot. Of the four ready lines, E01, E03 and E08 were released by 08:00 the next local morning; E04 was later. Keep E06 unresolved rather than treating missing history as zero or a confirmed shortage.

The timing pattern supports a focused review of release rules and exceptions with the warehouse lead. It does not prove why release waited or whether an earlier release would have prevented each late dispatch.

Analyze and share a reviewable result

Pin the warehouse comparison, East line detail and readiness and release outputs as Pinned Evidence. In Key Context, record the original promise rule, local time zone, November 5 review cutoff, 17:00 readiness rule and the unresolved E06 and M01 records. Generate an Analysis Result and check that it preserves the counts, missing evidence and unconfirmed cause.

Share the current Analysis Result with the intended colleague, with its Pinned Evidence and Key Context attached. If the evidence or context changes, generate the result again before sharing. Ask the colleague which lines they would investigate, what supports that choice and what remains unknown. Record whether the handoff worked in the workbook.

The downloadable guide gives the exact prompts and a checked reference answer. The workbook lets you compare those answers with what you observe in AIREA. Bring one approved operating question and its source to an AIREA pilot discussion.

Bring your next business question.

Explore how AIREA could fit the way your team works.

Join the pilot