Cash on delivery on Shopify: confirm orders over WhatsApp before you ship

Why COD orders get refused at the door, how a WhatsApp confirmation with Confirm and Cancel buttons cuts returns, and what to do on a No: cancel or restock.

If you sell with cash on delivery, you know the pattern: the parcel travels across the country, the customer is not home or has changed their mind, and you pay the outbound and return shipping for nothing. Confirming the order over WhatsApp within minutes of checkout is the cheapest fix, and it works because the customer is still holding their phone.

Why a WhatsApp confirmation works better than a call

  • It arrives instantly and asynchronously; nobody has to pick up.
  • The customer taps a button instead of typing, so replies are unambiguous.
  • It doubles as an order summary, which catches wrong sizes and addresses early.
  • It creates a written record that the order was confirmed, useful when a courier reports a refusal.

How the flow works in Beacon Messenger

  1. A customer places an order with a cash-on-delivery or manual payment gateway.
  2. Shopify sends the orders/create webhook. Beacon Messenger recognises the gateway and queues the Cash on delivery confirmation automation, after any delay you configured.
  3. The customer receives your approved template with the order details and two quick-reply buttons: Confirm order and Cancel order.
  4. When they tap Confirm, Meta sends the reply to Beacon Messenger's webhook, which adds the tag beacon-cod-confirmed to the order in Shopify. Tapping Cancel adds beacon-cod-cancelled.
  5. Your fulfilment team filters orders by tag. Ship the confirmed ones, hold or cancel the rest, and follow up manually on orders with no reply.

Creating the template in WhatsApp Manager

Create a utility template with a body such as "Hi {{1}}, thanks for ordering from {{2}}. Order {{3}} totals {{4}} and will be paid in cash on delivery. Please confirm so we can ship it." Add two Quick reply buttons labelled Confirm order and Cancel order. Utility templates with quick replies are normally approved within minutes to a few hours. In Beacon Messenger, map {{1}} to customer first name, {{2}} to shop name, {{3}} to order number and {{4}} to order total.

Handling no replies

Not every customer responds. Decide a rule, such as shipping after 24 hours without a reply for repeat customers and holding first orders, and make it visible to whoever packs. The delivery log shows whether the confirmation was delivered and read, which helps distinguish a customer who is ignoring you from one whose number is wrong.

What should happen when the customer says No: cancel, restock, tag

A COD confirmation is only half a workflow. The other half is what your store does with a No, and this is where automation has burned merchants before. One reviewer of SuperLemon wrote on 9 September 2021, in the app's 1- and 2-star reviews, that "Auto order cancel has NOT been selected. Yet when the client replies to the COD with No, their system cancels the order on shopify!" and that "The cancelation does NOT restock the item". That is one merchant's report about a much older version of that app, but it names the two ways a decline can go wrong: an action you did not choose, and an action that only half completes. Cancelling an order and putting its items back into inventory are separate decisions in Shopify, and a WhatsApp app should not make either of them for you silently.

Beacon Messenger deliberately does not cancel orders, restock inventory or issue refunds when a customer taps Cancel. What it does is narrower and reversible: it records the reply on the message's log entry, adds the tag beacon-cod-cancelled to the order (removing beacon-cod-confirmed if it was there), and sends the customer a one-line acknowledgement in the language of the original message, for example "Understood, your order {order} has been marked as cancelled. Reply here if that was a mistake." The acknowledgement exists in English, Spanish, Portuguese and Hindi. Free-text replies are classified too, so a customer who types "no", "cancelar" or "nahi" instead of tapping the button is tagged the same way. Because the order itself is untouched, a customer who changes their mind an hour later costs you a tag change, not a re-created order.

That leaves the cancel-and-restock step to you. Manually, open the order and click Cancel order; Shopify's help centre notes that the Restock inventory option "is selected by default, which returns the canceled items to your inventory", and that after cancelling, "the details about what items are restocked and refunded is stored in the order's Timeline" (Canceling orders). Shopify Flow also has a Cancel order action whose fields include Reason, Refund, a Staff note and "Restock items", which "when checked, items from the order are returned to the store's inventory" (Cancel order action). Note, though, that Flow's trigger reference lists tag triggers for customers but not for orders, and merchants on the Shopify Community report using a third-party trigger app to start a workflow when an order tag is added. Until Shopify adds a native trigger, the most dependable setup is the tag plus a daily filtered view, or a Flow workflow started by such an app if you already use one.

  1. Decide the rule first: cancel immediately on No, or hold for a manual check. Many COD merchants hold, because a share of declines are misunderstandings that a quick call recovers.
  2. If you automate through Flow with a tag trigger from a companion app, add a condition that the order is still unfulfilled, then use Cancel order with Restock items checked and a staff note such as "Cancelled by customer via WhatsApp COD confirmation".
  3. Filter your Orders page by the tag beacon-cod-cancelled once a day to catch anything the workflow skipped, and by beacon-cod-confirmed to release orders for packing.
  4. Turn on the Skip cash-on-delivery orders option in the order confirmation automation so a COD customer receives one message asking for a decision, not two.

Things to avoid

  • Sending the confirmation from a personal WhatsApp account or an unofficial gateway. Automated sends from those get numbers banned.
  • Asking for anything beyond a confirmation in the first message. Keep it to the order; questions about substitutions can come after the tap.
  • Charging customers to confirm. The message is a utility conversation billed to your Meta account; it should never be a paywall for the shopper.

More guides