The Ecwid integration is planned, not built yet. Once it is: a COD order is placed, we call the customer, they press 1 to confirm or 2 to cancel, and we add a private admin note and update the fulfilment status in Ecwid. Request early access to be in the first group.
Planned design, based on Ecwid's order webhooks and REST API
Ecwid has no order tags, so the answer goes into private admin notes and fulfilment status.
A line is added to the order's private admin notes, and fulfilment status can move to Processing.
Payment status is set to Cancelled and fulfilment status to Will not deliver.
After the last retry, a line in the private admin notes flags the order.
An order cancelled in Ecwid before we call is skipped.
Ecwid's private admin notes are a single field that can only be replaced as a whole. We read the current notes first and add our line to them, so anything your team has written stays. We never overwrite the field blindly.
Ecwid webhooks carry the order id but not the order, and their signature covers the event, not the body. So for every event we fetch the order from your store before calling, rather than trusting what the webhook says.
The same calling engine runs behind every platform
Calling hours in IST, a delay after the order, retry gaps and when to give up.
The order is checked again just before the call. If it was already cancelled or confirmed, we don't call.
Numbers on your do-not-call list are skipped.
Edit the script as plain words. No call-flow builder needed.
Event received, call attempts, key pressed and what was written back, for every order.
Every incoming store event is logged and can be replayed.
How each way of confirming a COD order compares in practice
| Keypad call | WhatsApp message | SMS | In-house calling team | |
|---|---|---|---|---|
| Reaches customers without WhatsApp | - | |||
| What the customer does | Presses 1 or 2 on the call | Taps a button or replies | Replies or opens a link | Talks to an agent |
| Answer saved to your store automatically | Depends on the tool | Depends on the tool | - | |
| Keeps up with order spikes | Needs more callers | |||
| Can handle questions or address changes | - | - | - | |
| What you pay for | Calls made, from a prepaid wallet | Messages sent | SMS sent | Salaries, phones and time |
Other platforms, guides and tools
Request early access and tell us your order volume. We'll contact you when Ecwid is ready for pilot stores.