What data is necessary to preserve in order for a dispute to be investigated?

Depends on the type of dispute, but most often requires changes to the order and its payment, proof of delivery, communication between the customer and seller, return events and the rules of the marketplace in force at the time. It is important to preserve not only the current state, but also the chronology.

What dispute resolution procedures need to be agreed upon before the system is implemented?

It must be clear who is dealing with the different referrals, what evidence is needed and when the specialist responsible is involved. The system collects information and follows deadlines. Only actions based on clear approved rules are automated, and conflicting cases are forwarded for review.

How does the buyer get a clear answer about the marketplace dispute?

The dispute-handling employee finds a history of ordering, delivery and communication. The buyer and seller are given a specific need for documents and further progress. The decision is made according to the platform's responsibility and the terms of the particular transaction.

How must a dispute resolution reach the seller's payment?

The dispute process transmits an approved decision linked to the transaction and amount. The settlement system applies a refund or a change in detention and returns the result of the enforcement. Completion of the dispute proceeding must not be considered proof that the money has already been transferred.

Marketplace transaction dispute management system

The dispute-handling employee sees the order, payment, delivery and correspondence in one place. The decision can be based on the circumstances and rules of a particular transaction.

Customer, seller, logistics and payment information is collected from multiple channels, and the rules of resolution apply unevenly.

How the solution works

The buyer's or seller's appeal is tied to the transaction and the disputed part of the order.
The collected proofs of delivery, communication and condition of the item are provided to the assessor.
The responsible employee makes an informed decision in accordance with the applicable dispute procedure.
The decision is forwarded to the settlement and both parties are informed of the outcome and possible follow-up.

Key challenges

Dispute documents and transaction history are stored separately

Solution capabilities

Linking the dispute to the transaction

The employee sees the disputed part of the order, the party to the transaction and previous referrals. He can continue the examination without re-collecting this information.

Collection of Dispute Papers and Explanations

Buyer, seller and delivery details are saved with origin and delivery time; missing proof can be requested.

Deadlines for reply and transmission

In the event of a failure to respond to a party or approaching the deadline for a decision, the case is referred to the assessor in charge according to the dispute procedure.

Decision and financial execution

The basis of the decision remains traceable, and enforcement of the repayment or payment change comes from the settlement system.

Business context

Dispute documents and transaction history are stored separately: Customer, seller, logistics and payment information is collected from multiple channels, and the rules of resolution apply unevenly.
Dispute resolution restores clarity to both sides of the deal: The buyer and seller can view the circumstances of a delivery or a good differently. Documents collected in one place allow to examine a specific transaction and clarify the decision. Visible terms and financial execution help to complete the issue on which further trust in the platform depends.

Core features

Linking the dispute to the transaction
Collection of Dispute Papers and Explanations
Deadlines for reply and transmission
Decision and financial execution

Key integrations

Marketplace Ordering System: Order and line history, changes, and state of execution.
Payment system: Events in a payment, refund or payment dispute.
Courier/Delivery systems: Acceptance of the shipment, proof of delivery and actual deadline.
Customer and Seller Communication Channels: Communication and evidence provided in relation to a particular transaction.
Source of rules and politicians: The version of the marketplace rule in effect at the time of the dispute.

Potential impact (%)

The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.

Time of the employee to gather evidence of the dispute

16–42%Decreasing

This illustrative scenario assumes that 40-70% of information searches and repeated cross-checks can be addressed. That share is assumed to fall by 40-60%. Company data is needed to verify both the addressable workload and the resulting change.

The type of dispute selected compares the active time of the employee allocated to gather evidence before and after the implementation of the decision.

Time between registration of the dispute and settlement

6–25%Decreasing

This illustrative scenario assumes that 20-50% of waiting caused by missing information or unclear responsibility can be addressed. That share is assumed to fall by 30-50%. Company data is needed to verify both the addressable share and the resulting change.

The time to solution is measured by marking the wait separately for the customer, seller or external partner.

Part of negative reviews of the marketplace dispute

4–15%Decreasing

Indicative assumption: 15-30% of negative reviews relate to an unexplained course of the marketplace dispute. The solution could reduce this proportion by 25-50%. This is a scenario of potential; the assumptions need to be verified by feedback collected by the company.

When a company starts collecting reviews, negative reviews about the marketplace dispute are counted from all assessments received on the topic. The same method of evaluation is used before and after installation and similar customer groups are compared. Without initial data, the actual change is not determined.

Conditional calculation scenarios. The assumptions have not been validated against client measurements.

When this solution is relevant

Customer, vendor, logistics and payment information is collected from multiple channels and decision rules apply unevenly
Longer settlement of the dispute, higher compensation costs and lower confidence on both sides
Dispute documents and transaction history are stored separately
The operations team does not have one exception job

Implementation requirements

The team agrees on what order, delivery and correspondence data is needed to deal with the dispute. Responsible staff, response deadlines, and a way to verify that a confirmed refund or other correction of money has already been made.