Premium resale
marketplace.
An online place to sell premium items you no longer use.
Prepared for Scherazade Jamali
5 November 2026 · Functional proposal
No store to build.
Approve or request changes.
available to buyers.
and enjoy.
Think of it as one online shop with items from different people. Sellers add their own items, buyers shop in one place, and your team manages the sale. The platform earns an agreed fee when an item sells. You do not need to buy all the items yourself.
One sale, step by step.
An example to explain the business. Prices and fees can be changed below.
What if something goes wrong?
The seller cannot supply it
The order is cancelled. If money has already been collected, your team follows the agreed refund process.
The item is wrong or damaged
The item does not sell
Who does what?
There are three simple roles. Your team runs the website through Admin.
Buyer
Browse, purchase, track orders and request support or eligible returns.
Seller / supplier
Add items, confirm they are available, prepare sold items for collection and track money earned. Individuals and businesses use the same profile.
Admin
Check items, manage orders, arrange delivery, help with complaints and pay sellers.
One person can buy and sell using the same account. “Supplier” means seller here. The founder and assigned staff use Admin, with only the permissions needed for their work.
How this differs from a store-based marketplace
| Area | Store-oriented model | Proposed listing-led model |
|---|---|---|
| Getting started | Create and manage a branded store | Create a profile; submit individual items |
| Shopping | Storefronts alongside a catalogue | One shared, curated catalogue |
| Seller workload | Store settings, presentation and inventory | Availability, listings, order actions and proceeds |
| Inactive items | Depends on platform policy | Expiry, reminders and renewal confirmation |
| Business sellers | Often built around merchants | Optional business eligibility, without mandatory stores |
| Trust & fulfilment | Require explicit operating rules | Also require clear checks, owners and policies |
Payments & responsibilities
Automation handles routine steps. Assigned people handle checks and exceptions.
What the seller receives
Example sale breakdown. Change the item value, commission and fees in the settings.
When can the seller withdraw?
The payment provider must support the selected collection and payout process.
Who does the work?
Automation, exceptions & privacy
Routine automation
Contact verification messages, required fields, approval notices, listing expiry, payment deadlines, courier events and payout eligibility checks.
Human decisions
Physical inspection, authenticity assessment, disputed evidence, parcel claims and financial exceptions. These tasks stay with the assigned Admin team or specialist partner.
Privacy
Home addresses, identity documents and payout details are restricted to the roles that need them. Public seller profiles use display names. All sensitive staff actions are logged.
System checks
Queue events, retry failed notices, verify provider callbacks and reconcile money. Duplicate events must not create duplicate orders, refunds or payouts.
Decisions we will make together
Once the idea is clear, choose how you want your business to work.
Project & marketplace details Client information, market, listings and operations
Choose how the marketplace should operate. These settings update the scope and journeys below.
Your current direction
What the website will handle
What still needs to be agreed
These choices need an owner, a policy or a validated partner.
Explore approval, delivery and payment in more detail
Detailed example flows
Play the sequence, or step through it at your own pace.
Choose a scenario
Notification sequence
Who is notified at each step. These notices are simulated.
Full workflow details
These are simulated event notices. Production email requires a sender domain and a delivery provider.
What the website handles for you.
It keeps the information organised and sends updates so your team does less follow-up.
Everyday administration
The website keeps track of items, approvals, orders, deliveries and money due to sellers. It sends reminders and hides expired items. Your team still handles physical checks, complaints and unusual payment problems.
Private information stays private
Buyers see item information, not a seller’s identity documents or bank details. People can only manage their own account and orders. Staff only receive the access needed for their work, and important changes are recorded.
Technology used to build the website
Next.js
The website and the screens used by buyers, sellers and your team.
Supabase
Sign-in, saved information, files and rules controlling who can access them.
Includes the current model, responsibilities and workflow sequences.