In a marketplace, a buyer and a vendor are strangers, and you sit in the middle. When an order goes wrong, both sides look to you. A clear dispute process protects customers, keeps good vendors, and stops small problems from turning into lost trust. This guide covers how to resolve disputes, who should pay for refunds, and how to deal with fraud, including cash-on-delivery problems.
How to resolve a marketplace dispute
To resolve a marketplace dispute, collect evidence from both sides, check it against your published policy, offer a quick fair resolution, record the decision, apply any refund through your payment ledger and allow one appeal. Follow these seven steps:
- Collect the order details and evidence from the buyer and the vendor.
- Check the facts against your published dispute and refund policy.
- Offer a fast resolution: refund, replacement or partial credit.
- Decide and notify both sides with a short written reason.
- Apply the outcome in your ledger, including the vendor's share.
- Allow one appeal within a set period.
- Review dispute patterns to fix the cause.
The most common marketplace disputes
Most disputes fall into a small number of types. Knowing them lets you write rules in advance instead of improvising every case.
- Item not received: the buyer says the order never arrived.
- Not as described: the product differs from the listing.
- Damaged or spoiled: especially common with food and groceries.
- Missing or wrong items: part of the order is absent or incorrect.
- Late delivery: the order arrives well after the promised time.
- Vendor cancellation: the vendor cannot fulfil an accepted order.
- Payment issues: double charges, failed payments or refund delays.
Write a clear dispute and refund policy
A written policy turns an argument into a rule. Publish it where buyers and vendors can both see it, and keep it short enough to be read. Cover these points:
- What can be disputed and which categories (for example perishable goods) have different rules.
- The reporting window: how long after delivery a buyer can raise a problem. The right length depends on what you sell.
- What evidence is needed: photos, order numbers and a short description.
- Response times: how quickly each side must reply, and how fast you will decide.
- Possible outcomes: full refund, partial refund, replacement or rejection.
- Who bears the cost in each situation, as explained below.
- The appeal process, if any.
Publish your terms on a dedicated page and link to them from the checkout and the vendor dashboard. Have the policy reviewed by a qualified professional in your country, since consumer rules vary. This guide is general information, not legal advice.
Who pays for a refund?
Decide this before the first dispute. There are three common approaches, and you can combine them depending on the cause:
| Cause | Usually borne by | Why |
|---|---|---|
| Vendor error (wrong item, spoiled, not as described) | The vendor | They control the product and packing. |
| Delivery problem (lost, damaged in transit) | Marketplace or rider, depending on your model | Delivery is your service, not the vendor's. |
| Buyer remorse or change of mind | Per your policy, often the buyer | Not a fault of either seller or platform. |
| Platform or payment error | The marketplace | The fault is yours to fix. |
The table shows common approaches, not rules. Choose what suits your category and market, and state it plainly to vendors before they join.
When a refund is approved, reverse the matching share in your ledger: the vendor's part from their balance and your commission from yours. The guide to paying vendors shows a worked example of this reversal.
What evidence to collect
Good decisions rely on good records. Make it easy for both sides to supply and for you to see:
- The order timeline: placed, accepted, prepared, picked up and delivered, with times.
- Photos of the item or packaging from the buyer.
- Messages between buyer, vendor and rider.
- The delivery confirmation, such as a handover code recorded by the rider.
- The vendor's stock or preparation notes.
The delivery rider app records pickup and delivery confirmation, which gives you a timeline when a buyer claims an order never arrived.
Keep the process fast and fair
- Acknowledge quickly. Tell the buyer you received the report right away, even if the decision takes longer.
- Give both sides a say. Ask the vendor for their account before you decide.
- Set internal targets. For example, a first response within a day. Treat this as an example and set your own.
- Explain decisions. A short reason reduces repeat complaints.
- Be consistent. Similar cases should get similar outcomes.
Cash on delivery and rider disputes
Cash on delivery adds its own problems: customers who refuse an order at the door, riders who record a collection but do not hand over the cash, and disagreements about change or amounts. Reduce them with clear steps:
- Record every cash collection in the rider app and reconcile each rider's balance daily.
- Require a delivery code or confirmation before an order is marked delivered.
- Define what happens when a customer refuses: who pays the delivery fee and whether the vendor is compensated for perishable items.
- Keep a log of rider cash held, collected and handed over, so shortages are visible quickly.
Handling common cases: quick guidance
These are example approaches to adapt to your own policy, not fixed rules:
- "My order never arrived": check the rider's delivery confirmation and timeline. If delivery was not confirmed, refund the buyer and investigate with the rider and vendor. If it was confirmed with a code, ask the buyer for more details before deciding.
- "The item was damaged or spoiled": ask for a photo. If it is clearly the vendor's packing or quality, charge the vendor. If it shows signs of rough handling in transit, treat it as a delivery issue.
- "Items are missing": compare the order against what the vendor marked as prepared, and refund the missing items rather than the whole order where possible.
- "The vendor cancelled": refund immediately and track vendors who cancel often, since repeated cancellations harm buyers.
- "I changed my mind": apply your policy. Many marketplaces limit these refunds, especially for food and other perishable goods.
Set up a simple dispute workflow
A workflow with clear owners keeps cases from stalling. A lightweight version looks like this:
| Stage | Who acts | Example target (set your own) |
|---|---|---|
| Report received | Buyer submits a claim with details | Acknowledge on the same day |
| Vendor response | Vendor replies with their account | Within one business day |
| Review | Support or admin checks evidence | Decide within a few days |
| Resolution | Admin applies refund, replacement or rejection | Same day as the decision |
| Appeal (optional) | Senior reviewer rechecks | One appeal per case |
The targets above are examples. Pick numbers your team can meet consistently, because a missed promise is worse than a slightly longer promise you keep.
A neutral reply template
Whatever the outcome, communicate calmly and clearly. A short template you can adapt:
Hi [Name], thank you for reporting a problem with order [number]. We have reviewed the details and the information from [the other party]. Our decision is [outcome] because [short reason]. [Next step, for example: the refund will appear within X days]. If you believe we missed something, you can reply within [time] to request a review.
Tone matters. A buyer who feels heard often stays, even when the answer is no.
Preventing fraud
Fraud on marketplaces comes from both sides. Watch for these patterns:
- Fake or prank orders, especially with cash on delivery.
- Repeat no-shows or refusals by the same buyer.
- Refund abuse, where a buyer claims non-delivery or damage repeatedly.
- Vendor fraud, such as listing items they cannot supply or asking buyers to pay outside the platform.
- Fake reviews to boost a vendor's ranking.
Practical controls include verifying phone numbers, limiting the value of a new buyer's first cash-on-delivery order, flagging accounts with repeated refusals, requiring vendor approval, keeping all communication and payment on the platform, and reviewing unusual order patterns. Handle personal data carefully, and follow your local privacy rules when you store or share information about users.
Use your admin tools
You need one place to see orders, refund requests and rider activity. In VendMart the multi-vendor admin panel includes order management, refunds and dispatch, and the vendor panel lets vendors see and respond to their orders. You can explore both in the live demo. Whatever software you use, make sure disputes, refunds and payouts all connect to the same order record.
Protect vendors too
A marketplace that always sides with buyers loses its best sellers. Protect vendors by:
- Requiring evidence from buyers, not just a claim.
- Letting vendors respond before a decision.
- Offering a way to appeal an unfair outcome.
- Reversing penalties when a claim proves false.
Good vendor treatment also helps recruitment, as covered in how to attract vendors to your marketplace and how to onboard your first 50 vendors.
Learn from the patterns
Every dispute tells you something. Review them monthly and ask:
- Which vendors appear most often, and why?
- Which categories generate the most problems?
- Are many disputes about late delivery, pointing to a rider or zone issue?
- Do unclear product listings cause "not as described" claims?
Fixing the cause, such as better listing rules or rider coverage, costs less than resolving the same dispute again and again.
Mistakes to avoid
- Having no written policy, so every case is argued from scratch.
- Deciding without hearing the vendor.
- Slow responses, which turn a small problem into a public complaint.
- Not reversing the vendor's share in your ledger after a refund, which causes accounting errors.
- Ignoring cash-on-delivery reconciliation.
- Treating every buyer claim as true or every vendor as guilty.
- Never reviewing dispute data, so the same issues repeat.
Frequently asked questions
Who pays when a marketplace order is refunded?
It depends on the cause and your policy. Vendor errors are usually charged to the vendor, delivery losses to the marketplace or rider, and platform errors to the marketplace. State the rules to vendors before they join.
How long should buyers have to report a problem?
It depends on what you sell. Perishable goods need a short window, while other products can have longer ones. Set the period in your policy and apply it consistently.
How do I stop cash-on-delivery fraud?
Verify phone numbers, limit the value of a new buyer's first cash order, flag repeated refusals, record every cash collection in the rider app and reconcile rider balances daily.
Should the marketplace or the vendor handle disputes?
Start with a direct conversation between buyer and vendor, with the marketplace stepping in when they cannot agree or when delivery is involved. Keep the final decision with you so outcomes are consistent.
Next step
A fair, written process makes a marketplace safer for everyone. For the full picture of running one, read the complete guide to multi-vendor marketplace scripts and the launch checklist, then see how refunds and orders work in the live demo.
