Skip to content
⁨NDDev Dev⁩, home page
Community
Language: English
Display
Theme
Motion

Marketplace development

NDDev builds marketplaces where sellers and buyers meet on one platform: an offer catalogue, seller pages, comparison, favourites, payments and a separate account for each side. We built the frontend and integrations of Abonmarket, a subscription marketplace, this way: a catalogue by category, comparison, a partner map and a user profile on Next.js.

Who it is for

Anyone building a platform with many sellers: marketplaces for services, subscriptions, rentals and goods, and B2B supplier platforms. It also fits teams who already have a backend and need a strong frontend.

  • Catalogue with filters and comparison
  • Seller and buyer accounts
  • Offer moderation
  • A frontend for your existing API

How a marketplace is put together

A marketplace has three sides: the buyer, the seller and the platform administrator. We design a separate path for each. Buyers search and compare, sellers list offers and see orders, and administrators moderate listings, handle disputes and set the commission.

  • a catalogue by category and subcategory with filters
  • seller and offer pages
  • comparison, favourites and a partner map
  • a seller account: offers, orders, statistics
  • a buyer account: purchases, subscriptions, history
  • an admin panel for moderation and commission settings
  • payments and payment provider webhooks
  • language versions on next-intl

We write the frontend in Next.js with Feature-Sliced Design: catalogue, comparison, favourites and profile live in separate layers and evolve independently. On Abonmarket the backend and API belonged to the client, so we pinned the shape of API responses with contract tests: when the server changes a response, a test shows it before release.

When a backend is still missing, we build it on FastAPI and PostgreSQL: catalogue, orders, roles, payments and notifications in one database, with offer search through Elasticsearch or Meilisearch.

How a marketplace reaches the market

  1. Platform model

    We settle who pays, what the commission is charged on, how a seller joins and who is responsible for a disputed order.

  2. First version

    We build the core buyer and seller path to test demand on real deals. The scope of the version goes into the specification.

  3. Integrations

    We connect payments, email, maps and external directories, and pin API contracts with tests.

  4. Growth

    We add roles, seller reports, new categories and languages based on what the first months show.

Work in this area

  • Abonmarket

    The front end and integrations of a subscription marketplace: an offer catalogue, organisation pages, comparison, a map and a personal profile on top of the client's REST API.

Questions from platform owners

How much does a marketplace cost?

The lower end of the price is in the price block. The total depends on the number of roles, the commission model, payment flows and whether the backend has to be built from scratch. We review the task, describe the first version in a specification and fix the price and timeline there.

We already have a backend. Can you build just the frontend?

Yes, that is how we worked on Abonmarket: the frontend and integrations were ours, the backend and API stayed with the client. We agree the API contract, cover it with tests and log server defects in a shared list for your team.

Can we start with a small version?

Yes, and we recommend it. The first version carries the core path: find, compare, buy. Accounts, reports and new categories follow once the platform has its first sellers.

How are payments protected?

We verify payment notifications by signature and process them idempotently, so a repeated webhook still means one charge. Card data stays with the payment provider, and the platform keeps statuses and amounts.

Will the platform cope with growth?

We cache the catalogue and search in Redis, move heavy work to background queues, and PostgreSQL grows with the catalogue. Before launch we run load tests.

Who owns the platform’s code?

Code rights are transferred as agreed, usually together with the repository and server access.

from ₽840,000

Free warranty
120 days

Prices are starting prices for information only and are not a public offer. The final price is fixed in the specification.

Web development

Describe your platform: who sells and who buys

Tell us about the commission model and what is already in place. We will outline the first version of the platform and give you a price.

We reply within 24 hours

Assistant

Loading the assistant…