Planned: integration not built yet

COD Order Confirmation Calls for Ecwid

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.

How it will work on Ecwid

Planned design, based on Ecwid's order webhooks and REST API

Connect your Ecwid store
An Ecwid app token for your store, and order webhooks sent to our endpoint.
Tell us your COD method
Ecwid payment method names are free text, so you tell us which name means cash on delivery.
Customers get called
Hindi or English. Press 1 to confirm, 2 to cancel.
Ecwid order updated
A line is added to the private admin notes and, if you want, the fulfilment status moves to Processing.

What will change in your Ecwid admin

Ecwid has no order tags, so the answer goes into private admin notes and fulfilment status.

Confirmed: note and Processing

A line is added to the order's private admin notes, and fulfilment status can move to Processing.

Cancelled: Cancelled, Will not deliver

Payment status is set to Cancelled and fulfilment status to Will not deliver.

Unreachable: admin note

After the last retry, a line in the private admin notes flags the order.

Already cancelled: no call

An order cancelled in Ecwid before we call is skipped.

What an Ecwid store will need

  • An Ecwid app token for your store, encrypted on our side and only sent to Ecwid's API for your store.
  • Order webhooks for new and updated orders. A change to a Cancelled payment status is treated as a cancellation.
  • Your COD payment method name, since Ecwid lets each store name its payment methods freely.

Your existing notes are kept

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.

Why we fetch every order

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.

What every connection includes

The same calling engine runs behind every platform

Calling window and retries

Calling hours in IST, a delay after the order, retry gaps and when to give up.

Fresh check before dialling

The order is checked again just before the call. If it was already cancelled or confirmed, we don't call.

DND check

Numbers on your do-not-call list are skipped.

Hindi and English scripts

Edit the script as plain words. No call-flow builder needed.

Order timeline

Event received, call attempts, key pressed and what was written back, for every order.

Webhook replay

Every incoming store event is logged and can be replayed.

Confirmation call vs the alternatives

How each way of confirming a COD order compares in practice

Keypad callWhatsApp messageSMSIn-house calling team
Reaches customers without WhatsApp-
What the customer doesPresses 1 or 2 on the callTaps a button or repliesReplies or opens a linkTalks to an agent
Answer saved to your store automaticallyDepends on the toolDepends on the tool-
Keeps up with order spikesNeeds more callers
Can handle questions or address changes---
What you pay forCalls made, from a prepaid walletMessages sentSMS sentSalaries, phones and time

COD Confirmation for Ecwid: FAQ

Want COD confirmation calls on Ecwid?

Request early access and tell us your order volume. We'll contact you when Ecwid is ready for pilot stores.