KwadMarket Docs
Product Roadmap

Roadmap

Prioritized feature ideas for a production C2C marketplace

Features not currently implemented, ordered by leverage for this product. The scraper gives KwadMarket something most secondhand marketplaces don't have: live retail price data. Lean into it.

Roadmap vs plan

This section is product features, not fixes — engineering debt lives in the remediation plan. The detailed spec pages here (data models, flows, decisions) predate the current priorities; treat the priorities on this page as authoritative and the spec pages as design material for when a feature gets picked up.

Differentiators (build these — they use what you already have)

  1. "New price" comparison on every deal. Shop.price per product is already stored and deals link to catalog products (DealProduct). Show "€89 — sells new for €129 (-31%)" on deal cards and detail pages. This is the killer feature of pairing a scraper with a C2C market, and it's mostly a mapper change.
  2. Price-drop / availability alerts on catalog products. Users follow a product; the scraper already refreshes prices (syncPrice); notify on drops. Drives recurring visits.
  3. Fair-price guidance when creating a deal. During the deal stepper, after the user picks products, suggest a price range from current new prices (and later, from past sold deals). Better-priced listings → more transactions.
  4. Build-from-components awareness. ProductComponent (parent/component relation) exists in the schema. An FPV quad listing could auto-display its known components (FC, ESC, motors, VTX) — huge for buyers evaluating used builds. → Drone builds spec

Core marketplace features (table stakes, none implemented yet)

  • Favorites / watchlist on deals + saved searches with email alerts ("new 5-inch frame under €50").
  • Ratings & reviews after a transaction — trust is the currency of C2C; needs a "transaction" concept (buyer marks received / seller marks sold-to-user).
  • In-chat offers: structured price offers (offer/accept/decline messages) instead of free-text haggling; later this becomes the hook for payments.
  • Report listing / report user + admin moderation queue for reports (a deal moderation queue already exists — same pattern).
  • In-app + email notifications center (new message, deal status, offer received). → Notifications spec
  • Seller profile upgrades: response time, member-since, verified email badge, sold-count (public profile page already exists).

Growth / UX

  • Geolocation: location is a free-text string today; structured location (city + radius search) matters a lot for pickup-heavy categories like drones/LiPos. → Spec
  • Multi-language (FR/EN) via next-intl — decide early, retrofitting i18n is painful. → Spec
  • PWA / mobile polish: C2C browsing is majority-mobile; the chat especially benefits from web push.
  • Draft autosave + "my listings" management (relist expired, mark reserved).

Later / heavier bets

  • Payments & escrow (Stripe Connect): hold buyer payment until delivery confirmed; this is what lets you take a commission. Significant compliance work — only after traction. → Spec
  • Shipping label integration (Mondial Relay / Chronopost style for the FR market). → Delivery spec
  • Image-based listing creation: user photographs gear, match against the scraped catalog.
  • Public price-history charts per catalog product from scraper history (start retaining price snapshots — cheap to begin now, valuable later). → Scrapers spec
  • Admin analytics dashboard: deals/day, conversion to discussion, time-to-sell per category — the admin shell already exists.
  • Auctions, bidding — complexity without demand at small scale.
  • Native mobile apps — PWA first.
  • Federated/social login beyond Google+Facebook (already done) — diminishing returns; Discord is the one exception worth considering for this community.

Status of earlier roadmap items

The original production roadmap (mid-2026) listed these; reconciled status:

FeatureStatus
Full-text search (Meilisearch)Implemented — remaining polish in the search spec
Error tracking (Sentry)Moved to engineering: plan phase 7 / best practices
Payment escrow, verification, notifications, delivery, disputes, legal⬜ Specs ready — see this section
Geolocation, i18n, media, Discord login, OG sharing, drone builds⬜ Specs ready — see this section
Additional shop scrapers⬜ Ongoing — spec

On this page