Service

Second hand marketplace development

For operators of resale and pre-owned marketplaces who need listings with condition grading, offers and counter-offers, payment held until the buyer confirms receipt, moderation and seller ratings designed around their category of goods, rather than a classifieds script where buyers and sellers are left to sort out trust between themselves.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A resale community for a particular category, say vintage bicycles or children's outdoor kit, usually starts as a social media group or a classifieds board.

Sellers post photographs and a price; buyers comment or message; the deal is done by bank transfer and a parcel, or in a car park.
It works while the group is small and everyone knows each other.
As it grows, so do the problems.
A buyer pays and the item never arrives, or arrives in a far worse condition than the photographs suggested, and the group admin has no record of what was agreed and no money to refund.
Sellers get haggled down in public comments and give up listing.
Items that should never be sold appear and are reported after they have been bought.

Where it gets harder

The admin moderates by hand in the evenings, searches old threads to settle arguments and has no way to know which sellers are reliable.

Good listings sink under new posts within hours.
A buyer who wants to make an offer below the asking price has to do it in a message the seller may never see.
There is demand, there is a community, and there is no mechanism anyone trusts to hold the money, grade the goods and keep the bad actors out.

Scope of the service

What the build covers

A custom second-hand marketplace build normally covers listing, negotiation, protected payment, delivery and reputation. Sellers create listings against category templates with the attributes that matter in your category, a condition grade from a scale you define with written criteria, photographs with minimum requirements, and a price with or without offers allowed. Prohibited item rules are enforced at listing time where they can be, with a reporting mechanism and a moderation queue for the rest. Buyers make offers and sellers accept, decline or counter, with expiry and a record of every step. Payment runs through a payment provider that supports holding funds: the buyer pays at acceptance, the funds are held, the seller ships with a label generated through the carrier or arranges local collection, the buyer confirms receipt or raises a problem within a window, and the funds are released to the seller less your fee or the dispute is decided by your moderator. Ratings run both ways after release. Promoted listings, saved searches, alerts and seller-to-buyer messaging complete the picture, with commission and payout statements for sellers and configurable VAT rules for your fees.

We map your category first: what a condition grade means for your goods, what attributes a listing needs, what is prohibited, how disputes have actually gone in the community, whether local collection matters and which payment provider will hold funds. Each becomes a named stage in the scope document.

Deliberately out of scope

Authenticating items ourselves, acting as the seller or shipping on their behalf, tax or trading-status determinations for sellers, and your own accounting beyond fee revenue and payout statements

When the scope grows

Scoping scenario

A marketplace for pre-owned camera equipment wants an optional authentication step where an item is shipped to a partner for inspection before it goes to the buyer, with the held payment released only on a pass, graded listings with mandatory shutter counts for bodies, and a trade-in flow for a partner retailer. The inspection step inside the held-payment flow and the trade-in partner make this a custom build, and the scope document says so plainly.

Deliverables

What you receive

Discovery notes from walking through a listing, an offer, a held payment, a dispute and a payout in your category
A written scope document naming each stage, the grading scale, the prohibited item rules, the dispute process, the payment provider and what is left out
Designs of the listing flow with grading and photographs, the offer screens, the buyer protection timeline, the moderation queue and the dispute view
The build, including held payment, release and payouts where in scope, deployed to your hosting or ours
Migration of members and open listings from your current group, board or platform
Training for your moderators and operations team, with written guides for sellers and buyers
Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

Onboarding

Access to your current group, board or platform and any payment tools; your grading criteria, prohibited item list and the payment provider under consideration.
Project stage: Onboarding
Planning

Discovery with the founder and whoever moderates and handles disputes; the listing templates, grading scale, offer rules, protection window and dispute process are written into the scope document.
Project stage: Planning
Design

Listing, offer and protection timeline screens designed for sellers and buyers on their phones; moderation, dispute and payout views designed for your team.
Project stage: Design
Development

Built in layers: listings and moderation first, then offers and messaging, then held payment, shipping and release, then disputes, ratings and payouts.
Project stage: Development
Client review

A few of your members list, offer, pay, ship and confirm receipt with the payment provider in test mode, your moderator decides a test dispute, and everyone tells us where it breaks.
Project stage: Client review
Revisions

Changes from the review are made and re-checked against the scope document.
Project stage: Revisions
Ready for launch

Members and listings migrated, held payment and release verified against live provider accounts you control, carrier labels tested, launch checklist signed off.
Project stage: Ready for launch
Delivered

Sales run through the marketplace; hosting and maintenance continue under their own agreement if taken.
Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

Payment providers that support holding funds and paying out to sellers
Parcel carriers for label generation, tracking and drop-off points
Identity verification services for seller onboarding, as a record of the result
Image services for photograph checks and background removal
Email and SMS providers for offer, shipping, receipt and dispute notifications
Accounting software for fee revenue and payout reconciliation
Map services for local collection areas

How we would approach it

Worked example

Concept demo

A camera equipment marketplace with optional inspection

The situation

A marketplace for pre-owned camera equipment wants an optional authentication step where higher-value items are shipped to an inspection partner before going to the buyer, with the held payment released to the seller only on a pass and returned to the buyer on a fail, graded listings with a mandatory shutter count for camera bodies, and a trade-in route where a partner retailer makes a fixed offer on a listing.

Why it is a custom build

The custom route is needed because of the inspection state inside the held-payment flow and the trade-in partner, which go beyond the direct seller-to-buyer protection and single shipping leg the package assumes.

The scope we would propose

Category templates with required attributes per item type
A protection flow with an inspection state between shipped and received
Two shipping legs with labels for each, release and refund rules tied to the inspection result
A partner role that can make offers on listings in bulk

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

Category templates and the depth of grading and required attributes
Payment provider and how holding, release and refunds will work with it
Protection window rules and the dispute process
Shipping label generation, local collection or both
Moderation depth and prohibited item rules
Fee model: per sale, listing fees or promoted listings
Volume of members and listings to migrate
Hosting choice: your own hosting or ours

Custom development · Commerce

Discovery notes from walking through a listing, an offer, a held payment, a dispute and a payout in your category
A written scope document naming each stage, the grading scale, the prohibited item rules, the dispute process, the payment provider and what is left out
Designs of the listing flow with grading and photographs, the offer screens, the buyer protection timeline, the moderation queue and the dispute view
The build, including held payment, release and payouts where in scope, deployed to your hosting or ours

Priced per proposal. A written proposal is the only binding figure.

Get a project quote See the software package

FAQ

Frequently asked questions

When is the package enough and when do we need a custom build?

If graded listings, offers and counter-offers, payment held until the buyer confirms receipt, carrier labels or local collection, a moderation queue and two-way ratings cover your marketplace, the second-hand marketplace package is the right fit and we quote for that. Inspection or authentication steps inside the protection flow, partner trade-in routes or category-specific pricing tools point to the custom route.

Where does the buyer's money sit until the item arrives?

With a payment provider that supports holding funds and paying out to sellers, connected during the build and named in the scope document. The marketplace records the payment, the hold, the release or refund against the order; the funds themselves sit with the provider under its terms, not with the platform or with us.

Does the platform decide whether a seller is trading as a business?

No. It records who sold what to whom and for how much and produces statements. Questions of trading status, tax and consumer rights between sellers and buyers are for your own advisers and the terms you publish.

Can you move our existing community across?

Members can be invited in bulk and open listings imported from an export of your current board or platform, with sellers asked to add the grade and attributes the new templates need. The scope document states what can be carried over once we have seen the data.

Who owns the marketplace afterwards?

You do. The source code, member records, listings and order history are handed over at delivery. Hosting and maintenance are optional and agreed separately.

Get a project quote for second-hand marketplace software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership

Second hand marketplace development

What goes wrong today

What the build covers

Deliberately out of scope

When the scope grows

What you receive

How a project runs

Onboarding

Planning

Design

Development

Client review

Revisions

Ready for launch

Delivered