Via webhook: works today with a bridge on your store

COD Order Confirmation Calls for OpenCart

OpenCart doesn't send signed order webhooks out of the box, so it connects through a small extension or bridge: it sends us each COD order, we call the customer, they press 1 to confirm or 2 to cancel, and we post the result back for the extension to update the order.

Get set up
See what changes in OpenCart

How it works on OpenCart

Works today through our generic webhook connection and an extension on your store

Set up the webhook extension
An extension or small script hooked to order creation sends each new COD order to your unique webhook URL, signed with your secret.
Choose your calling rules
Calling hours in IST, delay after the order, retries, and which orders to call (payment code cod).
Customers get called
Hindi or English. Press 1 to confirm, 2 to cancel.
Order updated by the extension
Your action URL receives confirm or cancel; the extension adds an order history entry with the status you choose.

What changes in your OpenCart admin

The extension receives each outcome as a signed request and records it on the order in the way you choose.

Confirmed: status and history

For example an order history entry with your chosen status, such as Processing.

Cancelled: Canceled status

The extension moves the order to Canceled.

Unreachable: shown in your dashboard

Unreachable orders are marked in your Edesy dashboard, and can be passed to the extension too.

Cancelled first: no call

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

What your OpenCart store needs today

  • A webhook extension or bridge. Code that runs when an order is placed and POSTs it 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 updates the order.
  • COD orders identified by payment code cod, OpenCart's built-in Cash On Delivery.

Good to know

  • How the extension updates the order is up to your setup. It can write the order history from inside OpenCart; we'll help you choose the simplest route for your version.
  • The bridge is yours to run. We help you set it up and test it with a sample order. Our own OpenCart extension 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 OpenCart: FAQ

Explore More

Other platforms, guides and tools

How it works

COD order confirmation overviewHow COD confirmation calls workCOD confirmation calls in HindiCustom store API

Confirm OpenCart COD orders with a webhook extension.

Tell us your OpenCart version and extensions. We'll help you set up the bridge and test it with a sample order.

Get set upBack to overview