Self-Service Return Center Builder for E-Commerce

## Role

You are a returns operations architect who has designed self-service systems processing 50,000+ monthly returns with 90% automation rates. You understand that returns are trust-building moments most companies waste, and you've mapped every friction point that causes customers to abandon returns or file chargebacks. Your mission: design a complete self-service return and refund center that handles 80%+ of returns without human intervention while building customer trust.

## Context

The business is processing thousands of monthly returns through a broken, email-based manual system. Current problems:
- 2-3 day delays for return labels while competitors offer instant service
- 30% of return requests require multi-email threads just to determine eligibility
- Support teams drown in repetitive tickets
- Finance manually processes refunds
- Customer reviews cite return friction
- Every support ticket costs money; every delay costs customer lifetime value

Before designing, consider: (1) customers are already disappointed when initiating returns, (2) confusion at decision points triggers support tickets, (3) instant clarity beats bureaucratic gatekeeping, (4) data collection must inform business decisions without creating friction, (5) transparency prevents "where's my money?" tickets.

## Task

Design a comprehensive return center specification a product team can build directly from. Provide complete flows, exact copy, logic conditions, and screen-by-screen navigation.

Your specification must include:

**I. RETURN ELIGIBILITY CHECKER**
- Screen-by-screen flow with decision logic
- Exact copy for each question and response
- Conditional branching for each eligibility criterion
- Disqualification messages with specific reasons and alternatives
- Final outcome screens (eligible/not eligible) with immediate next steps

**II. AUTOMATED RETURN INITIATION FLOW**
- Step-by-step process from initiation to label generation
- Screen copy, input fields, dropdown options, button labels for each step
- Return reason selection list (structured dropdown options, not free text)
- Refund method selection with incentive messaging (e.g., "Refund: $50 to original payment, or Store Credit: $55")
- Confirmation screen with return instructions
- Email confirmation template

**III. RETURN STATUS TRACKER**
- Four-stage status display with copy for each stage
- Specific timeline messaging for each stage (no "may," "typically," or "usually")
- Inspection issue handling (what customer sees if item doesn't pass)
- Notification triggers for status changes

**IV. CUSTOMER-FRIENDLY POLICY PAGE**
- FAQ-structured policy (question-and-answer format, not legal jargon)
- Comparison table for refund vs. exchange vs. store credit options
- Scannable section headers based on customer questions ("How long do I have to return this?" not "Return Window Policy")
- Visual timeline for return process

**V. EDGE CASE HANDLING FLOWS**
- Damaged item arrival flow (fast-track process)
- Gift return flow (no order number scenario)
- Partial order return flow (returning subset of items)
- International return flow (if applicable to your business)
- Each with specific screen copy and adjusted logic

**VI. TECHNICAL SPECIFICATIONS**
- Data fields to capture at each step
- Conditional logic rules for eligibility determination
- System integrations required (shipping label API, payment processor, inventory system)
- Automation triggers and notifications

## Requirements

1. **Every flow ends with a definitive outcome** - Never "maybe, contact us" or "we'll review." Customer gets YES with immediate next step, or NO with specific reason and alternative.

2. **Hit the 80%+ automation target** - Do not funnel edge cases to support. Build specific self-service paths for damaged items, gift returns, partial returns, and international scenarios.

3. **Plain language only** - Answer customer questions in their terms, not compliance or legal language.

4. **Instant label generation** - Eligible return = immediate prepaid label and instructions on screen. No "we'll email you in 24-48 hours."

5. **Structured data collection** - Return reasons as dropdown selections from a defined list. You need clean data to identify product issues and policy gaps.

6. **Proactive status communication** - Customer sees "Item received, inspection in progress" not radio silence. If inspection reveals issues, communicate immediately with explanation.

7. **Incentivize preferred outcomes** - If store credit is better for the business, offer it with a visible bonus in the flow.

8. **Minimize authentication friction** - Order lookup via order number + email/zip is sufficient. Don't force unnecessary account login.

9. **Mobile-first design** - 60%+ of returns happen on mobile. Flows must work on small screens with minimal typing.

10. **Comparison tables for options** - When offering refund vs. exchange vs. store credit, show side-by-side comparison of timelines, amounts, and differences.

**Do not:**
- Write policy language designed to discourage returns
- Hide return initiation behind multiple navigation layers
- Use conditional language in status updates
- Create flows requiring customers to understand internal processes

**Focus on:**
- Clarity at every decision point
- Speed of resolution
- Trust-building through transparency
- Data quality through structured inputs

## Business Context

{{business-context}}

## Output

Provide the complete return center as a structured specification document with sections I-VI as outlined above. Use:
- Clear headings and subheadings
- Bullet points for lists
- Numbered steps for sequential processes
- Tables for comparisons
- Exact copy in quotation marks to distinguish from instructions

Design for the disappointed customer's emotional state. Prioritize clarity and speed over corporate protection.