What it is

Product

Luxury Resale Marketplace

A premium marketplace for pre-owned luxury goods, where every listing can be checked for authenticity.

What it is

The product in one paragraph: what it does, for whom, the problem it solves.

Luxury Resale Marketplace is an international marketplace where individual and business sellers sell pre-owned luxury goods, a used luxury watch being the typical item, to buyers anywhere in the world. Buying second-hand luxury carries one fear above all: that the item is fake. So every listing can be checked by an external authentication provider, and a buyer who wants more can have the item inspected by a human specialist at a hub before it is delivered. Around that core sits a complete marketplace: listings, search, offers, payment with commission and payouts, shipping, chat, ratings, returns and disputes, and a back office.

Genuine items

Listings carry the result of an external digital authentication, and a buyer can have an item inspected by a specialist at a hub before delivery.

A sale that runs safely

From offer to delivery the payment is collected, the commission kept, the seller paid out and the item tracked.

Deals stay inside

Buyer and seller talk in the product’s chat, which blocks personal contact details.

Sellers you can judge

Star ratings and a visible reputation let a buyer judge a seller before buying.

Who uses it

Every role, what it does in the product and where.

Visitor

Guest

Browses the catalogue and listings without signing in; is asked to sign in to buy, save, make an offer or message.

Public web · mobile app

Buyer

Sofia Marin

Finds genuine items, negotiates, pays, may request an inspection at the hub, follows the order and rates the seller.

Public web · mobile app

Individual seller

Daniel Weber

Lists personal luxury items, gets them authenticated, sells, ships and gets paid.

Public web · mobile app

Business seller

Claire Arden, Maison Arden

Does the same as an individual seller, as a company, with company details.

Public web · mobile app

Administrator

Elena Petrou

Runs the marketplace: users, moderation, orders, payouts, returns and disputes, settings and reports. Signs in with a second factor.

Admin web

Inspection operator

Jonas Keller

A specialist at the hub: receives items, inspects them and records the result, in a restricted workspace. Signs in with a second factor.

Admin web (hub workspace)

Modules

The parts of the product, each in a line, and which come first.

Accounts

Registration, sign-in, roles, seller onboarding and seller type, profiles and privacy controls.

First release

Listings

Creating, editing and withdrawing listings with attributes, condition and up to ten photos; listing moderation. Video on listings comes later.

First release

Catalogue

The home page and featured selections, browsing, search and filters, listing pages, saved items and prices in the buyer’s currency. Advanced search and recommendations come later.

First release

Digital authentication

Listings sent to the authentication provider; results, certificates and the handling of inconclusive results.

First release

Physical inspection

Routing an order through the hub, the hub workspace, inspection results and failed inspections. More hubs come later.

First release

Offers

A buyer’s price offer on a listing and the seller’s answer, with an expiry. Counteroffer chains come later.

First release

Orders

Checkout of one item from one seller, reservation, the order lifecycle and order oversight. Multi-item orders come later.

First release

Payments

Collecting payment, commission, payment hold, payouts, refunds and checkout currencies. More providers come later.

First release

Shipping

Shipping labels, direct and two-leg shipments through the hub, and tracking.

First release

Messaging

Buyer–seller chat with contact blocking, reporting and blocking users, and chat moderation.

First release

Reputation

Buyers’ star ratings of sellers and the reputation shown on profiles and listings.

First release

Returns and disputes

Return and dispute requests, staff review and the refund decision.

First release

Notifications

Transactional email and push notifications and each user’s preferences. SMS comes later.

First release

Administration

Administrator accounts and user management, marketplace settings, reports and exports.

First release

How it works

The product’s main loop, drawn step by step.

  1. List

    A seller onboards with the payment provider and lists an item with photos and condition.

  2. Authenticate

    The listing is checked by the authentication provider and published with its result and certificate.

  3. Find and offer

    A buyer finds it, asks in chat without exchanging contact details, and buys at the listed price or makes an offer.

  4. Pay

    The item is reserved, the payment is collected and the commission recorded; the buyer may ask for inspection at the hub.

  5. Ship and inspect

    The seller gets a label and ships directly to the buyer, or to the hub, where a specialist inspects the item and sends it on.

  6. Complete and rate

    On delivery the order completes, the seller is paid and the buyer rates the seller; a buyer with a problem opens a return or dispute that staff resolve.

Buyer and seller see each step’s status on their own surface, and an item cannot be sold twice.

Sample company

The fictional company and people every sample on this site uses.

Maison Arden Horlogerie — a business seller of pre-owned luxury goods in Antwerp, Belgium, played by Claire Arden. It lists on the marketplace with the other people below, so every sample on this site reads as one story.

People

  • Sofia Marin · Buyer
  • Daniel Weber · Individual seller
  • Claire Arden · Business seller
  • Elena Petrou · Administrator
  • Jonas Keller · Inspection operator
  • Guest · Visitor

“Today” on every screen is 2026-10-27.

About this site

Every page of this site, where its content comes from, and how to read it.

This site shows the product before it is built: what it is, how it is built and what keeps its data safe, how it is used — its flows, step by step, and its screens — then its design: its pictures, layouts, email templates and components. It is the reference the product is held against; where it proposes something the product does not have yet, it says “proposed”.

Product

What the product is, who it is for, what it is built with, how its parts fit together, what keeps its data safe — and the product in use: its flows step by step, then its screens.

Architecture

How the product is put together, drawn for the customer: the system in its world, its parts, its modules, how data moves, where it runs.

Security

What keeps the customer’s data safe, in the customer’s words: where it lives and who can reach it, how it is kept from loss and from attack, what stays on record — and what is still to be discussed.

Flows

The product in use, step by step: signing in first, then the flows of the product itself. Each flow is a page of its own with a step player.

Screens

The screens of the product in its picked shell.

Design

The design system: the basics every screen is drawn with, the pictures, the layouts, the email templates, the components and the charts.

Design

The basics of the design — principles, colors, type, spacing, shape, motion, the logo and its loaders, icons and states — each on a page of its own.

Illustrations

Pictures in the product’s own style and colors: for every state a screen can be in, and for the cases of the product’s domain — some of them moving, with a reserve for later.

Layouts

The frames every screen sits in — the sign-in, the application’s shell, the page a wrong address lands on — each in several variants with the product’s pictures in motion. One of each is selected.

Email templates

The letters the product sends, as a mail client shows them: the one template, the common letters, and the ones the product’s own flows need.

Components

Every component on one page, one section each: what it is for, its variations and states, its sizes. The standard set, the product’s own, and a reserve for later.

Charts

The product’s figures drawn as the product shows them — each use of a chart on its screen or card, in the palette, in both themes.

Project

What was decided, what changed, and what comes next.

Decisions

Every choice made on this site — languages, stack, color scheme, logo, layouts — with the alternatives beside it and the reason.

Changelog

What changed on this site between showings, by date.

Next steps

What this site will get next, in order, and ideas for the product beyond it.

Where this comes from

WhatFilesWhat it gave
`docs/blueprint/` — 01-brief, 02-architecture, 03-roadmap, GLOSSARY, DECISIONS (D-001…D-053), ASSUMPTIONS, OPEN-QUESTIONSProduct, actors, surfaces, domain model and states, main flows, decisions, constraints, open questions. Phases up to consistency approved; adequacy still pending.undefined
`docs/blueprint/modules/*.md` (14 modules, 228 capabilities)Screens per surface, flows end to end, domain components, notifications, figures, security per moduleundefined
*(not a basis)* `docs/initial-data/` — requirements (S-03 v0.2), meeting transcript (S-04), WBS estimate (S-05)Client's words on the product, the three-surface structure, "RN WEB", pilot scope, open questions Q01–Q22undefined
*(not a basis)* `docs/research/2026-10-26-luxury-resale-competitors/`Six competitors: trust signals, flows, statuses, fees. No visual identity researched.undefined

How to read this site

In this section

Technology stack

The three parts of the system — web client, mobile client, server — each described with its technologies, then hosting, quality and the shared API contract.