RB Marketplace and its Android shopping app
For RB Marketplace, Netbase built an English-first multi-vendor marketplace for West Africa on Laravel, then built the customer shopping app on that marketplace's own API. This record sets out what was delivered on each side, what deliberately stayed in the web panel, and what the project documents do not support. No result is claimed.
Submit a project See the other records
Record at a glance
- Evidence level
- Portfolio record: delivered scope from the project documents, no measured result
- Client
- RB Marketplace; its legal entity and its founder are not named
- Market
- West Africa, English-first
- Netbase role
- Built the marketplace, and the customer shopping app on its API
- App scope
- Android, with iOS in the extended scope
- Service
- Custom Product Engineering
- Published metrics
- None
What the marketplace contains
The buyer side is a storefront with search and filters, a wishlist, a cart, coupons and checkout. The vendor side covers registration with administrator approval, store profiles, product and inventory management, order fulfilment and tracking updates, earnings, commission deductions and payout requests. The administrator side controls vendor approval, product moderation, commission, payouts, campaigns and analytics. Around all three sits a customer REST API with device tokens and notifications, transactional email configured with SPF and DKIM, and 90 days of post-launch support.
What the shopping app contains
The app was built on the marketplace API rather than beside it, so the catalogue, the cart and the order record are the same ones the storefront uses. It was delivered for Android, with iOS in the extended scope, across more than 45 screens in six phases running from kickoff and an API audit through to quality assurance and handover.
Shoppers get category and brand browsing, smart search, product comparison, flash sales, a persistent cart with coupons and shipping costs, checkout through a secure web view, order tracking, returns with photographs, cancellations and invoice download. Around that sit a server-synced wishlist, an address book, reviews, dark mode and offline browsing, Google, Facebook and Apple sign-in, and an in-app notification panel fed by push notifications for order updates, flash sales, and alerts when an item comes back into stock or its cost drops.
What the app deliberately does not do
Administrator work stays in the web panel. Vendor approval, moderation, payouts and campaign management are done in a browser, and the app is a shopping client only. That is a scope boundary worth copying: a marketplace that tries to put its back office on a phone in the first release usually ships neither side well.
Technology and delivery
The marketplace is a Laravel application exposing a customer REST API, and the app consumes that API. The project documents record no mobile framework, so none is named here. Transactional email was configured with SPF and DKIM at the marketplace end, and the engagement included 90 days of support after launch.
Evidence level and limitations
- This is a portfolio record. It reports scope taken from the proposal, the agreement and the support documents, and nothing those documents do not state.
- No result, figure or count is published. The seller, product and rating counts in the source home-page mockup are placeholders, and a live catalogue changes anyway.
- The client's legal entity, its founder and the live domain are withheld.
- No app-store or marketplace listing is claimed for either mobile platform.
- An internal creator and dropship model appears in the source as strategy. It is not delivered scope and is not described here.
- The client is named here on Netbase's own authority, recorded in the claim register on 25 September 2026. No consent from this client is on record, and no confidentiality obligation covers the project. If the client asks not to be named, this record reverts to the anonymised form the register keeps for it; the methodology page carries the address for that request.
- The image on this page is illustrative. It shows no client system and no interface.
Questions a buyer asks
Was the app published to an app store? The documents record delivery for Android, with iOS in the extended scope. They do not record a store listing, so none is claimed here.
Does the app include the vendor or administrator tools? No. Those stay in the web panel, and the app covers the shopping journey only.
Are any usage or sales figures available? No. Nothing in the source documents measures an outcome, so this record publishes scope and stops there.
Building a marketplace and an app for it?
Comparable work is scoped through Custom Product Engineering, the recurring operational patterns are set out under marketplace and classifieds operations, and the methodology page explains how evidence on this site is graded; the other work records carry the same grading. When you are ready, submit a project brief. OutsourcingVN is operated by Netbase JSC and is Netbase's own outsourcing-services platform.