Is the Adobe Commerce integration available now?

Not yet. It's planned. Request early access; in the meantime the webhook bridge described on our Magento page works for Adobe Commerce stores too.

Why Adobe I/O Events rather than a plugin?

I/O Events is Adobe's own signed event system, so no extra extension has to run on your store to tell us about new orders.

Why do I need to enable integration tokens as bearer tokens?

From Adobe Commerce 2.4.4 that option is off by default. It's needed so we can add order comments and cancel orders with the integration token you create.

The order-save event fires on every save. Won't customers get several calls?

No. We work out from the order's state whether it's new, and each order gets only one confirmation journey.

How is confirmation recorded without tags?

As an order comment. If you hold COD orders until they're confirmed, the order can also be released from hold.

Which languages can the call be in?

Hindi and English scripts are available today. You can edit every line; the order number, amount and store name are filled in for each order.

When do customers get called?

Only inside the calling hours you set, 9 am to 9 pm IST by default. Orders placed at night are called the next morning, and you choose the delay after the order and how many retries to make.

Pay as you go from a prepaid wallet, based on calls made. Share your monthly COD order volume and we'll send pricing for your volume.

Planned: integration not built yet

COD Order Confirmation Calls for Adobe Commerce

The Adobe Commerce integration is planned, not built yet. It will use Adobe I/O Events: an order is saved, we call the COD customer, they press 1 to confirm or 2 to cancel, and the order gets a comment or is cancelled through the Adobe Commerce API. Request early access to be in the first group.

Request early access

See what changes in Adobe Commerce

How it will work on Adobe Commerce

Planned design, based on Adobe I/O Events and the Adobe Commerce REST API

Connect through Adobe I/O Events

Subscribe the order-save event to our endpoint, and create an integration token for order updates.

Choose your calling rules

Calling hours in IST, delay after the order, retries, and which orders to call (payment method cashondelivery).

Customers get called

Hindi or English. Press 1 to confirm, 2 to cancel.

Adobe Commerce order updated

Confirmed orders get an order comment (and can be released from hold); cancelled orders are cancelled.

What will change in your Adobe Commerce admin

Adobe Commerce has no order tags, so confirmation is an order comment, optionally combined with hold and release.

Confirmed: order comment

A comment in the order history; if you hold COD orders until confirmed, the order can be released from hold.

Cancelled: order cancelled

When the customer presses 2, the order is cancelled through the Adobe Commerce API.

Unreachable: order comment

After the last retry, a comment flags the order for your team.

Already handled: no call

The order is checked just before dialling; cancelled orders are skipped.

What an Adobe Commerce store will need

Adobe I/O Events set up for your instance, with the order-save event sent to our endpoint. Events are signed by Adobe and we verify each one.
An integration access token for order comments and cancellation. On Adobe Commerce 2.4.4 and later, using an integration token as a bearer token has to be switched on in the admin.
COD orders identified by payment method cashondelivery.

Why we fetch the order

The order-save event fires every time an order is saved, not only when it's created, and may not include every field. We work out whether an order is new or cancelled from its state, fetch it from your store when details are missing, and make sure each order gets one confirmation journey however many events arrive.

On Magento Open Source? Adobe I/O Events isn't available there; see the Magento page for the webhook bridge that works today.

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 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

COD Confirmation for Adobe Commerce: FAQ

Want COD confirmation calls on Adobe Commerce?

Request early access and tell us your Adobe Commerce version and order volume.

Request early access Back to overview