Wix makes it simple to sell online and to offer cash on delivery as an offline payment option. What it doesn't do is check with the customer before you ship. For stores in India, where a refused COD parcel comes back as a return-to-origin (RTO) charge, that check is worth adding.
This guide covers what you can do inside the Wix dashboard today, how COD orders appear, and how an automated press-1-to-confirm call is designed to fit into Wix.
Selling on Wix with COD? See COD confirmation calls for Wix for the integration plan and the pilot list.
How COD shows up on a Wix order
In Wix you set up cash on delivery as a manual (offline) payment method in your site's payment settings, with the name and instructions the customer sees at checkout.
On the order:
- Payment status is unpaid until you mark it paid after the courier collects the cash.
- The payment method is shown on the order, so your team can tell COD orders apart from prepaid ones.
- Fulfilment status tracks whether the order has been shipped.
- Order tags are supported in Wix's order system and API, which makes them a clean place to record a confirmation without touching payment or fulfilment status.
The manual workflow (and where it breaks)
- Filter the Orders list to unpaid orders, and open the ones placed with cash on delivery.
- Call each customer and read out the order and amount.
- Record the answer on the order, as a note or tag your team agrees on.
- Cancel refused orders so stock is released, and fulfil the confirmed ones.
- Retry the customers who didn't pick up.
Wix Automations can help around the edges, for example by notifying your team when a new order arrives. They don't make the confirmation call.
The manual process works at low volume. It strains when orders arrive overnight, when retries depend on someone remembering, and when the calling list isn't done before the courier pickup.
Apps in the Wix App Market cover the usual categories: WhatsApp and SMS messaging, order notification tools, and call-based confirmation services. When you compare them, check where the answer ends up: on the Wix order itself (tag or cancellation) or only in the app's own dashboard.
How call-based confirmation is designed to work on Wix
This is how Edesy's COD confirmation calls are designed to work with Wix once the integration is built.
1. The integration is installed as an app
Wix sends order events to apps, and accepts order updates from them. So the connection is installed on your site as an app rather than set up with a key you paste in.
Wix's event payloads are signed tokens (JWTs) rather than plain JSON, so every event is verified with the app's public key before it's trusted. That verification is the reason Wix needs a small adapter of its own instead of the generic setup used for other platforms.
2. Rules and the call
Only unconfirmed COD orders would be called by default. Default calling rules, all adjustable: first call 2 minutes after the order, between 9 am and 9 pm IST, up to three attempts (30 minutes, then 2 hours apart), give up after 48 hours. Orders are checked again just before dialling.
The script reads out your store name, order number and COD amount in Hindi or English: press 1 to confirm, press 2 to cancel. Every line is editable.
3. The answer is written back as a tag or a cancellation
| Customer outcome | Planned change in Wix |
|---|---|
| Pressed 1 | Order tag such as COD-CONFIRMED |
| Pressed 2 | Order cancelled with Wix's order cancel |
| No answer after all attempts | Order tag such as COD-UNREACHABLE, for your team to follow up |
| Cancelled before the call | Not called |
Tags are written through Wix's order tagging API and cancellations through its order cancel endpoint, so nothing about payment status changes. Labels are configurable to match what your team uses.
Edge cases worth deciding up front
Whether you confirm by hand today or wait for the integration, these situations come up in the first week on a Wix store. Decide them, and which tag each one gets, early:
- Two orders from the same customer. Each order gets its own call, because confirmation is per order. If customers often split one purchase into several orders, tell your team to look for duplicates in the unreachable list.
- The customer wants to change the address. A keypad call records yes or no; it can't take a new address. Ask such customers to press 1 only if the address is right, and keep a short manual round for the ones who call back. If address changes are common, a conversational AI voice agent for COD verification is the better fit.
- The number is wrong or switched off. After the last attempt the order is marked unreachable. Decide whether your team calls once more, holds the order, or cancels it after a set time.
- The customer answers but presses nothing. This is recorded separately from unreachable, as "no input", so you can treat it differently, for example with one more manual call.
- Partly prepaid orders. If a customer paid part of the amount online, the call should read out only the cash amount due on delivery, not the order total. Check this during setup with a real order.
Why a tag, and not the fulfilment or payment status
It's tempting to record a confirmation by marking the order paid or fulfilled. Both cause problems. Marking a COD order paid before the cash is collected makes your payment records wrong until the courier remits it. Marking it fulfilled can trigger shipping emails before anything has shipped. A tag changes neither, is visible in the order list, and can be filtered on by your team. That is why the design writes the confirmation as a tag and only uses Wix's cancel for a clear "no".
Integration status, stated plainly
Wix is planned and not built yet. There is no Edesy Wix app to install today, and nothing is self-serve for Wix. Join the pilot list on the Wix page and we'll set it up with you when it's ready. Demand from Wix stores decides how soon it is built.
If you run a headless store on Wix with your own backend, the custom store API is live and can be used today: your backend sends a signed order webhook and receives confirm or cancel on its own URL. See the webhook API guide.
What to do in the meantime
You can tighten the manual process right away:
- Agree on tags. Pick one label each for confirmed, cancelled and unreachable, and use them on every order. When an automated call takes over, it can use the same labels.
- Call in batches before pickup, not order by order through the day.
- Use one short script, so every customer hears the order number and amount the same way. Our COD confirmation script guide has Hindi and English versions.
- Put a number on refusals. The COD RTO calculator shows what each avoided return is worth with your courier rates.
Pricing
Calls are paid as you go from a prepaid wallet. Share your monthly COD volume with us for pricing.
Next step: See COD confirmation for Wix and join the pilot list.