COD Confirmation & NDR Calling AI India: Cost

Dvaarik acts on four kinds of order event. Each one needs a connected store, and the three follow-up workflows stay off until you switch them on.

Shopify documents webhooks as event notifications and uses orders/create as its worked example, and Shiprocket defines an NDR as a shipment the courier could not deliver. Those official definitions explain the triggers; the Dvaarik behaviour in the table comes from the current product code. Setup guides: Shopify, WooCommerce and the custom store API.

A connected Shopify store signs every order event with its app's secret. Dvaarik verifies the signature, matches the order against your cash-on-delivery payment method and ignores prepaid orders, which get an "order confirmed" message instead. An order that arrives more than six hours after it was placed is ignored rather than treated as a new request. WooCommerce orders are matched on their cash-on-delivery payment method the same way, and a cancelled or refunded WooCommerce order stops the follow-up.

Duplicates are fenced twice. Shopify can retry a delivery with the same webhook ID, and a store can send the same order through two subscriptions; Dvaarik keeps each delivery once and one case per order, so a customer is never asked twice about one order.

The case then follows the strategy you chose: WhatsApp only, WhatsApp then a call, a call first, or manual review, after the delay you set. WhatsApp messages skip anyone who opted out of your messages. Calls wait for calling hours, skip your Do Not Contact list and go only to customers whose consent to be called is recorded.

Each new COD order also gets a risk level, low, medium or high, with up to three reasons, worked out only from your own business's recent orders in Dvaarik and the order itself: an earlier parcel to this number sent back, cancelled or failed orders, several COD orders from one number in a day, a weak address or an invalid PIN code. If you choose, a high-risk order waits for you instead of being messaged or called; it is not held in your store.

Once your COD confirmations workflow is on, the customer's answer is applied to the order itself:

• Shopify: a confirmation tags the order cod-confirmed and releases an optional "Waiting for COD confirmation" shipping hold; a cancellation cancels the order and restocks it without requesting a refund; a new address replaces the shipping address and is read back from Shopify. An order that shows a payment is never cancelled, and an address cannot change once shipping has started. The Shopify app needs the write_orders permission, and the hold needs the merchant-managed fulfilment-order permissions.
• WooCommerce: a confirmation adds a private order note and moves a pending or on-hold order to processing; a cancellation sets the order to cancelled and WooCommerce restores the stock, never for an order paid online; a new address is written to the order and read back. The store's REST API keys need Read/Write access.

• A custom-built store: each decision is sent as a signed action to the actions endpoint its developer exposes, and the store answers applied, rejected or pending. Without an actions endpoint, the decision is recorded for your team.
• Magento (early access): a confirmation becomes a private comment in the order's history with the order's status unchanged; a cancellation uses Magento's own Cancel, which returns the stock, never once anything is invoiced or shipped or for an order paid online; a new address is written with the store's own region and the recipient kept. The Magento connection has run end to end on one real Magento Open Source 2.4.9 store so far.

The customer is told the store will confirm, and the WhatsApp note that the change is done goes out only after the store shows it. A failed-delivery answer is applied automatically only if you switch on automatic reattempts or returns; otherwise it waits for your approval on the Failed deliveries page. A Shopify store can also offer "Pay online now": the confirmation message adds a button to Shopify's own payment page for the order, and an order paid before it ships closes as prepaid.

A failed delivery reaches Dvaarik in one of three ways: a Shopify fulfilment update that shows a failed attempt, Shiprocket's undelivered push, or your own software through the custom store API. For Shiprocket, Dvaarik trusts the push only for the tracking number: the buyer's phone and the order come from Shiprocket's own API on your Shiprocket API user, so a forged push cannot make Dvaarik contact a number of its choosing. The Shiprocket connection is set up with the Dvaarik team.

Each failed delivery opens one case, so repeated courier scans of the same parcel do not repeat the conversation. The customer answers Deliver again, New address or Return order. For a parcel Shopify fulfilled, the answer is added to the Shopify order as a tag with a note for your shipping team, because Shopify has no courier controls of its own.

Requests to Shiprocket are not sent automatically. Shiprocket's NDR processing guide has the seller submit the reattempt, corrected address or RTO choice in its panel, and that step stays with your team.

Shopify does not publish an abandoned-checkout event. Dvaarik starts from checkout create and update events that carry a phone number, waits for the delay you choose (1 to 48 hours), and refreshes the same checkout instead of opening another case. By default only shoppers who agreed to receive messages get a reminder.

Immediately before sending, Dvaarik asks Shopify whether the checkout became an order. A completed purchase closes the reminder; if Shopify cannot answer, Dvaarik retries a few times and then stops rather than message a buyer who may have paid. The reminder is a WhatsApp marketing template with the cart's photo, a Complete checkout button and a Stop promotions button, and you can follow it with a call. WooCommerce's order webhooks do not describe an unfinished cart, so a WooCommerce store sends checkout events through the custom store API.

Dvaarik charges ₹0.50 for each call minute, in 30-second steps of ₹0.25, and ₹0.05 for each successful AI reply. A WhatsApp confirmation, failed-delivery or shipping message is a template that Meta bills to your own WhatsApp Business account; Dvaarik adds no charge to it, and a customer tapping a button is not an AI reply. Language coverage on calls follows the speech models you connect, so check the rate card of the speech model that covers your buyers' languages.

The table is scenario arithmetic, not a measured customer result: replace the counts and durations with your own. A 40-second call is charged as two 30-second steps, ₹0.50. Meta's message charges, your phone company's charges and your speech and AI providers' charges are separate from this table of Dvaarik charges; the pricing page is the current public direct-rate reference.

Most of the setup is self-serve:

1. Sign up as a D2C brand and connect the store on the Top Products page: for Shopify, a custom app's Client ID and Client secret with the read_products, read_orders, read_customers, read_fulfillments and write_orders permissions (plus the merchant-managed fulfilment-order permissions if you want shipping held until the customer confirms); for WooCommerce, REST API keys with Read/Write access; for Magento, an integration's access token.
2. For Shopify, add the connection URL from your dashboard to the store's webhooks; events are verified with your app's secret. For WooCommerce, pressing Test with Read/Write keys creates the order webhooks; with a Read-only key the Dvaarik team sets them up. Magento needs no webhook: new orders are read from the store. The Shiprocket connection is set up with the Dvaarik team.
3. Connect your own WhatsApp Business number. The order message templates need Meta's approval in each language you use: English, Hindi or Telugu.
4. For calls, connect your phone company account with a working number and your speech and AI accounts, keep credits in your wallet, and make sure the customers you call have recorded consent.
5. On the COD confirmations, Failed deliveries and Cart recovery pages, choose the contact strategy, delays and attempts, and switch each workflow on.
6. Place a test order with your own number before any customer sees a message.

Magento connects in early access (Magento integration). BigCommerce and other platforms are not connected directly; a custom-built store can send the same events, and carry out the decisions, through the custom store API.

Do not use an order-support workflow as permission to contact an unrelated list. These workflows act on the merchant's own order, checkout or delivery events; bought, rented or scraped lists do not belong in them.

TRAI's current UCC definition excludes transactional and service voice calls, while still placing commercial communications inside a registered-sender and access-provider framework. The exact classification depends on the call's purpose and content. A COD or delivery-problem call should stay limited to that order. An unfinished-checkout reminder is promotional: Dvaarik sends it as a WhatsApp marketing template with a Stop promotions button, by default only to shoppers who agreed to receive messages, and a reminder call needs the merchant's own compliance review.

The primary regulatory reference is TRAI's 2025 amendment to the Telecom Commercial Communications Customer Preference Regulations. This page describes product controls, not legal advice.