Service health
Review the owner-facing checks that show whether the storefront, search, checkout review, hub pickup, messages, support, and provider handoffs are ready to operate.
Storefront Availability
- Customer routes should load the intended page, stylesheet, images, manifest, route links, noindex headers, and current/future boundary copy.
- Placeholder domains should stay ambiguous and separate from the Netlify demo until launch approval changes.
- Route checks should catch homepage fallback, missing images, bad redirects, and broken demo map links.
Search and Listings
- Search results, category pages, item pages, seller pages, and the homepage feed need matching titles, images, prices, seller context, and handoff cues.
- Quality checks should watch empty categories, bad image/title matches, stale auctions, missing seller signals, and incomplete item evidence.
- Saved-search demand should be visible without changing ranking fairness or seller standards.
Checkout Review
- Cart review, buy-now actions, accepted offers, bundles, credits, and handoff choices should stop before payment in the current demo.
- Future checkout needs authorization health, fee math, refund paths, receipts, report windows, and rollback controls.
- Owner review should confirm that checkout, finance, settlement, and policy pages tell the same order story.
Auction Closeout
- Auction pages should preserve reserve status, top bid behavior, bid increments, close timing, winner state, and support holds.
- Health checks should flag auctions with mismatched images, missing reserve state, stale countdowns, or unclear winner follow-through.
- Closeout readiness should connect auction operations, checkout review, settlement review, and support coverage.
Hub Pickup
- Hub routes should show service area, intake hours, accepted categories, item checks, pickup windows, QR release, fees, and issue handling.
- Operators should see capacity pressure, late intake, pickup no-shows, release exceptions, event staffing, and category coverage.
- Customer-facing pages should keep pickup expectations visible before bids, offers, or cart review.
Messages and Notices
- Inbox, message threads, bid alerts, offer updates, support notices, and pickup reminders should link back to the related listing, order, case, or hub action.
- Delivery review should show queued, sent, muted, failed, action-needed, and owner-reviewed states before live notification services connect.
- Required notices should stay separate from optional updates and preference choices.
Support Coverage
- Support queues should show owner, severity, response target, documentation status, seller response, hub proof, and outcome path.
- Health review should watch aging cases, unresolved reports, seller delays, refund exposure, pickup issues, and restricted item appeals.
- Escalation paths should connect support, trust, risk, finance, privacy, and owner approval.
Provider Checks
- Hosting, identity, payment, payout, media, notification, carrier, support, and analytics providers need owner contacts, approval status, and fallback instructions.
- Provider issues should identify affected customer actions, seller actions, staff actions, notice decisions, and rollback authority.
- Launch approval should not proceed until provider ownership and incident contacts are clear.
Marketplace Reporting
Executive reports, service health packets, support outcomes, hub operations, and owner approval.
Launch Rehearsal
Timed runbook, route smoke tests, service watch, support drills, rollback practice, and approval evidence.
Service Activation
Checkout, identity, notifications, media, carriers, support, and launch guardrails.
Event Delivery
Delivery status, retry review, replay controls, owner alerts, privacy limits, and recovery paths.
Security Response
Provider incidents, recovery, evidence, customer notices, and rollback authority.
Traffic Protection
Rate limits, blocked traffic, secure headers, route availability, provider state, and alerts.
Communications
Bid alerts, seller messages, support notices, delivery review, and preferences.
Shipping Rates
Carrier health, rate availability, service rollback, tracking delay, and support fallback.
Notification Preferences
Quiet hours, urgent overrides, provider state, failed notices, consent, and rollback review.
Notification Delivery
Queued, delayed, muted, failed, blocked, and action-needed notice states.
Marketplace Analytics
Demand, liquidity, category health, hub performance, support load, and finance signals.
Catalog Quality
Category fit, required attributes, variants, duplicates, media proof, and repairs.
Search Indexing
Noindex safety, future public page scope, private routes, sitemap, and rollback.
Domain Launch
DNS cutover, SSL, redirects, noindex release, monitoring contacts, and rollback checks.
Support Operations
Queue staffing, evidence handoff, response targets, refund authority, appeals, and quality review.
Hub Network
Service areas, capacity, pickup routing, intake cutoffs, and local events.
Staff Queue
Support, trust, seller operations, hub issues, severity, and ownership.
Employee Accounts
Shift coverage, queue ownership, role boundaries, training, escalation, and access removal.
Launch Decision
Approval scope, blockers, health checks, rollback controls, and evidence.
Owner Handoff
Evidence bundle, service gaps, acceptance checks, deployment safety, and ownership.
Current demo state
Service health is represented as owner review.
The static demo shows service health checks, related routes, provider ownership, support pressure, and launch approval without connecting live accounts, payments, payouts, or outbound notifications.
Future platform state
Service health needs connected signals.
A live marketplace needs uptime checks, error budgets, alert routing, provider status, customer notice decisions, staff escalation, rollback controls, and owner review tied to real operating events.