Return Eligibility Rules: How to Approve, Deny, or Hold every Return Request
Approve a return request when the applicable rules are satisfied, deny it only when a clear and lawful exclusion applies, and hold it when specific missing information prevents a reliable decision. For ecommerce teams, the safest approach is to evaluate each item against the applicable consumer rights, the policy attached to the purchase, the return reason, and the supporting evidence. Approving a return should also be kept separate from approving a refund.
A useful eligibility framework gives support agents and automated workflows the same decision logic. It should explain what happens next, who owns unresolved cases, and how customers can challenge an incorrect decision. The framework below is an operational design, not a substitute for jurisdiction-specific legal advice.
Define what approve, deny, and hold actually mean
Many returns problems begin with ambiguous statuses. A customer sees “approved” and expects money back, while the warehouse understands it as permission to receive a parcel. Define the scope of each decision before writing eligibility rules.
| Decision | Operational meaning | Required next step |
|---|---|---|
| Approve | The request qualifies for the specified next action, such as a physical return or an exchange process. | Explain instructions, applicable costs, and any lawful inspection conditions. |
| Deny | A confirmed rule excludes the requested remedy, after checking relevant rights and exceptions. | Give a specific reason and a review route, plus any available alternative. |
| Hold | A material fact remains unresolved, so the request needs evidence or human review. | Name the missing fact, assign an owner, and communicate the next update. |
Return authorization, receipt, inspection, and refund are separate events. Record them separately, even if some orders move through several events at once. A no-return refund also needs its own workflow rather than a fictitious warehouse receipt.
Apply rules in the right order
Do not build a single checklist where every failed condition produces a denial. A final-sale restriction may be relevant to a change-of-mind request but inappropriate for a defective item. Use a decision hierarchy that resolves these conflicts.
- Identify applicable rights and obligations. Establish the relevant market, transaction type, and complaint category. Mandatory consumer protections can limit what a store policy may exclude.
- Retrieve the policy associated with the purchase. Keep the policy version and any order-specific promises available. Do not automatically apply a newer, more restrictive policy to an older purchase.
- Classify the return reason. Separate change of mind, fit, damage, defect, wrong item, missing contents, and other fulfillment issues.
- Check item-level conditions. Evaluate timing, product restrictions, quantity, condition requirements, and any previously completed remedy.
- Resolve missing or conflicting evidence. Hold only when the uncertainty can materially change the decision.
- Select the authorized remedy and next action. Confirm whether the outcome is a return, exchange, repair assessment, refund, or another permitted resolution.
Official UK guidance distinguishes faulty goods from unwanted purchases and explains that distance-selling transactions have additional cancellation rules. EU consumer guidance likewise distinguishes withdrawal rights from legal guarantees for faulty goods. These are jurisdiction-specific examples, not a worldwide return policy. The practical lesson is to keep statutory-rights checks separate from discretionary store benefits.
Turn policy language into testable conditions
Choose the correct clock
A return window is incomplete unless it specifies the event that starts it and the action that must happen before it ends. Order placement, dispatch, delivery, cancellation notice, return handoff, and warehouse receipt are different events.
Store these timestamps separately. For a delivery-based store policy, use the relevant item's delivery event rather than assuming every item arrived with the first parcel. Define how time zones, boundary dates, replacement deliveries, and corrected delivery records are handled. Any legally prescribed calculation takes precedence over an internal convenience rule.
If the delivery date is missing or disputed, do not silently substitute the purchase date and deny the request. Use a documented fallback or route the case for review.
Match the reason to the right condition test
Condition requirements should follow the request category. “Unused with tags” may be relevant to a discretionary fashion return. It should not automatically reject a complaint that a product failed during use.
- Change of mind: Check the applicable cancellation rights or store-policy conditions, including any lawful restrictions.
- Wrong item: Compare the ordered item with the received item. An incorrect SKU should trigger a fulfillment investigation, not an automatic rejection because it differs from the order.
- Damaged or defective item: Establish the reported problem and applicable remedy. Do not assume ordinary resale-condition rules settle the complaint.
- Incomplete order: Investigate packing and fulfillment records before asking the customer to return items they say never arrived.
Evaluate individual items, not just entire orders
One order can contain an eligible item, an excluded item, and an item awaiting review. Store the decision at line-item and quantity level. This avoids denying the entire order because one product has a restriction.
For bundles, gifts, promotional products, and partial returns, document how the refund will be calculated and whether associated items must be returned. Keep these calculation rules separate from the eligibility decision, and check that deductions or conditions are lawful and consistent with the purchase terms.
Request only evidence that changes the decision
Useful evidence can include an order reference, product identifier, description of the fault, relevant photographs, or a return handoff receipt. Specify why each item is needed. A photograph may help identify visible damage, but it cannot establish every intermittent or internal fault.
Missing packaging, unavailable photographs, or an account email mismatch should not become universal denial rules. Where appropriate, offer an alternative verification method and collect only the personal information needed to resolve the case.
Use a decision matrix for routine cases
The following examples illustrate workflow design. They are not universal policy terms, and every outcome remains subject to the applicable rights and purchase conditions.
| Request | Initial route | Reason |
|---|---|---|
| Change-of-mind request meets the relevant window and item conditions. | Approve | The applicable eligibility checks are satisfied. |
| Change-of-mind request is outside the applicable window, with no overriding right or approved exception. | Deny | A confirmed time restriction applies. |
| A final-sale item is reported as defective. | Assess the defect route | The final-sale label alone does not resolve a statutory-rights claim. |
| The delivery date is disputed and determines eligibility. | Hold | A material timing fact needs verification. |
| The same unit already has an active return authorization. | Link to the existing case | Prevent duplicate processing without discarding the customer's underlying request. |
| A customer reports receiving a different product. | Review fulfillment evidence | An item mismatch may support the complaint rather than invalidate it. |
Make holds temporary and accountable
A hold is useful only if someone can resolve it. Every hold should contain a reason code, the exact missing information, an assigned team, a next-review date, and a customer-facing explanation.
Separate customer action from internal action. “Please confirm which item is damaged” is different from “We are checking the warehouse packing record.” Customers should not be asked repeatedly for information already supplied, or made responsible for retrieving internal records.
An internal hold does not automatically pause a legal deadline. Configure reminders and escalation around applicable obligations. If the team has enough information to approve one item but not another, progress the eligible item rather than freezing the entire request.
Risk indicators should generally trigger proportionate review rather than act as proof of abuse. Repeated returns or a high order value may justify attention, but they do not by themselves establish that a particular request is invalid.
Explain decisions without creating new promises
Customer messages should state the decision, its scope, the reason, and the next step. Avoid unexplained “policy violation” notices or approval messages that promise an immediate refund when further lawful steps remain.
- Approval example: “Your return request for the jacket is approved. Follow the return instructions below. This authorizes the return; we will confirm the refund separately under the applicable policy and consumer rights.”
- Denial example: “We cannot approve this change-of-mind request because it was submitted after the return period applicable to your purchase. If the item is faulty, incorrect, or the delivery date shown is wrong, reply so we can review the request under the appropriate rules.”
- Hold example: “We need to confirm which item you received before deciding this request. Please send the product identifier from the item or packaging, if available. Your case is assigned to our support team, and we will provide the next update by the date shown below.”
Use these as writing patterns, not universal legal wording. Populate actual dates and conditions from verified records rather than adding promises the operation cannot meet.
Implement rules with an audit trail and test cases
Represent each rule with a scope, condition, outcome, priority, exception route, and explanation. Record which policy version and facts produced the decision. Keep the original request timestamp when a customer corrects information or support reopens the case.
Before enabling automatic denials, test boundary dates, split shipments, mixed-item orders, reported defects on restricted products, duplicate submissions, and missing delivery events. Also test what happens when two rules disagree. A general product exclusion should not silently override a higher-priority rights assessment.
If you are evaluating a returns platform, the official 17RETURNS product page is a relevant starting point. Verify the exact rule conditions, exception handling, audit records, and integration behavior you need through documentation or a demonstration. Do not assume a returns tool supports this entire framework simply because it provides a return-request workflow.
Start automation with clear, low-ambiguity cases. Route unresolved rights questions, conflicting records, and discretionary exceptions to trained reviewers. Track approval reversals, overturned denials, hold age, and the reasons agents override rules. These measures help identify unclear policies and broken inputs; they should not become targets for rejecting more returns.
FAQ
Does approving a return mean the refund is approved?
Not necessarily. Approval may authorize shipment back, while the refund follows a separate decision or processing step. Explain the distinction clearly, and do not use inspection or internal status labels to postpone a remedy beyond an applicable legal deadline.
Can a final-sale label justify every denial?
No. It may govern a discretionary change-of-mind return where permitted, but it does not automatically remove rights relating to faulty, misdescribed, or incorrect goods. Assess the complaint category and relevant jurisdiction before applying the restriction.
What if tracking says delivered but the customer disagrees?
Treat the delivery date as disputed if it affects eligibility. Review the available delivery evidence and the customer's account rather than treating one status as conclusive in every case. A non-receipt complaint may need a delivery investigation instead of a standard return workflow.
Should requests close automatically when customers do not respond?
An administrative closure may be appropriate under a documented process, but it should not imply that applicable consumer rights have expired. Send a clear reminder, retain the original request history, and provide a reopening route. Check legal obligations before configuring automatic closure.
Who should be allowed to override a return rule?
Assign authority by exception type. Support may handle defined goodwill exceptions, fulfillment teams can investigate shipment discrepancies, and compliance or legal specialists should resolve uncertain rights questions. Record the approver and reason so overrides can be reviewed consistently.
Sources
- GOV.UK: Accepting returns and giving refunds — UK guidance on faulty goods, distance-selling cancellations, and limits on return restrictions.
- Your Europe: Guarantees and returns — EU consumer guidance on withdrawal rights, exceptions, and remedies for faulty goods.
- 17RETURNS official product page — a product-evaluation starting point, not verification of every workflow requirement described in this guide.
