How to Organize Returns and Refunds in an Online Store

The short answer: what a working returns process looks like

Returns are unavoidable, and chaos around them costs more than the returns themselves: money gets stuck, items get lost, customers contact support five times. A working system has four parts:

1. Return policy — clear rules published on the site.
2. Operational flow — the same path for every request, with statuses and owners.
3. Refund — through the same payment channel the customer used.
4. Accounting — returned items go back to stock or are written off, and the return is recorded in the books.

Return policy

Keep the policy short and unambiguous. It must answer:

• Time window: how many days after delivery the customer has.
• Conditions: intact packaging, original condition, tags, a receipt or order number.
• Exclusions: items that cannot be returned (for example, for hygiene reasons or made to order).
• Who pays return shipping in each case: defect, store error, "didn't fit".
• Refund method and timing.

The rules must comply with consumer protection law in your country — have a lawyer review them, especially timelines and procedures for defective goods. Link the policy in the footer, on product pages and in the order confirmation email.

From request to warehouse

Every request moves through fixed statuses:

Practical tips:

• Offer a return form in the customer account instead of free-form emails — you immediately get the order number, reason and photos.
• Let customers choose the return reason from a list (defect, wrong size, not as described, changed mind). This data later shows which product pages and suppliers need fixing.
• Send notifications at every status — this removes most support requests.
• Take photos at inspection: they protect you in disputes.

Refunds through the payment gateway

The main rule: refund to the original payment method.

• Online card payment — use the refund function in your payment provider's dashboard or API. The refund is tied to the original transaction, so you never need the customer's card details.
• Partial refund — most gateways let you refund part of the amount when one item from an order is returned. Check your provider's documentation.
• Cancel before capture — if the payment was only authorized (a hold) and not captured, it is usually voided rather than refunded, which releases the money faster.
• Cash on delivery — refund in cash or by bank transfer based on the customer's request, with a document on file.
• Bonus points and promo codes — decide in advance whether points go back to the account and how a discount is split on partial returns.

Keep in mind that once a refund is issued, when the money actually appears on the card depends on the customer's bank. Tell the customer the refund has been sent and explain what affects the timing.

If returns are frequent, automate them: when an order in your CRM or admin panel gets the "Return approved" status, the system calls the gateway API and stores the refund transaction ID on the order.

Accounting: stock and books

• Items in good condition return to available stock only after inspection, not when the request is created.
• Defective items go to a separate warehouse or a "quarantine / write-off" status and never back on sale.
• Exchanges are recorded as a return plus a new order, so stock and revenue stay correct.
• In accounting, a return is a separate document linked to the original sale, not a deleted order.
• If you use an accounting service or 1C, returns must sync there the same way sales do.

Common mistakes

• A policy of "manager's discretion" with no written rules.
• Refunding to a different card or in cash for an online payment without a good reason.
• Putting items back on sale before inspection.
• Deleting orders instead of recording returns — this breaks analytics and accounting.
• Not collecting or analyzing return reasons.