Three boxes of returns are waiting at the warehouse door, and no one knows which order they belong to. Meanwhile, the customer has sent their second message asking, "When will my money be refunded?"
Returns are inevitable in e-commerce; chaos stems from undefined processes. Without a standard workflow, both inventory and customer trust suffer.
In this article, we cover end-to-end management from return acceptance to inventory entry, return invoicing, and refunds. We also discuss how to reduce return rates.
Table of Contents
Receiving the return request
If return requests come in scattered across WhatsApp, email, and marketplace panels, tracking is lost. A single request ticket must be opened, and all correspondence linked to it.
At the time of the request, the order number, product, and return reason must be mandatory fields. Missing information delays opening the box in the warehouse.
Marketplace returns should be pulled automatically, and returns from your own site should enter the system via a form. Keeping manual lists does not scale.
The request status must be visible to the customer; steps like "received", "in transit", and "inspected" reduce uncertainty. Uncertainty increases support load.
We covered the support connection in the e-commerce customer service and CRM article.
Acceptance and rejection rules
The conditions under which a return will be accepted must be in writing and known to everyone. A "let's accept it for now" approach left to the representative creates inconsistency.
The rejection rule for products with hygiene seals or signs of use must be clearly defined. Gray areas create both stock issues and disputes.
Time limits must also be regulated, taking legal and platform terms into account. Every exception must be approved and logged.
Partial return scenarios are common in multi-product orders. The specific line item being returned must be clearly stated in the document.
Check the marketplace rules together with Hepsiburada integration and other channel articles.
Return shipping organization
Generating a return code for the customer speeds up the process and reduces shipments to the wrong address. Parcels arriving without a code remain unclaimed in the warehouse.
Who bears the shipping cost must be established as a policy. Product defects and customer change of mind should not be subject to the same rule.
The tracking number must be linked to the return record. The "In Transit" status becomes visible to both the customer and the warehouse.
The incoming return receiving screen should be managed as a separate work order from outbound shipping. Mixed count errors originate here.
We covered the incoming shipment side in the incoming shipment and return management article.
Product inspection and classification
When the box is opened, the product must be classified as resellable, requiring repair, or scrap. Putting it back into stock without classification passes problems on to the next customer.
The inspection form should be short and mandatory; adding photos provides evidence in disputed cases. This is especially mandatory for high-value products.
The correct SKU must be verified by scanning the barcode. Issuing a return for the wrong product generates stock discrepancies.
Inspection time should be limited by an SLA; a return sitting on the shelf for three days ties up cash. Speed is part of customer satisfaction.
We summarized the barcode layout in the barcode management article.
Return to stock
Resellable products should immediately be made available for sale in stock. Delayed entry causes items to appear "out of stock" on the channel.
Damaged products must be recorded in a separate location; the main shelf must not be mixed. Otherwise, the wrong product is resold.
Channel sync must be triggered the exact moment stock is replenished. Being in stock at the warehouse but out of stock on the site causes lost sales.
If your current ERP system maintains financial stock records, platform movements must be reflected there as well. Dual-record ownership must be clear.
Compliance was covered in the warehouse and marketplace stock compliance article.
Return document and invoice
A return invoice or return dispatch note is mandatory to prevent distortion of financial records. Stock entry without documentation causes issues in subsequent audits.
The document must be linked to the original sales document. If the link is broken, the return-reconciliation dispute drags on.
In e-invoice scenarios, the return document type must be selected correctly. The wrong scenario generates errors on both the integrator and taxpayer sides.
For partial returns, line amounts must be stated clearly. Rounding differences may seem minor but create major disputes.
The document chain was examined in the document chain from sale to invoice article.
Refund and reconciliation
Refunds must be triggered after product inspection is approved. Early refunds increase the risk of empty boxes or wrong products.
Return deductions in marketplace payouts must be monitored through panel reconciliation. Even if operations say "we refunded," the payment file might differ.
On your own site, card refunds or EFT processes must be managed with an SLA. If promised timeframes to customers are not met, complaints increase.
Cash and bank movements must be recorded in the correct account within the current system. While platforms accelerate operations, financial record discipline must be maintained.
The collection side was addressed in the collection and payment receipt article.
Return reason analysis
Return reasons cannot be reduced without being coded. "Didn't like it" on its own does not isolate product, size, or content issues.
Weekly reason reports should be reviewed on a category and SKU basis. Recurring reasons represent improvement opportunities.
Wrong-size returns decrease with size charts and visual improvements. This provides a profit increase cheaper than advertising.
Damaged delivery returns point to packaging standards. If caused by the carrier, a documented dispute process is initiated.
Read the profitability impact marketplace profitability analysis article alongside.
Customer communication
Silence during the return process is the main source of dissatisfaction. A brief notification at each status change is sufficient.
The reason for rejected returns must be clear and documented. Vague answers that prolong the discussion harm the brand.
Time promises must be realistic; saying "it will be refunded today" and waiting three days breaks trust. SLA-based template messages ensure consistency.
Post-return satisfaction measurement indicates the quality of the process. The repurchase rate can also be read from here.
We explained the measurement in the measuring satisfaction with CSAT article.
Return line on the platform
EQLEM is a solution platform; it does not replace your existing ERP system. It connects the return operation to the order, stock, and document pipeline.
When requests, shipping, inspection, and return to stock proceed on a single record, chaos decreases. The support team does not have to navigate three screens.
Financial documents can be transferred to the existing system; the accounting order is preserved. Operations accelerate, and record ownership remains clear.
When channel returns are pulled via integration, the need for manual lists ends. The error rate also becomes visible.
You can review the order pipeline in the e-commerce order invoice flow article.
Frequently asked questions
Should we automatically accept every return?
No; there should be written acceptance-rejection rules, and exceptions must be tied to an approved record.
When should the refund be made?
After product inspection is approved; early refunds increase the risk of empty or damaged products.
Is returned stock immediately made available for sale?
Only products classified as sellable are made available; damaged ones are kept in a separate location.
Will our current accounting system be affected?
EQLEM works alongside it; return documents can be transferred to your existing ERP system.Double data entry see the article.
Returns are inevitable, but a chaotic process is not. A single request record and clear rules cut out most of the chaos.
Do not restock without inspection and classification; otherwise, you pass the problem on to the next customer.
Link document and money refunds to the original order; this is how reconciliation disputes are shortened.
Code return reasons and review them weekly; a return that cannot be reduced only generates cost.
Give status updates to the customer; silence is the root cause of most complaints.
By consulting with the EQLEM team you can clarify your return process setup.