- Scope and timestamp
- Record buyer SKU, pack version, warehouse or site, storage unit, snapshot time and the source report. Identify which locations the report includes. A company-wide total is not automatically usable at a particular customer site, especially when transfers require time or a different packaging configuration.
- Physical quantity
- Record counted or system-reported on-hand quantity and its exact unit. Distinguish the last physical count from the current transaction balance. Reconcile open receiving or dispatch transactions before relying on the snapshot; an old count copied into a new report is not a fresh warehouse observation.
- Quality or condition hold
- Identify held quantities, lot or carton references, hold reason, responsible owner and release status. Keep a forecast release date distinct from an actual release decision. Microsoft documentation shows that blocked quantities and inspected sample quantities can differ; never infer the held scope from the number of packs examined.
- Reservations and commitments
- List the allocation or reservation source, customer or internal purpose, quantity and status. Agree how commitments reduce availability in the buyer system. Do not subtract the same commitment twice because it appears both in an allocation report and in an order-reservation report.
- Incoming quantities
- Record open PO or transfer reference, expected quantity, unit, expected receiving date and conditions before use. Distinguish booked, shipped, received and released stages. Incoming cartons may support a planning discussion while still being unavailable for present dispatch or service use.