A units target becomes more concrete when compared with the event’s selling window. It still does not tell you how many customers will buy. Use pace as a capacity and plausibility question, then keep observed visitor and transaction counts separate from the planning arithmetic.
Use selling hours, not total work hours
The contribution planner has two time inputs. Selling hours describe when purchases can happen. Total work hours support the optional time allowance and may include making ready, travel, setup and packing down. If a market sells for four hours but takes six hours of your time, use four for pace and six for the work-time scenario.
A constructed target
The worked example needs 12 units to cover $140 of entered event-fixed costs, or 19 units to include a $90 time allowance. Over four selling hours, that is 3 units per hour for the cash-cost threshold and 4.75 units per hour for the time-inclusive target. The tool reports averages, not a claim that sales will arrive evenly.
Units are not transactions
A person may buy more than one item, or a sale may combine products with different contributions. If the scenario requires 19 units, that might be 19 one-unit transactions or fewer multi-unit transactions. Do not call 19 units “19 customers” without a documented assumption. Likewise, event attendance is not a count of people who reached your booth or considered your products.
| Measure | Meaning |
|---|---|
| Units sold | Number of items sold in the defined model |
| Transactions | Completed purchases, possibly with several items |
| Booth visitors | A locally defined observation, if you actually count it |
| Event attendance | Organizer’s broader measure, with its own definition |
Check handling capacity
Ask whether packaging, payment, questions and restocking can support the required pace with the staff available. Use a practice setup to time the actual steps, without pretending that a practice customer represents real demand. Identify a bottleneck you can change, such as unclear pricing or packaging that takes too long.
Review by time block
After the event, record hourly transactions and units if feasible. A strong first hour and slow final hour can produce the same total as a steady day but suggest different stock and staffing choices. Compare the observed pace with the original scenario as an explanation exercise, not as proof that a future event will behave the same way.