Shipping & dispatch

Assigning couriers (AWB)

On the Ship tab, tick the orders and press Assign AWB. The system asks Shiprocket to allot a courier and airway bill to each order, one by one, in the background, at a pace the courier's systems accept.

You immediately land on a batch page that updates live:

• ✅ ok: AWB assigned (shown per order)
• ✕ failed: the courier's actual reason, and a Retry failed only button (you never resubmit the whole batch)
• ⚠ skipped: e.g. the order was cancelled after you selected it; the system re-checks right before acting, so a cancelled order can't ship

Batches are crash-proof: if the server restarts mid-batch (updates happen), it continues from where it stopped. Orders already done are never re-done.

When the batch finishes, the queue refreshes itself in the background, so orders that just received an AWB drop off the list without you pressing Reload. An order whose shipment already carries a live AWB is never offered for shipping again; if the courier's systems still list a stale copy of it, that copy is hidden and counted separately above the list.

The finished batch page carries the next step: a Schedule pickup button that acts on the batch's successful orders, so the flow continues from there without hunting the orders down again.

Per-order courier choice exists too; the order page shows which of your preferred couriers actually service that pincode, with rates and ETAs.

Labels

Labels come with the AWBs: when an assign batch finishes, the label PDFs are generated automatically (50 shipments per printable sheet) and attached to the same batch page. Each order's row says which PDF its label is in, and the PDFs stay on the page so you can reprint any time — the recent-batch pills on the Ship tab lead back to every batch.

If a label couldn't be generated, the batch page shows a Generate the missing labels button covering exactly those orders.

Pickup

Schedule pickup books the day's shipments into your Shiprocket pickup queue. "Already in the pickup queue" counts as success, so pressing it twice is safe.

The default package

Courier pricing and serviceability need a parcel size. During setup you enter your standard box (L×B×H cm + weight kg). When a product arrives without dimensions, the system uses your default and flags it on the needs-attention queue so you fix the product data at the source.

Dispatch close: the handover check

"Pickup scheduled" only means a request reached the courier. The dispatch close proves the handover:

1. When the van arrives, open Ship → Dispatch close.
2. Scan each parcel (AWB or order number) as it's loaded.
3. The screen reconciles live: expected (everything packed) vs scanned vs missing vs unexpected (a parcel that shouldn't be going: not packed, or already handed over; it can't inflate your count).
4. Close at zero discrepancy, or a manager closes with a reason (from your workspace's reason list if you've defined one in Settings → Operations policies, free text otherwise).
5. Download the manifest CSV (order, AWB, courier, time, scanner).

Next morning, anything packed-but-never-scanned is waiting on the needs-attention list, and so is anything scanned out that the courier still hasn't moved.

Tracking after pickup

Delivery statuses sync back from Shiprocket automatically (you set the interval). Delivered, in-transit, NDR and RTO states update on their own, feed the Returns/RTO/COD screens, and are searchable by AWB.