GWP Daily Issuance Tracker

This template records how many gift-with-purchase units were issued on a given day, tied to a qualifying spend threshold. It also captures starting and remaining allocation so you can see when stock or promo units are running low. Use it when a campaign needs controlled issuance rather than ad-hoc handoffs. The stop-issue fields help document when distribution should pause.

It is usually completed by the store associate, cashier, promo coordinator, or location lead who actually issues the gift-with-purchase item. A manager or supervisor should review exceptions and sign off on the record. If multiple people issue units in one day, assign one person to consolidate the log to avoid duplicate counts. The recorded_by and reviewed_by fields make ownership clear.

Complete it daily, and update it during the day if issuance is tracked in real time. If your campaign is high-volume, log entries at each shift change or each allocation update so the remaining balance stays accurate. Waiting until the end of the week increases the chance of over-issue and missing the exact stop-issue moment. The date field should reflect the actual issuance day, not the review day.

Set allocation_status to indicate the campaign is closed or paused, record the stop_issue_notice_issued field, and note the time the notice went out. If any units were issued after the allocation was exhausted, mark over_issue_flag and explain the exception. This creates a clear audit trail for inventory reconciliation and manager follow-up. The form should show whether corrective action was taken.

The biggest mistake is entering units_issued_today without updating remaining_allocation, which makes the log unreliable. Another common issue is leaving exception_reason blank when an over-issue occurs or when the stop-issue notice was delayed. Teams also sometimes use free text for counts instead of numeric inputs, which leads to validation problems. Keep the threshold and allocation fields consistent with the actual campaign rules.

Yes, you can rename campaign_name to match a specific promotion, product line, or store event. You can also add conditional logic for different thresholds, locations, or gift tiers if your program has branching rules. If some locations do not need exception tracking, keep the core issuance fields and hide extras with progressive disclosure. The template is meant to be adapted without changing the daily control structure.

It can be paired with POS, inventory, or campaign reporting workflows by using the same campaign_name, location, and date fields. Many teams export the log to reconcile issuance against stock movement or qualifying transactions. If you connect it to another system, keep the field definitions aligned so units_issued_today and remaining_allocation mean the same thing everywhere. That reduces manual re-entry and reconciliation errors.

A structured form gives you required fields, validation, and a consistent review path, which are hard to enforce in ad-hoc notes or messages. It also creates a cleaner audit trail for stop-issue events, exceptions, and manager sign-off. Spreadsheets can work, but they often miss the exact time a notice was issued or who reviewed the record. This template is better when you need repeatable daily control across locations.