Local Pickup (QR Acceptance) Dispute & Arbitration Protocol
Effective Date: 01/23/26
Applies To: User-to-user transactions recorded on the Platform for in-person exchange (“Local Pickup”) using QR verification
Incorporation: This Protocol is incorporated into and governed by the UDRR.
1. Purpose
This Protocol defines a clear acceptance mechanism for in-person transactions using QR verification, while preserving limited exceptions for fraud, duress, and technical error. It is designed to be simpler than shipped goods disputes and primarily determined by scan records and the transaction terms.
2. Scope
Applies when the transaction record specifies:
- Local pickup / in-person exchange, and
- QR verification as the acceptance step.
3. Definitions
- QR Scan Event: A platform-logged event indicating that the buyer scanned a transaction-specific QR code and confirmed acceptance, including timestamp, transaction ID, and both parties’ account identifiers.
- Acceptance: Buyer confirmation that the item was received and inspected to the buyer’s satisfaction at pickup.
- Finality Presumption: After a valid QR Scan Event, the transaction is presumed complete.
- Exception Claim: A post-acceptance claim permitted under Section 8.
4. Core Principles
- Inspect before scan: buyer is expected to inspect/test in person before scanning.
- Scan = acceptance: the scan is a strong, objective marker of completion.
- Narrow exceptions only: to prevent abuse while preserving fairness.
5. Timelines
- Pre-scan disputes (no scan happened): claim window 14 days from scheduled pickup date (or from purchase if no date set).
- Post-scan exception claims:
- Technical error / wrong transaction / mistaken scan: must be filed within 72 hours of the scan.
- Duress/coercion: must be filed within 72 hours of the scan.
- Counterfeit/stolen goods: must be filed within 14 days of the scan (or longer if the transaction record explicitly allows, up to 30 days).
- Response/reply/extensions follow UDRR.
6. Evidence Rules (Local Pickup)
Primary evidence:
- QR Scan Event logs (including confirmation screens completed)
- Any co-presence check results (if enabled)
- Transaction record/listing terms and disclosures
- In-app messaging around pickup time
Secondary evidence:
- photos/videos taken at pickup (timestamped if possible)
- third-party verification (manufacturer authentication, serial validation)
- police report reference number (for stolen goods claims) where appropriate and lawful
- witness statements (limited weight unless corroborated)
7. Burden and Standard of Proof
The claimant bears the burden by preponderance of the evidence.
8. Dispute Types and Decision Rubric
A. No QR Scan Happened (Non-Completion)
Use when pickup failed or acceptance was never recorded.
- If seller cannot show a QR Scan Event and cannot show delivery by other agreed method: buyer may receive refund per transaction terms.
- If buyer no-show is proven (messages, scheduled time, repeated attempts): neutral may deny refund or allocate costs per disclosed no-show policy.
B. QR Scan Happened — Default Rule (Finality Presumption)
If a valid QR Scan Event exists, the buyer’s later “not as described” or “damage” claim is generally denied because inspection was available at pickup.
Proceed to exceptions only if buyer alleges an Exception Claim below.
C. Exception Claim: Technical Error / Wrong Transaction / Mistaken Scan
Buyer must show:
- scan was associated with the wrong transaction ID, or
- scan was recorded without completing the acceptance confirmation screen, or
- clear log inconsistency.
If proven within 72 hours:
- neutral may void the scan’s finality, reopen merits, and order appropriate remedy.
D. Exception Claim: Duress / Coercion
Buyer must show credible evidence of coercion (prompt report, consistent narrative, contemporaneous messages, safety report, pattern indicators).
If proven within 72 hours:
- neutral may void finality and order remedy appropriate to circumstances, including refund without return if return is unsafe or impractical.
E. Exception Claim: Counterfeit / Stolen Goods
Because counterfeit/stolen status may not be discoverable at pickup, this exception is broader but still evidence-based.
Buyer must provide objective verification, such as:
- manufacturer authentication/denial,
- serial/IMEI check results,
- qualified third-party appraisal,
- law enforcement report reference (when appropriate).
If proven:
- buyer prevails (refund), and neutral may order return procedures consistent with safety and law (e.g., surrender to authorities, or return to seller if lawful and safe).
F. Exception Claim: Latent Defect Not Reasonably Discoverable at Pickup
This should be narrow. Buyer must show:
- defect existed at pickup,
- defect could not reasonably be discovered through ordinary inspection/testing at pickup, and
- the defect is material.
If proven:
- neutral may award partial refund, repair cost contribution, or return-for-refund depending on item type and disclosed terms.
9. Remedies (Local Pickup)
- Refund (full/partial)
- Return-for-refund with safe return procedure and deadlines
- No refund (seller prevails)
- Fee allocation per UDRR/fee schedule
Return logistics: If return is ordered, define:
- safe meeting method, or
- tracked shipping return (if parties agree), or
- third-party drop-off (optional).
10. QR Acceptance UX Requirements (Operational Requirements)
To strengthen enforceability and reduce disputes, the Platform should implement:
- Two-step acceptance:
- scan QR, then
- tap “I inspected and accept this item” (with a short checklist: test power-on, verify serial, verify condition).
- Conspicuous finality disclosure: “Scanning confirms receipt and acceptance; disputes are limited after scan.”
- Transaction-specific QR: single-use token bound to transaction ID.
- Anti-replay controls: token expires after scan; audit logs immutable.
11. Non-Compliance
Non-compliance with an award may trigger platform enforcement actions consistent with UDRR.
12. Appeals
Appeals follow UDRR. For Local Pickup, new evidence must be objective (logs, authentication results) or explain why it was unavailable within the short exception windows.