Why Cancellation and refund policy in LLD? - Purpose & Use Cases

The Big Idea

What if your refund process could run itself flawlessly, freeing you from endless manual work?

The Scenario

Imagine you run a small online store and handle cancellations and refunds by manually checking emails and updating spreadsheets.

Customers call or email asking about their refunds, and you have to dig through records to find their order status.

The Problem

This manual method is slow and stressful.

It's easy to make mistakes like missing a refund or giving wrong information.

As orders grow, keeping track becomes impossible and customers get frustrated.

The Solution

Designing a clear cancellation and refund policy system automates these tasks.

It tracks requests, applies rules, and updates statuses automatically.

This reduces errors, speeds up responses, and keeps customers happy.

Before vs After

✗ Before

Check email -> Find order in spreadsheet -> Update refund status manually

✓ After

User clicks cancel -> System checks policy rules -> Refund processed automatically -> User notified

What It Enables

It enables smooth, reliable handling of cancellations and refunds at any scale, improving trust and efficiency.

Real Life Example

Think of a popular ride-sharing app where users cancel rides and get refunds instantly without calling support.

Key Takeaways

Manual refund handling is slow and error-prone.

Automated cancellation and refund policies streamline the process.

This improves customer satisfaction and scales with business growth.

Practice

1. What is the primary purpose of a cancellation and refund policy in a system?

easy

A. To define rules for stopping services and returning money

B. To increase the price of products

C. To track user login times

D. To manage database backups

Solution

1. Step 1: Understand the role of cancellation policies

   Cancellation and refund policies set clear rules about when and how users can stop services and get money back.

2. Step 2: Eliminate unrelated options

   Options about pricing, login times, or backups do not relate to cancellation or refunds.

3. Final Answer:

   To define rules for stopping services and returning money -> Option A

4. Quick Check:

   Cancellation policy = service stop rules [OK]

Hint: Cancellation policies define service stop and refund rules [OK]

Common Mistakes:

• Confusing cancellation policy with pricing strategy
• Thinking it manages user authentication
• Assuming it handles technical backups

2. Which of the following is a correct component to include in a cancellation policy data model?

easy

A. login_attempts: int

B. user_password: string

C. product_price: float

D. allowed_cancellation_time: datetime

Solution

1. Step 1: Identify relevant data for cancellation policy

   The allowed cancellation time defines until when a user can cancel and get a refund.

2. Step 2: Exclude unrelated fields

   User password, product price, and login attempts are unrelated to cancellation timing.

3. Final Answer:

   allowed_cancellation_time: datetime -> Option D

4. Quick Check:

   Cancellation policy needs cancellation time [OK]

Hint: Cancellation policy needs allowed cancellation time field [OK]

Common Mistakes:

• Including unrelated user or product fields
• Confusing cancellation time with login data
• Using incorrect data types for time

3. Given this pseudocode for refund calculation:

if cancellation_time <= allowed_cancellation_time:
    refund_amount = full_price
else:
    refund_amount = 0
print(refund_amount)

What will be printed if cancellation_time is after allowed_cancellation_time?

medium

A. Error

B. full_price

C. 0

D. null

Solution

1. Step 1: Analyze the condition

   If cancellation_time is after allowed_cancellation_time, the else branch runs.

2. Step 2: Determine refund amount

   In else, refund_amount is set to 0, so 0 will be printed.

3. Final Answer:

   0 -> Option C

4. Quick Check:

   Late cancellation = zero refund [OK]

Hint: Late cancellations get zero refund [OK]

Common Mistakes:

• Assuming refund is full regardless of time
• Expecting an error due to condition
• Confusing variable names

4. Identify the bug in this refund policy code snippet:

def calculate_refund(cancellation_time, allowed_time, price):
    if cancellation_time > allowed_time:
        refund = price
    else:
        refund = 0
    return refund

medium

A. Price variable is not used

B. Refund is given after allowed time instead of before

C. Function does not return any value

D. Refund is always zero

Solution

1. Step 1: Understand refund logic

   Refund should be given if cancellation_time is before or equal to allowed_time.

2. Step 2: Check condition logic

   Current code gives refund if cancellation_time is after allowed_time, which is incorrect.

3. Final Answer:

   Refund is given after allowed time instead of before -> Option B

4. Quick Check:

   Refund condition reversed = bug [OK]

Hint: Refund condition must check cancellation before allowed time [OK]

Common Mistakes:

• Reversing the refund condition
• Ignoring return statement
• Misusing price variable

5. You are designing a cancellation and refund system for an online booking platform. Which approach best balances user trust and system scalability?

hard

A. Allow partial refund based on how close cancellation is to booking time

B. Allow full refund anytime, no restrictions

C. Allow full refund only if cancellation is made 24 hours before booking time, else no refund

D. Never allow refunds to avoid complexity

Solution

1. Step 1: Consider user trust

   Partial refunds based on cancellation timing show fairness and flexibility, building trust.

2. Step 2: Consider system scalability

   Partial refund rules can be implemented with clear logic and scale well without manual intervention.

3. Step 3: Evaluate other options

   Full refund anytime is costly; no refunds reduce trust; strict cutoff is less flexible.

4. Final Answer:

   Allow partial refund based on how close cancellation is to booking time -> Option A

5. Quick Check:

   Partial refund balances trust and scalability [OK]

Hint: Partial refunds balance fairness and system load best [OK]

Common Mistakes:

• Choosing no refund which harms user trust
• Allowing full refund anytime which is costly
• Using strict cutoff without flexibility