A request needs enough detail to act on
“Do you sell Barcelona shirts?” does not identify a shortage. “I need two of this home design, Player Version, size M” gives you a combination to review. Confirm that the buyer still wants it and clarify any unresolved details before counting it.
A confirmed requirement is not automatically a paid order. Keep your own record of whether it is an agreed request, a reservation or a completed sale. Do not describe an unpaid enquiry as revenue.
Use one count for one requirement
Record demand that still needs to be fulfilled. Do not add last week’s completed sale to this week’s outstanding customer request and call both current demand. Recent sales are useful context, but they are a separate signal.
If several messages concern the same buyer and the same requirement, count the pieces once. Recheck old requests that may have expired, changed size or already been fulfilled.
Pair demand with the stock available to it
Choose a consistent approach to reservations. If a reserved customer request remains in confirmed demand, the matching reserved piece can be counted only against that request—not another buyer. Alternatively remove both the covered demand and its allocated stock from this review. Never exclude reserved stock while retaining already-covered demand by accident.
Check the inputs.
- Exact design or photo reference
- Confirmed version, size and number of pieces
- Requirement still outstanding
- No duplicate messages counted
- Reservation treatment recorded