COD Confirmation
Confirm cash-on-delivery orders on WhatsApp before you ship — with reminders and order tags.
| 🛒 New COD order | ⚠️ COD Unconfirmed |
| ✅ Confirms | ✅ COD Confirmed |
| ❌ Cancels | ❌ COD Cancelled |
One message, two buttons — and the Shopify order updates itself from whatever the customer taps. No setup needed for the tagging.
This is the automation most stores install Wapify for. Cash-on-delivery orders are placed with nothing at stake, so a meaningful share of them are never going to be accepted at the door — and every one you ship blind costs you the courier fee both ways. Asking the customer to confirm on WhatsApp before you ship turns that guesswork into a yes or a no.
What fires it
A new order whose payment method is cash on delivery. Wapify matches the order's payment gateway against the usual COD names — cash_on_delivery, cod, cash, pay_on_delivery, cash-on-delivery, الدفع_عند_الاستلام — case-insensitively. If your store uses a custom gateway name, set the COD gateway override so it's recognised.
Each order gets exactly one confirmation, and it's sent once — reopening or editing the order doesn't re-send it.
Orders it never sends for
Point-of-sale orders are always skipped — they were sold face to face — and there's no setting for them. Draft orders are skipped by default: they're built by hand in Shopify admin, which usually means you've already spoken to the customer, and asking again by message reads as though you weren't listening. If your team takes orders by phone and still wants them confirmed, switch on Send for draft orders under advanced settings: "Also confirm orders you create by hand in Shopify admin." Those orders then get this message only — Thank You won't also send.
Want a message for those anyway? Thank You covers draft and point-of-sale orders with a thank-you rather than a confirmation request. And you can always send a confirmation by hand from the Orders page or your Inbox — skipping only applies to the automation firing on its own.
When to send
By default the message goes out immediately. You can hold it for up to 12 hours, in one-hour steps.
When to send
How long to wait after the order is placed before the confirmation goes out.Immediately is right for most stores — the customer just checked out, so the message arrives while the order is still on their mind. A delay is useful if you batch-process orders, or if you want a chance to catch obvious mistakes before the customer is asked to commit.
COD Confirmation is deliberately exempt from quiet hours. It's the one message that directly answers something the customer just did, and holding a 3am order until 11am leaves it unshipped for hours. Its reminder, on the other hand, does observe quiet hours — nobody needs chasing at 5am.
What the message says
The confirmation opens with a picture of the order's products side by side — up to four; a bigger order shows three and "+N" for the rest — so the customer recognises their order at a glance. Below it, it lists what they need to check before the courier arrives: the delivery address, the products they ordered, and the total to have ready. Three things are bolded and no more — the address, the amount, and the inspection policy — because those are the three that cause a delivery to be refused at the door.
Mention product inspection
Off by default, like every line under Add to the message — the default message is the order and nothing it promises. Tick it and pick your policy; the help text under it quotes the exact sentence that will be sent, in the language it will be sent in, so you're never guessing.
✅ تقدر تعاين المنتج عند الاستلام.
🚫 حفاظًا على المنتج، غير مسموح بفتح الشحنة أثناء الاستلام.
Set it to whatever your couriers actually do. This is the sentence the customer will quote back at the door, and a mismatch between it and reality is how a delivery turns into an argument. The unchecked wording gives the reason before the rule on purpose — "not available" is a refusal with nothing behind it, and the customer is being asked to accept it while holding their own parcel.
Mention your return policy
Off by default, because it's a promise to the customer and shouldn't be something you make by not looking. Switch it on and the message carries one extra line:
The line adapts to what you allow and for how long — in both languages, with correct Arabic number agreement.
Switch it on and pick which promise the line makes:
🔄 لا يوجد استرجاع أو استبدال بعد الاستلام.
If you take no returns, saying so here is worth more than saying it at the door. On cash on delivery, a customer who discovers it after paying refuses the parcel — and you pay for the round trip. In the confirmation, it's a term they agreed to before the courier moved.
Picking neither action under "Customers can" is the same as switching the whole thing off — it is not read as refusing returns, which is the separate choice above. Wapify says so rather than letting you think a line is going out that isn't.
Order tags
Once the automation is on, every COD order is tagged on your Shopify Orders page, and every customer response updates the tag. There is nothing to set up for this part — the COD page only reminds you which tags to filter by.
| Event | Order tag |
|---|---|
| 🛒 New COD order placed | ⚠️ COD Unconfirmed |
| ✅ Customer confirms | ✅ COD Confirmed |
| ❌ Customer cancels | ❌ COD Cancelled |
| 📵 The number isn't on WhatsApp | 📵 No WhatsApp — call them instead |
| 🙋 Customer taps Need support | 🙋 Needs support — answer them in the Inbox |
Tags are swapped, not stacked. When a customer confirms, the ⚠️ COD Unconfirmed tag is removed and ✅ COD Confirmed takes its place — an order never carries two contradictory tags, and a customer who changes their mind updates the order correctly. That makes the tags reliable enough to filter and to build Shopify automations on.
A customer can cancel until you fulfill the order, even days after they confirmed it. Tapping Cancel then swaps ✅ COD Confirmed for ❌ COD Cancelled and asks them why. Once you've fulfilled the order, or part of it, a Cancel tap changes nothing: the customer is told the order is already prepared for shipping and can't be cancelled now, and the order keeps its tag. You can reword that reply under Templates → Automatic replies (Too late to cancel).
A customer who cancels by mistake can undo it. The reply to Cancel tells them to tap Confirm on the order message within 24 hours. That swaps ❌ COD Cancelled back to ✅ COD Confirmed and removes the cancel reason. If the 24 hours have passed, or you've already cancelled the order in Shopify, the order stays cancelled and they're told so. You can reword both replies under Templates → Automatic replies (Order cancelled and Too late to confirm). If your store is connected to Bosta, an order that was cancelled and then confirmed also gets a note saying so, with the customer's Bosta acceptance rate, whichever notes you've ticked above.
Cancelling in WhatsApp tags the order. It never cancels it in Shopify. Cancelling an order is irreversible and touches inventory and payments, so it stays a human decision. Filter your orders by ❌ COD Cancelled and cancel them yourself when you're ready.
An order nobody answers keeps its ⚠️ COD Unconfirmed tag until the customer replies. Wapify writes tags only — it never changes the order's risk level in Shopify.
What a Confirm tap can chain into
The customer's Confirm tap isn't only a tag. Two other things can hang off it:
- InstaPay deposit — Egyptian stores can ask the customer to transfer part of the order the moment they confirm. It fires on the tap rather than on the order, so with this automation off it never fires on its own.
- Upsell — COD order confirmed is one of its send triggers.
Follow-up reminder
Most people who don't answer aren't refusing — they missed the message. The reminder sends a second, shorter message to anyone who hasn't tapped a button, between 1 and 48 hours after the first (4 hours by default).
The reminder spells out the consequence — the order stays unshipped — because that's what makes tapping a button feel necessary.
It's sent once. A customer who ignores both is left alone.
Advanced settings
Show advanced settings at the bottom of the COD tab opens four more cards, each with its own switch: asking for a detailed address, asking for their location on the map, sending for draft orders and flagging duplicate orders. All four start off.
Ask for a detailed address
COD orders arrive with the address the customer typed in a hurry, and a courier can't deliver to “Maadi”. Switch on When the address is too short, ask the customer to share it again and Wapify checks the street address on every COD order. When it's shorter than the number of characters you set — anywhere from 5 to 60 — a message asks the customer for the full one.
When to ask decides when it goes:
The address you already have is quoted back. A customer who reads their own half-written address understands in one glance why they're being asked again.
The button opens a short form inside WhatsApp. When they send it, the new address replaces the street address on the Shopify order and on the customer's saved address (which becomes their default, so their next order starts from it), the order is tagged 📍 Address Updated, and a note records what it said before — so an order you've already looked at tells you that it moved.
What gets measured
Only the street address — the first address line. Not the apartment or floor line, not the city, the governorate or the country, and the reply replaces only that same line. Everything else the customer entered at checkout, including their phone number, is left exactly as it was.
That matters when you pick your threshold: you'll be looking at a full address in Shopify, but the count only covers the street. Twenty characters is the default and is roughly “15 Road 9, Maadi”. An order with an empty street line is always asked; an order with no shipping address at all — a pickup — never is.
It's asked once per order, and on Free it counts as one message from your allowance. An order you've already shipped or cancelled is never asked.
Reminding them
Tick Remind them if they don't reply and pick when — between 1 and 48 hours after the ask (4 hours by default). One shorter message goes out with the same Send My Address button, and the answer lands on the order exactly as it would from the first one.
Sent once, and only while the address is still the problem.
It isn't sent if the customer has already sent the address, written anything back in the chat (an address typed as a message counts), or tapped Cancel — or if the order has shipped or been cancelled, or its street address is long enough now because you fixed it yourself. Like every reminder, it waits out quiet hours.
Ask for their location on the map
A written address gets the courier to the street. A pin gets them to the door. Switch on Ask for their location on the map — "Ask every customer to share their location, so the courier can find them." — and every COD order with a delivery address gets one more message asking for their pin. Right after the customer taps Confirm, it goes as WhatsApp's own Send location message, in the same words as the template: one tap opens their map. Unlike the detailed address above, there's no threshold: everyone is asked. Both can be on at once.
The button opens WhatsApp's own location picker. A pin sent from the attachment menu counts too, even one sent before you ask. You can reword this message in Templates → Automatic replies.
When to ask works as for the address: After the customer confirms the order (the default — no Confirm, no ask) or Right after the confirmation message. WhatsApp only lets a business send the Send location message within 24 hours of the customer's last message, so with the second the ask is a message with a Share My Location button, and tapping it brings the Send location message.
A customer who sends a pin before tapping anything has confirmed the order, exactly as a Confirm tap would, and isn't asked for it again. A pin never undoes a cancellation.
With the detailed address on too, they're asked one thing at a time. When an order's address is too short, the address form goes first, and the Send location message follows as soon as they send the form. If they haven't sent it 23 hours later, the map is asked for anyway — the last moment WhatsApp still allows the Send location message. Orders whose address is fine get only the map, as above.
When the pin arrives:
- its Google Maps link goes into the order's note, with the place name when WhatsApp gives one;
- the order is tagged
📍 Location Shared; - the customer is thanked — "Thanks, we've added your location to your order 📍"
The street address on the order isn't changed: it's what the courier's label prints, so the pin sits beside it. A customer who taps the button and then types instead of sending a pin gets the picker again.
It's asked once per order, never for an order already shipped or cancelled. On Free it counts as one order-update message. In the Inbox, COD order → Shared their location filters to everyone who sent one, and you can ask by hand from a WhatsApp chat with the Ask for their location on the map template.
Reminding them to share it
As with the address, tick Remind them if they don't reply and pick when: between 1 and 48 hours after the ask, 4 hours by default. One reminder goes out with the same Share My Location button, and a pin sent from it lands on the order exactly as one sent from the first message.
It's sent once, and not at all if they've already sent a pin, written back to you, tapped Cancel, or the order has shipped or been cancelled.
Customer acceptance rate
Some customers accept nearly everything they order. Others refuse routinely, and they do it at every store, not just yours. If you ship with Bosta, Wapify can note which kind you're dealing with directly on the order, using Bosta's own record of the customer: how many of their Bosta deliveries they took and how many came back, across every store shipping with Bosta.
The acceptance rate is part of the Growth and Pro plans. On Free and Starter the card shows what it does, locked; nothing is looked up or written to your orders. A key you connected stays saved if you move to a lower plan, so it works again as soon as you're back on Growth or Pro. See Plans.
| Delivery history | Order tag |
|---|---|
| Above 70% delivered | ✅ High Acceptance |
| 40–70% delivered | ⚠️ Medium Acceptance |
| Below 40% delivered | 🚫 Low Acceptance |
These are Bosta's own bands, so a customer reads the same in Wapify as in Bosta's tools. One delivery is enough to rate a customer.
The note and the tag are chosen separately for each level — tag only your Low customers, say, or add the note to Medium and Low too. They say different things on purpose. The tag carries the verdict to the Orders list, where you can filter, sort, bulk-select and build Shopify Flow automations on it. The note carries the numbers behind that verdict, where you'll read them with the order open:
The note as it appears on the order. It follows your admin language, and it never just repeats the tag.
A customer Bosta has never delivered to gets neither a note nor a tag — there's nothing to judge yet. Until you connect Bosta, nothing is written to any order. The same record shows at the top of the customer panel in the Inbox.
Bosta limits how often one account can look customers up, so Wapify asks as rarely as it can. New orders are looked up together: the tag and note land a few minutes after the order arrives (at most about five), with one request to Bosta for all the orders that came in meanwhile. A customer Bosta answered about in the last week is tagged straight away. Each answer is reused for a week, so an order delivered or returned in the last few days can take up to a week to show in a customer's rate, and opening a chat in the Inbox also looks up your other recent chats in the same request. If the limit is reached anyway, Bosta blocks lookups for your whole Bosta account — its own dashboard stops showing the rate too — and every further attempt can keep that block going. So Wapify stops asking for an hour; if Bosta is still refusing at the next try, it waits 4 hours at a time until Bosta answers. The COD card and the Inbox say so, and waiting orders are tagged as soon as Bosta answers. Connecting a new API key doesn't help, since the block is on the account. An order still waiting after three days is left untagged.
How to switch it on
- In your Bosta dashboard, open Settings → API Integration and create an API key with Read/Write access. (A Read Only key can't look the rate up.) Copy it — Bosta only shows it once.
- In Wapify, open the Connection page, find the Bosta card at the bottom, click Connect and paste the key. Wapify checks the key with Bosta before saving it.
- Once connected, each level has an Order tag and a Note tick-box. Tags start ticked for all three levels and notes start unticked — change them per level and save.
Tag values are always in English, on every store, even when you use Wapify in Arabic: a saved search or a Flow trigger built on 🚫 Low Acceptance has to keep matching when you switch the admin language. The note is the half that follows your language.
It writes a note, never a risk assessment. Shopify's risk assessments accumulate rather than replace, so one written today would still sit on the order after the customer's history changed. A note is unambiguous and sits where you'll read it.
Your Bosta key
Wapify uses the key only to look up the customer's phone number in Bosta's acceptance rate, once per new order and when you open their chat. The key is never shown again after you connect — only its last few characters — and you can disconnect it from the same card at any time. It is deleted when you uninstall Wapify.
Duplicate orders
A customer who isn't sure their order went through orders again. Two identical parcels go to the same address, the customer takes one, and you pay for the round trip on the other — the same money a refused delivery costs, for an entirely avoidable reason. Shopify shows the two orders as unrelated rows, minutes or days apart.
With Flag duplicate orders ticked, Wapify checks each new order against that customer's last 30 days and flags it when all three of these hold:
- Same customer — matched on the phone number the order carries, so guest COD orders count too.
- Same items — the whole basket, not an overlap. Someone who added a second product is shopping, not double-ordering, and isn't flagged.
- The earlier order hasn't shipped — checked against Shopify at that moment, not from a cached copy. Once a parcel is with the courier there's nothing left to stop, so the order isn't flagged.
| Situation | Order note | Order tag |
|---|---|---|
| Same items as an earlier order that hasn't shipped | 🔁 Possible duplicate order | 🔁 Duplicate Order |
The note names the earlier order, so you can open it and decide. If the quantities differ between the two, it says so — don't assume the parcels are twins.
Nothing is cancelled, merged or changed. Two identical orders are sometimes genuinely two orders — the same gift for two people. Wapify tells you; you decide.
Where the results show up
- Shopify orders — tags, acceptance notes and duplicate flags, filterable in your admin.
- Logs → COD Confirmation — every message with its status and what the customer answered.
- Analytics — confirmation rate, COD value confirmed, how fast customers answer, and the order funnel.
- Feedback Center — the reasons customers gave when they tapped Cancel.
- Inbox — anyone who replied with words instead of a button.
Sending one by hand
Select orders in Shopify, open the ⋯ menu and choose Send order confirmation. A manual send skips the configured delay and ignores quiet hours, and by default won't message someone who already received one. See Actions on the Orders page.