Loading…
A single manifest API to access multiple India-domestic couriers, pincode-aware per-order allocation, and a predictable weekly COD remittance cycle — for merchants who ship anywhere from 1 to 10,000 orders a day.
A courier aggregator is a shipping platform that connects a merchant's ecommerce operations to multiple courier partners through a single manifest API, dashboard and reconciliation flow. Instead of maintaining a direct commercial relationship, integration and reconciliation with each of Blue Dart, Delhivery, Xpressbees, Ecom Express, Ekart and other Indian couriers separately, the merchant works with one platform that handles the multi-courier layer. The category has matured significantly in the last decade. Aggregators today are less about pure "rate arbitrage" between couriers and more about the operational layer on top — how allocation is done, how COD money flows back to the merchant, and how weight disputes are handled. These operational choices, more than headline per-kg rate cards, tend to shape a merchant's actual cost-per-delivered-order. Based on how the aggregator category operates in the Indian domestic parcel market, current at the time of review (see footer for review date).
• Order manifest and AWB generation across multiple couriers from one panel • Per-order courier selection — merchant-driven, rule-based or AI-driven • Pickup scheduling with the selected carrier • Tracking, NDR (non-delivery report) handling and RTO (return-to-origin) processing • COD collection, reconciliation and remittance to the merchant • Weight-discrepancy workflow — the recurring friction point in Indian shipping economics • Integration with ecommerce storefronts (Shopify, WooCommerce, Magento and similar)
Four-step flow: the merchant hands the order to the aggregator, the aggregator picks the best-fit courier from its integrated set, the courier delivers to the customer, and delivery status + COD flow back through the aggregator to the merchant.
Delivery success varies significantly between metro and Tier-3 pincodes. A single blanket courier default that performs well in Bengaluru may consistently under-deliver in remote UP or Bihar pincodes — driving up RTO on the geographies where D2C order growth is now concentrated.
Cash-on-delivery still accounts for a large share of Indian ecommerce orders. That means working capital is tied up until the courier remits the collection — the cadence and reliability of remittance directly affects the merchant's finance planning.
Almost every domestic courier reserves the right to re-weigh a shipment in transit. Deductions on volumetric or dead-weight discrepancies are a recurring friction point, and without an AWB-level evidence trail these deductions are difficult to contest.
Delivery re-attempt patterns differ by courier, category and geography. Merchants that route everything through one default courier lose optionality when that courier's re-attempt flow is weak in a specific pincode.
Indian merchants sell across Shopify, WooCommerce, Magento, marketplaces and custom stacks. A shipping platform needs to plug into all of these without a bespoke integration project for each.
Public per-kg rate cards are almost never what the merchant will actually be billed once category, volume, zone mix, COD share and surcharges are factored in. Comparing aggregators on advertised rates alone is rarely useful.
A merchant shipping 500+ orders/day cannot resolve a shipment cluster failure through a chatbot funnel. Access to a real person on WhatsApp, email or phone becomes a leading indicator of platform reliability.
How many actively integrated couriers are on the platform, and what categories (documents, parcels, heavy, reverse, cross-border) they cover. Depth matters more than raw carrier count if you ship a category-heavy mix.
Rule-based (merchant-configured), pincode-history-based, or AI-driven. Tighter allocation to the destination pincode's real courier performance lowers the RTO tail in Tier-2/3 markets.
COD dominates Indian ecommerce. How predictable is the cash cadence, and how visible are the reasons when an amount is held rather than remitted?
How quickly are disputes surfaced (same-week vs. bulk-invoice), where is the AWB-level evidence trail, and what is the accepted-vs-rejected rate?
A named merchant success contact — reachable on WhatsApp, email or phone — is a leading indicator of whether the platform can respond when a shipment cluster goes wrong.
Is the standard onboarding path available for merchants shipping single-digit orders per day, or is core capability gated behind an enterprise plan tier?
Shopify, WooCommerce, Magento and marketplace integrations should be first-class. Custom-API integration should exist for teams that need it, but not be the only path.
Based on publicly available information from each provider's official website and public documentation, current at the time of review (see the footer for the exact review date). Several fields on other providers' sides vary by plan tier and commercial agreement — merchants should verify their own plan-specific terms directly.
| Evaluation dimension | ShipyBox | Shiprocket (per public docs) | NimbusPost (per public docs) | iThink Logistics (per public docs) |
|---|---|---|---|---|
| Active domestic carriers on platform | Multiple India-domestic carriers + growing set | 25+ carriers (publicly claimed) | Multiple carriers (publicly claimed) | Multiple carriers (publicly claimed) |
| Minimum monthly volume on standard path | No minimum | Plan-tier dependent | Plan-tier dependent | Plan-tier dependent |
| COD remittance cadence | Weekly cycle every Saturday for most undisputed shipments | Cadence varies by plan (D+2 advertised on select plans) | Cadence advertised across plans | Cadence advertised across plans |
| Per-order allocation model | Pincode + category-aware, AWB-level | Rule-based (advertised across plans) | Rule-based (advertised across plans) | Rule-based (advertised across plans) |
| Weight-dispute workflow | Same-week AWB-level dispute raising, evidence surfaced per AWB | Available; workflow varies by plan | Available; workflow varies by plan | Available; workflow varies by plan |
| Support model | Named merchant success contact across account sizes | Dedicated support advertised on higher plan tiers | Dedicated support advertised on higher plan tiers | Dedicated support advertised on higher plan tiers |
| API for integrations | Yes | Yes | Yes | Yes |
| Ecommerce integrations | Shopify, WooCommerce, Magento, and more | Shopify, WooCommerce, Magento, Wix, BigCommerce, custom | Shopify, WooCommerce, Magento, custom | Shopify, WooCommerce, Magento, custom |
| International shipping | Not offered on primary plan | ShiprocketX cross-border product | Available | Available |
| Fulfillment / warehousing | Not offered | Yes — Shiprocket Fulfillment | Not offered as a bundled product | Not offered as a bundled product |
| Checkout product | Not offered | Yes — Shiprocket Checkout | Not offered | Not offered |
Multi-carrier routing, AWB-level weight reconciliation and dedicated merchant success contact are part of the standard onboarding, not enterprise-only unlocks.
Weight-discrepancy deductions and COD holds are surfaced per-AWB in the dashboard, not delivered as bulk end-of-month adjustments.
A fixed weekly settlement date is easier for finance teams to plan against than a variable D+5-to-D+9 window; hold reasons are shown per shipment.
Discrepancies are cross-checked against the manifested LBH and raised with the courier the same week they are scanned, subject to each carrier's dispute-resolution process.
Each order is scored against candidate couriers using pincode delivery history, SLA, cost, COD acceptance and category — reducing reliance on a single blanket default that under-performs in Tier-2/3 markets.
Coverage, product policies and merchant success practices are designed around Indian logistics operating conditions rather than adapted from a global template.
The standard onboarding supports merchants shipping single-digit orders per day, without a minimum monthly commitment on the standard path.
• 10 to 10,000 orders a day across D2C, small B2B or hybrid commerce • COD-heavy order mix (35%+ COD share) that would benefit from predictable weekly settlement • Multiple pincode geographies — including Tier-2 and Tier-3 — where per-order carrier allocation matters more than a single blanket default • A finance team that values planning predictability over marketing "D+1 by default" claims • A support expectation of talking to a real person when something goes wrong
• Merchants who need integrated fulfillment warehousing as part of the same contract • Merchants who need an integrated checkout product on their storefront • Merchants who need an owned international cross-border network as part of the primary plan — ShipyBox does not currently offer this • Very-large-enterprise buyers who prefer an incumbent single-vendor stack across shipping + fulfillment + checkout Being clear about these limits saves everyone a wasted evaluation call.
Ships to metros + Tier-2 pincodes, ~45% COD, mostly apparel and lifestyle SKUs. Previously used a single-carrier default which under-performed in Tier-2 UP and Bihar pincodes with elevated RTO. Moves to ShipyBox to score orders across multiple carriers per destination pincode and to move from an unpredictable COD cadence to a weekly Saturday settlement.
Higher-value SKUs with tight margin per shipment. Historical friction has been weight-discrepancy deductions arriving in a bulk invoice weeks later, with no per-AWB evidence trail. Moves to ShipyBox for the same-week AWB-level dispute workflow and dashboard-visible deductions.
Ships to 12,000+ pincodes including remote Tier-3 destinations where courier coverage varies. Wants an allocation engine that uses actual delivery history in that pincode rather than a single blanket default. Adopts ShipyBox for per-order pincode-aware allocation and a named merchant success contact on WhatsApp.
How AWB-level carrier allocation works on ShipyBox.
FeatureEvidence trail, same-week disputes and dashboard visibility.
GlossaryHow COD flows and remittance cycles work in India.
LandingCompetitor-specific comparison for merchants evaluating Shiprocket.
GuideEvaluation framework beyond rate cards.
Register free or talk to our team for a personalised quote — no minimum monthly commitment on the standard onboarding path.
How we compare: The information on this page about other courier aggregators is based on publicly available information from each provider's official website, press releases and public documentation, current at the time of review shown below. Product details, pricing models and network coverage change over time — merchants evaluating providers should verify current specifics directly with each vendor. ShipyBox does not represent the operational details of any competitor beyond what those competitors themselves have publicly disclosed. This page is reviewed on a 90-day cadence.
Published: 2026-07-28 · Last reviewed: 2026-07-28