Skip to main content

Courier — Shiprocket

Decision: Shiprocket as the first courier partner (notes #6), integrated as a Medusa fulfillment provider. Shiprocket itself aggregates many Indian carriers (Delhivery, Blue Dart, DTDC, …), so one integration yields multi-courier rate-shopping.

Medusa fulfillment provider (custom)​

class ShiprocketFulfillmentProvider {
getFulfillmentOptions() // serviceability + carrier list
calculatePrice(option, data, ctx) // rate shopping by pincode/weight
createFulfillment(data, items, order)// create SR order + AWB
cancelFulfillment(fulfillment)
createReturn(returnOrder) // reverse pickup (RMA)
getFulfillmentDocuments() // label/manifest
}

Flow​

Capabilities mapped​

NeedShiprocket
Rate shoppingserviceability + rate API
AWB + labelcreate order/AWB, print
Pickup schedulingpickup API
Live trackingtracking API + webhooks
NDR / RTOwebhook events → ops workflow
COD reconciliationCOD remittance reports → Finance
Returns (RMA)reverse pickup

Heavy goods​

Large solar consignments may exceed parcel limits → LTL/freight path (separate provider, v2). Modeled as an alternate fulfillment option; flagged in Orders.

Webhooks​

Shiprocket → /v1/webhooks/shiprocket (verified) → shipment.updated / order.delivered → Medusa fulfillment state + downstream (FSM install job, Warranty eligibility).

Tenant config​

SHIPROCKET_EMAIL/SHIPROCKET_PASSWORD (secret) or token, pickup locations, COD toggle, weight/serviceability defaults.

Open questions​

  • Freight/LTL partner + phase for heavy solar.
  • Multi-pickup (per-warehouse) setup for the first tenant.