Returns and Refunds Management
A returns process customers can start themselves, with reason codes, pickup, quality check on arrival and a refund or credit note that reconciles against the original order. Built and run by GullySystem.
Why Returns Turn Into Accounts-Team Guesswork
A customer messages to say an item does not fit or arrived damaged, and without a structured process someone has to decide by feel whether to accept it, arrange pickup by phoning the courier separately, and then remember to actually issue the refund. The item can sit unresolved for weeks, and the refund promised on a call never gets logged anywhere your accounts team can see.
What a Structured Returns Process Includes
Customer-Raised Return Requests
The customer starts a return from their own order page, choosing a reason from a list rather than a free-text message.
Approval Rules by Reason and Value
Some reasons and values can approve automatically, while higher-value or unusual returns are held for a person to review.
Reverse Pickup Scheduling
A pickup is requested from the courier automatically once a return is approved, instead of a separate phone call.
Quality Check on Arrival
The returned item is checked against its stated reason before a refund is released, with the outcome recorded against the return.
Refund or Credit Note, Reconciled
The refund or credit note is generated against the original order and payment method, so accounts can match it without cross-checking manually.
An Example: Size and Fit Returns on an Apparel Store
An apparel brand's biggest source of returns is size and fit, and today a customer emails a photo and waits for someone to reply before a pickup is even arranged. A structured process lets the customer select 'wrong size' as the reason and immediately book a pickup within the return window, routes the item through a quality check on arrival, and issues a refund or a credit note for a store exchange automatically once the check passes, with every step visible to the customer on their own order page.
What Shapes the Cost and Timeline of a Returns Process
- How many return reasons need their own approval rule
- Whether refunds go back to the original payment method, a credit note, or both
- How quality check on returned items fits your current warehouse process
- Whether reverse pickup uses the same courier accounts as forward delivery
- How your accounting software should record refunds and credit notes
Frequently asked questions
Do we need a structured returns process if return volume is low?
Even low volume benefits once returns cost you staff time to track by phone or email. What decides it is less the number of returns and more whether refunds are currently getting lost or delayed because nobody owns the process end to end.
What makes returns handling cost more to build for one business than another?
The number of different approval and refund rules, for example different treatment for a damaged item versus a wrong size versus a change of mind, adds more logic than the pickup or refund steps themselves.
What usually takes the longest to agree?
Your approval rules, which reasons can auto-approve and which need a person to review, because that decision has to be settled before the workflow can be built around it.
Can refunds be recorded automatically in the accounting software we use?
Yes, where your accounting software supports it, refunds and credit notes can be exported or synced rather than entered twice.
Who owns the return and refund records?
You do. The return history stays in a system you control and can be reported on or exported.
What policy decisions do we need to make before this is built?
Your list of acceptable return reasons and window, your refund-versus-credit-note policy, and who approves returns above a certain value.
Tell us what you need.
Send a short brief and one of our engineers will come back to you — usually the same day.
- No obligation
- We reply the same working day
- Your details stay private