HomeBlogProcess Automation
Process Automation

Returns After 11.11: Build Your Reverse Logistics Process Before Peak

Returns After 11.11: Build Your Reverse Logistics Process Before Peak

If you sell online in Singapore, design your returns process before 11.11 rather than after it. A returned order typically costs two to three times what the outbound order cost to fulfil, once you count inbound freight, refund handling, inspection labour, repackaging and the stock that never comes back in sellable condition. Peak season does not just raise that cost, it concentrates it: the returns from a 11 November campaign arrive through late November and December, colliding with year-end stock-take, Form C-S preparation and Chinese New Year ordering. A manual process that works quietly at 40 orders a day does not survive 400. The weeks between now and the end of October are the last practical window to fix it, because from November onwards your team will be fulfilling, not redesigning.

What does a return actually cost a Singapore SME?

Most owners price a return as the refund plus postage. That undercounts it badly. The real cost of one returned item breaks down roughly like this:

Add these up on a S$45 order and the economics change completely. On a 6 to 10 per cent return rate across general merchandise, and considerably higher in apparel and footwear, a strong 11.11 can convert a profitable campaign into a break-even one during December, long after everyone has congratulated themselves on the gross revenue number.

Why does the returns decision have to be made before peak?

Because the decisions are upstream of the campaign, not downstream of it. Three things lock in before a single order ships:

Your policy is published, not improvised. Marketplace return windows on Shopee, Lazada and TikTok Shop run on their own timers, which means requests keep arriving weeks after the campaign ends. Your own webstore policy, listing copy and packaging inserts have to state the terms clearly, and those assets have to be written, printed and uploaded before campaign content freezes in late October.

Your inventory positions assume a recovery rate. If you plan to resell returned units, that assumption belongs in the buy you are placing now for November and December stock. Deciding in January that 40 per cent of returns are unsellable is a write-off. Deciding it in September is a purchasing input.

Your December calendar is already full. Year-end payroll, the 30 November filing deadline, closing stock valuation and Chinese New Year factory lead times all land in the same six weeks as the returns wave. Nothing gets built in December. It only gets survived.

Which parts of the returns process should you automate first?

You do not need a returns management platform to fix this. You need five things to stop living in WhatsApp threads and a shared spreadsheet, in this order:

  1. A single intake point that issues a reference number. One form, one RMA number, one record. This alone removes most of the back-and-forth, because every subsequent message attaches to a case instead of restarting the conversation.
  2. Automatic status notifications. Received, inspected, approved, refunded. Customers chase because they are uninformed, and each chase costs you handling minutes at exactly the time you have none.
  3. A distinct inventory state for returned goods. Returned-pending-inspection must be a separate location in your system, never an automatic add-back to sellable stock. Auto-restocking a damaged unit is how you oversell during peak.
  4. Structured credit notes for refunds. Every refund on a GST-charged sale needs a proper credit note trail so your output tax adjusts correctly. If you are moving to InvoiceNow, build this now while the volume is still low.
  5. Reason codes on every case. Wrong size, damaged in transit, not as described, changed mind. Without this you are recording a cost. With it, you are collecting the data that tells you which three SKUs and which one courier are generating a disproportionate share of your losses.

How do you stop returned stock disappearing from your books?

Returned inventory is the single most common source of unexplained shrinkage in Singapore SME retail operations. The parcel comes back, someone puts it on a shelf behind the packing bench, it is never counted, and it surfaces during a stock-take as a discrepancy nobody can explain.

The fix is physical and procedural: one designated returns area, three clearly labelled states (pending inspection, restock, write-off), and a rule that stock only moves between states through a system transaction. Then inspect on a fixed cadence, weekly at minimum, so nothing ages quietly in a corner for two months.

Time your October stock-take to establish the baseline before the returns wave, and you gain something valuable: any variance you find in January is attributable to peak season activity rather than to accumulated drift of unknown origin. That turns a vague suspicion into a measurable number you can act on.

What does a working process look like by the numbers?

Reasonable targets for an SME processing 200 to 800 returns across a peak quarter:

At 500 returns, cutting 12 minutes per case recovers roughly 100 staff hours in a quarter, which is most of a month of one person's capacity, released in the exact weeks when capacity is scarcest.

What should you do in the next four weeks?

Week of 22 September: pull your last 12 months of returns and calculate your actual rate by category and your true per-case cost. Most owners are surprised, in one direction or the other.

Week of 29 September: write the policy. Windows, conditions, who pays return shipping, what is non-returnable. Make it unambiguous, because ambiguity is what generates disputes.

Week of 6 October: build the intake form, the reference numbering and the notification templates. Set up the returns area and its three states.

Week of 13 October: run 20 live cases through the new process, fix what breaks, brief seasonal staff, and lock the campaign assets before content freeze.

None of this is glamorous, and none of it appears in a 11.11 results announcement. It is simply the difference between knowing what your peak quarter earned and hoping that it earned something.

Frequently Asked Questions

Do I need dedicated returns software, or can I use what I already have?

Start with what you have. Most SMEs can build a functional process from a form tool, their existing inventory system and a small set of message templates. Dedicated returns platforms earn their cost above roughly 150 to 200 cases a month, or when you are running several marketplaces plus your own webstore and need one consolidated view. Below that threshold, process discipline delivers more than a licence fee.

How should I handle GST on a refund?

A refund on a GST-charged sale normally requires a credit note so your output tax is adjusted in the correct accounting period. The practical failure is not the tax treatment but the record-keeping: refunds issued directly through a payment gateway or marketplace with no matching document in your accounts. Make the credit note a required step in the process, not something reconstructed at year-end.

Should returned stock go straight back into sellable inventory?

No, not automatically. Every returned unit should land in a pending-inspection state and move to sellable only after a human confirms its condition. Automatic add-back is a direct cause of overselling during peak, and overselling on a marketplace during a campaign costs far more in ratings and penalties than the unit is worth.

Ready to Transform Your Business?

Let Digital Perpetual help you automate, streamline, and grow.

Get Started with Digital Perpetual →
ecommerce returns reverse logistics 11.11 inventory management process automation year-end close