How to Evaluate a Courier Partner: A Framework for D2C Brands

Choosing a courier partner is one of the higher-stakes operational decisions a D2C brand makes — but most evaluations stop at "what's the rate?" That single question misses six other dimensions that drive the actual unit economics. This framework walks through the seven evaluation axes worth weighing, the right questions to ask under each, and how to score a courier before committing volume.

What does a good courier-partner evaluation framework look like?

A weighted scorecard across seven dimensions:

Dimension	Why it matters	Typical weight
1. Pincode coverage	Orders to unserviceable pins die in your funnel	15%
2. SLA reliability	First-attempt delivery rate, transit consistency	20%
3. NDR and RTO performance	Drives a large share of total cost	20%
4. COD handling	Fees + remittance cycle = real cash flow impact	10%
5. Tech and integration	API quality, dashboard, webhook reliability	10%
6. Cost competitiveness	Per-shipment rate + true cost layers	15%
7. Dispute and claims process	Weight correction, damage, lost-shipment recovery	10%

The weights are starting points; adjust by category. Apparel brands should weight reverse-pickup quality higher; high-AOV brands should weight SLA reliability higher.

What pincode coverage actually matters?

Don't compare on "20,000 pincodes" claims. Compare on your top 1,000 customer pincodes.

Pull your last 90 days of order data, list distinct delivery pincodes ranked by volume, and ask the courier for serviceability on that exact list. Three things to check:

• What percentage is serviceable? Below 95% on your top 1,000 is a red flag.
• What's the SLA per zone? Serviceability without SLA isn't useful.
• Which categories have restrictions? Some carriers exclude liquids, batteries, fragile items.

For zone-and-pincode comparison across 15+ carriers on your specific list, the shipping rate calculator is the fastest way to model serviceability without manually pulling each carrier's sheet.

How do you assess SLA reliability before signing?

Three sources of signal, in order of credibility:

1. Your own pilot data. Manifest 200–500 shipments across your top zones over 4–6 weeks; measure first-attempt delivery rate, transit-day variance, and stuck-shipment rate by lane. This is the only fully reliable signal.
2. Peer references. Three D2C brands of similar scale and category who use the carrier. Ask specifically about month-on-month variance, not headline averages.
3. Carrier's published benchmarks. Useful as a starting point but always optimistic.

A good carrier delivers 80%+ first-attempt on standard surface express and 88%+ on premium services. Anything materially below is a workflow gap, not a one-off.

What NDR and RTO metrics should you ask about?

Six questions, with expected answers in a healthy mid-sized D2C operation:

• What's your NDR rate by zone? Single-digit on Local, low-teens on ROI. Above 20% on any zone is a flag.
• How does your NDR re-attempt workflow work? Automated re-attempt with customer comms is the minimum acceptable.
• What's your average RTO rate on COD orders for D2C brands? 8–12% is healthy on apparel; 4–8% on lower-return categories.
• How quickly are NDR tickets resolved? Same-day or next-day for re-attempt confirmation; longer is a workflow gap.
• Do you support OTP-based COD verification? Increasingly important for new-buyer COD risk reduction.
• What's your reverse-pickup TAT? End-to-end from request to warehouse receipt: 7–12 days is good.

For brands running multi-carrier, the NDR management workflow across all carriers can be unified at the aggregator layer.

How should you evaluate COD handling?

COD has three sub-dimensions: fee structure, remittance cycle, and dispute handling.

• Fee structure: flat ₹X plus Y% of order value (whichever is higher). Typical: ₹30–₹60 flat with 1.5–2.5%. Watch for hidden processing fees per remittance.
• Remittance cycle: D+2 vs D+7 vs D+15 affects your working capital. Most direct contracts at sub-10K-orders/day are D+7 or longer; aggregators can offer faster cycles.
• Dispute handling: when a COD order is undelivered with cash unaccounted, how fast does the courier resolve it? Anything over 30 days is unhealthy.

A courier with D+2 remittance and a 7-day dispute SLA is materially different from one with D+15 remittance and a 45-day dispute SLA, even if the per-shipment freight is identical.

What tech and integration questions matter?

Eight items to verify:

1. REST API quality — endpoints for booking, tracking, NDR, reverse, COD remittance. Test in sandbox before signing.
2. Webhook reliability — tracking events should fire within minutes of scans. Test by checking webhook logs against the courier's dashboard.
3. Bulk manifest support — can you book 1,000+ shipments in a single API call or CSV upload?
4. Tracking webhook structure — standardized event codes, scan timestamps, scan location.
5. Reverse AWB generation — programmatic, not manual.
6. Address validation — pincode serviceability lookup, address structure parsing.
7. Reporting API — daily and monthly summaries pullable.
8. Multi-warehouse support — if you ship from multiple FCs, the API should handle origin-specific routing.

For multi-carrier brands, the unified tech layer comes from the aggregator — individual carrier APIs don't need to be productionized.

How do you score cost competitiveness honestly?

The mistake most brands make: comparing per-shipment rates from the rate card.

The right comparison is true cost per delivered shipment, which factors in:

• Forward freight per shipment (rate + GST)
• RTO cost allocated across delivered orders
• Reverse pickup cost allocated
• COD handling fees
• Working capital cost on COD remittance cycle

A courier with a 10% higher per-shipment rate but a 4-point lower RTO rate and D+2 remittance is often cheaper on true cost. Model both.

What about the dispute and claims process?

Often ignored at contract stage, expensive when it bites. Five questions:

• What's the claim filing window for damage / lost shipments? 7–30 days is standard; longer is friendlier.
• What documentation is required? POD, photos, customer affidavit — verify reasonable.
• What's the SLA for claim resolution? 15–30 days is healthy; over 45 days is a workflow risk.
• What's the typical settlement amount as % of declared value? Less than 100% is normal; below 60% is a flag.
• Is there a weight-correction dispute SLA? 7–14 days for verification.

A courier that drags claims for 60+ days effectively becomes a financing cost on your operations.

How do you run the evaluation in practice?

A 6-week sprint that works for most D2C brands:

• Week 1: pull top-1,000 pincodes + last 90 days operational data. Define your scorecard weights.
• Week 2: shortlist 3–5 carriers. Send the structured RFP with the questions above.
• Week 3: pilot setup — sign limited-volume agreements with the top 2 candidates.
• Week 4–5: pilot 200–500 shipments per carrier. Measure SLA, NDR, RTO, COD remittance.
• Week 6: scorecard finalized; allocation decision made.

Don't sign a multi-year exclusive contract without a pilot. The "discount for exclusivity" almost never pays back.

How does ShipPrime simplify the evaluation?

ShipPrime's 15+ courier partners pre-aggregate the seven evaluation dimensions:

• Pincode coverage — combined panel covers 18,700+ pincodes across India.
• SLA reliability — historical carrier-by-zone performance visible on the dashboard.
• NDR/RTO — unified NDR management across all carriers.
• COD — D+2 remittance regardless of which carrier handled the shipment.
• Tech — single API and webhook for all carriers; no per-carrier integration.
• Cost — aggregator-negotiated rates pooled across thousands of D2C brands.
• Disputes — single dispute workflow with documentation requirements normalized.

The practical effect: instead of evaluating, signing, and integrating 5 carriers individually, you evaluate ShipPrime once and route across 15+ carriers from one stack.

Frequently Asked Questions

What's the most important factor in choosing a courier partner? Not rate. SLA reliability and RTO/NDR performance drive more of your unit economics than per-shipment freight. Evaluate on true cost per delivered shipment, not on rate card numbers.

How long should a courier pilot run? 4–6 weeks at 200–500 shipments per carrier is enough to read SLA, NDR, RTO, and COD remittance honestly. Less than 4 weeks is too noisy; longer than 8 weeks delays the decision unnecessarily.

Should D2C brands use one courier or multiple? Most well-run D2C brands use 3–6 carriers concurrently. Single-carrier brands face SLA-breakage risk and miss zone-specific optimization. Above 6 carriers, the operational complexity outweighs the gain.

What questions should I ask before signing a courier contract? Pincode serviceability for your top 1,000 pins, SLA by zone, NDR/RTO rates for similar brands, COD fee + remittance cycle, claim filing windows and settlement rates, API quality, and exit terms. The detailed scorecard above covers the rest.

Is an aggregator better than direct courier contracts? For brands below 10,000 orders/day, aggregators typically offer better rates than direct contracts because they pool D2C volume. Above that volume, hybrid is common — direct contracts for forward bulk + aggregator for reverse or specific carriers.

How often should I re-evaluate my courier mix? Quarterly review of allocation performance; annual full re-evaluation if there's been material category, geographic, or volume change. Don't re-pilot every quarter — that creates churn — but don't lock in a multi-year exclusive either.

Closing Thought

A courier-partner decision affects unit economics, customer experience, and operational complexity for years. Spend the 6 weeks to evaluate properly across all seven dimensions, weight by your category specifics, and run a real pilot before committing. The shortcut decisions are the ones that cost most over time.

---

Want to evaluate 15+ couriers against one scorecard? Start a free ShipPrime account or see ShipPrime pricing.