Automating E-Commerce Returns: Application, Reverse Logistics, Refunds, and Invoices

Returns are the process nobody in e-commerce wants to own: marketing won't discuss it (bad luck), engineering schedules it last (volume's low anyway), and customer service silently absorbs it (the volume is not low at all). So most brands run returns as a human relay race: the customer DMs support, support emails instructions, the warehouse notifies accounting over LINE when the package arrives, accounting refunds manually, and the invoice gets forgotten. One return often consumes more labor than ten normal orders.

We take orders every day, and we handle returns every day. This article breaks the return-and-refund flow into four stages — application, reverse logistics, refund, invoice — and covers how to automate each one, and how to push down the cost of abuse without antagonizing your normal customers.

First, the Law: Seven Days Is a Right of Rescission, Not a Trial Period

For distance sales (online shopping), the seven-day cooling-off period is a rescission right granted to consumers by Taiwan's Consumer Protection Act. It runs from the day the goods are received, and no reason is required. Two common misconceptions need clearing up: first, seven days of cooling-off is not seven days of trial — the goods must remain in a restorable condition; second, there are reasonable exceptions — perishables, opened personal hygiene products, customized goods, and so on can be excluded under the regulations, but you must state this clearly on the sales page. We sell food products, so some exceptions apply to us — and "spelling it out beforehand" is the only defensible posture. For the details, check the reasonable-exception categories announced by the Executive Yuan, and make sure your product pages and your returns policy page say the same thing.

Application and Reverse Logistics: Let Customers Self-Serve, Let the System Run Errands

The first step in automating returns is replacing "DM customer service" with "self-service application in the member center": the customer clicks return on the order page, ticks a reason, uploads photos (if damaged), and the system rules on it automatically — within seven days and not an excepted product, instant approval; only edge cases enter the manual review queue. This one step cuts more than half of the back-and-forth with support.

For reverse logistics, convenience-store returns are Taiwan's killer infrastructure: the system generates a return code, the customer drops the package at a 7-Eleven or FamilyMart — no label printing, no waiting for a courier. Once you've integrated the major carriers' return APIs, "has the customer shipped it, has it arrived" all become trackable states; the warehouse inspects, clicks confirm, and the refund flow triggers automatically — nobody has to notify anybody over LINE.

Refunds and Invoices: The Last Mile Where Things Go Wrong

• Credit cards get charge reversals, not bank transfers. Refund by the original route is the principle: for card orders, initiate the reversal through your payment provider so the money returns to the original card. Refunding card orders by bank transfer adds manual work — and creates a reconciliation discrepancy that will never match up.
• Collect a refund account for non-card payments. Cash-type payments — convenience-store payment codes, cash on delivery — have no "original route." Collect the customer's refund account at return-application time, not by chasing them down on refund day.
• The invoice must move with the refund. Full refund: void the invoice (or issue an allowance); partial refund: issue an allowance certificate. Skip this step and your revenue ledger and invoice ledger start drifting apart, and month-end reconciliation becomes an existential crisis. We built "refund succeeded → invoice handled automatically" as a single transaction; details in our piece on automating government e-invoicing: voids, reissues, and business-ID scenarios.

Facing Abuse: Tier by Data, Don't Punish Everyone

Genuinely abusive customers are a tiny minority — yet many brands defend against that 1% with a process that inconveniences 100%, paying for it with every normal customer's experience. The smarter approach is tiering:

1. Monitor return rates instead of blockading returns. Record each customer's return rate and returned-amount share. The vast majority will barely return anything in a lifetime — give them the painless flow.
2. Escalate only on anomalous patterns. High-frequency returns, always using the very last day of the cooling-off period, returned goods in abnormal condition — flag these accounts automatically, route their future orders to manual review, or restrict payment methods (for example, revoking cash-on-delivery eligibility).
3. Keep evidence for disputes. Filming or photographing outbound shipments, inspection records for returned goods — it feels redundant until one dispute pays for all of it.

The quality of your return flow decides whether the customer comes back after returning — handle it beautifully, and a return becomes the most memorable brand experience you ever deliver.

If your returns still run as a human relay race, start with the two stages that pay back fastest: self-service application and invoice automation. They're standard modules in our e-commerce system development services — come talk to us.