Shiprocket API integration for order and warehouse management

Shiprocket integration: in production use.

Keep Shiprocket for courier allocation, and run order, stock and warehouse work on Fretron CommerceOS. The integration books Shiprocket shipments, cancels them, raises the manifest and pickup, polls tracking back onto the order, and maps your pickup points. CommerceOS doesn't fetch Shiprocket rate quotes, so courier choice stays with Shiprocket.

Book a demo →

Two tools, two jobs

Shiprocket is a courier aggregator. Its plans page lists 42+ courier partners, automated tracking, a rate calculator, multiple pickup locations and COD reconciliation in every plan (Shiprocket pricing page, Nov 2026). CommerceOS doesn't try to replace any of that. Its job is upstream: pulling orders from your channels, holding one stock record, and running pick, pack and dispatch in the warehouse. The integration joins the two at the moment a packed order needs an AWB.

What Shiprocket's API guide covers, and what comes before it

The Shiprocket API lets a store or order system use most of the features in a Shiprocket account's panel (Shiprocket developers page, Nov 2026). Its step-by-step guide covers the shipping calls: authenticate, check which couriers can serve the order and at what charge, create the order, assign the AWB, request pickup, generate the manifest, label and invoice, then track by AWB (Shiprocket API helpsheet, Nov 2026).

What comes before that call sequence isn't in it: allocating the order to a warehouse, holding the stock record your channels sell from, and picking and packing the parcel. That's the order and warehouse side. With Fretron CommerceOS, that work runs first, and a packed order is booked with Shiprocket, with the AWB returned to the order.

What the Shiprocket API sync covers

Shiprocket's own API guide lays out the order of calls: authenticate, check courier serviceability, create the order, assign the AWB, generate the pickup, generate and print the manifest, generate the label, print the invoice and track by AWB (Shiprocket API helpsheet, Nov 2026). CommerceOS uses the parts of that sequence that move a packed parcel out of the door:

OperationIn CommerceOS
BookingA packed order is booked with Shiprocket and the AWB returns to the order
CancelA booking can be cancelled from the order before pickup
Manifest and pickupThe manifest and pickup request are raised for the day's bookings
TrackingShipment status is polled back onto the order
Pickup pointsEach warehouse maps to a Shiprocket pickup location
LookupAn existing Shiprocket shipment can be looked up from CommerceOS

Not covered: rate quotes. Shiprocket's serviceability call returns couriers with their shipping charge (Shiprocket API helpsheet, Nov 2026), but CommerceOS doesn't read or compare those rates.

Shiprocket, your Shopify store and a warehouse system: who does what

SystemIts job in the flow
Your Shopify storeTakes the order and the payment, and shows shoppers the stock it is given
Fretron CommerceOSPulls the order in, reserves stock against it, runs pick and pack, books the shipment with Shiprocket, and publishes stock back to your Shopify store automatically
ShiprocketAssigns the courier and AWB, takes the pickup request and manifest, and returns tracking, which CommerceOS polls back onto the order

Shiprocket also offers its own channel integrations for connecting a store or order system (Shiprocket developers page, Nov 2026). If you connect your Shopify store to Shiprocket directly as well, decide which system creates each Shiprocket order, so that no order is booked twice. For the broader comparison, see Shiprocket vs an OMS/WMS. To choose which warehouse ships each order, see Order allocation: which warehouse ships each online order.

Worked example: one Shopify order, end to end

A skincare brand gets an order on its Shopify store at 11:40 am for two serums and a cleanser, ₹1,249, prepaid. Illustrative numbers.

  1. Order in. The Shopify order is pulled into CommerceOS automatically.
  2. Allocate. Stock is reserved at the Pune warehouse, the location that holds all three SKUs.
  3. Pick. The picker scans the bin, then each item, on a phone. Labels print from the web, not the phone.
  4. Pack. The parcel is packed and checked at the pack bench.
  5. AWB. CommerceOS books the shipment with Shiprocket, and Shiprocket assigns the courier and AWB, which come back onto the order.
  6. Manifest and pickup. At 4 pm the day's 136 bookings from Pune go into one manifest and pickup request.
  7. Tracking. "In transit", "out for delivery" and "delivered" are polled onto the same order over the next two days.

Nobody re-keys the order into the Shiprocket panel, and the stock published to Shopify comes from the same record the picker worked from.

Setup prerequisites

  • A Shiprocket account with an API user. Shiprocket creates API users under Settings → API → Configure → Create an API User, with an email that is different from your main login; up to 4 API users are allowed (Shiprocket support article, Nov 2026).
  • Shiprocket's auth token is valid for 240 hours (10 days) and has to be regenerated after that (Shiprocket API helpsheet, Nov 2026). You add the Shiprocket API user to CommerceOS once, during setup.
  • Pickup locations created in Shiprocket for each warehouse.

Before go-live: a five-point check

  1. A separate API user. Shiprocket requires an API user email that differs from your main login, and allows up to 4 API users (How to create an API user, Nov 2026). Keep one for CommerceOS so you can tell its calls apart.
  2. Pickup locations named once. Each warehouse in CommerceOS maps to one Shiprocket pickup location. A misspelt or duplicate location is the most common reason a booking carries the wrong pickup address.
  3. Courier rules in Shiprocket. Courier choice stays in Shiprocket, so set your allocation preferences there before the first booking.
  4. One test order. Book, cancel and re-book one real order before you move the day's volume, and check that the AWB and tracking appear on the order.
  5. API user added once. Shiprocket's token lasts 240 hours (Shiprocket API document helpsheet, Nov 2026); add the API user to CommerceOS during setup rather than pasting a token.

Frequently asked questions

What is the Shiprocket API?
The Shiprocket API is Shiprocket's developer interface for using most of a Shiprocket account's panel features from your own store or order system. Its documented sequence covers authentication, courier serviceability, order creation, AWB assignment, pickup, manifest, label, invoice and tracking by AWB. You create a separate API user in Settings → API, and its auth token is valid for 240 hours (Shiprocket developers page and API helpsheet, Nov 2026).
Does Fretron work with Shiprocket?
Yes. Shiprocket is in production use with CommerceOS for booking, cancellation, manifest and pickup, tracking and pickup points.
What does the Shiprocket API sync?
From CommerceOS: bookings and AWBs, cancellations, manifest and pickup requests, polled tracking statuses, pickup locations and shipment lookup.
Can I use Shiprocket with my own warehouse system?
Yes. Shiprocket's API is meant for this: it lets developers and sellers connect their store or OMS to most panel features (Shiprocket developers page, Nov 2026). With CommerceOS, the warehouse work happens first and Shiprocket takes over at the AWB.
Does Fretron compare courier rates?
No. CommerceOS doesn't do rate shopping or read Shiprocket's rate quotes. Shiprocket's own allocation picks the courier.
Do I need an OMS if I use Shiprocket?
It depends on where the work before shipping happens. Shiprocket's API guide covers the shipping calls, from courier serviceability to tracking by AWB (Shiprocket API helpsheet, Nov 2026). If you sell on more than one channel or ship from your own warehouse, an order and warehouse system holds the stock record, reserves stock for each order and runs pick and pack before Shiprocket assigns the courier. Fretron CommerceOS does that work and books the packed order with Shiprocket.
Can Fretron CommerceOS book Shiprocket shipments for packed orders?
Yes. A packed order is booked with Shiprocket from CommerceOS, and the AWB comes back onto the order. The day's bookings then go into one manifest and pickup request, and tracking is polled back onto the same order.
Does the Shiprocket integration need Shiprocket API credentials?
Yes. Create a Shiprocket API user under Settings → API → Configure, with an email that is different from your main login (Shiprocket API helpsheet, Nov 2026). You add the Shiprocket API user to CommerceOS once, during setup.

Sources

Partner and marketplace details were read on their own pages on 5 Nov 2026. Check them before you rely on them.

Keep Shiprocket. Fix the warehouse before it.

We'll show a live order going from Shopify to a Shiprocket AWB.

Book a demo →