Giveaway prize inventory: separate wins from fulfillment

The short answer

Giveaway prize inventory: separate wins from fulfillment is not mainly about adding another tool. It is about deciding who records what, at which moment, and how that context reaches the next owner. Track won, fulfilled, missed, and cancelled states so screen counts match physical inventory.

Why this decision belongs before event day

Giveaway prize inventory: separate wins from fulfillment is difficult to improvise once the aisle fills up. One extra field, an unclear owner, or an untested result screen can change wait time and record quality. Put the criteria below into a rehearsal and run one visitor journey from beginning to end on the devices the team will actually use.

What to diagnose first

Inventory problems appear when the only question is how many remain. Separate starting quantity, won but not handed over, fulfilled, no-show, cancelled, and physical remaining stock. Define whether a cancellation returns an item to available inventory or removes it because of damage or loss. Otherwise the screen count can look correct while the physical position is not.

A concrete field example

Label every prize box with the same name and quantity used on screen. A draw increases the won count but does not yet move the item. The fulfillment operator records completion when handing it over and removes it from the box. At a shift change, reconcile three views together: unfulfilled winners, available quantity on screen, and the count of physical items.

Failure patterns to watch

1. Winning and fulfillment are one state, so a reserved prize is accidentally treated as available again.
2. Similar prize types share an unlabeled box and staff decrement the wrong item.
3. A cancellation restores the screen quantity without confirming the physical destination of the prize.

How to know the work is complete

Put the decision on one page

Do not compare feature names alone. Write down how each choice changes staff and visitor behavior in the booth.

A practical workflow

Give every step an owner and a deadline. A checklist without ownership is usually the first thing to fail during a rush.

1. Record initial quantity and the physical storage location for every prize.
2. Separate won, fulfilled, missed, and cancelled states.
3. Count physical stock against the screen during every handoff.
4. When reversing a fulfillment, confirm both the reason and stock disposition.
5. After close, reconcile remaining items with all final results.

1. Record initial quantity and the physical storage location for every prize.

Turn “Record initial quantity and the physical storage location for every prize.” into an observable field procedure. Write its completion condition, owner, backup, and review point, then reproduce one important exception on the actual device. At close, pass unfinished work to a named person so follow-up can understand the result without oral reconstruction.

• Write the completion condition and owner for: Record initial quantity and the physical storage location for every prize.
• Verify one exception and its handoff on the real device.

2. Separate won, fulfilled, missed, and cancelled states.

Turn “Separate won, fulfilled, missed, and cancelled states.” into an observable field procedure. Write its completion condition, owner, backup, and review point, then reproduce one important exception on the actual device. At close, pass unfinished work to a named person so follow-up can understand the result without oral reconstruction.

• Write the completion condition and owner for: Separate won, fulfilled, missed, and cancelled states.
• Verify one exception and its handoff on the real device.

3. Count physical stock against the screen during every handoff.

Turn “Count physical stock against the screen during every handoff.” into an observable field procedure. Write its completion condition, owner, backup, and review point, then reproduce one important exception on the actual device. At close, pass unfinished work to a named person so follow-up can understand the result without oral reconstruction.

• Write the completion condition and owner for: Count physical stock against the screen during every handoff.
• Verify one exception and its handoff on the real device.

4. When reversing a fulfillment, confirm both the reason and stock disposition.

Turn “When reversing a fulfillment, confirm both the reason and stock disposition.” into an observable field procedure. Write its completion condition, owner, backup, and review point, then reproduce one important exception on the actual device. At close, pass unfinished work to a named person so follow-up can understand the result without oral reconstruction.

• Write the completion condition and owner for: When reversing a fulfillment, confirm both the reason and stock disposition.
• Verify one exception and its handoff on the real device.

5. After close, reconcile remaining items with all final results.

Turn “After close, reconcile remaining items with all final results.” into an observable field procedure. Write its completion condition, owner, backup, and review point, then reproduce one important exception on the actual device. At close, pass unfinished work to a named person so follow-up can understand the result without oral reconstruction.

• Write the completion condition and owner for: After close, reconcile remaining items with all final results.
• Verify one exception and its handoff on the real device.

Adapt the method to real field conditions

There is no single giveaway operations setup for every event. Conversation length, booth traffic, staffing, prize handoff location, and the team responsible for first contact all change the right design. Convert the guidance below into questions your team can verify in rehearsal. Remove a field or move a role when the observed result is clearer than the original plan.

Event-day checklist

Before the doors open, pretend one real visitor has arrived and test the full path below.

• Record initial quantity and the physical storage location for every prize.
• Separate won, fulfilled, missed, and cancelled states.
• Count physical stock against the screen during every handoff.
• When reversing a fulfillment, confirm both the reason and stock disposition.
• After close, reconcile remaining items with all final results.
• Visitor QR forms, business card OCR, and staff entry
• Per-lead field notes, ownership, and follow-up status

Measure output and quality together

Lead count alone can make a fast form look successful. If the resulting records cannot support a relevant follow-up, that speed did not create pipeline.

How this maps to BoothCatch today

1. Visitor QR forms, business card OCR, and staff entry
2. Per-lead field notes, ownership, and follow-up status
3. Instant and scheduled giveaways with inventory and fulfillment records
4. Event lead CSV export

A 20-minute closeout review

Review delays and bad records while the event is still fresh. The goal is not to blame an individual. Find the form, signage, role, or physical path that the team can change next time.

• Records missing information needed for first contact
• Duplicates and leads without a clear owner
• The step with the longest visitor wait
• Differences between winner and physical fulfillment records
• Questions to remove or add before the next event

Frequently asked questions