A marketplace app connects two groups of people who need each other. Customers looking for home cooks, tutors, mechanics, venues, rental equipment or handmade products on one side; the people who sell or provide those things on the other. The business in the middle does not own the stock or do the work. It owns the place where the two sides meet, and it earns from making that meeting reliable.
That middle position makes a marketplace harder to build than a normal business app. A booking app for one cleaning company has one set of prices, one calendar and one team. A marketplace has many sellers with their own prices, schedules and standards, and customers who expect all of them to behave like one trustworthy product.
Here is what each side needs, and what can wait.
Decide what kind of marketplace you are
Before features, be clear about what changes hands. The answer shapes almost everything else.
- Products. Sellers list items, customers order them, someone delivers. Stock, variants, shipping or delivery zones and returns all matter.
- Services by appointment. Providers list services, customers book a time. Availability, calendars, cancellations and no-shows matter. This is closer to a booking app with many businesses inside it.
- Leads or enquiries. Customers post a request, providers respond with quotes, and the job is arranged between them. The platform charges for leads or subscriptions rather than taking a cut of each job.
- Directory with discovery. Providers have profiles, customers find them, read reviews and call or message directly. No transaction happens inside the app.
A directory or lead model often proves the idea faster than a full transactional marketplace: no payment flow, no payouts, no dispute handling, and a quick answer on whether customers search for what you plan to list. Local Meals, an app I designed and developed for Order of Malta Lebanon, is that discovery shape: vendor profiles with photo galleries, descriptions and menus, a map with directions and a call button, and reviews from visitors.
The customer side
The customer experience decides whether anyone comes back. It needs:
- Browse and search. Categories, a search box that tolerates misspellings, and filters that match how people actually decide: area, price range, availability, rating. If your sellers are local, a map view and "near me" sorting usually matter more than clever ranking.
- Clear listings. Photos, a plain description, the price or how pricing works, what is included, delivery or service area, and the seller's profile and reviews. Inconsistent listings make a marketplace look untrustworthy, so seller tools should push toward complete ones.
- Ordering or booking. A cart for products, a time picker for services, or a request form for quotes. Show the total, fees and expected time before the customer commits.
- Status and messages. The customer should always know what is happening: confirmed, preparing, on the way, completed. In-app chat or a structured message thread keeps conversations on the platform, which protects both sides when something goes wrong.
- Reviews. Only from customers who actually completed an order or booking. Open reviews from anyone get gamed within weeks.
- Account basics. Sign-in by phone number or email, saved addresses, order history, and the ability to delete the account.
The seller or provider side
Sellers are your supply, and a marketplace with poor supply has nothing to show. Their tools need to be fast enough to use between jobs.
- Onboarding and approval. Sign-up, business details, documents if your category needs them, and a review step before the profile goes live. Approval is how you control quality early on, and it is much easier to loosen later than to add once bad listings are already live.
- Listing management. Add and edit products or services with photos, prices, options and availability. Templates and required fields keep listings consistent.
- Orders, bookings and calendar. Accept or decline, update status, manage working hours and days off. Push notifications for new orders matter here more than anywhere else, because a seller who misses an order costs you a customer.
- Earnings. What they sold, what the platform took, what has been paid out and what is pending. Sellers who cannot follow their money stop trusting the platform quickly.
Sellers can get a separate app or a mode inside the customer app. Separate apps keep each experience simple; one app with a seller mode is cheaper to maintain at the start. Sellers who work from a shop or office often do better with a web dashboard.
Money: commissions, payments and payouts
How the platform earns has to be decided before the build, because it touches checkout, seller earnings, reporting and the admin.
- Commission per order. The platform takes a percentage or fixed fee from each transaction. This needs payments inside the app and a payout process to sellers.
- Subscription or listing fees. Sellers pay to be listed or featured. Payments are simpler: the platform bills sellers, not every customer order.
- Lead fees. Providers pay to receive or respond to requests.
Taking a commission means you are collecting money on behalf of other people and paying it out to them. Some payment providers support split payments and seller payouts directly; others only collect into your account, and you pay sellers yourself on a schedule. Which options are available depends on your country, your provider and your business setup, so confirm that with the provider before designing the flow. Many marketplaces start by collecting payment, recording each seller's share in the system, and paying out weekly by bank transfer, with the app showing sellers exactly what is due. Cash on delivery is also common, and then the money moves the other way: the seller or driver collects, and the platform invoices its commission.
If you are building for Lebanon, I covered the practical options in accepting payments in your app or website in Lebanon.
Whatever the model, the backend needs a proper ledger: every order, fee, refund and payout recorded as its own entry, never just a balance number that gets overwritten. That is what lets you answer a seller's "why was I paid this much?" with a list rather than a guess.
Trust and disputes
A marketplace sells trust as much as it sells products. The features that build it are rarely the ones founders mention first:
- Verified sellers. Approval, a visible badge or join date, and the ability to suspend an account.
- Reviews tied to real orders, with the option for sellers to reply and for the admin to remove abusive content.
- Cancellation and refund rules written down and enforced by the system: who can cancel, until when, and what happens to the money.
- Reporting. A "report a problem" option on orders, listings and profiles, routed to the admin.
- Reasons to stay on the platform. With commissions, both sides are tempted to swap numbers and continue outside. Payment protection, order history, reviews and support that only apply to in-app orders make staying worth it.
The admin panel
The admin is where the business actually runs the marketplace, and it is usually bigger than the founder expects. At minimum it needs seller approval and suspension, listing moderation, order and booking oversight, refunds and dispute notes, commission settings, payout tracking, category management, review moderation and basic reports by seller, category and period. Roles matter too: someone handling support should not see payout settings. I wrote more about this in what your app's admin panel actually needs.
What a first version should include
The most common mistake with marketplaces is building every feature for both sides before either side has shown up. A sensible first version:
- Picks one category and one area. Ten good sellers in one city beat two hundred thin listings across a country.
- Uses approval for every seller, so early customers only see listings you are proud of.
- Keeps money simple. One payment method that works for your market, a ledger, and manual scheduled payouts.
- Ships the customer app, a seller tool and an admin, with ordering or booking, status updates, notifications and reviews.
- Leaves out promoted listings, coupons, loyalty, multi-currency, complex seller analytics, and automated dispute flows. Handle those by hand from the admin until volume justifies building them.
Then measure whether it works: searches that end in an order, sellers who respond on time, and customers who order again.
Arabic, English and regional details
If your sellers and customers are in Lebanon or the GCC, plan for Arabic and English from the start. Sellers will write listings in either language, sometimes mixed, so search needs to handle both, and the layout needs to switch properly to right-to-left. Addresses are often described by landmarks rather than street numbers, so a map pin plus a free-text description works better than a rigid address form. Many customers will prefer to confirm details on WhatsApp, and notifications there can be part of the flow; I covered how that works in WhatsApp notifications for business apps.
How I build it
A marketplace is mobile app development plus a substantial web side. I build the customer app, and the seller app or mode, in React Native for iOS and Android. The backend is .NET Core or Next.js on Postgres, which handles the relational side of a marketplace well: sellers, listings, orders, fees, payouts and reviews all linked and queryable. The admin, and a seller dashboard where that makes more sense than an app, is a Next.js web app. Everything runs in Docker on a Linux server with a CI/CD pipeline, monitoring and backups, and I handle the App Store and Google Play releases.
The closest work to show is a mix. Local Meals covers the discovery side: vendor profiles, galleries, map and reviews in a React Native and .NET Core app on both stores. NeonTask covers the operational side: requests from many clients routed to the right people and tracked through to invoice and payment, with a web app for dispatchers and a mobile app for technicians. A marketplace combines both problems: making supply easy to find, and making every order traceable from request to payout.
What to send me
To start, a short note covers it: what is being sold or booked, who the sellers or providers are and roughly how many you expect at launch, how you plan to earn (commission, subscription or leads), which city or country you start in, and whether you have sellers lined up already.
Email hello@eliechaaban.com or use the contact section, and we can go through it on a call and agree a first version that gets real sellers and real customers using it.