Dress rehearsal

Production dry run

One complete pre-launch run: order, email, support, refund/recreate, mobile smoke, analytics note, and rollback.

Launch starts not with fanfare, but with one boringly successful order.

Prepare the dry-run window

Choose a window when the owner is available, support is open, Vercel logs are visible, Stripe Dashboard is open, and real users are not flowing in yet.

Preview and production URLs written down.
The go/no-go owner is known.
There is a place for notes and screenshots.

Run one order

Run one controlled order like a normal user: question, method, checkout, webhook, access, email, and archive.

Order received paid status.
Customer path does not show internal IDs unnecessarily.
Email and recovery work.

Break it gently

Check lost link, duplicate webhook, support lookup, refund/recreate decision, and rollback note.

Support can find the order without a secret.
Refund/recreate decision written.
Rollback owner knows the button.

checklist

What to check

Dry-run window scheduled.
One order completed.
Emails checked.
Support ticket closed.
Mobile smoke completed.
Rollback drill understood.
Go/no-go written down.

red flags

When to stop

Team says: we will check after ads.
Webhook is not proven, but checkout works.
Support does not know where to find an order.
There is a manual workaround without instructions.

done when

Definition of done

Dry run passed end-to-end.
Every issue has an owner and resolution.
Final launch QA updated after dry run.