Sales demand analysis

Stage 2 · Analysis

The operator jobs behind Sales searches

Interpret observed language, identify required evidence, and preserve record authority before proposing Tools.

  1. 1

    Close and understand one service date

    Review completed Sales, gross Sales, completed-Sale count, average Sale, item quantity and item Sales for the Kitchen-local day.

    The current producer proves completed Order gross Sales only. Refunds, discounts, tax, tips, tenders and net Sales remain absent unless their owning producers exist.

    Evidence: restaurant daily sales report · restaurant close of day report

  2. 2

    Reconcile totals to completed transactions

    Trace a period total back to its completed Sales, line quantities, channels, order numbers and accountable closers.

    A bounded PII-free ledger makes the aggregation defensible without exposing Orders, customers, raw actor ids or FinancialFacts.

    Evidence: restaurant sales summary · restaurant item sales report

  3. 3

    Understand what sold

    Review stable item quantities and gross line Sales within the selected Kitchen and period.

    Item rollups use captured Sale lines and stable source identities. Renamed or missing current catalogue items must not rewrite historical Sales.

    Evidence: restaurant product mix report · restaurant sales by item

  4. 4

    Compare equivalent periods

    Compare the same bounded gross-Sales measures across complete owner-local periods.

    Comparisons preserve timezone, currency, range and metric semantics. A change explains what happened, not why it happened.

    Evidence: week over week restaurant sales · restaurant sales by period

Record map

Evidence the capability owns, references, or derives

kitchen.finance.sale

Kitchen Sale

ownedavailable

Owner: Sales

Immutable completed KitchenSale owns the captured gross Sale, item lines, quantities, currency and source identities.

  • Sale and source Order identity
  • completed time
  • currency-safe gross amounts
  • item quantities and captured prices
  • channel, Menu and closer references

kitchen.finance.sales-report

Sales report

projectionavailable

Owner: Sales

The bounded server projection derives gross Sales measures without becoming another Sale or claiming net revenue, payment, cost or profit.

  • Kitchen-local period
  • currency-separated totals
  • counts, averages and item rollups
  • transaction reconciliation and exclusions

Required record questions

What must Sales make knowable?

  • Which Kitchen, owner-local timezone and inclusive date range define the report?
  • Which immutable completed KitchenSales are included and which historical Orders lack canonical Sales?
  • Which currency groups must remain separate?
  • Which exact gross-Sale, item-Sale, delivery-fee, quantity, count and average definitions are used?
  • Which transaction rows reconcile to each aggregate?
  • Which Menu, item, channel, order type and closer identities were captured at the Sale?
  • Which refunds, discounts, taxes, tips, payments or costs are absent rather than zero?
  • Is the selected period complete, bounded and within query limits?
  • Which comparison period uses equivalent calendar and metric semantics?
  • Which deduction is an observation versus an unsupported causal explanation?
Analysis conclusion
Sales owns bounded reporting over immutable completed KitchenSales. The current evidence proves gross Sales, counts, averages, quantities, item rollups, delivery fees and reconciled transaction summaries—not net revenue, payments, costs, profit or accounting.
Review proposed Tools