In-Store Event Planning Checklist

Steps a store manager runs to plan, promote, staff, and execute an in-store event — trunk show, product launch, loyalty night, or vendor demo — from pre-event budgeting through post-event ROI review.

Use this workflow
1

Pre-Event Planning

  1. Define the event objective and target KPIs

    • Name the primary objective — new-customer acquisition, loyalty enrollment, sell-through of a slow SKU, vendor co-op activation — and pick the KPIs that will measure it: door count, conversion rate, UPT, ATV, loyalty signups, attributed comp lift vs. a non-event Saturday.

    Collects list Collects paragraph
  2. Lock the event date against the local calendar

    • Check city event calendars, school district calendars, and competing retailers in the trade area. Avoid the home-team game weekend and the weekend a neighboring anchor runs its own draw. Confirm the date does not collide with a corporate planogram reset or markdown cadence.

    Collects date
  3. Build the event budget and co-op request

    • Line-item the costs: incremental labor hours, signage and print, refreshments, giveaways / GWP, entertainment, security, permits. Estimate income: incremental sales lift, vendor co-op contribution, ticket revenue (if applicable). Submit to district manager for sign-off before any deposit is paid.

    Collects number
  4. Confirm whether alcohol will be served

    • Alcohol service at an in-store event triggers state ABC requirements — most states require a one-day permit, a licensed server, and proof of host liquor liability coverage. Wine-and-cheese trunk shows are the most common case; do not skip this question.

    Collects list
2

Permits and Insurance

  1. Verify ADA accessibility of the event layout

    • ADA Title III applies to the event footprint, not just the everyday store. Keep a 36-inch clear path through fixtures, demo tables, and queue lines. Accessible restroom and checkout must remain reachable.

  2. Pull the one-day ABC permit and liquor liability

    • File the one-day permit with the state ABC at least 14 days out (some states require 30). Bind host liquor liability coverage through the corporate broker — most general liability policies exclude alcohol service. Save the permit copy with the event folder; the server must keep it on-site.

    Collects file
  3. Confirm fire-code occupancy with the local marshal

    • Posted occupancy on the certificate is the ceiling, not a target. For events expected to draw a crowd, call the fire marshal to confirm queueing plan and second-exit clearance. Demo tables and signage often block egress paths without anyone noticing.

3

Marketing and Promotion

  1. Design in-store signage and window graphics

    • Submit artwork to the visual director against the brand template — window cling, A-frame, register talker, fitting-room mirror cling. Print lead time is typically 7-10 business days; build that into the request.

  2. Segment the loyalty list and queue the email send

    • Pull the segment from Klaviyo or the loyalty platform — VIP tier, store-radius ZIP codes, lapsed-90-day buyers. Schedule the announcement send for T-21, the reminder for T-7, the same-day text for T-0 morning. Suppress employees and the do-not-contact list.

    Collects number
  3. Schedule the social posts and paid boost

    • Queue Instagram and Facebook posts at T-14, T-7, T-3, and event day. Geo-target the paid boost to the trade-area ZIP codes; broad-radius boosts burn budget on out-of-market impressions. Tag the vendor partner so they re-share.

  4. Send the press release to local media

    • Local paper community calendar, neighborhood Patch, and any lifestyle blogger who has covered the store before. Editors want copy at least 2 weeks out; same-week pitches rarely land.

4

Staffing and Training

  1. Build the event-day schedule with skills mix

    • Post the schedule in Homebase or 7shifts at least 14 days out — predictive scheduling laws in NYC, Seattle, SF, Oregon, Philadelphia, and Chicago impose premium pay for changes inside the notice window. Confirm at least one key holder, one alarm-trained associate, and a Spanish-speaking associate if the trade area calls for it.

  2. Assign event-day roles to associates

    • Greeter, register, fitter / stylist, demo lead, restock runner, loss-prevention floor walker, closer. Walk each associate through their role; a floor with no defined greeter is a floor where customers wander out.

  3. Train associates on the promo and loyalty offer

    • Walk the team through the discount code, GWP threshold, loyalty signup script, and any vendor talking points. Register the promo in the POS (Lightspeed / Shopify POS / Square) and ring a test transaction to confirm the discount applies correctly before event day.

  4. Brief the team on shoplifting and crowd protocol

    • Larger crowds shift shrink risk — more cover for concealment, distracted associates. Reinforce the observe-document-call policy: do not pursue past the door. Confirm the LP officer (or floor walker) knows the EAS gate response and the police non-emergency number.

5

Floor Plan and Setup

  1. Draft the event floor plan and traffic flow

    • Sketch demo table, queue line, checkout overflow, and re-routed fixture moves. Keep aisles at 36 inches, exits clear, and the planogram end-caps photographable for the post-event corporate report.

    Collects image
  2. Stage event SKUs and confirm on-hand depth

    • Pull the available-to-sell on each promoted SKU. Stockouts an hour into the event kill conversion and burn customer goodwill. Place a rush replenishment order from the DC or vendor-direct if WOS is under expected event lift.

  3. Set up demo tables, fixtures, and signage

    • Install window graphics, A-frame, mirror clings, and register talker per the visual director's photo. Walk the planogram one last time so the floor is reset, not picked-over.

  4. Test POS, payment terminals, and Wi-Fi

    • Ring a test transaction on every register including the pop-up. Confirm chip, contactless, and mobile-wallet acceptance. Event crowds saturate guest Wi-Fi; reserve bandwidth for the POS network or queue an LTE backup.

6

Event Day Execution

  1. Hold the pre-shift huddle and assign zones

    • Twenty minutes before doors. Review goals, promo mechanics, the loyalty signup script, break rotation, and the panic-button protocol. Confirm everyone knows the manager-on-duty for the shift.

  2. Track hourly door count and conversion

    • Log traffic, transactions, UPT, and ATV every hour against the non-event baseline. If conversion is lagging by mid-day, redeploy a floor associate from restock to active selling.

  3. Run mid-event cash drops at threshold

    • Event-day cash volume is multiples of a normal Saturday. Drop every $500 in twenties to the safe — drawers over threshold are the single biggest loss risk in a busy store. Manager spot-checks the X-report at midday.

  4. Log any incidents and resolutions

    • Capture anything that interrupted the event — POS outage, shoplifting incident, medical call, vendor no-show, customer complaint. Include time, response, and follow-up owner. This is the document the district manager will read first.

    Collects paragraph
7

Post-Event Wrap-Up

  1. Reconcile the Z-report and event deposit

    • Pull the Z-report, tie cash to deposit, and reconcile card batches against the processor. Flag any voids, post-voids, or high-refund cashiers for the LP audit list.

  2. Send the attendee thank-you and feedback survey

    • Email the loyalty list that opted in at the event with a thank-you, a short NPS-style survey, and a follow-up offer. Send before the weekend ends — engagement drops sharply by day 5.

  3. Debrief with staff and the vendor partner

    • Forty-five minutes, on the floor, before the next Saturday shift. Capture what worked, what did not, and one change to bake into the next event template.

  4. Submit the event ROI report to the DM

    • Compare actual cost against budget, attributed comp lift against the non-event baseline, loyalty signups, and vendor co-op recovery. Note the ROI and the one change for next time.

    Collects list Collects number Collects number Collects signature