Interactive demo

Marketplace analytics

Give owners a single place to read marketplace health across buyer demand, seller supply, category liquidity, hub operations, support pressure, and finance signals.

DemandSearches, saves, offers, bids
LiquiditySell-through, time to sale
OperationsHubs, support, releases
FinanceFees, credits, holds

Demand Health

  • Track searches, result clicks, saved searches, item saves, offer starts, bid starts, cart reviews, and empty searches.
  • Demand should be readable by category, price band, handoff choice, hub area, device size, and buyer intent.
  • Repeated empty searches become supply requests for seller recruiting, hub intake, and category planning.

Liquidity Signals

  • Sell-through, time to first bid, time to first offer, watcher-to-bid rate, offer acceptance, and listing age show whether inventory is moving.
  • Auctions need bid depth, reserve miss rate, closeout speed, and winner follow-through.
  • Buy-now listings need cart starts, offer attempts, price-drop response, and similar-item demand.

Category Health

  • Cards, retro games, electronics, sneakers, collectibles, art, books, automotive, garden, and home each need their own proof and performance view.
  • Category health should show active listings, watched items, sell-through, report rate, proof gaps, hub capacity, and seller concentration.
  • Operators can spot categories that are hot, thin, risky, oversupplied, or ready for a local event.

Hub Performance

  • Hub analytics show intake volume, check time, packing queue, pickup holds, no-shows, event turnout, and issue rate.
  • Local hubs should be measured against category demand and support pressure, not just item count.
  • Capacity warnings can guide event scheduling, seller intake windows, and pickup staffing.

Seller Quality

  • Seller analytics roll up response time, listing quality, fulfillment speed, report cooperation, review rate, and repeat buyer activity.
  • Owner views should separate strong sellers, rising sellers, sellers needing coaching, and sellers blocked by trust issues.
  • Seller growth actions should tie back to quality, category demand, and buyer transparency labels.

Support Load

  • Support analytics show open reports, aging cases, missing documents, seller response delays, hub proof needs, refund exposure, and appeal volume.
  • Owner views should connect support pressure to category, seller, handoff type, hub, and item proof quality.
  • Every launch wave needs a support staffing readout before more inventory is promoted.

Finance Signals

  • Finance analytics show marketplace fees, hub service lines, credits, refunds, holds, seller release aging, and category margin.
  • Settlement and payment readiness should explain why funds are ready, held, refunded, or awaiting owner action.
  • Credits and refunds need clear separation from seller earnings and service revenue.

Owner Review

  • Owners need saved views for weekly health, launch readiness, category growth, hub capacity, seller quality, and support pressure.
  • Each metric should have a definition, source route, owner, review cadence, and decision it supports.
  • Launch needs event history, permissioned exports, scheduled reports, and change notes.
Marketplace reporting engine

Marketplace Reporting

Executive reports, category health, seller performance, hub operations, support outcomes, and finance exports.

Network rollout center

Network Rollout

Demand, liquidity, hub utilization, seller cohorts, events, and expansion gates.

Seller analytics dashboard

Seller Analytics

Demand signals, listing health, price actions, service levels, and seller-quality prompts.

Search quality center

Search Quality

Ranking reasons, saved-search demand, category handoff, placement labels, and review controls.

Search discovery center

Search Discovery

Phrase search, filter use, seller quality, saved alerts, and demand signals.

Pricing and sold comps

Pricing & Comps

Sold comps, category signals, reserve guidance, and price actions.

Hub network map

Hub Network

Service areas, capacity, pickup routing, item checks, and local events.

Payment and payout readiness

Payment Readiness

Credits, holds, refunds, seller releases, tax readiness, and finance ownership.

Unit economics center

Unit Economics

Fees, hub service cost, category contribution, refund exposure, and support load.

Monetization controls center

Monetization Controls

Sponsored placement, seller budgets, buyer labels, reporting, and owner review.

Fee schedule builder

Fee Schedule Builder

Category fee rules, seller plans, hub service lines, effective dates, and rollback.

Service health center

Service Health

Storefront, search, checkout, hubs, messages, support load, and provider checks.

Catalog quality center

Catalog Quality

Category fit, required attributes, duplicate risk, media proof, and seller repair pressure.

Operator console

Operator Console

Finance, routes, support pressure, service levels, launch gates, and owner review.

Current demo state

Marketplace health is represented as guided analytics.

The demo connects demand, liquidity, category health, hub performance, seller quality, support load, and finance signals using the current walkthrough data.

Future platform state

Live analytics need measured events.

Launch needs event collection, metric definitions, permissioned exports, scheduled reports, saved owner views, alert thresholds, history, and review ownership.