Article5 min readUpdated
Marketplace App UI UX Design: Buyer and Seller Screens
Marketplace app UI UX design for founders: e-commerce app design in India, seller onboarding, verification and product listing UX.
By Tithi Mondal, UI/UX Designer
Most founders start a marketplace app by designing the buyer side: the home page, search, product cards. That is understandable, but it is half the product. Without sellers who can sign up, get verified and list products easily, there is nothing to buy. This post covers marketplace app UI UX design for both sides, with extra detail on seller onboarding and listing, the part most often under-designed.
Two sides, two sets of screens
Treat buyers and sellers as separate users with separate goals.
| Role | Main goal | Key screens |
|---|---|---|
| Buyer | Find a trustworthy product and pay | Home, search, product page, cart, checkout, orders |
| Seller | Get set up and sell | Onboarding, verification, listings, orders, payouts |
| Admin | Keep quality and handle disputes | Seller review, listing moderation, support |
Decide early whether sellers use a separate app or a section of one app. A separate seller app often works better, because a seller's daily tasks (add stock, accept orders, check payouts) are very different from a buyer's tasks.
Buyer side: e-commerce app design in India
For the buyer experience, a few decisions carry most of the weight.
- Search first. A visible search bar, autocomplete, and tolerance for spelling mistakes and Hinglish.
- Filters that matter: Price, category, rating, delivery area. Keep them in a bottom sheet with an Apply button and a visible count of results.
- Product cards: One good photo, name, price in rupees, rating, and a clear tag for any discount.
- Product page: Swipeable photos, price, seller name and rating, delivery estimate, description, and a sticky Add to cart or Buy now button.
- Seller visibility: On a marketplace, the buyer is trusting a stranger. Show the seller's name, verification mark and rating on the product page.
- Checkout: Address, delivery option and payment with UPI first. See UPI payment UX and checkout design for the payment states.
- Returns and help: A clear, honest explanation of returns on the product page, and an easy way to contact support.
Seller onboarding: the first test of your platform
A seller is giving you their time and often their business identity. Onboarding should feel respectful and short.
On a seller app I designed for a marketplace in Tanzania, Sokoni, the seller journey covered onboarding, verification and listing management. The lessons below come from that kind of flow, and they apply broadly.
- Explain the value first. One or two screens on what the seller gets, before asking for details.
- Start with a phone number and OTP, like any mobile app. See app onboarding UX best practices.
- Collect shop basics in steps: shop name, category, location, a logo or photo. Skip anything not needed to start.
- Show a checklist of what remains: profile, verification, first listing. Let the seller see progress.
- Allow browsing the seller dashboard while verification is pending, so they feel they have started.
Verification: make the status visible
Sellers often need to be verified before they can sell. The risk is a dead end where the seller submits documents and hears nothing.
- State what is needed up front, with examples of acceptable documents.
- Guide photo capture with a frame and tips.
- Show a status clearly: Not started, Submitted, In review, Approved, Needs changes.
- Say what happens next and roughly when, using a time your operations team can keep.
- If rejected, be specific. Which document, what was wrong, and a button to upload again.
- Notify the seller by push, SMS or WhatsApp when the status changes.
Verification rules and what counts as sufficient are business and legal decisions for you. The design makes the process visible and fair.
Product listing UX: get the catalogue built
A listing form is where sellers either create your inventory or give up. Many sellers will list from a phone, often a budget Android, and often several items in one sitting.
- Photos first. Let the seller take or choose photos, because the photo often tells them what to write.
- Short form, in a sensible order: Title, category, price, stock quantity, description.
- Smart defaults and suggestions: Category suggestions from the title, previous values reused.
- Plain field help: An example under each field, such as "Example: Cotton saree, red, free size".
- Save as draft automatically, so a call or a dropped network does not lose the work.
- Preview showing how the buyer will see the listing before publishing.
- Duplicate listing to create similar products in a few taps.
- Bulk or quick edit for price and stock, since these change daily.
Listing management
Once there are listings, the seller needs a simple control room.
- A list with photo, name, price, stock and a status badge: Live, Draft, Out of stock, Under review.
- Quick toggles for availability and a fast price edit without opening the full form.
- Clear messages if a listing is rejected, with the reason and a fix button.
- Search and filter once the list grows.
- Orders and payouts in separate, plainly named sections.
Trust and quality for both sides
A marketplace keeps trust through consistency. Use the same status words everywhere. Show ratings only when enough reviews exist to be meaningful. Give buyers a clear route to report a problem and give sellers a clear route to respond. Support the local language of your sellers, and keep icons and labels simple. More on that in designing apps for Indian users.
Plan the build in stages
A sensible first release has the core buyer loop, seller onboarding and listing, and a basic admin. Add reviews, promotions and analytics later. Costs depend on the number of screens and user roles, and my UI/UX design cost guide explains the drivers.
If you are designing a marketplace, see my mobile app design service or get in touch.
Frequently asked questions
Should a marketplace have a separate seller app?
Often yes, because seller tasks like adding stock and checking payouts differ from buyer tasks. A seller section inside one app can work for a simple first release.
How do I make product listing easier for sellers?
Start with photos, keep the form short, give examples under fields, save drafts automatically and show a preview before publishing.
What should a seller verification screen show?
What documents are needed, a clear status such as Submitted or In review, an honest timeline, and specific reasons with a re-upload button if something is rejected.
Which side of a marketplace should I design first?
Design both together. Sellers create the catalogue, so a weak seller flow leaves buyers with nothing to buy.