Handling returns and disputes on Tutus: a practical guide

A package arrives at an apartment in Lyon. Inside is a vintage 1990s raw denim jacket listed on Tutus as "Size M, pristine condition." The buyer puts it on; the sleeves sit two inches above the wrists, and a tape measure reveals the chest width has shrunk by four centimeters due to improper washing by a previous owner.

In standard peer-to-peer fashion marketplaces, this triggers an exhausting script: the buyer messages the seller, the seller accuses the buyer of altering the garment, and both parties submit ticket requests to customer support reps who rely on generic policy macros. On Tutus, the transaction follows a deterministic, code-driven resolution path designed to minimize friction while enforcing seller accountability.

The Mechanics of the Escrow Clock

When a purchase occurs on Tutus, funds do not transfer immediately to the seller's account. Instead, the payment enters the Tutus Universe Escrow Ledger, a dedicated smart-contract account locked against early withdrawal.

The clock starts upon verified carrier delivery. The platform ingests delivery webhooks directly from logistics partners (such as Mondial Relay, La Poste, or DHL). Once status changes to "Delivered," a strict 48-hour inspection window opens.

During this 48-hour window, three actions are possible:

1. Explicit Acceptance: The buyer confirms the item in the application. Escrow releases instantly to the seller's Wevar balance or fiat bank account.
2. Passive Acceptance: The 48-hour timer expires without buyer interaction. System logic automatically releases the escrow funds to the seller. Claims submitted after hour 48 are rejected by policy, preventing indefinite liability for sellers.
3. Dispute Initiation: The buyer halts the escrow clock by opening a structured dispute protocol before the 48th hour.

By tethering fund release directly to real-time shipping events rather than arbitrary calendar days, the platform removes administrative ambiguity.

The Evidence Ledger: Standardizing the Claim

Disputes on Tutus are structured to eliminate emotional narrative. A buyer cannot simply state "this doesn't fit right" or "I don't like the color in person." The platform categorizes claims into explicit policy triggers: Not as Described (material defects, unlisted wear), Dimension Mismatch, Authenticity Doubt, or Item Undelivered.

When opening a dispute, the buyer must submit standardized media evidence within 24 hours of filing:

• For Dimension Mismatches: A photograph showing a physical measuring tape laid across the garment alongside the seller's original listing measurements.
• For Unlisted Defects: High-resolution, multi-angle photographs under natural lighting, accompanied by a side-by-side comparison with the original listing images.
• For Fabric and Tag Misrepresentations: Close-up macro photos of the care label and composition tag.

Mia, WEVONE's underlying platform intelligence, parses the submission against the original listing metadata stored in the universe ledger. In its current implementation (live in early production), Mia performs OCR on garment tag uploads and cross-checks written descriptions against buyer-submitted images. A automated computer-vision tool for detecting fabric wear against original photos remains in beta testing.

A Worked Case: The Composition Discrepancy

Consider a concrete transaction from last month involving a trench coat sold for €180. The seller listed the item as "100% Cashmere Coat."

Upon delivery, the buyer opened a dispute at hour 14, submitting a photograph of the internal composition label reading "70% Wool, 30% Polyamide."

Here is how the system handled the claim:

1. Escrow Lock: The €180 balance remained frozen in the Tutus Escrow Ledger.
2. Automated Verification: Mia parsed the text from the buyer's upload ("70% Wool") and matched it against the listing's structural database entry ("100% Cashmere"). The system identified a 100% factual discrepancy.
3. Resolution Path Generation: Rather than defaulting immediately to a costly physical return, the system generated a two-option resolution path based on defect severity algorithms:
   • Option A (Partial Refund): The buyer keeps the coat and receives an immediate 35% (€63) refund from the escrowed balance. The seller receives the remaining €117. This option eliminates return shipping costs and re-listing labor.
   • Option B (Full Return): The buyer rejects Option A. The system automatically issues a prepaid, trackable return shipping label funded by a deduction from the seller's pending balance. Upon carrier scan confirming return shipment, the remaining escrowed funds revert fully to the buyer.

In this instance, the buyer selected Option A. The escrow settled in under three minutes from the time evidence was uploaded, requiring zero human intervention from platform administrators.

Cross-Universe Reputation and Friction Points

Disputes are not isolated events on Tutus; they feed directly into WEVONE's universal trust infrastructure. Every dispute resolution updates a user's cross-universe Contribution Score.

A seller who consistently misrepresents item measurements or fabric composition incurs deductions to their Contribution Score. If their score drops below platform thresholds, their listings lose priority ranking across Tutus, and their privilege to offer instant-payout options is suspended. Conversely, buyers who file persistent, rejected claims (e.g., claiming non-receipt when carrier GPS confirms delivery) face temporary holds on their ability to initiate disputes without manual review.

Because this Contribution Score spans all WEVONE universes—including Nest (short-term rentals) and Mission (local services)—a history of bad-faith listings on Tutus negatively impacts a user's standing when applying to host a property or offer local technical labor. This cross-domain risk creates a strong structural incentive for honesty.

Honest Limitations and Edge Cases

While code-driven dispute resolution excels at objective, measurable discrepancies (wrong measurements, incorrect fabric tags, missing items), it encounters clear limitations with subjective qualities:

• Odor and Storage Smells: Cigarette smoke, mold, or heavy perfume cannot be verified via image parsing. These cases currently require manual escalation to a human community curator, creating a 24-to-48-hour operational bottleneck.
• Counterfeit Verification: While minor brand tags are easy to parse, high-tier luxury authentication remains an active challenge. For items priced over €500, Tutus relies on third-party physical verification hubs, adding transit time and platform overhead.
• Carrier Transit Damage: When a box arrives crushed and the contents torn, liability between carrier negligence and inadequate seller packaging can be ambiguous. Until carrier APIs provide automated damage-assessment data, these claims require manual evidence review.

WEVONE does not claim to have solved human dishonesty. However, by replacing vague support channels with cryptographic escrow holds, structured evidence submission, and cross-universe reputation penalties, Tutus turns what is traditionally a marketplace's largest operational cost into a deterministic, self-enforcing protocol.