NimbusPost & iThink WhatsApp Order Updates (2026 Guide)

NimbusPost and iThink Logistics both list buyer shipment updates on their sites. According to NimbusPost's site, it offers WhatsApp tracking updates and WhatsApp buyer notifications, and according to iThink Logistics' site, it offers real-time WhatsApp and SMS updates. If you want order, NDR and COD-confirmation messages that come from your brand's own verified number, with templates you control and replies that reach your team, connect the aggregator's API or export to a middleware tool. That tool then sends Meta-approved utility templates through a WhatsApp Business API provider such as RichAutomate.

This guide is for Indian D2C, Shopify and WooCommerce sellers who ship through an aggregator dashboard instead of a single courier contract. It covers what each aggregator says it does for buyer communication, which shipment events are worth a WhatsApp message, how to wire it all up without a native connector, and what it costs. Every vendor feature below comes from the vendor's own website. Where we could not confirm something there, we say so instead of guessing.

Why aggregator sellers need a WhatsApp layer of their own

Shipping aggregators solve the courier problem. One dashboard and one wallet give you several courier partners with automatic allocation, and you no longer have to negotiate with each courier separately. What an aggregator does not fully solve is the conversation with your buyer. That conversation decides whether a COD parcel is accepted or comes back as RTO.

For most Indian D2C brands, cash on delivery is still a large share of orders, and every returned COD parcel costs you twice. You pay forward shipping and return shipping, and the stock sits in transit for days instead of being sold again. Most RTOs start with a quiet failure: the buyer was not home, the phone was switched off, the address was incomplete, or the buyer changed their mind and nobody asked them before dispatch.

WhatsApp is where Indian buyers actually read messages, so it is the cheapest place to catch these failures early. A good WhatsApp layer lets you:

• Confirm COD orders before you ship, so fake or impulse orders never reach the courier.
• Warn buyers when a parcel is out for delivery, so they keep cash ready and stay reachable.
• Recover failed deliveries with a simple "reschedule or update address" reply after an NDR.
• Close the loop after delivery with a thank-you, care instructions or a review request.

The aggregator's own notifications may cover some of this. The question is whether those messages carry your brand, use your wording and send replies back to a team inbox you control. If you have read our WhatsApp COD confirmation and RTO reduction guide, this post applies the same ideas to sellers who work through NimbusPost or iThink.

What NimbusPost says it offers

NimbusPost presents itself as a multi-courier shipping platform for Indian eCommerce sellers. Here is what its homepage says, in its own words where possible:

• Courier aggregation: according to NimbusPost's site, it is "Managing 25+ eCommerce Couriers So You Don't Have To," with multi-courier shipping and smart courier allocation that it says can "allocate the best-performing courier using AI."
• Buyer notifications: NimbusPost's site lists "WhatsApp tracking updates" and "WhatsApp Buyer Notifications," and its feature list includes "Email & SMS Notifications."
• NDR and calls: the site lists NDR management with "post-NDR IVR follow ups," and mentions "free IVR calls" to confirm COD orders and recover abandoned carts.
• Tracking page: NimbusPost offers a "Branded Tracking Page" with your logo, header and banners, which its site says comes "at no extra cost."
• RTO and COD: the site names an "RTO Suite" and offers "Early COD Remittance," but the homepage does not detail the RTO Suite's features or state a remittance timeline.
• Integrations: NimbusPost mentions "API Integration" and "Custom Integrations."

What we could not confirm on NimbusPost's public pages: whether it pushes shipment-status webhooks to your own server, the exact wording or sender of its WhatsApp notifications, and whether those messages can come from your brand's own WhatsApp number. Ask your NimbusPost account manager before you design a workflow around any of these.

What iThink Logistics says it offers

iThink Logistics also positions itself as a single shipping platform covering several courier partners. According to iThink Logistics' site:

• Courier aggregation: sellers can "Sell, ship, and track with ease by choosing multiple courier partners through one single shipping platform." The site claims delivery to "more than 29,000 serviceable pin codes in India" and international shipping to 180 countries. It does not state a courier count on its homepage.
• Buyer notifications: iThink Logistics' site promises "real-time WhatsApp and SMS updates."
• NDR: the site says its "AI-driven NDR shipping platform will also take care of every non-delivery and resolve issues within 24 hours," and refers to an "NDR 6 step plan."
• RTO reduction: it lists a "Recommendation engine to reduce RTO" and an "auto reattempt feature" that it says "reduces the chances of a return."
• Tracking page: the site lists "white-label tracking" without describing it further.
• COD remittance: iThink Logistics' site mentions "weekly and Next day COD remittances."
• API: sellers can "Connect your website with iThink API," and the site mentions a "single rest API" for omnichannel sellers.

What we could not confirm on iThink Logistics' public pages: public webhook documentation for tracking-status changes, and whether its WhatsApp updates can go out from the seller's own number. Third-party guides suggest the API documentation is available inside the seller dashboard, so check there or ask iThink support directly.

NimbusPost vs iThink Logistics: buyer-communication features at a glance

This table only shows what each vendor says on its own website. "Not stated" means we did not find the feature on the vendor's public pages, not that it does not exist.

Both aggregators cover the basics of telling a buyer where the parcel is. Neither one publicly says it will send those messages from your brand's own verified WhatsApp number, with your own approved templates and replies landing in your team inbox. That gap is why many sellers add their own WhatsApp Business API number on top. The same pattern applies if you ship directly with couriers, as our guides to Shiprocket WhatsApp order tracking and Delhivery WhatsApp integration explain.

Which shipment events to map to which WhatsApp template

Do not send a WhatsApp message for every scan. Buyers get tired of "in transit" pings, and every extra message costs money and wears down your number's quality rating. Pick the moments where a message changes what the buyer does. The table below is a practical starting map. Event names vary between aggregators and couriers, so match them to the status labels your NimbusPost or iThink account actually returns.

Three points matter here. First, the NDR message is the one that pays for itself. A buyer who taps "Reschedule" and gives a working landmark is a parcel you do not lose to RTO. Second, Meta decides the final category when it reviews a template. Keep transactional templates factual, because a promotional line in a shipping update can get the template classified as marketing. Third, review and reorder requests are often treated as marketing, so budget for the higher rate and send them only to buyers who opted in.

For more wording ideas and timing rules, see our guide to WhatsApp order status tracking automation.

How to connect NimbusPost or iThink to RichAutomate (the honest route)

To be clear: RichAutomate has no native NimbusPost or iThink Logistics connector today, and neither does it offer a one-click integration in either direction. The route that works is the same one sellers use with most Indian aggregators:

1. Order confirmation from your store. RichAutomate connects natively to Shopify and WooCommerce store webhooks, so the "order placed" and COD-confirmation step can fire as soon as an order is created, before it reaches the aggregator.
2. Get shipment status out of the aggregator. Use what your account provides. That can be a status webhook if your account manager enables one, a scheduled call to the tracking API using each AWB, or a periodic CSV export of shipments and NDRs from the dashboard.
3. Pass it through middleware. A no-code tool such as Zapier, Pabbly Connect or Make can receive the webhook, poll the API on a schedule or watch a Google Sheet where you paste the export. It then reshapes each status change into a message request. If you have a developer, a small script on a cron job does the same thing.
4. Send through RichAutomate's public developer API. The middleware calls the API with the buyer's number, the approved template name and its variables, such as name, order ID, amount, courier and tracking link.
5. Handle replies in the team inbox. When a buyer taps "Reschedule" or types a new landmark, the reply lands in RichAutomate's shared inbox or starts a chatbot flow that collects the new date. Your ops team then updates the NDR action in the aggregator dashboard.

The weak point is the write-back. Unless your aggregator lets you submit NDR actions by API, somebody still has to enter the buyer's reschedule request in the NimbusPost or iThink panel. For most sellers that is acceptable, because the expensive part is reaching the buyer and getting an answer, and that part is automated.

A few build tips:

• Deduplicate by AWB and status. Polling can see the same status twice. Store the last status sent for each AWB and skip repeats.
• Respect quiet hours. Queue non-urgent updates overnight and send them in the morning. Out-for-delivery and NDR messages are the exceptions.
• Normalise phone numbers. Store numbers with the 91 country code and strip spaces, or sends will fail.

An NDR and RTO playbook for COD sellers

Tools only help if the sequence around them is sensible. This simple playbook works for most COD-heavy catalogues:

1. Confirm before dispatch. Send the COD confirmation template within minutes of the order. Ship only confirmed orders right away. Give unconfirmed orders a reminder a few hours later, and hold or cancel them according to your own policy.
2. Offer a prepaid switch. In the confirmation flow, offer a payment link for buyers who would rather pay now. Every COD order that becomes prepaid is one fewer cash-collection risk.
3. Warn on out-for-delivery. Tell the buyer the amount to keep ready and ask them to reply if they will not be available. That reply lets you act before the courier marks an NDR.
4. Act on every NDR the same day. Send the reschedule template as soon as the NDR appears, collect a date or a corrected address, and enter it in the aggregator's NDR panel. Leave the aggregator's own IVR or auto-reattempt running alongside.
5. Escalate before RTO. After a second failed attempt, send one clear last-chance message, and have a person call high-value orders.
6. Learn from the data. Tag every RTO with its reason, such as unreachable, refused, wrong address or fake order. Then tighten your COD rules for repeat offenders and risky pin codes.

None of this guarantees a specific RTO rate, and you should be wary of any vendor that promises one. What it does is turn silent failures into conversations, and conversations are where parcels get saved.

What it costs: RichAutomate plans and Meta charges

RichAutomate uses Client Pay billing for this setup. You add your own payment method to your WhatsApp Business Account, and Meta bills its per-message charges to you directly. RichAutomate adds a flat platform fee of ₹0.10 per message. You get two invoices, one from Meta and one from RichAutomate, at the lowest unit cost.

Plan prices are in INR and include GST, with ₹0 setup and a 7-day free trial. Meta's rates above are approximate and can change. Always check Meta's official WhatsApp Business pricing page for current India rates and for the rules on messages inside the 24-hour customer service window. Current figures are on our WhatsApp Business API pricing page.

Here is a worked example. A brand shipping 3,000 orders a month sends about four utility messages per order: COD confirmation, shipped, out for delivery and delivered. That is roughly 12,000 messages. The bill comes to about ₹1,200 in RichAutomate platform fees, roughly ₹1,440 to Meta at the approximate utility rate, and ₹899 for the Pro plan. The total is about ₹3,539 a month, or around ₹1.18 per order. Saving even a handful of COD parcels from RTO usually covers that, because each returned parcel costs two-way shipping and blocked stock. NDR messages only go to the small share of orders that fail, so they add little.

If you are still choosing a provider, our comparison of the best WhatsApp API for logistics in India covers what to look for beyond price.

Bottom line

According to NimbusPost's site, it already offers WhatsApp tracking updates, NDR management with IVR follow-ups and a branded tracking page. According to iThink Logistics' site, it offers real-time WhatsApp and SMS updates, AI-driven NDR handling and an RTO recommendation engine. Both are solid foundations. When you want COD confirmations, NDR recovery and delivery updates sent from your own verified number, with your own templates and a team inbox for replies, the dependable path runs from the aggregator's API, webhook or export, through middleware, to an official WhatsApp Business API provider.

Ready to cut RTOs with COD confirmations and NDR reschedule messages on your own WhatsApp number? Start your 14-day RichAutomate free trial, connect your number with ₹0 setup, and send your first approved order-update template this week.