GBCORP BLOG · IT SERVICES

Marketplace Mobile App: Buyers, Sellers and the Operator on a Phone

Published January 7, 2024 · 6 min read

A marketplace on a phone is three apps pretending to be one: the buyer's, the seller's and the operator's. The engine has to serve all three from one place, and it has to pass the stores' rules for marketplaces.

Marketplace Mobile App: Buyers, Sellers and the Operator on a Phone

A marketplace mobile app lets many sellers list, buyers shop across them in one cart, and the operator take a commission while everyone gets paid correctly, all from phones. GBCORP’s white-label marketplace and ordering platform carries the buyer app, the seller app and the operator console in production, so an operator launches a branded marketplace on iOS, Android and the web within days at a flat monthly plan, with payments through its own gateway and the data in its own project.

Three apps, one engine

AppWhat it doesWhere
Buyer appSearch across sellers, one cart, one checkout, tracking per seller, reviews, disputesiOS, Android, web
Seller appListings, stock, orders, fulfilment, payouts, statements, messagesiOS, Android, web
Operator consoleSeller approval, listing review, commissions, disputes, reportsWeb

One cart, split orders, exact payouts

A buyer pays once; the order splits per seller; each seller fulfils its part; the buyer tracks each part. Commission is configured per category, seller or plan. Payouts are calculated net of commission and fees, held until delivery is confirmed, and released on a schedule with statements. Refunds reverse the split. The ledger reconciles to the operator’s gateway to the cent.

Trust and safety in the core

Sellers verified with documents before listing. Listings reviewed before publication. Word rules in listings and messages. Tripwires for suspicious patterns. A safety queue for the operator and house rules accepted at sign-up. Reporting and blocking in the buyer app. These are the features the stores check for in a marketplace, and the features that keep buyers.

Store rules for marketplaces

Both stores treat a marketplace as an app with user-generated content: moderation, reporting, blocking and account deletion must exist, and physical goods must be paid through the operator’s own gateway rather than in-app purchase. GBCORP’s engine meets each rule, and its own marketplace apps pass review on every release.

Checklist before launch

  • Categories and the commission per category or plan.
  • Seller onboarding rules and documents required.
  • Delivery model: per seller, platform drivers, pickup, or a mix.
  • Payout schedule and hold period.
  • Payment-gateway account in the operator’s name.
  • The three numbers to watch: active sellers, orders per buyer, dispute rate.

The numbers to expect

Live within one to five working days on the web, store listings after review, a flat monthly plan. Marketplaces with tender flows, unusual commission logic or thousands of sellers are custom work on the same engine, scoped in a week and quoted per release. Customised or more complex functionality is quoted separately before any work starts.

A worked example

A regional association of craft producers wants a marketplace app so its hundred members can sell under one brand. On the platform, each producer gets a seller account and a storefront, the association approves them with documents, buyers shop across producers in one cart, commission per category pays for the platform, and payouts run weekly with statements. The association’s own drivers collect on two days a week. The app is in both stores under the association’s name in three weeks, and the console shows active sellers and orders per buyer every Monday.

Delivery models on a marketplace

Sellers deliver their own orders. The platform runs drivers who collect from sellers on a schedule. Buyers collect from a seller or a central point. Any mix by category or zone. Each is configuration, with fees calculated per model and shown before checkout, and the driver app is the same one GBCORP’s delivery products use.

Reports the operator reads

Active sellers and new listings per week. Orders and value per buyer. Commission by category. Payouts made and pending. Late shipments and disputes per seller. Searches with no results, which is the list of what to recruit next. Exports for the accountant. All in the console, so the operator recruits and removes sellers from evidence.

Multi-market from the core

Languages, currency, tax and the payment provider are configured per market, with right-to-left layouts as a setting. Sellers and buyers are tagged to a market, and commission can differ per market in the same console. A marketplace in two countries runs one platform with two configurations.

Growth built in

Seller referral links with a commission holiday. Buyer referral rewards. Featured listings sold to sellers as a plan. Search with no results shown to the operator as recruitment targets. Loyalty points across sellers, so a buyer who shops with three producers earns on one card. Each is a configuration, switched on when the operator wants it, with its result in the console, so the operator can see which one moved orders per buyer and switch off the ones that did not.

Ownership of the marketplace

Brand, data and accounts are the operator’s. Store and payment accounts are in the operator’s name. Seller and buyer data are exportable. On custom releases, the code is the operator’s, and no credentials are retained by GBCORP after a hand-over unless a support contract requires them.

Questions we hear first

Do sellers need a separate app?

The seller app is part of the engine; a seller signs into it with the same account it used to apply.

Can we run services as well as goods?

Yes. Bookable services with calendars sit beside products in the same cart.

How are sellers paid?

Automatically calculated payouts on a schedule, through the operator’s own payment provider, with statements.

Who owns the marketplace?

The operator: brand, data, accounts and, on custom work, the code.

Where to start

The GBCORP Marketplace and Ordering Platform is the product; the GBCORP mobile app development hub sets out the method. For the operator’s side in depth, read multi vendor marketplace app development explained.

GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Premium Business, and EV's & Solutions.