Define responsibility before building the storefront
A marketplace separates the platform, seller, fulfilment team and payment provider. Decide whether you sell goods, digital products or services. For each model, describe when an order becomes complete and who resolves a complaint. A shared storefront does not create a shared fulfilment process automatically.
Design seller and catalogue approval
Map application, review, approval, suspension and reactivation. Establish common product fields, categories, variants and image requirements. A listing in the wrong category should enter a review workflow rather than publish silently. Show the seller what needs correcting and preserve a record of the decision.
Split the operational order by seller
A customer may use one basket while receiving separate shipments. Link the parent order to seller suborders and display their individual states. Test cancelling one item while the remaining items continue. Explain shipping costs, delivery expectations and support responsibility before payment, rather than leaving these decisions to support staff later.
Separate commission calculation from reconciliation
Specify the calculation base, campaign funding and partial-refund treatment. Confirm that the chosen payment provider supports the operating country and business model. A sample integration is not evidence of availability. Keep provider transaction identifiers alongside calculated amounts and a traceable adjustment history.
Build an exception queue for operations
The administration panel needs more than completed orders. Give support staff queues for failed payment notifications, missing stock, delivery disputes and seller restrictions. Limit who can alter financial or order states. Record the actor, time and reason so a support action can be explained later.
Pilot one category with a few sellers
Include a two-seller basket, partial refund, disabled seller and duplicate payment notification in acceptance tests. For a meaningful proposal, share your product model, seller workflow, payment provider and existing integrations. Estimate the operational scope as well as storefront design; postpone features that do not help validate the pilot.
Worked example: make the scope concrete
Illustrative scenario. Adapt these checks to your own workflow.
One marketplace cart can create different delivery and return journeys for each seller. Define seller approval, commission and support ownership, then pilot a limited seller group.
A common failure and why it matters
A seller dashboard alone does not create a marketplace. Review payment-provider terms and applicable requirements for settlement separately. Track collection, transfer and refunds together.
How to verify the delivered work
Test a two-seller cart, one cancellation and a partial refund. Reconcile commission after changes and prevent one seller from accessing another's customer or order data.
Implementation and maintenance checklist
The meaningful test of sales software includes cancellation and correction, not only the perfect order. Link product identity, price validity, stock movement and payment records. If the customer and operations team see different states, the difference should have an explanation. When a process stops halfway, determine which step completed before repeating anything. A clear reconciliation trail helps both support and accounting understand the same transaction.
- Catalogue: Test a variant, discounted price, unavailable item and withdrawn product. Do not select only the easiest product family. Include missing optional fields and long descriptions so the page and business rules are tested together.
- Order: Define acceptance for repeated clicks, delayed payment responses, cancellation and partial return. A safe retry should not repeat a charge or stock deduction. Test communication after an uncertain result so customers are not encouraged to pay again unnecessarily.
- Operations: Let staff trace an order to payment and warehouse activity using stable identifiers. Assign someone to investigate end-of-day discrepancies and define how customers are informed. Document which system is authoritative when the storefront, payment provider and stock service briefly disagree.
Further reading
docs.stripe.com — connect / marketplaceLet’s bring this idea to your product.
Define your project goals and technical needs with us.
Let’s talk about your project


