BigCommerce has no order tags. How is confirmation recorded?

By order status plus a staff note. You choose the status for confirmed orders, for example Awaiting Fulfillment.

My store uses custom order statuses. Will that work?

Yes, that's the plan. Status ids are configured per store rather than fixed, so you map your own statuses.

How do you know the webhook really came from my store?

BigCommerce doesn't sign webhooks, so we set a secret header when the webhook is created and reject any request without it. We also fetch the order from your store's API rather than trusting the webhook body.

Can I use it today some other way?

If you can send a signed webhook from your own code or an automation tool, the custom store API works today and posts confirm or cancel back to a URL you choose.

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 BigCommerce

Q: Is the BigCommerce integration available now?

Not yet. The integration is designed and planned. Request early access and tell us your order volume; stores that ask first help decide what we build next.

The BigCommerce integration is designed but 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 the order moves to the status you choose with a staff note. Request early access to be in the first group.

Request early access

See what changes in BigCommerce

How it will work on BigCommerce

Planned design, based on BigCommerce's order webhooks and API

Connect your BigCommerce store

An API account token with order access, and an order webhook that carries a secret header we generate.

Map your order statuses

Pick the status for confirmed orders, such as Awaiting Fulfillment. Status ids are set per store, never hard-coded.

Customers get called

Hindi or English, inside your calling hours. Press 1 to confirm, 2 to cancel.

BigCommerce order updated

Confirmed orders move to your chosen status with a staff note; cancelled orders move to Cancelled.

What will change in your BigCommerce admin

BigCommerce confirms orders by status, not tags. You choose which status each outcome uses.

Confirmed: status you choose

For example Awaiting Fulfillment, plus a staff note saying the customer confirmed on the call.

Cancelled: Cancelled status

When the customer presses 2, the order status is set to Cancelled.

Unreachable: staff note

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

Already cancelled: no call

An order moved to Cancelled before we call is skipped.

What a BigCommerce store will need

An API account with access to orders. Its access token is encrypted on our side and only sent to your store's API.
Order webhooks for order creation and status changes. BigCommerce doesn't sign webhooks, so we add a secret header when the webhook is created and check it on every delivery.
Your status choices. Status ids can differ between stores, so you tell us which status means "confirmed" for your workflow.

Why we fetch every order

BigCommerce webhooks carry only the order id, not the order itself. For each event we fetch the order and its shipping address from your store to get the customer's name, phone number and amount before calling. A cancellation is detected when an order's status changes to Cancelled.

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

Want COD confirmation calls on BigCommerce?

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

Request early access Back to overview