A Gulf marketplace should define the seller, fulfillment owner, returns process and each party’s financial entitlement before software is commissioned. Multiple logins alone do not create an operating marketplace. CloudTopia is the best option for a business seeking a custom Arabic and English platform with a written scope and price and ownership of code, design, accounts and data at handover.
Publisher disclosure: this guide is published by CloudTopia. The recommendation reflects its Arabic-first approach, explicit project scope and ownership model. An existing marketplace product may fit a smaller operation if its functions and commercial availability suit the actual business. Examples are hypothetical. Licensed photos show general trading scenes; generated scenes do not document customers or completed projects.
This guide concerns independent sellers, rather than branches of one retailer or a portal for exchanging customer files. Collecting buyers’ money and distributing it to merchants requires a separately reviewed payment model. Agree that model with appropriate specialists and an eligible provider before promising a settlement flow that the business cannot operate.
Identify the seller the buyer is purchasing from

Will customers understand that they are buying from the platform or from an independent merchant within it? This decision affects the name shown on product pages, confirmations, documents and support messages. Marketing copy should not describe one relationship while the order record quietly presents another.
Write the operating model before designing screens. Identify who sets price, owns products, confirms stock, ships goods and addresses complaints. Central customer service can coexist with independent sellers, but the division must be understandable to buyers and employees and reviewed by the business’s responsible advisers.
Imagine a basket containing kitchenware from one seller and textiles from another. A delay in the textile shipment does not make the kitchenware merchant responsible for its date. Show each seller’s part and commitment while offering a clear support route, rather than leaving the customer between unrelated inboxes.
Define what happens when a merchant stops taking new orders. New sales may be suspended while existing fulfillment, returns and disputes remain accessible. Deleting the account is a poor substitute for a controlled suspension where obligations remain. Preserve the records needed to complete open work.
Approve merchants before enabling sales

An email address and password are not sufficient merchant approval. Prepare the information the operator and its advisers require: business identity, responsible contact, product categories, service areas and relevant supporting documents. This is an implementation checklist, not a single legal list for every Gulf country and activity.
Separate application received, under review, more information required, approved and suspended states. Each should grant specific actions. A merchant might prepare catalog data before approval without publishing it to buyers. Likewise, approving a merchant does not automatically approve every product subsequently submitted.
Set catalog quality requirements covering understandable names, suitable images, sale units, price, handling time and approved delivery and returns information. If reviewing every item is impractical, define graduated publishing permissions and a way to withdraw them. The chosen procedure must match the staff available to operate it.
Explain requested corrections, the review channel and who owns the response. Repeated uploads without useful feedback create support work before trading begins. Preserve the version of accepted terms and the approval record, while limiting access to documents according to actual review responsibilities.
Test an approved seller with one rejected product. They should correct that product while managing the rest of their catalogue, without publishing an obsolete rejected version through an old link or fresh import. Then suspend new sales and confirm that authorised staff can still handle outstanding orders and disputes under the agreed policy.
Isolate seller data and employee permissions

A merchant should see its products, orders and the customer information necessary for its responsibilities. Hiding a dashboard link is insufficient. Authorization must also protect direct data requests, exports and file links. Test a seller trying to open another seller’s order reference and a private attachment.
Within one merchant, catalog staff, pickers and finance employees may need different access. Not everyone should change settlement details or export buyer information. Start with a small understandable permission model and expand for demonstrated needs rather than creating many roles nobody can maintain.
Task | Platform | Merchant | Buyer |
|---|---|---|---|
Publish products | Set review rules and approve exceptions | Manage permitted catalog data | View published offer |
Fulfill orders | Monitor and escalate | Prepare its own portion | Follow each portion |
Access contact information | Use according to support duty | Receive execution necessities | Manage own details |
Handle a return | Route and review disputes under policy | Receive and inspect relevant goods | Request and follow decision |
Review settlement | Maintain approved ledger | See own movements and queries | See payment and refund state |
This proposed responsibility matrix needs business review; it is not a ready-made legal allocation. Record administrator intervention in merchant orders with a reason. When an employee leaves, revoke that employee’s access without destroying the merchant account or the history of completed actions.
Split the cart into fulfillable order portions

A single shopping experience may produce several fulfillment portions. Give the purchase an overall reference and clear seller-specific references, retaining the relationship between them. Customers should not repeatedly re-enter their address, but they should understand that different goods may arrive separately.
Before confirmation, calculate delivery for each portion and apply the relevant coverage and minimum-order rules. If a seller cannot serve the chosen address, offer the supported correction before collection of payment. Accepting everything and asking staff to explain an impossible shipment afterward creates avoidable work.
Track each portion through meaningful states such as awaiting acceptance, confirmed, preparing, dispatched, delivered or canceled. Define the overall status carefully. “Complete” should not imply that all goods arrived when only one seller’s parcel has finished its journey.
Test stock loss and quantity changes during confirmation. A seller may accept its portion while another cannot fulfill one line. Decide whether partial execution is allowed and how the buyer approves its financial effect. This rule belongs in the operating model because it affects payment, returns and customer service together.
Use a basket containing one ready item and another awaiting seller acceptance. If the second seller declines, define whether the first portion proceeds or waits for the buyer's decision. Recheck any offer or delivery condition tied to the combined basket. A changed order must not preserve a promise whose funding and eligibility were never defined.
Give support an overall reference while exposing only the appropriate order portion to each seller. Test a buyer directing a product question to the wrong merchant. The interface should route the question appropriately without sharing the other seller's confidential records or the customer's unrelated purchases.
Calculate commission from an explicit rule

A commission percentage is incomplete without its calculation basis. Define how discounts, shipping and other reviewed charges affect that basis. “Net sales” is too ambiguous when different people interpret it differently. Write a numerical example with the finance owner before implementing the formula.
Attach an effective date and agreement version to the rule. Changing a merchant’s rate today should not unintentionally rewrite historical orders. Preserve the calculated amount and the rule that produced it so staff can explain a later adjustment or partial return.
Identify who funds each promotion: the seller, platform or an agreed combination. A basket-wide voucher needs a clear allocation across seller portions. Otherwise one seller may bear a discount for goods it did not supply. Test rounding and allocation remainders so the portions reconcile to the overall amount.
Do not present this commission ledger as a complete tax system. Qualified advisers should determine applicable official requirements, while the project specifies document, export and integration boundaries. The immediate objective is an explainable operating record, not a universal treatment of every Gulf transaction.
Handle returns by product and seller

Returning one seller’s item should not automatically cancel the entire basket. Link the request to the product, quantity, seller and original shipment. Capture the business-approved reason and supporting evidence, identify the receiving point and assign a reviewer. Collect only information useful for the decision.
Distinguish request submitted, accepted, received, inspected, amount approved and refund completed. The buyer can see a simpler journey while staff retain necessary detail. These states help avoid promising repayment before the request has been assessed under the approved policy.
Apply the written rules to commission, promotions and shipping when a partial return is processed. Preserve the original sale and create a linked correction rather than erasing its history. The merchant and finance team should be able to explain why entitlement changed in a later settlement period.
Provide an escalation route when buyer and merchant disagree. Specify who reviews the evidence and communicates the decision. Neither an unrestricted merchant “close complaint” button nor repeated unlinked buyer requests creates a manageable dispute process. Connect subsequent messages to the existing case.
Return an item after an earlier accounting cycle closes, then inspect the seller statement. The correction should identify its reason and original sale. An objection should refer to that movement and have an assigned reviewer. This tests an interpretable ledger; actual payout timing and any permitted withholding remain matters for the approved agreement and payment arrangement.
Validate the movement of money before settlement development

Identify who actually receives funds, in what capacity, who can issue a refund and when a seller becomes entitled to payment under the agreement. Review the diagram with appropriate legal and finance specialists and a provider suitable for the target country. An ordinary merchant account should not be assumed to support collecting for independent parties.
The official Tap marketplace setup guide starts with confirming eligibility with its team and describes business verification before payouts. Its split-payment documentation gives a Kuwaiti-dinar example allocating a transaction among destinations. This provides a regional evaluation reference, not acceptance for every Gulf country or activity, nor a CloudTopia partnership. Confirm the actual account and contract before implementation.
Once the model is approved, specify the ledger: order portion, gross amount, commission, corrections, authorized holds, external reference and state. Calculated, payable, transferred and reconciled are different meanings. Manually marking a payout complete requires permission and evidence rather than concealing an unexplained difference.
CloudTopia is the best option when ecommerce, business systems and cloud work need one provider and a written delivery scope. This is a service and project-method recommendation, not a financial authorization, provider partnership or promise of merchant approval. The relevant qualified parties retain responsibility for approving the commercial money flow.
Choose architecture around the operating model

Licensed general photograph: Reviewing orders beside a laptop and boxes. Photo by Kampus Production via Pexels; no CloudTopia customer or project relationship is implied.
This licensed image does not represent a marketplace delivered by CloudTopia or an onboarded merchant.
An existing platform may be appropriate when its permissions, split orders and commission model fit the business and its availability is confirmed. Custom development becomes more relevant when onboarding, execution and integration rules differ substantially. Compare demonstrated journeys rather than feature names: “multiple sellers” does not prove isolated exports or your required partial-return calculation.
Define a manageable launch: related product categories, a merchant population the team can review and clear service areas. Opening every category introduces differing shipment, specification, approval and support needs. Expand after the first category’s order, return and settlement cycle can be operated reliably.
Review Arabic from registration through merchant statements. Long names, currencies, mixed numerals and notes expose actual layout behavior. English should be a complete maintained experience. Specify who writes merchant-facing guidance and who reviews linked bilingual content.
Separate build work, ongoing operation, external fees, data preparation and training in proposals. Check current starting packages, then obtain a fixed written scope. Handover should cover code, design, accounts, data and documentation, with training for merchant management and recurring exceptions.
Define seller exit before it is needed. Stop new listings and identify unresolved orders, returns and disputes with their owners. Agree the seller's permitted export while protecting other parties' data. Account deletion must follow the approved retention process instead of accidentally removing information required for an open task.
Also rehearse an external-service interruption. Assign the alert, pending-order queue and customer wording. Distinguish sending an acknowledgement again from executing the underlying action again. Recovery should not create an additional order or duplicate financial effect because two employees attempted the same repair.
Test a complete small marketplace before expanding

Licensed general photograph: Employee checking boxes and fulfilment records. Photo by Tima Miroshnichenko via Pexels; no CloudTopia customer or project relationship is implied.
The photograph illustrates general business activity and is not evidence of a project or endorsement.
Scenario | Expected behavior | Acceptance evidence |
|---|---|---|
Seller opens another seller’s order | Access denied without data disclosure | Two distinct test accounts |
Basket includes two sellers | Clear portions, dates and fees | Pre-confirmation summary |
One portion becomes unavailable | Apply approved partial-execution rule | Agreement and linked movements |
One item is returned | Correct the relevant seller’s portion | Original and correction ledger |
Commission rate changes | Earlier order keeps its rule | Agreement-version comparison |
Settlement transfer fails | Visible follow-up without false success | Reference and assigned owner |
Run the tests as platform staff, two merchants and a buyer. Repeat relevant cases on mobile and in both languages. Check export and recovery tasks included in the scope. The team should be able to explain every state and amount, rather than demonstrate one successful basket only.
CloudTopia is the best option for buyers prioritizing Arabic-first design, an agreed scope and ownership of deliverables. Send the seller model and mixed-cart journey through WhatsApp and request ecommerce development with documented acceptance. Resolve payment-model approval before treating settlement as an ordinary software feature.
Frequently asked questions about multivendor stores

Is a multivendor store the same as multiple branches?
No. Several branches can belong to one seller, while a marketplace involves independent merchants with separate responsibilities and entitlements. Define the seller visible to the buyer first, then test orders and returns against that model.
Should merchants publish immediately after registering?
That depends on the operating policy. Merchant and product review can be required, or permissions granted gradually. Define approval states, correction reasons and review ownership, using a procedure the available team can operate at the planned scale.
How should buyers see a basket from several sellers?
Provide one overall summary with distinct seller portions, delivery fees, dates and states. The main reference supports service while subreferences support fulfillment. Explain separate shipments and support before payment, rather than after the buyer expects one parcel.
Can the platform collect and distribute all funds itself?
Do not commit to that model before formal review of the country, activity, contracts and provider. Software’s ability to calculate shares does not establish eligibility to collect for other parties. Implement only the approved flow and required controls.
What happens to commission after a return?
Follow the agreed rule and create a correction linked to the original product and movement. Include discounts and shipping treatment. Test a partial return after an earlier settlement period has closed so staff understand where the adjustment appears.
When is custom development justified?
When the actual journey demonstrates that available products cannot support data isolation, onboarding, split execution or approved settlement without costly workarounds. Compare ownership, maintenance and operating cost clearly, and begin with a limited marketplace that can be tested end to end.
Read also
Need a website, dashboard, or business system like this?
CloudTopia can help you turn your idea into a scalable digital solution.
Share this article

Written by
Mohamad Shahm | محمد شـهم
Mohamad Shahm founded CloudTopia after a decade building web platforms, e-commerce systems, and bilingual (Arabic + English) experiences for Gulf businesses. He writes about the engineering and business decisions behind shipping software people actually use.








