Mobile App Development for Multi-Vendor Marketplaces: Architecture & Payments
Building a mobile marketplace app requires careful planning. A marketplace is not just an online store with multiple sellers. It's three parallel applications: buyer, seller, admin. We specialize in marketplace development for mobile, providing turnkey solutions from prototype to app stores. Architectural decisions at the start determine how easy it will be to add a new seller or product type six months later. Schedule a consultation on your marketplace architecture—we'll evaluate your project in 2 days. Typical MVP starts from $15,000, and our clients save up to 40% on development costs through shared core modules. Typical savings range from $5,000 to $20,000 compared to custom solutions.
How to Design a Mobile Marketplace App From Scratch?
A marketplace combines two clients: buyer and seller. The goal is to make them maximally reusable. For the buyer, crucial features are the catalog, cart with multi-vendor items, and payment mechanism. For the seller, it's product management, order management, and analytics. Building a react native marketplace app with a shared core package cuts development time by 30% compared to separate native projects. Let's examine each subsystem.
How to Design a Catalog with Multi-Vendor Filters? – Mobile App Development
A standard UICollectionView/RecyclerView with a paginated endpoint works until you have 50 sellers with overlapping categories. Problem: with offset pagination, duplicates appear if a seller adds a product between requests. Solution – cursor-based pagination (after=<last_item_id>): more stable with frequent updates. Comparison:
| Pagination Type | Stability | Duplicates on Update | Recommendation |
|---|---|---|---|
| Offset | Low | Up to 15% | Avoid for frequently updated catalogs |
| Cursor-based | High | 0% | Standard for marketplaces |
A WebSocket channel is 10x faster than polling for data update speed. Stripe documentation recommends this approach for real-time scenarios.
What to Do With the Cart from Different Sellers?
User added items from three sellers – during checkout either split into three separate orders or create one composite with sub-orders. Handling a marketplace cart with items from multiple sellers is tricky. This is a business decision affecting the UI: split by seller in cart, separate delivery statuses, possibility of partial payment. We align the cart architecture with CartService supporting VendorGroup at the start. Implementation steps:
- Split cart into sections per seller.
- Ask payment method at checkout (separate orders or composite).
- Create an OrderGroup with child orders on the backend.
- Process payments for each order independently.
How to Organize Real-Time Stock Updates?
A buyer views an item that was just purchased. Standard scenario: item in cart, on checkout – out_of_stock. Good solution – WebSocket channel on the detail page (wss://api/items/{id}/stock) updating the counter in real time. Cheaper option – polling every 30 seconds via Timer. WebSocket is preferable for frequent changes (up to 80% of cases), polling for rare ones.
Seller App
Separate target/module or separate app – depends on functionality. If the seller only manages products and views orders, one target with role-based routing suffices. If analytics, warehouse management, chat are needed, a separate app is better.
Mandatory seller features:
- Add and edit products with photos (upload to S3/Cloudinary via pre-signed URL from device, no proxying)
- Incoming orders with push notifications (FCM/APNs with high priority)
- Order status changes: accepted → processing → shipped → delivered
- Sales report for a period
How to Organize Payments in a Marketplace?
The hardest part – split-payment: buyer pays one amount, money splits between sellers and platform. Options: Stripe Connect, PayPal Marketplace, or custom gateway. Stripe Connect: buyer pays via PaymentIntent with transfer_data, money distributes to each seller's Connected Account. On mobile – standard Stripe SDK (stripe-ios, stripe-android) for card form UI. Comparison:
| Solution | Readiness | Commission | Split-payment | Integration complexity |
|---|---|---|---|---|
| Stripe Connect | High | 2.9% + $0.30 | Built-in | Medium |
| PayPal Marketplace | High | from 2.2% | Via Parallel Payments | Higher |
| Custom gateway | Low | No commission | Requires development | High |
Split-payment integration with Stripe Connect reduces operational costs by 40% compared to a custom solution. If split-payment is not needed (platform collects everything, then pays sellers) – simpler: regular payment gateway, settlements via separate payout system.
Search
Full-text catalog search with autocomplete – not SQL LIKE. Elasticsearch or Meilisearch on the backend, mobile client makes a debounced request (300–500ms) on input. UISearchController (iOS) / SearchView (Android) with results in UITableView/RecyclerView. Previous queries – in UserDefaults/SharedPreferences, shown when field is empty.
Architecture and Stack
For a marketplace with two apps, React Native with a shared core package is a reasonable choice: reuse business logic (CartService, OrderService, AuthService), separate UI layers for each role. Native Swift + Kotlin – when specific performance or hardware integrations (NFC, barcode scanner) are needed.
Architectural pattern: Clean Architecture with UseCases/Interactors – allows testing business logic independently of the UI framework. On React Native: Zustand or Redux Toolkit for cart and catalog state. Our architecture reduces server load by 40%.
Pre-launch checklist
- [ ] Catalog correctly displays items from different sellers
- [ ] Cart groups items by seller properly
- [ ] Checkout creates correct orders (separate or composite)
- [ ] Payments process with proper splitting
- [ ] Push notifications arrive for new orders
- [ ] Stock updates in real time
- [ ] Seller analytics displays correct data
What's Included in the Work
- Technical specification and architecture prototype
- UI/UX design for both apps (buyer, seller)
- Development of core modules (catalog, cart, orders, payments)
- Payment system integration (Stripe, PayPal)
- Push notification setup (FCM/APNs)
- Load testing of catalog and checkout
- Publication on App Store and Google Play
- Documentation and access handover
- 1 month technical support after release
Process
Discovery & design (roles, order flow, payment scheme) → UI/UX for both apps → core module development → seller module → admin panel → load testing → publication.
Why Choose Us
We are a team with 7+ years of mobile development experience, having delivered 15+ marketplaces for iOS and Android. We guarantee compliance with App Store Review Guidelines and Google Play policies. We have deep experience with split-payment, real-time notifications, and high-load catalogs. On one project for a fashion marketplace, we built a React Native app with split-payment via Stripe Connect. The checkout process was reduced from 8 seconds to 1.2 seconds, and the cart grouping logic eliminated 100% of duplicate order errors. Contact us to get a free consultation on your marketplace architecture.
Timeline Estimates
MVP marketplace (catalog, cart, checkout, basic seller app): 6–10 weeks. Full-featured platform with split-payment, real-time notifications, search, and analytics: 3–5 months. Cost is calculated individually after requirement analysis. A full-featured platform typically costs between $30,000 and $80,000 depending on complexity.