Shiprocket integration: order push, AWB, tracking and NDR

What the integration does

Shiprocket is a shipping aggregator: one account gives access to many courier companies, with one panel for labels, pickups, tracking and cash-on-delivery remittance. Its API exposes most of what the panel does.

An integration removes the copying. Without one, someone exports orders from the store, uploads them to Shiprocket, books pickups, and pastes tracking numbers back. With one, a paid order in your system becomes a shipment by itself, and the customer and your team see where it is without anyone opening the Shiprocket panel.

Data that flows each way

The main flow, step by step

1. Create an API user in the Shiprocket panel under Settings, then API. It needs an email address different from the account's main login.
2. Log in by API to get a bearer token, and send it in the Authorization header on every call.
3. Check serviceability for the delivery pincode. This step is optional in Shiprocket's lifecycle but is what lets checkout refuse an address no courier serves.
4. Create the order with the buyer's address, items, payment method, and package dimensions and weight. Your own order number goes in as order_id; the response returns Shiprocket's own order_id and a shipment_id. They are different numbers.
5. Assign a courier and generate the AWB for the shipment.
6. Generate the pickup, then the label, invoice and manifest.
7. Track. Tracking events arrive by webhook; the same data can be fetched by AWB.
8. Act on exceptions: NDRs, returns and cancellations.

Limits and rules Shiprocket documents

Two points follow from that table. The webhook is protected by a shared token, not a signature computed over the message, so the token has to be long, secret and checked on every request. And because the guides do not describe retries for a webhook your server missed, a scheduled tracking check is part of a sound build, not an extra.

Shiprocket's documentation also notes that its earlier Postman-hosted reference stays available until 30 November 2026. An integration written against old examples should be checked against the current guides.

Common failure modes

• Wrong weight or dimensions. Both are required when the order is created, and courier rates are quoted against them. Guessed values lead to disputes later; they should come from product data.
• Expired token. Everything works for ten days after launch, then every call fails. Token renewal has to be automatic.
• Mixed-up identifiers. Your order number, Shiprocket's order id, the shipment id and the AWB are four different values. Storing only one makes later calls impossible.
• An order pushed twice. A timeout followed by a retry can create a duplicate unless your code first checks whether the order already has a shipment id.
• COD offered where no courier serves it. The serviceability check was skipped at checkout.
• NDRs seen too late. Nobody looked at the panel over a weekend and the parcels came back. NDRs need to reach a person, with the customer's number, on the day they are raised.
• Status that never updates. The webhook URL contained a blocked word, or returned something other than 200.

Fees

As of October 2026, Shiprocket's pricing page lists four plans:

The shipment cost is an average that Shiprocket quotes for each plan; the charge for a real parcel is calculated per shipment. The page also describes plan-fee refunds at set monthly shipment counts. Read the page for the current terms before budgeting.

What WavX builds around it

For a client who needs shipping connected to a custom store, an ERP or an order system, WavX builds:

• Automatic order push once an order is paid or confirmed, with a guard against sending the same order twice.
• A serviceability check at checkout, including whether cash on delivery is available.
• Courier choice by your rules, using the couriers, ratings and rates the serviceability call returns.
• Storage of every identifier, label and manifest against the order.
• A tracking receiver plus a scheduled check, feeding the customer's order page and messages through WhatsApp, SMS or email.
• An NDR queue for your support team, with the action sent back to Shiprocket in time.
• Return booking from your admin panel, and a view of shipped, delivered and returned orders for reconciling COD remittance.

This sits inside e-commerce development. If the store is on Shopify, start with Shopify and Shiprocket. For the business side of failed deliveries, read how to reduce COD returns.

Pricing is quoted after scoping. The software cost estimator carries third-party integrations as a ₹60,000 feature line on top of a base build, as a planning figure.

When Shiprocket's own integration is enough

Shiprocket's features page describes ready channel integrations, more than twelve of them, covering Shopify, WooCommerce and marketplaces such as Amazon, which fetch orders and sync inventory automatically. If you sell on one of those and ship every order the same way, connect the channel in the Shiprocket panel and do not commission anything.

Custom integration is for the cases that leaves out: a custom-built store, an ERP that must hold the shipping record, courier rules of your own, or support staff who should handle NDRs without learning another panel.