N NoBullshit.wiki 中文

Snack shop marketing planner - group-buy voucher pre-launch checklist - rules, price, photos, redemption, and refund gates, each failed item annotated with the exact review it will become

Works with:Claude / GPT-4 classCategories:Snack ShopLevel:Intermediate Updated

You are a checklist writer for a snack chain's
marketing team. Write a "Snack Shop Group-Buy Voucher
Pre-Launch Checklist" for planners to tick through
before submitting a deal to the platform.

Context paragraph, at the top of the checklist: group-
buy deals fail almost exclusively after launch -
customer arrives, the scale reads over and they owe
the difference, the item they picked is out of scope,
the clerk cannot redeem the code. Every unchecked item
on this list corresponds to a review that will appear
on the platform, so each item is written as: the
check question + the review a failure becomes.

Gate 1 - Rules (wording pinned, no ambiguity)
- If the deal includes bulk items: is the grams
  figure "fixed 100 g" or "100 g minimum,
  over/under settled at register"? Is the overage
  settlement written?
- Is the "any item" scope itemized, or just "anything
  in store"? - clerks blocking customers with "that
  one's not included" is where that ambiguity lands
- Purchase limit, valid hours, weekend/holiday
  validity, combinability with other offers: one
  line each
- Review it becomes: "They said any item, then half
  the store was excluded when I got there"

Gate 2 - Price
- Voucher price vs buying the contents at shelf
  price - can the customer do that math? A deal
  priced above the parts is a review factory
- Margin after platform commission: computed? Does
  it cover the packing and weighing labor?

Gate 3 - Photos
- Are pictured items regular stock? Seasonal or
  soon-discontinued items pictured mean mid-campaign
  stockouts and reviews
- Does the pictured quantity match reality? Angled
  plating that inflates apparent volume gets called
  "shrunk" on arrival

Gate 4 - Redemption (must be tested before launch)
- Has the redemption flow been run once live in the
  POS - not "should be fine," but one transaction
  walked through in front of the planner?
- Is the staff script unified: a few grams over,
  swaps for equal-value items, overage amounts -
  can everyone on shift answer these three the
  same way?
- Peak-hour plan: do voucher holders queue with
  regular customers? Will the after-school rush
  jam at the register?

Gate 5 - Refunds and changes
- Do you know the platform's default auto-refund
  rule on expiry?
- Is the complaint contact and response time written
  into the deal's service script?

Close-out:
- All five gates pass before submission. Any gate
  failed: write which item, who fixes it, and the
  recheck date
- Archive the checklist with the deal - when a
  redemption dispute arrives, pull this first: if
  the dispute point was a checklist item, fix the
  process; if not, add a new item

Constraints:
- Every item must be answerable yes/no; no "rules
  are clear" or "pricing is reasonable"
- Review previews are one concrete sentence, not
  "creates complaint risk"
- No "strengthen pre-launch review" process talk

Why it is written this way

"The review a failure becomes" is the mechanism that makes people actually tick carefully. A checklist's greatest enemy is fast ticking - printed and fully ticked in two minutes, which equals unchecked. Writing each consequence as a literal review sentence ("they said any item, then half the store was excluded") slows the pen: the planner can see, in the customer's own words, what they are about to wave through.

Gate 4's "one live transaction in front of the planner" marks the line between knowing and doing. Redemption is where group buys crash - POS flow, staff script, peak queuing, none discoverable by desk review. "Should be fine" and one walked-through transaction are separated by a pile of traps, and the checklist turns the former into the latter by writing it as an action, not an awareness.

Rules sit first and finest-grained because they are the snack shop's own peculiarities. Gram wording (fixed vs top-up) and the "any item" scope are two ambiguity sources that restaurant deals simply do not have - platform templates will not think of them for you, yet reviews grow here. A generic group-buy checklist cannot be copied to cover these two gates, which is the reason this one exists.

Variables

Variable Description
Deal structure Whether the voucher includes bulk items and whether selection is fixed or pick-your-own - bulk pick-your-own deals need Gates 1 and 4 item by item; fixed bundles can relax

group-buy launchpre-launch checklistredemption