Marketplace setup
See the owner decisions that turn a marketplace from a polished commerce demo into a launchable operating model.
Brand and Domains
- Brand setup keeps logo, red accent, dark mode, app icon, page title, public footer, and placeholder-domain posture together.
- The demo site stays on the Netlify app domain while owned domains remain neutral, noindex placeholders.
- Live domain launch needs DNS, certificate, redirects, analytics decision, and legal review.
Category Catalog
- Category setup covers retro games, trading cards, GPUs, sneakers, local pickup, art, books, automotive, garden, and home.
- Each category carries proof rules, accepted-condition notes, seller prompts, buyer filters, and item-check expectations.
- Restricted item handling stays tied to seller education and staff review.
Seller Programs
- Seller setup separates casual sellers, power sellers, hub-assisted sellers, bulk import sellers, and timed-drop candidates.
- Each area needs listing quality, fulfillment choices, fee visibility, report expectations, and account-standing rules.
- Seller growth stays auditable through fair visibility labels and quality prompts.
Fee and Service Model
- Owner review keeps marketplace fees, auction fees, hub intake, packing, pickup, shipment service lines, seller plans, and refunds understandable.
- Seller finance, settlement ledger, and checkout review show the same math from different angles.
- Launch-ready commerce needs processor reconciliation, tax reporting, and seller payout controls.
Policy Pack
- Launch policy coverage includes buyer protection, seller standards, auction rules, returns, restricted items, condition standards, and hub handoff.
- Policy pages connect to report evidence, review gates, support timelines, and operator queues.
- Customer-facing copy stays concise while operator pages keep the full checklist visible.
Roles and Staff
- Role setup covers buyers, sellers, support, trust review, hub operations, marketplace operators, and admin review.
- Permission boundaries protect private account, payment, support, and identity details.
- Live operations need audit history, role changes, escalation rules, and support ownership.
Migration Readiness
Seller move, inventory import, policy mapping, customer notices, historical records, redirects, and cutover gates.
Owner Handoff
Evidence bundle, service activation gaps, deployment safety, ownership controls, and acceptance checks.
Domain Launch
Placeholder domains, DNS cutover, SSL, noindex release, monitoring, owner approval, and rollback.
Operator Console
Launch readiness, route coverage, finance, service levels, workflows, and demo playbook.
Fee Guide
Seller fees, hub services, pickup fees, shipping choices, returns, and category examples.
Fee Schedule Builder
Category fees, hub service lines, seller plans, customer labels, dates, and rollback.
Seller Plan Center
Seller tiers, team seats, usage limits, upgrade review, downgrade rules, and owner approval.
Restricted Items
Rejected inventory, category limits, seller education, and staff review paths.
Policy Pack
Buyer, seller, hub, payment, privacy, support, and approval policies.
Hub Network
Service areas, capacity, intake, pickup windows, local events, and routing.
Current demo state
Setup decisions are inspectable.
The demo shows brand, category, fee, policy, role, hub, route, package, and launch controls without taking over live domains or collecting private data.
Future platform state
Live owner launch requirements.
Launch needs domain activation, access controls, approved service agreements, support staffing, payment review, seller onboarding, and policy sign-off.