White-label
Marketplace software, white-labelled for you
A customizable two-sided marketplace under your branding. Original code, finished under your branding, scoped in writing before any build starts.
What it typically includes
- Seller onboarding, listings and order management
- Payments, split payouts and commission rules
- Reviews, disputes and admin tooling
The exact feature list is agreed in writing for your project - nothing above is a fixed bundle or a fixed price.
How white-labelling works
- Your name, logo, colours and domain throughout the product.
- Store listings and support channels under your company.
- Your content, your terms and your customer relationships.
Scope areas for this kind of build
The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.
Overview
Sell It as Your Own Product
- Agree branding, domain, commission rules and supported payment methods under written source, licence and operating terms; identify configuration versus implementation work.
Four balance records and reconciliation scope
- Scope separate customer, seller, courier and operator balance records with reconciled ledger references; software records do not themselves establish regulated custody or completed settlement.
Browse, Cart and Checkout in the Browser
- Proposed buyer scope: category and brand navigation, filtered search/autocomplete, product variants/reviews, a multi-seller cart and checkout rules for coupons, wallet credit and loyalty.
- Inspect an approved storefront demonstration or test build; no working storefront is supplied by this page.
Shop, Products, Orders and Payouts
- Proposed seller-web scope: shop profile/identity review, product CRUD, variant stock, bulk import/export, reviewed AI descriptions, order decisions, refund responses, analytics and withdrawal requests.
Run the Shop from a Phone
- Optional Flutter seller-mobile scope: order queue, product/stock changes, refund responses, customer chat, commission visibility and withdrawal requests, tested on agreed devices.
Assignments, Proof of Delivery and Cash
- Proposed courier scope: job offers, acceptance, pickup/customer navigation, status evidence and one-time-code handover, with earnings separate from cash collected on delivery.
Catalog, People, Finance and Configuration
- Proposed operator scope: moderation, cross-seller orders/history, refund/payout review, seller/courier approval, commissions, taxes, marketing and configuration. Review which changes require a code release.
- Inspect a permissioned operator demonstration or test build rather than infer an active admin account.
- For a scoped demonstration, follow one test order from search to seller acceptance, delivery handover, admin history, tax breakdown and ledger entries. Also inspect moderation, subscriptions, commissions, gateways, currencies, languages and zones. Use approved test data and record what actually works; no live-data tour is promised here.
Market-specific requirements to scope
Scope cash handling, local/provincial fulfilment and cross-border requirements from the actual target market, rather than infer adoption patterns or reference deployments.
For any provincial or cross-border scenario, agree currencies, languages, duties, restricted items, supplier/fulfilment boundaries and qualified local review.
What Is White Label Marketplace Software?
Marketplace
- Agree category depth, variants, brands, digital-goods handling, low-stock alerts, clearance rules and the approval state required before a listing becomes visible.
Logistics
- Define courier approval, job feed, permitted location capture, handover evidence and cash reconciliation; a verified account or one-time code does not guarantee physical delivery.
Money
- Separate buyer, seller, courier and operator records; define append-only movements, completion/refund reversals and payout reconciliation against actual provider results.
- Choose web, Android, seller and courier surfaces explicitly and test their shared permissions and records.
What Does White Label Ownership Mean?
- Agree Laravel/Flutter source access, database rights, licences, supported formats and handover terms. Payment, messaging, push and AI accounts need verified owner control and secure credential handling.
- Compare self-hosted, managed or licensed delivery through written source, hosting, per-transaction, update and third-party terms; white-label branding alone does not settle ownership.
- Optional customer web storefront and Flutter Android app, with separate agreed acceptance checks.
- Optional seller web panel and Flutter Android app, with tested role and stock/order boundaries.
Marketplace Features: Catalog, Checkout, Fulfilment and Payouts
Catalog and Categories
- Scope product galleries, supported video, category/brand records, reusable attributes and searchable tags.
- Agree image/video formats, rights, moderation, limits and failure handling for product media.
- Choose a tested category-depth limit and handling of moved, hidden or deleted branches.
- Define brand, attribute and colour libraries with editing permissions.
Variant Matrix
- Model colour, size and custom-attribute combinations as SKU records with their own price, stock and availability rules.
- Test variants across the agreed colour, size and custom attributes.
- Keep price and quantity ownership explicit for each SKU.
- Define stock thresholds, alert recipients and stale-inventory behaviour.
Search and Discovery
- Scope autocomplete, keyword search, filters, sorting, permitted search history and operator search keys; measure relevance on agreed examples.
- Test autocomplete, no-result, misspelling and unavailable-item cases.
- Define filtering by price, brand, rating, seller and supported attributes.
- Agree relevance, price, recency and popularity sort rules and tie-breaking.
Merchandising Rails
- Define featured, popular, best-selling and rated rails plus daily, flash and clearance promotions using explicit data and approval rules.
- Agree the records and windows behind featured, popular and sales-based rails.
- Define daily/flash offer start/end, discount ownership and conflicting promotion handling.
- Scope clearance availability and expiry or short-dated-stock rules with operator review.
Multi-Vendor Cart
- Model a multi-seller cart and per-seller order split; define guest session storage and account-merge conflicts.
- Test a cart spanning sellers with changed stock, unavailable items and partial fulfilment.
- Test guest-to-account merge, duplicate lines and price/quantity changes.
- Define save-for-later and wishlist ownership and stale-item behaviour.
Checkout and Coupons
- Agree whether and in what order coupons, wallet credit and loyalty may be combined; show the final authoritative charge.
- Define flat/percentage coupon eligibility at product, category and cart level with limits and reversals.
- Test idempotent order placement and reconcile uncertain results before retrying a payment or order.
Order State Machine
- Define awaiting-payment, acceptance, fulfilment, delivery and exception states, including cancellation, return and failure; record allowed transitions and actors.
- Agree the actual order-state inventory rather than promise a fixed state count.
- Scope line-item states for partial fulfilment and their order-level effect.
- Record state-change actor, reason, timestamp and source reference.
Refunds and Returns
- Define refund evidence, review, approval, provider submission and actual settlement separately; wallet credit and original-method refunds follow approved policy.
- Record refund reason, evidence and access limits.
- Test duplicate refund requests, callbacks, retries and concurrent approvals without assuming a state machine alone prevents duplicate spending.
- Choose supported refund routes and confirm actual provider settlement before marking money returned.
Four Wallets
- Separate buyer, seller, courier and operator balances; define atomic ledger/balance updates and reconcile against provider records.
- Agree the operating/legal model for each balance or wallet before implementation.
- Require a reference and reason for balance movements and test rollback/concurrency.
- Only expose wallet top-ups through explicitly supported, approved and tested payment routes.
Revenue Models: Commission, Subscriptions, Delivery and Placement
Possible mechanisms include sales commission, subscriptions, delivery charges, sponsored placement and branded deployments. Define each revenue record and liability separately; wallet balances or settlement delays are not automatically revenue.
Commission on Sales
- Define commission priority across global/category/seller/product rules, effective dates and completion/refund reversals; reconcile actual seller earnings.
Vendor Subscriptions
- Optional seller subscriptions can define product limits, commissions, placement and support terms; test billing, trial, grace, renewal and access-expiry rules.
Featured Placement
- Optional sponsored banners, search/category placement and event-participation fees need eligibility, labelling, budget and delivery records.
Wallet Float
- Wallet balances and payout timing require a reviewed custody/settlement model; do not assume held customer or seller funds are available revenue. Scope any top-up bonus and liability explicitly.
White-Label Deployment
- Branded deployments or redistribution require written source, third-party licence, support and operating terms for each client or territory.
- Compare commission, subscription and delivery-charge options against expected volumes, actual costs and applicable rules; no margin or revenue outcome is promised.
Admin Dashboard: Catalog, Orders, Payouts and Configuration
Scope module and record permissions for catalogue, finance, moderation and settings. Test the selected staff roles and direct API requests rather than assume a fine-grained console already exists.
KPI Dashboard
- Define GMV, order, account, sales and queue metrics with source, time window, permissions and reconciliation rules.
Catalog Moderation
- Scope listing approve/reject/bulk operations, editing permissions and category/brand/attribute ownership with audit and reversal where supported.
Cross-Vendor Orders
- Display cross-seller order state, permitted field changes, revised dates and invoices; privileged overrides require authorization, reason and history.
Refund Queue
- Define refund decisions, notes and evidence, then reconcile wallet or original-provider settlement outcomes.
Withdrawal Queue
- Define seller/courier payout request, review, approval and provider result separately; a mark-processed action is not proof of a successful transfer.
People and Approval
- Scope buyer access, seller/courier approval, suspension, subscriptions and zone assignment with least-privilege roles.
Marketing Surface
- Define banners, promotions, coupons and push/email/SMS campaign tools with reviewed audience, consent and send authority; no live marketing is activated.
Tax Configuration
- Use qualified tax requirements to scope zones, classes, listing rules, inclusive/exclusive display and order breakdowns; configuration is not tax compliance.
Business Settings
- Agree GMV, orders and growth calculations and freshness labels.
- Expose seller/listing review queues only to authorized staff.
- Reconcile refund and withdrawal queue counts with their underlying states.
- Define category, seller and product report windows and attribution.
What an engagement can include
Handover scope, source access, deployment rights, maintenance and third-party licences are agreed in writing; branding alone does not establish ownership of every component.
Customer App
- Scope customer browse, search, cart, checkout and tracking with explicit loading, stale, empty and error states.
- Wallet credit, loyalty and referral mechanisms are optional scope with separate eligibility and reconciliation tests.
- Scope notification permissions and support-chat privacy, access and failure handling.
Vendor App
- Optional seller-mobile scope covers catalogue, stock, order decisions, refund responses, buyer chat, balance records and withdrawal requests.
- Test mobile catalogue, stock and order changes against shared records.
- Define refund-response authority and buyer-chat visibility.
- Distinguish displayed earnings/balance from withdrawal request and actual payout.
Delivery App
- Optional courier scope covers job offers, navigation, status evidence, handover codes, cash collection and payout requests.
- Define acceptance, rejection, expiry and reassignment of jobs.
- Record location freshness/accuracy and permitted one-time-code handover.
- Reconcile earnings, cash collected and actual payouts separately.
Customer Storefront
- Proposed storefront scope includes categories, filters, variants, reviews and a cart across sellers, with each workflow independently tested.
- Test supported buyer search and discovery against approved product data.
- Connect seller-web catalogue and shop operations through scoped APIs.
- Agree indexable product/category content, canonical routes and search-engine limitations without promising rankings.
Vendor Web Panel
- Proposed seller-web scope includes identity review, bulk catalogue import, analytics and desk-based operations with per-role permissions.
- Define operator staff accounts and separate privileged functions.
- Test module-level permissions on direct API and record requests.
- Agree seller approval and listing moderation evidence and states.
Operator Console
- Proposed operator scope covers moderation, orders, refunds, payouts, people, marketing, tax and configuration with explicit staff-role boundaries.
- Agree maintained Laravel source delivery, readable formats, access rights and third-party terms.
- Design the actual schema and reversible migrations; no fixed table inventory is asserted.
- Assess separate AI, Blog and Tax modules with interface, data and release ownership.
Full Source Code
- Agree backend and selected Flutter project handover into the approved repository, with source/licence and external-dependency terms in writing.
- Apply approved app name, logo, splash screen and colour theme to selected surfaces.
- Review branded transactional-email templates and verify sending identity before activation.
- Configure a domain only under separate owner authority, with routing and rollback checks.
Deployment and Handover
- Scope approved infrastructure, queue workers, scheduler, storage, admin runbooks and configuration checklist; verify actual deployment and recovery.
- Choose provider accounts, plan, spending limits and deployment authority before provisioning.
- Test queue worker, scheduler and storage configuration, failure handling and secret ownership.
- Request written storefront, seller, courier and operator scope, source terms, repository destination and handover evidence before work starts.
Who Is This Marketplace Software Built For?
Potential audiences include operators with a product catalogue, seller network, fulfilment plan or buyer audience, plus agencies and integrators delivering under client branding. Fit and missing operational capabilities need evaluation; no finished marketplace is implied.
Discuss whether catalogue, sellers, fulfilment and purchase workflows match the intended operating model and whether an alternative starting point or custom scope is required.
Use Cases: Retail, Grocery, Fashion & Cross-Border
Retail, grocery, fashion and cross-border operations can share concepts, but configuration versus separate engineering must be assessed for each workflow.
A broad marketplace can scope category depth, brands, moderation, seller subscriptions, commission and an operator-controlled delivery option. Actual revenue, service levels and suitability depend on the chosen operating model and tests.
Technology options we may propose
Candidate choices include PHP/Laravel, Flutter, MySQL, Redis and modular packaging. Maintained versions, compatibility, staffing, licences and operating cost require review; no selected or deployed stack is established here.
Evaluate Laravel and a module-packaging option such as nWidart against the selected extension and release boundaries; choose versions through maintenance/security review.
How It Works: Browse, Buy, Fulfil and Settle
A proposed end-to-end test should follow one order through buyer, seller, courier and operator records and reconcile each relevant ledger with provider results.
How It Works
- Use an approved test order to inspect the intended discovery-to-settlement path, without treating the written flow as a completed transaction.
- Test category navigation, brand directory, keyword search and autocomplete.
- Exercise agreed price, brand, rating, seller and attribute filters and sorting.
- Inspect product media, variant selection, available-stock evidence and review moderation.
How we would approach the architecture
Layered Backend
- A candidate layered backend can separate HTTP validation, orchestration/transactions, data access and entity models; choose and test the actual boundaries.
Event-Driven Side Effects
- Define events for orders, state changes, seller approval, payout requests and refunds; make listeners idempotent and distinguish ledger authority from notification/analytics side effects.
Queues and Scheduler
- Evaluate Redis-backed workers, a process supervisor and a scheduler for media, documents, messaging, AI jobs, renewals, reminders and backups; test retries, permissions and duplicate effects.
Append-Only Ledgers
- Scope append-only ledger and state-change records with correction/reversal entries, authorized access and retention. Reconciliation and actual audit evidence remain required.
Horizontal Scale
- Consider stateless app instances, load balancing, MySQL reporting replicas, Redis, object storage and CDN delivery based on measured workload and consistency requirements.
How we would design for scale
Identify catalogue, search, orders, messaging and fleet-write workloads, then measure query, queue, cache, storage and failure behaviour. The mechanisms below are proposed design decisions, not already-tested capacity or readiness claims.
Catalogue and Read Load
- Measure catalogue queries and cache category, banner, configuration or rail data where appropriate; define invalidation, pagination and relation loading rather than promise no N+1 queries.
Order Tables at Peak
- Profile orders, items, notifications, chat and delivery queries; select indexes and archive rules with retention, report correctness and migration/restore tests instead of a fixed archive age.
Work That Runs Off the Request
- Queue suitable image, invoice, report, messaging and AI jobs with bounded retry and dead-letter handling; test checkout behaviour when a worker or provider fails.
Fleet Write Volume
- Model fleet update frequency, freshness, write volume and location retention; evaluate dedicated queues or time-based partitions only against measured demand.
Cached Reads
- Choose and validate caches for category, banner, configuration and rail reads with correct freshness and tenant boundaries.
Hot Tables Indexed
- Choose composite indexes from actual seller, courier, status and date queries; measure plans and write overhead.
Async by Default
- Identify which jobs may be asynchronous and which order/payment checks must complete before confirmation.
Fleet Write Load
- Evaluate delivery/history partitioning, dedicated position processing and recovery without promising a particular scale outcome.
Search Headroom
- Compare MySQL full-text, Elasticsearch or Meilisearch against relevance, consistency, cost and operational requirements; replacement is not assumed to be a drop-in.
Security and privacy requirements we can design for
Map the data and authority behind buyer/seller/courier/operator balances, tenant records, addresses, payment requests, cash collection and location history. Scope ledger corrections, atomic updates, tenant checks, payment-field handling and restricted location/contact access, then test the actual build. No single mechanism guarantees secure operation.
Verify browser/transport headers, session controls, network policy and secret ownership for the selected deployment and maintenance responsibilities.
Account and data control requirements
- Choose maintained password hashing, secure cookie/session settings, CSRF protection and assignment validation; test authentication and state-changing routes against agreed requirements.
- Define deletion/export/retention rules and any grace period with privacy review; obtain valid consent where required before marketing and test the actual data path.
Tenant Isolation
- Enforce seller/courier record ownership, model permissions and scoped API-token abilities; test direct and cross-tenant read/write attempts.
Payment Integrity
- Use approved hosted payment fields where suitable, verify webhook signatures, reconcile provider references and test idempotency/refund concurrency; no absolute card-isolation or double-spend guarantee is established.
Injection and XSS
- Test query parameterization, input validation, output escaping and rich-text sanitization with approved malicious-input cases; framework/library choice alone is not proof.
Audit Trail
- Record order/status changes, refunds, per-actor balance movements and AI usage/cost with redacted error logs, restricted audit access and tested retention.
Add-Ons: Search, Analytics, Integrations and Automation
The proposed marketplace scope and these optional extensions require separate written requirements, dependencies and acceptance checks. No completed base build or included extension is implied.
External Search
- Optional Elasticsearch/Meilisearch integration requires indexed fields, synchronization, backfill, access, failure and relevance tests against the chosen catalogue workload.
Advanced Analytics
- Optional cohorts, seller performance, basket analysis and forecasting require permitted data, defined metrics and evidence; reporting infrastructure is scoped separately.
ERP and Accounting Bridges
- Optional ERP/accounting/POS synchronization needs authoritative fields, conflict handling, idempotency and reconciliation; no zero-manual-work outcome is promised.
Loyalty and Membership Tiers
- Optional membership, delivery-fee benefits, member pricing, loyalty and wallet rules require eligibility, usage limits, billing and refund tests.
B2B and Wholesale
- Optional B2B pricing groups, minimum quantities, quote requests and credit terms need operator rules and financial/legal review where applicable.
Sponsored Placement Engine
- Optional sponsored-placement bidding requires budgets, eligibility, ad labels, placement evidence, dispute and actual payment handling.
Observability Stack
- Optional Prometheus/Grafana or equivalents, log aggregation and OpenTelemetry tracing require approved data collection, alert ownership and measured operating cost.
- Optional iOS builds of the selected Flutter applications need compatibility, signing, store-account authority, assets, review and release checks; store acceptance is not guaranteed.
Related commerce product directions
Related commerce categories may share requirements, but source, data, integration and deployment boundaries need their own scope. No universal ready-made coverage is claimed.
A multi-seller marketplace can be scoped around catalogue, fulfilment, review and dispute mechanisms, with evidence against agreed acceptance checks.
Follow the records
One marketplace, four different order outcomes
Open a proposed scenario to see how buyer, seller, courier and operator records connect. This is an explanatory workflow, not a running checkout or evidence of live fulfilment.
A multi-seller order completes
01Buyer confirms the charge
Show the authoritative total, seller split, stock and payment terms before accepting the order. A payment request is not a provider-confirmed receipt.
02Sellers accept their own work
Each seller sees only its permitted items and records acceptance/rejection. Keep the parent order distinct from per-seller and per-line status.
03Courier records the handover
Track accepted assignment, pickup and delivery evidence with fresh-location limits; one-time codes supplement rather than replace the operator delivery process.
04Operator reconciles the result
Match payment, commission, courier earnings and seller payout records to actual provider settlement, with references for corrections.
Stock changes or only part can be fulfilled
01Detect the changed item
Mark the affected SKU, quantity, seller and quote as changed; do not silently substitute an item or charge.
02Obtain the required decision
Apply the agreed rule for customer review, item removal or cancellation while unaffected seller orders retain their own states.
03Reconcile money and delivery
Record any reduced capture, refund request, delivery-fee change or split shipment separately from confirmed provider outcomes.
04Close only the resolved parts
Keep pending items and support ownership visible; a partially delivered order must not be shown as wholly complete.
Payment or refund result is uncertain
01Keep the uncertain state
Retain provider request and order references. Do not call an authorization, timeout or refund submission a completed charge or refund.
02Check the actual source
Reconcile approved provider records and callbacks before retrying, with idempotency and concurrent-review controls.
03Record a correction safely
Separate wallet-credit policy from original-method refund, require the proper reviewer and append correction/reversal entries.
04Notify from verified facts
Tell the buyer/operator what completed and what remains pending without inventing settlement times or automatically charging again.
Cash on delivery and partner payout
01Define collection authority
Agree cash eligibility, limits, collected-by role, receipt evidence and the effect of rejected or incomplete deliveries.
02Separate cash and earnings
Keep courier cash liability, courier earnings, seller proceeds and operator commission as different records.
03Review withdrawal instructions
Verify beneficiary ownership, approved payout route, amount and reviewer before a transfer; status labels cannot prove money arrived.
04Reconcile outstanding balances
Match collection, remittance, adjustments and actual payout results, with missing-cash and disputed-delivery exception owners.
Review engineering practices or discuss marketplace requirements.
Describe your Marketplace software
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.comMore pages on this build
4 pages describing this proposed build.