COD returns (RTO) on Shopify: confirm orders on WhatsApp first

Why cash on delivery orders come back undelivered, what each return costs, and how a WhatsApp confirmation with Confirm and Cancel buttons cuts the rate.

Every store that offers cash on delivery learns the same acronym within a month: RTO, return to origin. The parcel goes out, the courier knocks, nobody pays, and the box comes back. You have paid outbound shipping, you pay return shipping, the courier charges a COD handling fee whether or not cash changed hands, and the product has spent two weeks in a van. In markets where COD is the default payment method, India, much of the Middle East and North Africa, Southeast Asia and parts of Latin America, RTO rates of 20 to 30 percent are ordinary and 40 percent is not unheard of.

The single most effective fix is also the oldest: ask the customer whether they meant it before you ship. Call centres did this for years. WhatsApp does it cheaper, faster and with a record. This post is about the business side of that step, why orders come back, what a return really costs, how a confirmation message changes the numbers, and how to run the workflow in Shopify with Beacon Messenger doing the messaging.

Why COD parcels come back

Returns to origin have a handful of causes, and a confirmation message catches most but not all of them. It helps to know which is which before measuring results.

Causes of COD returns and whether a pre-shipment confirmation catches them
CauseShare of RTO (typical)Caught by confirmation?
Impulse order, customer changed their mindLargeYes, they tap Cancel or do not reply
Fake or prank order, invented name or addressMediumYes, no reply or a wrong number
Wrong or incomplete phone numberMediumPartly: the message fails, which is itself a signal
Ordered twice by mistakeSmallYes, the customer sees two messages
Customer not home, no cash on the dayMediumNo, this happens after shipping
Courier did not attempt deliverySmallNo

The first four rows are the ones a message prevents, and together they are usually more than half of all returns. The last two need a different fix, a delivery-day reminder or a better courier, and no amount of confirmation changes them. Keep that in mind when you set a target.

What one return costs

Merchants tend to count only the return shipping. The full bill is longer. Outbound shipping, return shipping, the courier's COD fee, packaging, the labour to pick, pack and later unpack and restock, and the item itself if it comes back damaged or out of season. For a 40 dollar order with a 10 dollar margin, a return can cost 12 to 18 dollars all in, which means one return wipes out the profit of one to two successful orders.

Put differently: a store doing 1,000 COD orders a month at a 25 percent RTO rate and 15 dollars per return is losing 3,750 dollars a month to parcels that were never going to be paid for. Cutting the rate to 12 percent saves close to 2,000 dollars monthly. Against that, a confirmation template on the WhatsApp Business Platform costs a few cents per order, and the customer's reply inside the conversation is free. Our pricing post has the current per-message rates by category.

How the confirmation works in Beacon Messenger

Beacon Messenger has a trigger called COD confirmation. It fires when a new order's payment method matches a cash on delivery pattern: the gateway is called cash on delivery, COD, contra entrega, contra reembolso, pago en efectivo, pagamento na entrega, or Shopify's generic manual. The post on which orders trigger a message covers the matching in detail, including why manual counts.

The message is an approved WhatsApp template with the order details and two quick reply buttons, typically Confirm and Cancel. The template examples post has wording that has passed Meta's review. When the customer taps a button or types an answer, the app matches the reply to the original message, classifies it, and does three things:

  • Records the reply on the message row in the log, so you can see it next to the order.
  • Tags the order in Shopify: beacon-cod-confirmed for a yes, beacon-cod-cancelled for a no. If the customer changes their mind and replies again, the opposite tag is removed and the new one added.
  • Sends a short acknowledgement in the template's language, for example a thank you with the order number for a confirmation, or a note that the order has been marked as cancelled and they can reply if that was a mistake.

What the app does not do is cancel the order, restock inventory or refund anything. It tags. The decision to act on the tag stays with you or with an automation you control, which is deliberate: a customer typing no in response to a different question should never silently cancel an order.

Running the workflow in the Shopify admin

The tags are the handle for everything that follows. A practical setup takes about fifteen minutes.

  1. Create a saved view on the Orders page filtered by payment status pending and tag beacon-cod-confirmed. Call it COD ready to ship. Fulfilment works from this view only.
  2. Create a second view for tag beacon-cod-cancelled. Once a day, cancel those orders in Shopify with the reason Customer, which restocks the items. Shopify Flow can do this step for you with a trigger on the tag being added, if you prefer no hands.
  3. Create a third view for COD orders with neither tag, placed more than a set number of hours ago. These are the unanswered ones. Decide a policy: a second message, a phone call, or ship after 24 hours for repeat customers and hold for first-time ones.
  4. Add the three counts to the end-of-day routine. The ratio of cancelled plus unanswered to total COD orders is your pre-shipment catch rate, which is the number the confirmation step is buying you.

The unanswered group deserves most of the thought. Some are genuine customers who do not check WhatsApp; some are fake orders with a real number belonging to someone else. A message that failed to deliver at all, visible as failed in the message log, is the strongest fake-order signal you will get before shipping, because it usually means the number does not exist on WhatsApp.

Timing and tone

Send the confirmation immediately on order creation, which is what the trigger does by default. The customer is still holding the phone, the purchase is fresh, and reply rates are highest in the first few minutes. A confirmation sent the next morning reads like a bureaucratic hurdle and gets ignored.

Keep the template short and make the buttons the obvious action. State the order number, the items in one line, the amount to pay in cash, and the question. Avoid asking the customer to type anything; a tapped button is classified cleanly, while a typed reply only counts if it starts with a word the app recognises, which the reply matching post lists. If your customers write in a language that is not on that list, the reply is recorded as other and you will see it in the log, but no tag is applied.

Measuring whether it worked

Measure RTO the same way before and after, and give it a full delivery cycle. The honest metric is returned parcels divided by parcels shipped, for COD orders only, over a month. Expect the shipped count to fall, because cancelled and unanswered orders never ship, and the returned count to fall faster. A store that moves from 25 percent to the low teens has removed the preventable half; getting below 10 percent usually needs delivery-day work too, which is what the shipping update trigger is for.

Two side effects are worth watching. Confirmed orders that still return, which point at courier or address problems rather than intent. And a rising cancellation rate at the confirmation step, which is not a failure of the message but a sign that something upstream, an ad, a price, a delivery promise, is attracting orders people do not mean. Both are cheaper to learn from a tag than from a returned box.

Where this stops being enough

Confirmation is the first line. Stores with very high RTO add an address check in the same message, a small prepaid incentive to switch away from COD, or a block on repeat offenders by phone number. Beacon Messenger does the first line and records enough, the reply and the tags on every order, for you to build the rest on top with Shopify's own tools. If you sell on cash on delivery and have not asked the customer yet, start there; it is the cheapest two percent of revenue you will ever recover.

Frequently asked questions

Does Beacon Messenger cancel a COD order when the customer replies Cancel?

No. It records the reply, tags the order beacon-cod-cancelled and sends an acknowledgement. Cancelling the order in Shopify, which restocks the items, is left to you or to a Shopify Flow automation triggered by the tag, so that a misread reply can never remove an order on its own.

What should I do with COD orders nobody answered?

Treat them as a separate queue. Check whether the message was delivered at all; a failed send usually means the number is not on WhatsApp and the order is probably not real. For delivered but unanswered messages, decide a hold period, send a reminder or call, and ship only once someone has confirmed or the hold has passed for a known customer.

How much does a WhatsApp COD confirmation cost per order?

One template message, charged at Meta's per-message rate for its category, which is a few cents in most countries. The customer's reply and the acknowledgement inside the conversation are not charged separately. Compare that with a return, which typically costs 12 to 18 dollars for a 40 dollar order.

How much can a confirmation step reduce RTO?

It removes the preventable causes: changed minds, fake orders, wrong numbers and duplicates, which are usually more than half of returns. Stores commonly move from 25 to 30 percent down to the low teens. Returns caused by the customer not being home or the courier not attempting delivery need a delivery-day reminder instead.

More guides