E-commerce
July 1, 2026
After returning a product, the customer wants to know the status of their return: parcel dropped off, carrier scan, warehouse reception, inspection, refund, or hold. If the status is vague, they will follow up.
Good return tracking explains each step and what triggers the refund.
This guide shows how to reduce customer inquiries about return statuses.
Summary
Why do return statuses trigger reminders?
Customers often think a return is completed as soon as the package is dropped off. In reality, the refund may depend on scanning, receipt, inspection, or validation.
The response must explain the difference between a dropped-off return and a processed return.
A step-by-step visible return reduces anxiety about the refund.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
Which statuses need to be clarified?
Clarify return created, label generated, parcel dropped off, first scan, in transit, received, under inspection, validated, refund issued, bank refund, and block.
Each status must indicate the next step.
How do you handle a follow-up that isn't moving?
If the customer has dropped off the parcel but the tracking is not updating, ask for proof of deposit and check the standard scan time. If the time limit has passed, open a carrier inquiry.
The customer needs to know when the wait time becomes abnormal.
How to explain the refund?
Explain whether the refund starts at drop-off, at scan, upon receipt, after inspection, or after validation. Also indicate the bank processing time after issuance.
The customer must distinguish between the refund issued and the money being visible.
When a quality control check is required, explain what is verified: product received, condition, accessories, serial number, or compliance with the declared reason. The customer will then understand why the refund is not instantaneous.
How do we reduce tickets?
Display a readable return tracking in the customer account, with steps, dates, and next actions. Send a notification if the return is received, blocked, or refunded.
Support needs to identify the steps that generate the most follow-ups.
Visibility reduces support volume.
Support can also display a next verification date when the status does not change. The customer then knows when a delay becomes an anomaly and when support will intervene.
This date reduces repeated follow-ups.
Which flow to follow?
The flow must explain the return step.
Identify the order, return, carrier, label, drop-off, proof, status, and request.
Check scan, transit, reception, inspection, validation, refund, and banking delay.
Explain the current status, the next step, and the refund trigger.
Open an inquiry, request proof, refund, transfer, reassure, or report a blockage.
Measure return reminders, missing scans, inspections, refunds, and satisfaction.
Which examples should be used?
“Your return has been dropped off, but the carrier's first scan does not appear yet.” “The refund has been issued; it may take a few days to appear in your account.”
The response must specify the step.
When to transfer?
Transfer is necessary for inconsistent proof, high-value return, lost package, blocked inspection, disputed refund, exceeded deadline, dispute or highly anxious customer.
The bot must transmit order, return, proof, carrier, status, deadline and risk.
Which KPIs should be monitored?
Follow up on outstanding returns, blocked statuses, missing scans, inspection delays, refunds, carrier investigations, and satisfaction.
This data shows where the return process lacks clarity.
Which mistakes should be avoided?
Avoid saying "wait" without a timeframe, promising a refund before the expected trigger, ignoring proof of deposit, or hiding an ongoing check.
The return must be trackable.
How can Qstomy help?
Qstomy can connect the chatbot to catalogs, countries, restrictions, retail events, orders, returns, stores, carriers, refunds, fees, and escalation procedures to answer accurately.
The chatbot helps the customer understand a restriction, an event, an in-store return, fees, or a return status without inventing an authorization, a refund, availability, or an exception that needs to be verified.
Explore AI support, AI sales agent, or request a demo.
Key takeaways
Key Takeaways
Return statuses must clarify drop-off, scan, transit, receipt, inspection, validation, refund, and bank processing time.
What the customer must understand
The customer must know where their return stands and what triggers the next step.
The right limit for the chatbot
The chatbot can track and explain, but it must hand over inconsistent proof, lost packages, and disputed refunds.
Enzo
July 1, 2026
