Via webhook: works today with a bridge on your store

COD Order Confirmation Calls for PrestaShop

PrestaShop connects through a small bridge: a webhook module or script sends us each COD order, we call the customer, they press 1 to confirm or 2 to cancel, and we post the result back so the bridge can move the order to the state you choose.

How it works on PrestaShop

Works today through our generic webhook connection and a bridge on your store

Set up the webhook bridge
A webhook module or small script sends each new COD order to your unique webhook URL, signed with your secret.
Map your order states
Pick which PrestaShop order state means confirmed and which means cancelled. State ids differ between stores.
Customers get called
Hindi or English. Press 1 to confirm, 2 to cancel.
Order state updated
Your action URL receives confirm or cancel; the bridge adds an order history entry with the state you mapped.

What changes in your PrestaShop admin

PrestaShop records changes as order history states. The bridge applies the state you map to each outcome.

Confirmed: your chosen state

For example a custom "COD confirmed" state or Processing in progress, added to the order history.

Cancelled: Canceled state

The bridge moves the order to the Canceled state.

Unreachable: shown in your dashboard

Unreachable orders are marked in your Edesy dashboard, and can be passed to the bridge if you want a state for them.

Cancelled first: no call

If the bridge sends a cancellation before we call, the call is skipped.

What your PrestaShop store needs today

  • A webhook bridge. A webhook module or short script that POSTs new orders to your webhook URL as JSON, signed with HMAC-SHA256 using the secret we give you. The format is the same as our custom store API.
  • An action URL that receives confirm or cancel, checks the signature, and adds an order history entry with the right state.
  • COD orders identified by payment module, ps_cashondelivery for PrestaShop's built-in Cash on delivery module.

Good to know

  • State ids are per store. If you created a custom state such as "COD confirmed", its id is specific to your shop, so we map states with you rather than assuming numbers.
  • Webservice is XML. If your bridge uses PrestaShop's webservice to change states, it sends XML and authenticates with a webservice key. A module that runs inside PrestaShop can change the state directly instead.
  • The bridge is yours to run. We help you set it up and test it with a sample order. Our own PrestaShop module is a later option if enough stores ask.

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 PrestaShop: FAQ

Confirm PrestaShop COD orders with a webhook bridge.

Tell us your PrestaShop version and modules. We'll help you set up the bridge and map your order states.