← Back to storefront

Launch checklist (BAIT)

Verify each before going live. Booking and payment stay disabled in the preview until these pass and you approve. No domain is connected; nothing is published.

1 · Dedicated paid calendar + Google conflicts

  • Dedicated HighLevel paid calendar for one-time pickups (adult-run, not a consulting calendar).
  • Payment is required to confirm; unpaid holds release. Verified before enabling the native paid widget.
  • No second public booking link that bypasses payment.
  • Parent-managed Google conflict calendar with generic Busy blocks only — never school, sports, or personal events.

2 · Stripe test configuration & products

  • Stripe connected in test mode using the correct BAIT location credentials — not another brand's.
  • One-time $10 and monthly $30 products configured (Prices). No live payments taken.
  • Recurring card billing explained on the first checkout before signup; first-of-month renewal tested.
  • Idempotent payment/booking process; no duplicate charge or visit on repeat checkout events.

3 · Monthly integration (server-side Stripe)

  • Verify customer & address; show exact remaining visit dates and amount due today.
  • Prorate = lower of (a) $30 × remaining visits ÷ that weekday's occurrences in the month (rounded once to cents) or (b) $30 − eligible prior payments, never below $0.
  • Count only paid, completed one-offs for the same verified customer, address & service month, net of refunds — never twice.
  • $30 on the next 1st (America/Chicago); month-to-month renewal terms shown; affirmative consent required for future charges.
  • A $0 upgrade still requires renewal consent and a valid payment method.
  • Authoritative payment/settlement verified — a success URL, pending status, or trial is not enough.

4 · Capacity & rescheduling

  • Reserve real route capacity before charging — a free-slot lookup is not a hold.
  • Monthly visits get their own capacity or share one reservation system; each weekly visit booked separately with HighLevel conflict validation on.
  • No recurrence shortcut that bypasses conflict validation.
  • If a payment succeeds but the slot is lost: do not show a confirmed booking — handle recovery explicitly.
  • Rescheduling moves one appointment to a verified free slot only, leaving the rest unchanged.

5 · Business contact & disclosure

  • Business contact set for inquiries (no personal phone or full name until approved).
  • No car washing, sanitizing, fabricated reviews, or invented policies.
  • Optional FAQ chat bubble left off until approved.
  • Founder story has no identifying photo/school/full name without approval.

6 · Domain connection (after approval)

  • Domain DungDoctor.com — do not connect or publish until you approve.
  • Other sites, calendar, Stripe, and DNS left untouched.
  • HighLevel domain flow publishes an unpublished project — confirm before publishing.

Test-mode scenarios to prove

  • One-off paid vs unpaid behavior
  • January $20 credit
  • Four-visit and five-visit months
  • Refunds and mismatched dates/addresses
  • $0 due still requires consent + valid method
  • First-of-month renewal, or failure path
  • Two customers chasing one slot
  • Repeated checkout events — no duplicate charge/visit
  • Moving exactly one appointment