Launch decision record
Review what a marketplace owner would approve, defer, or block before turning a commerce demo into a live resale marketplace.
Decision Summary
- Launch review should separate what is approved for a first market, what is deferred, and what blocks public service activation.
- Each decision needs owner, date, route evidence, customer impact, support impact, and rollback trigger.
- The first launch should focus on categories where item proof, seller readiness, and local handoff make the marketplace stronger.
Approved Scope
- Customer storefront, search, listing detail, auction detail, seller tools, hub pages, cart review, reports, and account activity are reviewable in the demo.
- Owner review can approve a focused first wave by category, hub city, seller cohort, support hours, and allowed handoff methods.
- Approved scope should list the exact routes, services, policies, and staff roles being activated.
Deferred Items
- Items can be deferred without blocking launch when they are outside the first category, hub, seller, or support scope.
- Deferred work should retain a target owner, next review date, buyer or seller impact, and dependency notes.
- Public copy should not imply deferred services are available before they are staffed, tested, and approved.
Blocking Items
- Payment execution, seller payout setup, identity review, support staffing, legal approval, domain switch, and incident response must be resolved before launch.
- Any blocked item should show why it blocks launch, who owns it, what proof clears it, and what customer-facing behavior is affected.
- Blocked items should remain visible in operator review until retested.
Rollback Controls
- Every launch wave needs triggers for pausing new listings, pausing auctions, disabling checkout, stopping seller onboarding, or switching domains back to placeholder mode.
- Rollback notes should include customer notice, seller notice, support script, staff owner, and verification steps.
- Service owners need authority boundaries before acting during a live issue.
Evidence Checklist
- Review package validation, route checks, noindex posture, placeholder domains, secret scan, Supabase read views, policy pack, access audit, and service activation evidence.
- Use the demo map for customer flows and the operator console for launch, finance, routes, workflows, and service levels.
- Final approval should record who accepted each area and what remains outside the launch scope.
Owner Handoff
Evidence bundle, activation gaps, ownership controls, deployment safety, and acceptance checks.
Launch Rehearsal
Timed launch practice, route checks, service watch, support drills, rollback, and approval evidence.
Service Activation
Checkout, payouts, identity, notifications, media evidence, carriers, support, and launch guardrails.
Launch Waves
Category sequence, seller cohorts, hub staffing, support pressure, and rollback gates.
Access & Audit
Role permissions, staff actions, approval records, privacy boundaries, and launch review.
Privacy & Data
Notice, retention, processor review, staff access, and launch approval.
Security Response
Incident readiness, access events, provider issues, evidence, and rollback.
Policy Pack
Buyer, seller, hub, payment, privacy, support, and approval ownership.
Terms & Consent
Accepted versions, notices, consent choices, withdrawal paths, and owner sign-off.
Unit Economics
Fees, hub services, seller releases, refund pressure, support cost, and owner review.
Monetization Controls
Fee lines, sponsored placement, seller notices, buyer labels, reporting, and rollback controls.
Payment Readiness
Authorization, credits, seller releases, refunds, chargeback review, and tax readiness.
Tax & Records
Seller statements, retained records, exemption review, finance approval, and owner sign-off.
Delivery & Pickup
Shipping, hub pickup, local pickup, QR release, issue handling, and logistics launch review.
Service Health
Storefront, checkout, listings, search, hub pickup, messages, support, and provider checks.
Domain Launch
Placeholder domains, DNS cutover, SSL, noindex release, monitoring, and rollback authority.
Compliance Readiness
Payment posture, seller verification, tax records, consumer protection, privacy, and launch gate.
Support Operations
Staffing, evidence handoff, response targets, refund authority, appeals, and quality review.
Insurance & Claims
Coverage rules, claim timing, seller holds, hub responsibility, and finance reconciliation.
Integration Evidence
Route coverage, data-layer views, deployment checks, noindex controls, and guard scripts.
Current demo state
The decision record is reviewable.
The demo shows approval scope, deferred items, blockers, rollback controls, and evidence links as static owner-review surfaces.
Future platform state
Public launch needs signed ownership.
Launch rollout needs named approvers, retained decision history, incident contacts, launch-wave controls, service activation proof, and rollback authority.