Planned: integration not built yet

COD Order Confirmation Calls for Shopline

The Shopline 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 the answer is saved on the Shopline order, with cancelled orders cancelled through Shopline's API. Request early access to be in the first group.

How it will work on Shopline

Planned design, based on Shopline's order webhooks and Open API

Connect your Shopline store
An app access token for your store and an order webhook, signed by Shopline and checked on our side.
Choose your calling rules
Calling hours in IST, delay after the order, retries, and which orders to call.
Customers get called
Hindi or English. Press 1 to confirm, 2 to cancel.
Shopline order updated
The confirmation is saved on the order; cancelled orders are cancelled through Shopline's order cancel API.

What will change in your Shopline admin

Cancellation uses Shopline's own order cancel. Exactly how confirmation is shown on the order will be fixed when the integration is built.

Confirmed: recorded on the order

Saved on the order through Shopline's order update, as a tag or note. We'll confirm which while building the integration.

Cancelled: order cancelled

When the customer presses 2, the order is cancelled through Shopline's order cancel API.

Unreachable: flagged

After the last retry, the order is flagged for your team in the same way as confirmed orders.

Already handled: no call

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

What a Shopline store will need

  • An app access token for your store, encrypted on our side and only sent to Shopline's API for your store.
  • An order webhook for new orders. Shopline signs webhooks with HMAC-SHA256, and we verify every delivery and ignore duplicates.

Still being verified

A few Shopline details still need checking against a live store before we build: whether Shopline sends a separate cancellation event (if not, we'll watch order updates), how COD orders are identified, and whether confirmation is best saved as a tag or a note. We won't promise these until they're tested.

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

Want COD confirmation calls on Shopline?

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