# Net Weight vs Gross Weight in Logistics: A Practical Guide for Sellers

Net weight vs gross weight is one of the most-confused pairs in Indian e-commerce shipping. Couriers care about gross weight (and sometimes volumetric), not net weight — but most sellers manage their inventory by net weight. The gap between the two is where invoicing surprises hide.

This guide explains both, shows how each one is calculated, and walks through how to pull gross weight down on every shipment.

## What is net weight?

**Net weight** is the weight of the product alone — no packaging, no filler, no outer carton, no tape. If you sell a 250 g phone case, the net weight is 250 g.

Net weight is what manufacturers stamp on product packaging (think "Net Wt: 200g" on a chocolate bar). It's the standard for product specs, inventory management, and consumer-facing labeling — but it is not what the courier bills you on.

## What is gross weight?

**Gross weight** is the total weight of everything that leaves your warehouse on a single shipment: product + retail box + outer carton + filler + tape + label. If your 250 g phone case ships inside a 100 g retail box, packed into a 300 g corrugated outer with 50 g of bubble wrap and 10 g of label/tape, the gross weight is 710 g.

Gross weight is what the courier weighs at pickup. It's also one of the two inputs into chargeable weight (the other being volumetric).

## What is tare weight (and how does it fit in)?

**Tare weight** is the weight of the packaging alone — outer carton, filler, tape, label, retail box if separate from the product. In our example, tare weight = 100 + 300 + 50 + 10 = **460 g**.

The relationship:

```
Gross weight = Net weight + Tare weight
```

Or, rearranged:

```
Tare weight = Gross weight - Net weight
```

Most invoicing variance comes from tare weight that's higher than necessary — packaging that adds 200–400 g without adding any value.

## How is gross weight calculated for shipping?

Three steps:

1. Weigh the **fully packed outer carton** on a calibrated scale just before pickup. Don't estimate.
2. Round up to the nearest 500g slab (every Indian courier bills by 500g slabs).
3. Compare against the volumetric weight using the formula (L × W × H in cm) / 5000 for surface. Chargeable weight = the higher of gross weight and volumetric weight.

Worked example: a 250 g phone case shipping in a 30 × 20 × 8 cm box.

- Net weight: 250 g
- Tare (retail box + outer + filler + tape + label): 460 g
- **Gross weight: 710 g → billed at 1.0 kg slab**
- Volumetric weight: (30 × 20 × 8) / 5000 = 0.96 kg
- Chargeable weight: max(1.0, 0.96) = **1.0 kg**

The 250 g product gets billed at the 1.0 kg slab because gross weight pushed it there. That's an entire slab of avoidable cost on every shipment.

To compute this across your top SKUs without manual math, the [volumetric weight calculator](/tools/volumetric-weight-calculator) on ShipPrime takes dimensions and gross weight and returns the chargeable slab.

## Why does gross weight matter more than net weight for shipping costs?

Three reasons:

- **Couriers weigh at the hub**, not at your warehouse. The number they record is gross weight from the scale, plus volumetric from their dimensioner. Net weight doesn't enter their system.
- **Slabs are unforgiving.** A shipment at 1.05 kg is billed at 1.5 kg. Cut tare by 100 g and you might drop a full slab.
- **Disputes are expensive.** If your declared weight (often net or estimated) doesn't match the courier's measured gross weight, you get a weight-correction surcharge — and the dispute process takes 7–15 days.

The fastest fix: weigh the packed outer carton, not the product, when entering shipping details.

## How can you reduce gross weight on your shipments?

Five practical steps:

1. **Audit your tare weight by SKU.** Pull a sample of 20–30 shipments, record net and gross, and compute tare. If tare is more than 40% of gross on light items, packaging is the lever.
2. **Switch from corrugated outer to poly mailer** for soft goods (apparel, accessories, books). A poly mailer adds 15–30 g of tare; a corrugated box adds 200–400 g.
3. **Eliminate void fill.** Air pillows, crumpled paper, and bubble wrap add tare without protecting most products. Fit the product, then size the box.
4. **Right-size cartons.** Buy 3–5 carton sizes that fit your top-selling SKUs, not one universal "big enough" box.
5. **Weigh before manifest.** A 100-shipment batch with a 10% slab error rate costs you the equivalent of one full pickup of free shipping per day. A ₹600 calibrated scale pays for itself in a week.

## How does ShipPrime handle gross weight and chargeable weight?

ShipPrime asks for gross weight and outer-carton dimensions during shipment booking, then surfaces the chargeable weight (max of gross and volumetric) across all 15+ courier partners before you allocate the order. That means you see the slab impact upfront — if a small packaging change drops you from 1.5 kg to 1.0 kg, you know it before printing the label.

The dashboard also reconciles declared gross weight vs courier-measured gross weight after pickup, so variance shows up as a tracked line item instead of a hidden invoice surprise.

## Frequently Asked Questions

**What is the difference between net weight and gross weight?**
Net weight is the product alone. Gross weight is the product plus all packaging (retail box, outer carton, filler, tape, label). Couriers bill on gross weight, not net.

**Why is gross weight higher than net weight?**
Because gross includes packaging, void fill, label, and tape — none of which is part of the product itself. Tare weight is the difference between gross and net.

**Which weight do Indian couriers bill on?**
Chargeable weight, which is the higher of gross weight and volumetric weight, rounded up to the next 500g slab.

**How do I calculate tare weight?**
Tare weight = Gross weight − Net weight. In practice, weigh the empty outer carton + filler + tape + label, or compute it from measured gross and known net.

**Is net weight ever used in shipping?**
For some hazmat, food-grade, or regulated shipments, net weight is required on documentation alongside gross. For freight pricing in standard e-commerce, the courier uses gross and volumetric only.

**What's the easiest way to reduce gross weight on light products?**
Switch from corrugated outer cartons to poly mailers and eliminate void fill. For most apparel, accessories, and small-product D2C categories, this cuts tare by 200–350 g per shipment.

## Closing Thought

Net weight is for your customers; gross weight is for your couriers. Optimizing the gap between them — through packaging audits, right-sized cartons, and disciplined manifesting — is one of the highest-ROI levers in Indian D2C shipping.

---

Want to see chargeable weight across 15+ couriers in one query? [Start a free ShipPrime account](/register) or [see ShipPrime pricing](/pricing).


Net weight vs gross weight decides what couriers actually bill you. Learn the difference, how to calculate each, and how to reduce gross weight on your shipments.

Net Weight vs Gross Weight in Logistics: A Practical Guide for Sellers

# Shipping vs Delivery: What is the Difference and Why It Matters

Shipping and delivery sound interchangeable, but in logistics they refer to two different events in two different timelines. Shipping is the carrier-side process — pickup, sortation, transit, and the last-mile attempt. Delivery is the customer-side event — the moment the parcel actually changes hands at the doorstep. Treating them as the same thing breaks SLAs, inflates support tickets, and quietly damages the brand promise.

For Indian D2C brands shipping under tight 2–6 day windows, getting this distinction right is what separates an honest expected-delivery date from a generic "5–7 working days" that customers stop trusting after their second order.

## What is shipping in ecommerce logistics?

Shipping is everything that happens once the order leaves your warehouse and enters the courier network. It is a carrier-side process, measured by manifests and AWB scans rather than by a customer signature. Shipping starts at handover and ends at the first delivery attempt.

The stages inside shipping:

- **Manifest creation** — order details and weight handed to the courier
- **Pickup** — physical handover from your warehouse to the courier vehicle
- **First-mile transit** — pickup hub to origin sortation centre
- **Linehaul** — long-distance transit between sortation hubs
- **Last-mile transit** — destination hub to the customer's local branch
- **Out for delivery** — parcel on the courier's vehicle for the day's attempts

All of this is "shipping." None of it is "delivery" yet.

## What is delivery in ecommerce logistics?

Delivery is the single discrete event at the end of shipping: the parcel changing hands at the customer's address, or being collected from a pickup point. It is measured in seconds and confirmed by a POD signal — signature, OTP, photo, or scan.

Three things matter at delivery:

- **Identity verification** — right person, right address
- **Payment collection** — for COD orders, cash or QR scanned and remitted
- **Proof of delivery (POD)** — captured for dispute defence later. The full mechanics are in the [POD guide](/resources/blogs/proof-of-delivery-guide).

Delivery is also the only metric the customer experiences directly. They don't see your sortation logs; they see whether the parcel arrived today.

## What is the practical difference for D2C brands?

The distinction shapes four operational decisions:

| Decision | Driven by shipping | Driven by delivery |
|---|---|---|
| Quoted SLA at checkout | Transit days by zone | Cutoff time + working days |
| Cost math | Forward shipping rate, fuel, COD fee | Reverse shipping when refused/returned |
| Customer comms | "Shipped" notification + AWB | "Out for delivery" + delivered email |
| Dispute handling | Lost-in-transit claim | Non-delivery / wrong-address dispute |

Shipping cost is what you pay the courier. Delivery success is what determines your RTO rate, support volume, and repeat-purchase probability.

## Shipping date vs delivery date — what should you tell the customer?

The shipping date is when you hand the parcel to the courier. The delivery date is the expected arrival at the customer's door. Most D2C brands quote only one number ("delivered in 5 days") and create ambiguity at both ends.

The better pattern:

```
Ships by Mon 24 June — Arrives by Wed 26 June
```

Two dates, both honest, set against the courier's pincode SLA rather than a blended national estimate. Real per-pincode SLA data comes from the courier dashboard or your shipping aggregator's API — ShipPrime exposes per-pincode SLA across 15+ partners so the dates at checkout reflect actual transit, not a guess.

## What are the common mistakes brands make?

- **Quoting "delivered in 5–7 working days" on every order** regardless of pincode. Sets the wrong expectation on both ends — too tight for North-East orders, too loose for local orders.
- **Marking the order "delivered" in the system when the AWB hits "out for delivery"** — creates a gap where customer support hears "I haven't received it" while the panel says "delivered."
- **Treating shipping date as delivery date in customer comms** — "your order has shipped" without a separate delivery ETA leaves the customer guessing for 3–5 days.
- **Counting RTO from shipping date instead of delivery attempt date** — distorts the RTO funnel and hides where the leak actually happens.
- **Treating COD remittance cycle as a shipping cost** when it's actually a post-delivery event. Remittance delay is a working-capital cost, not a shipping cost.

## How does ShipPrime separate shipping and delivery?

ShipPrime's dashboard surfaces both timelines independently. The shipping view tracks manifest, pickup, and transit milestones across 15+ courier partners. The delivery view tracks attempt status, NDR cycle, and POD capture per shipment.

At checkout, the rate calculator pulls per-pincode shipping SLA across all enabled couriers, so the expected delivery date shown to the customer reflects the actual transit window — not a blended "5–7 days" guess. The [branded tracking page](/track-order) keeps both stages visible to the customer on your own domain, which cuts "where is my order?" support tickets by 40–60%. COD remittance lands in D+2 from successful delivery, irrespective of how long shipping took.

## Frequently Asked Questions

**What is the difference between shipping and delivery?**
Shipping is the carrier-side process from warehouse pickup through transit to the first delivery attempt. Delivery is the discrete event of the parcel changing hands at the customer's address. Shipping is measured by AWB scans; delivery is measured by POD capture.

**Is the shipping date the same as the delivery date?**
No. Shipping date is when the parcel is handed to the courier. Delivery date is when the parcel reaches the customer's address. The gap between them is the transit window, which varies by zone (1–2 days local, 3–6 days rest of India).

**Why does the difference between shipping and delivery matter for D2C?**
Because customers experience delivery, not shipping. Quoting a single number ("5 days") instead of separate shipping and delivery dates creates expectation gaps that show up as bad reviews, RTO refusals, and support tickets. Two honest dates beats one blended guess.

**What is POD and how is it linked to delivery?**
POD (proof of delivery) is the confirmation captured at the moment of delivery — signature, OTP, photo, or scan. It marks the formal end of the shipping lifecycle and the start of the remittance cycle for COD orders. Read more in the [POD guide](/resources/blogs/proof-of-delivery-guide).

**When does an order count as "delivered" in your system?**
When the courier's AWB scan registers a successful POD event, not when it hits "out for delivery." Marking earlier creates a gap where the panel says delivered but the customer hasn't received the parcel — usually the source of disputes.

**Should I quote a delivery date or a shipping date on my product page?**
Both. "Ships by [date] — Arrives by [date]" is the clearest pattern. Customers want to know when it leaves and when it arrives. Single-date quotes ambiguate which event is being promised.

## Closing Thought

Shipping is what you pay for. Delivery is what the customer remembers. Once the team is clear on which event each metric and message refers to, SLAs sharpen, support volume drops, and the brand promise stops drifting between "ordered" and "received."

---

Want per-pincode shipping and delivery SLAs at checkout? [Start a free ShipPrime account](/register) or [see ShipPrime pricing](/pricing).


Shipping and delivery sound interchangeable but mean different things in logistics. Learn the exact difference, SLA implications, and why it matters for D2C.

Shipping vs Delivery: The Real Difference for D2C Sellers (2026)

Shipping vs Delivery: What is the Difference and Why It Matters

# What is Zone Skipping? How It Reduces Shipping Costs for D2C Brands

Zone skipping is the logistics practice of bulk-moving parcels closer to their destination zone before they enter the courier's normal sortation network. Instead of one parcel hopping through three or four courier hubs, a truckload of parcels skips those intermediate stages and joins the local last-mile leg directly. For high-volume D2C brands, this cuts both transit time and per-shipment cost by 15–30% on long-haul orders.

The technique has been standard in US/EU logistics for years and is now mature enough in India that aggregator-level brands shipping 200+ orders a day to distant zones can build it into their cost model. This post explains how it works, when it pays back, and where it doesn't.

## How does zone skipping actually work?

A normal D2C parcel from Bengaluru to Patna travels through five legs:

1. Warehouse → Bengaluru hub (first-mile pickup)
2. Bengaluru hub → Hyderabad sortation
3. Hyderabad → Kolkata sortation
4. Kolkata → Patna hub
5. Patna hub → customer's door

Each hub stop adds 12–36 hours of dwell time and a per-parcel handling charge. Zone skipping consolidates outbound orders to the same distant zone (say, all Patna-bound orders for the week) into a single truck and delivers them straight to the Patna hub. The middle three legs disappear. Only the first-mile and last-mile remain on the per-parcel cost.

The same principle works for any high-volume origin-destination pair where the freight cost of one consolidated truck divided across many parcels lands below the standard per-parcel rate.

## What does the cost math look like?

A worked example for 500 parcels/week shipping Bengaluru → Patna, average chargeable weight 1 kg:

Standard surface shipping:
- 500 × ₹160 per parcel = ₹80,000/week
- Average transit: 5–6 days

Zone-skipped option:
- 1 truck Bengaluru → Patna hub (line haul) at ~₹35,000 for 500 kg
- Last-mile only at Patna (~₹50/parcel × 500) = ₹25,000
- **Total: ₹60,000/week**
- Average transit: 3–4 days

Savings: ₹20,000/week (25%) plus 1–2 days off transit. The math turns negative below ~150 parcels/week on the same OD pair, because the line-haul cost stops amortising.

## When does zone skipping make sense?

Three conditions must hold:

- **Sustained volume** to a specific destination zone — typically 150+ parcels/week, ideally same-day-dispatch ready.
- **The destination zone is far** — long-haul ROI or Special zones (North-East, Tier-3 outliers) where the per-parcel hub cost is highest.
- **You can hold orders by 12–24 hours** to consolidate the truck, without breaking customer SLA.

If any of these break, standard parcel shipping is cheaper and faster.

## When is zone skipping not the right call?

- **Volume below threshold** — under 100 parcels/week to one zone, the truck cost dominates.
- **Local and zonal orders** — savings are minimal because intermediate hubs don't add much cost on short legs.
- **Time-sensitive SKUs** — perishables, gifts with date promises, or any order quoting <72h delivery doesn't tolerate consolidation hold.
- **Mixed-weight loads** — zone skipping economics get noisy if weight per parcel varies 5×. Best for catalogues with consistent SKU weight.
- **Returns-heavy categories** — reverse logistics doesn't zone-skip well, so brands with 30%+ RTO see the savings eroded on return flow.

## How can D2C brands access zone skipping in India?

Direct relationships with line-haul fleet operators work above ~1,000 parcels/week per destination zone. Below that, the practical access route is via shipping aggregators that already run consolidated long-haul lanes on behalf of multiple brands.

The aggregator side of zone skipping looks like normal multi-courier shipping at the booking layer — you pick a service level (Express, Surface, Economy), the platform routes via a consolidated lane when one exists for your OD pair, and the savings show up as a lower zone rate. ShipPrime exposes consolidated-lane pricing alongside standard surface rates so brands can pick the cheaper option per order without managing the logistics behind it.

## How does zone skipping compare to other shipping cost levers?

| Lever | Savings range | Effort | When it works |
|---|---|---|---|
| Right-sized packaging | 10–25% | Low (one-time) | Any volume |
| Multi-carrier rate negotiation | 5–15% | Medium (quarterly) | 500+ orders/month |
| Zone skipping | 15–30% on long-haul | Medium-High | Sustained volume to specific zones |
| RTO reduction | 5–15% effective cost | High (ongoing) | COD-heavy brands |
| Switching to surface from air | 40–60% | Low | When customer SLA allows |

For most D2C brands under 200 orders/day, the higher-ROI levers are right-sized packaging and RTO reduction. Zone skipping enters the picture once you cross 150+ daily orders with clear zone concentration. The full per-shipment cost breakdown is in [True Cost Per Shipment for D2C](/resources/blogs/true-cost-per-shipment-d2c).

## How does ShipPrime handle zone skipping?

ShipPrime routes orders across 15+ courier partners and consolidated long-haul lanes from a single API call. When your OD pair has a consolidated lane available, the dashboard surfaces it alongside standard surface rates so you can pick the cheaper option per order or set a default routing rule. No manual line-haul booking required.

For brands shipping 200+ orders/day, the routing engine identifies high-volume OD pairs automatically and recommends lanes worth consolidating, with the expected savings per shipment. COD remittance lands in D+2 regardless of which lane the order ships through, and pricing remains transparent at the per-shipment level.

## Frequently Asked Questions

**What is zone skipping in shipping?**
Zone skipping is the logistics practice of consolidating multiple parcels into a single line-haul truck that bypasses the courier's intermediate sortation hubs and goes directly to the destination zone's last-mile network. It cuts both per-parcel cost and transit time.

**How much can zone skipping save?**
Typically 15–30% on long-haul orders (ROI and Special zones) when volume to a single destination is sustained above 150 parcels/week. Savings are minimal on local and zonal orders.

**What is the minimum volume needed for zone skipping?**
Around 150 parcels/week per destination zone is the practical break-even. Below that, the fixed cost of the line-haul truck doesn't amortise across enough parcels to beat standard per-parcel pricing.

**Does zone skipping affect delivery time?**
Yes — usually positive. By skipping 2–3 intermediate hub stops, transit shortens by 1–2 days on long-haul lanes. The trade-off is an upfront 12–24 hour hold to consolidate the truck, which still nets faster than standard hub-to-hub transit.

**Is zone skipping the same as direct injection?**
Closely related. Direct injection drops parcels at the destination zone's first sortation hub; zone skipping can go a stage further by bypassing that hub too and joining at the last-mile branch. Both cut intermediate sortation costs.

**Can small D2C brands do zone skipping?**
Not directly — line-haul truck minimums are too high. Indirect access is via shipping aggregators that run consolidated lanes across multiple brands' volumes. The brand books normally; the aggregator picks the consolidated lane when one exists.

## Closing Thought

Zone skipping is a high-ROI lever once your volume to specific destinations is steady, and a distraction below that threshold. The honest order of operations for most D2C brands: right-size packaging first, reduce RTO second, negotiate carrier rates third, and only then think about consolidated lanes. Run them in that order and the shipping cost line item drops without complicating the back office.

---

Want consolidated-lane pricing alongside standard rates? [Start a free ShipPrime account](/register) or [see ShipPrime pricing](/pricing).


Zone skipping cuts D2C shipping costs by 15-30% on long-haul orders. Learn how it works, when it makes sense, and the volume threshold to break even.

What is Zone Skipping? Cost-Saving Logistics for D2C (2026)

What is Zone Skipping? How It Reduces Shipping Costs for D2C Brands

# How Pre-Orders Can Boost Sales for D2C Brands in India

Pre-orders let D2C brands collect cash upfront, validate demand before manufacturing, and create scarcity-driven urgency around new launches. Used well, they lift launch-week revenue by 30-80% over a standard launch, cut dead inventory close to zero, and turn an unproven SKU into a funded SKU before the first unit is shipped.

Used badly, they erode customer trust within one cycle. The line between the two is operational discipline — clear shipping dates, proactive communication, and a shipping setup that can actually deliver when the pre-order window closes. This post walks through the model, the math, and the execution playbook.

## What are pre-orders in D2C?

A pre-order is a customer purchase placed before the product is available to ship. The customer pays now (or commits to paying), and the brand ships at a stated future date. Pre-orders work for three kinds of products:

- **New launches** — first batch of a new SKU
- **Restocks** — popular SKUs that sold out, now coming back
- **Limited editions** — drops with fixed inventory, often with a deadline

The pre-order window is typically 7–30 days. Shipping happens at a stated date after the window closes.

## Why do pre-orders boost D2C sales?

Three structural advantages over a standard launch:

### 1. Cash flow comes in before COGS goes out

A standard launch requires the brand to buy or manufacture inventory (cash out), warehouse it (cash out), and then sell it. Pre-orders flip this — cash in first, then manufacturing. For a brand at 20–30% gross margin, this is the difference between bootstrapping the next launch and needing external capital.

### 2. Demand is validated before scale-up

If a 14-day pre-order window sells 500 units, you know to manufacture 750–1,000 for the broader launch. If it sells 50 units, you cancel the SKU or rework the offer before sinking capex into inventory. This is one of the cheapest market-validation experiments available.

### 3. Scarcity + countdown drive urgency

A "Pre-order open until 15 July — Ships 1 August" message creates a closed window. Closed windows convert better than open-ended availability. Most D2C brands see 30–50% lift in conversion rate during pre-order vs equivalent standard inventory periods.

## What categories work best for pre-orders?

- **Apparel, especially limited drops** — natural fit for scarcity-driven model
- **Beauty and skincare new launches** — strong demand validation use case
- **Premium electronics and lifestyle SKUs** — high AOV, customers tolerate wait
- **Books, prints, art, collectibles** — community-funded model

Categories that don't pre-order well: low-AOV impulse items (₹200–₹500 phone accessories), perishables, anything with sub-3-day standard availability expectation, and categories where competitors have instant shipping.

## How do you set up pre-orders on Shopify, WooCommerce, or Magento?

### Shopify

Native pre-order is limited; most brands use one of:

- A pre-order app (Pre-Order Manager, PreProduct, Notify Me)
- A custom theme modification that adds a "Pre-order" button + custom "Ships [date]" text
- A separate landing page with a payment gateway

### WooCommerce

The free **WooCommerce Pre-Orders** plugin handles most pre-order workflows: collect upfront or on shipping, set a release date, send automated emails on launch day. Setup takes 30–45 minutes.

### Magento and custom sites

Magento has community modules; custom sites usually wire pre-orders via a "pre-order" product type with shipping logic gated by a release date in the database.

For all three, the technical setup is the easy part. The hard part is the customer communication and shipping execution.

## What customer communication does pre-order require?

Six touchpoints, none of them optional:

1. **At checkout** — clearly state "Pre-order — Ships by [date]." Not buried in fine print, prominent next to the price.
2. **Order confirmation email** — repeat the ship date and include the order ID.
3. **Mid-cycle update** — a week before ship date, send "Your pre-order is being prepared, ships [date]" to keep the order top of mind.
4. **Ship date update** — when the AWB is generated, send tracking immediately.
5. **Delay notification (if applicable)** — if the ship date slips, communicate proactively before customers ask. One-day silence on a delay erodes more trust than the delay itself.
6. **Post-delivery follow-up** — for the first pre-order batch, ask for feedback. Customers who pre-ordered are your highest-affinity buyers.

## What shipping setup do pre-orders need?

Three operational requirements:

### 1. Dispatch readiness on the stated ship date

Manufacturing + QC + packaging must all be in place 2–3 days before the stated ship date. Missing the ship date is the single biggest pre-order trust violation.

### 2. Bulk AWB generation when the window closes

A 500-unit pre-order batch ships in 1–2 days. Manual AWB generation across multiple courier panels is operationally impossible at that scale. A shipping aggregator's bulk AWB workflow turns the dispatch from a 2-day data-entry exercise into a 30-minute label-print exercise. ShipPrime supports bulk AWB across 15+ courier partners.

### 3. Multi-courier failover for pincode coverage

The 500-unit batch will include pincodes where your primary courier doesn't serve well. Without multi-courier failover, you're delaying 5–10% of the batch and breaking the ship date for those customers. Aggregator pincode-level routing across 18,700+ pincodes solves this.

## What pre-order math should D2C founders model?

A worked example for a brand running a 14-day pre-order on a new SKU at ₹2,000 AOV:

- Expected pre-order volume: 400 units (based on past launch data)
- Cash collected upfront: 400 × ₹2,000 = ₹8 L
- Manufacturing cost: 400 × ₹800 (40% COGS) = ₹3.2 L
- Shipping cost (effective): 400 × ₹200 = ₹80,000
- Other launch costs: ₹20,000
- **Profit margin on pre-order batch: ₹4.0 L (50% of GMV)**
- **Working capital position: positive ₹4.8 L before any inventory is paid for**

Compare to the standard model:

- Manufacture 400 units upfront: -₹3.2 L cash out
- Sell over 30–60 days: ₹8 L revenue trickled in
- Working-capital position at start: -₹3.2 L

The pre-order model funds itself; the standard launch requires capital. For a bootstrapped D2C brand, this difference is often the difference between scaling and stalling.

## What are the most common pre-order mistakes?

- **Vague ship dates** — "Ships in 4–6 weeks" instead of a specific date. Customers anchor on the longer end and feel disappointed at week 5.
- **Missing the ship date with no notification** — guaranteed return wave and review damage.
- **Shipping pre-orders piecemeal** — half the batch goes out on day 1, half on day 4. Customers compare on social media and feel cheated.
- **Not capping pre-order quantity** — over-promising on volume the manufacturing can't meet.
- **Treating pre-orders as final sale by default** — Indian consumer protection requires standard return rights even for pre-orders, with limited exceptions for personalized SKUs.
- **No clear comms on what's included vs out-of-stock variants** — confused customers send 5× more support tickets.

## How does ShipPrime support pre-order launches?

When the pre-order window closes and 400+ orders ship in a single day, ShipPrime's bulk AWB generation across 15+ courier partners processes the batch in minutes instead of hours. Multi-courier failover across 18,700+ pincodes means every order in the batch ships on the same day, including the long-tail pincodes a single courier wouldn't cover.

The branded tracking page keeps the post-purchase experience on your domain, NDR automation contacts customers within 4 hours on failed attempts, and COD remittance lands in D+2 — useful for the post-launch cash cycle. Transparent per-shipment pricing starts at ₹19/500g with zero setup fees, so the cost math holds even on a one-off launch batch.

## Frequently Asked Questions

**What is a pre-order in D2C?**
A pre-order is a customer purchase placed before the product is available to ship. The customer pays (or commits) now, the brand ships at a stated future date — typically 7-30 days after the pre-order window closes. Used for new launches, restocks, and limited editions.

**How much can pre-orders lift launch sales?**
A well-run pre-order typically lifts launch-week revenue 30-80% over a standard launch, primarily through scarcity-driven urgency, demand validation, and upfront cash flow. The lift is highest in apparel, beauty new launches, premium lifestyle SKUs, and limited editions.

**Are pre-orders legal in India?**
Yes. Indian consumer protection law treats a pre-order as a contract — the brand owes the customer either the product by the stated date or a refund. Standard return rights apply unless the SKU is personalized or made-to-order.

**How do I set up pre-orders on Shopify?**
Use a pre-order app (Pre-Order Manager, PreProduct, Notify Me) or a custom theme modification. Both let you display a "Pre-order — Ships [date]" button instead of "Add to Cart" until the release date, collect payment upfront, and send automated launch-day emails.

**What's the biggest pre-order mistake D2C brands make?**
Missing the stated ship date without proactive communication. One missed pre-order ship date erodes more trust than three months of standard delays — customers feel the brand has broken a specific promise tied to a payment they already made.

**Do I need a shipping aggregator for pre-orders?**
Once pre-order volumes cross 200 units shipping in a single window, yes. Bulk AWB generation, multi-courier failover for pincode coverage, and same-day dispatch capability are operational requirements at that scale. Single-courier setups produce uneven ship dates that break the launch promise for 5-10% of customers.

## Closing Thought

Pre-orders are the highest-leverage launch model in D2C — cash before COGS, demand before scale, urgency built in. The model only works when the shipping execution matches the marketing promise. Get the dispatch date right, generate AWBs in bulk, route across 15+ couriers for pincode coverage, and pre-orders pay for the next launch instead of funding the last apology.

---

Want bulk AWB and multi-courier routing for your next pre-order launch? [Start a free ShipPrime account](/register) or [see ShipPrime pricing](/pricing).


Pre-orders unlock upfront cash, demand validation, and launch urgency for D2C brands. Setup, communication, and shipping playbook for 2026.

How Pre-Orders Boost Sales for D2C Brands in India (2026)

How Pre-Orders Can Boost Sales for D2C Brands in India

# What is a Supply Chain Network? Design and Optimization for D2C Sellers

A supply chain network is the set of nodes — suppliers, warehouses, transport lanes, customer endpoints — that move your inventory from origin to final delivery. For Indian D2C brands, network design is the underlying decision that determines whether you can credibly promise 2-day delivery to a Patna customer, or whether you quote 8 days and hope.

Most D2C founders treat their supply chain network as fixed — one warehouse, one set of couriers, "good enough" for now. But the network is the highest-leverage decision in shipping economics. Adding a second warehouse, switching to a multi-courier mix, or consolidating long-haul lanes can shift cost-to-serve by 20–40% in a quarter. This post defines the components, the design rules, and the trigger points for redesign.

## What does a supply chain network include?

Five node types and the lanes that connect them:

- **Suppliers** — raw materials, finished goods, packaging vendors
- **Inbound transport** — bulk freight from suppliers to warehouses
- **Warehouses** — single central, regional hubs, or fulfilment-partner sites
- **Outbound transport** — line haul + last-mile across 15+ courier partners and 18,700+ pincodes
- **Customer endpoints** — pincode-level delivery addresses across India

The complexity isn't in any single node — it's in the lanes between them. A 200-order/day brand might have 10 suppliers, 1 warehouse, 5 courier partners, and 2,000 active customer pincodes. That's a few hundred meaningful lanes to manage.

## Why does network design matter for D2C?

Network design controls three things customers actually feel:

- **Delivery time** — distance from warehouse to customer plus carrier transit
- **Shipping cost** — distance, weight, zone, COD fee — all set by where inventory sits
- **Stockout risk** — single-warehouse setups stock-out on regional spikes; multi-warehouse setups don't

For a D2C brand at 500 orders/day shipping from a single Bengaluru warehouse, the median customer in Lucknow gets a 5-day delivery and a ₹220 effective per-order cost. Adding a small fulfilment node in Delhi cuts North India delivery to 2 days and effective cost to ₹160. Same brand, same products — different network.

## What are the main network design models?

### Model 1 — Single centralised warehouse

One warehouse serves all of India. Common starting setup.

- **Pros**: low capex, simple inventory management, one team to train
- **Cons**: long-haul shipping cost on 30–50% of orders, slow delivery to distant zones

Best for: brands under 200 orders/day, low SKU count, where customer geography is concentrated near the warehouse.

### Model 2 — Regional hubs (2–3 warehouses)

Two or three warehouses placed to cover major demand clusters — typically one each in West (Bengaluru/Mumbai), North (Delhi NCR), and East (Kolkata) for pan-India brands.

- **Pros**: cuts average delivery time by 1–3 days, cuts shipping cost by 15–25%, lowers stockout risk
- **Cons**: higher inventory carrying cost (each SKU stocked at multiple sites), operational complexity, multi-warehouse WMS needed

Best for: brands at 500+ orders/day with national customer base.

### Model 3 — Distributed fulfilment via 3PL network

Inventory placed at multiple 3PL partner warehouses across the country, often with software-managed allocation by pincode.

- **Pros**: near-customer delivery (1–2 days), variable-cost ops, scales without warehouse capex
- **Cons**: 3PL margin reduces unit economics, less control over packaging quality, integration overhead

Best for: brands at 1,000+ orders/day or with high seasonality.

### Model 4 — Hybrid (own warehouse + 3PL nodes)

Central warehouse owned + 3PL nodes for specific regions where you don't have scale to justify your own.

- **Pros**: control where it matters, flexibility where it doesn't
- **Cons**: most complex to manage; needs strong tech stack

Best for: brands transitioning from Model 1 to Model 3 over 12–24 months.

## When should a D2C brand consider redesigning its network?

Five trigger points:

1. **Average delivery time exceeds 4 days** — your network is too centralised for your customer geography.
2. **Effective shipping cost per order exceeds 12% of AOV** — too much long-haul, not enough regional inventory placement.
3. **Stockouts are concentrated in specific regions** — single-warehouse demand spikes outpace inventory replenishment.
4. **RTO rate is highest in distant zones** — long transit time amplifies "customer changed mind" and refusal rates.
5. **Order volume has 3×'d in 12 months** — your old single-node setup is past its sweet spot.

Any one of these on its own justifies a network review. Two or more together is the trigger to act.

## How do you actually optimize a supply chain network?

### Step 1 — Map current demand by pincode

Pull 90 days of order data, plot by 6-digit pincode, identify the 20% of pincodes that drive 80% of orders. This is your demand map.

### Step 2 — Compute current cost-to-serve by zone

For each zone (LOCAL, ZONAL, METRO, ROI, SPECIAL), calculate average shipping cost and average delivery time. Identify the worst-performing zones.

### Step 3 — Model alternative network configurations

Run "what if we added a Delhi node" or "what if we used a 3PL in Hyderabad" against the demand map. Estimate the delivery-time and cost-per-order impact. The math is simple enough to do in Excel for most brands.

### Step 4 — Pick the highest-ROI change

Don't redesign the whole network at once. Pick the single change with the best expected payback (usually a regional node in your worst-performing zone) and pilot it for 90 days.

### Step 5 — Wire the routing logic

Once a new node exists, the question is which orders ship from where. This is the routing layer — typically handled by a WMS + shipping aggregator combination that knows your inventory placement and chooses the closest fulfilment point per order.

## How does ShipPrime fit into supply chain network optimization?

ShipPrime sits at the outbound transport layer of your network. The platform routes orders across 15+ courier partners and 18,700+ pincodes by pincode-level SLA, surfaces transit-time and cost data by zone, and supports multi-warehouse setups where each warehouse has its own service area.

For brands evaluating a multi-warehouse move, the dashboard's zone-level cost-to-serve reporting is the data you need to model the case. For brands already operating multi-warehouse setups, ShipPrime's API supports warehouse-to-order routing rules so each parcel automatically ships from the closest fulfilment node. COD remittance lands in D+2 across all nodes, and transparent per-shipment pricing starts at ₹19/500g.

## Frequently Asked Questions

**What is a supply chain network in simple terms?**
A supply chain network is the set of suppliers, warehouses, transport lanes, and customer endpoints that move inventory from origin to final delivery. For D2C brands, the design of this network determines delivery speed, shipping cost, and stockout risk.

**When should a D2C brand add a second warehouse?**
Common triggers: average delivery time over 4 days, effective shipping cost over 12% of AOV, recurring stockouts in specific regions, or 3× order growth in 12 months. Any one of these justifies a network review.

**What are the main supply chain network design models?**
Four common models: single centralised warehouse, 2–3 regional hubs, distributed fulfilment via 3PL network, and hybrid (own + 3PL). Choice depends on order volume, SKU count, and customer geography.

**How do you optimize a supply chain network for D2C?**
Map demand by pincode, compute zone-level cost-to-serve, model alternative configurations, pilot the highest-ROI change for 90 days, and wire warehouse-to-order routing logic via a WMS plus shipping aggregator.

**Is a 3PL the same as a warehouse?**
No. A warehouse is a physical site that holds inventory. A 3PL (third-party logistics provider) is a service that operates one or more warehouses on your behalf and may also provide fulfilment and shipping. You can own a warehouse, lease a warehouse, or use a 3PL's warehouse.

**Can a small D2C brand benefit from multi-warehouse setup?**
Below 200 orders/day, the inventory carrying cost of stocking SKUs across multiple sites usually outweighs the shipping savings. Above 500 orders/day with national customer base, multi-warehouse typically pays back inside 6 months.

## Closing Thought

The supply chain network is the silent multiplier on every D2C decision. Customer acquisition pours orders into the network; the network decides whether those orders convert into repeat customers or one-time disappointments. Once you can model cost-to-serve and delivery time by zone, network design moves from being an instinct to being a quarterly business review item — which is where it belongs.

---

Want per-zone cost-to-serve data across 15+ couriers? [Start a free ShipPrime account](/register) or [see ShipPrime pricing](/pricing).


Supply chain network design — suppliers, warehouses, transport, customers — decides delivery speed and cost. Multi-warehouse rules and optimization for D2C.

What is a Supply Chain Network? Design Guide for D2C (2026)

What is a Supply Chain Network? Design and Optimization for D2C Sellers

# Carrier Mix Strategy for D2C: How to Allocate Orders Across Couriers

A carrier mix strategy is the set of rules that decides which courier handles each order — based on destination pincode, SLA needs, category, COD vs prepaid, and historical performance. For Indian D2C brands above 100 orders/day, a deliberate multi-carrier strategy outperforms single-carrier defaults by 12–25% on true cost per delivered shipment and materially de-risks SLA breakage.

This guide covers why multi-carrier matters, the rules that drive allocation, and how to operationalize without drowning in complexity.

## Why does carrier mix matter?

Three reasons, each independently sufficient.

1. **No single carrier wins every lane.** Carrier A might be strongest on Delhi-NCR ROI; Carrier B on Maharashtra Zonal; Carrier C on Northeast Special. A single-carrier brand pays the loser's rate on every lane the chosen carrier doesn't win.
2. **Single-carrier risk is real.** A festive-season SLA breakage on your only carrier breaks the quarter. Multi-carrier brands absorb the same breakage by shifting allocation.
3. **Category-specific optimization compounds.** Apparel returns route through reverse-strong carriers; high-AOV through premium SLA carriers; long-tail ROI through deep-network carriers. Single-carrier defaults can't do this.

The brands at 1,000+ orders/day that use one carrier are typically paying 15–25% more on true cost than peers using a deliberate mix.

## What does a good carrier mix look like at different volumes?

Directional guidance by stage.

| Volume stage | Carrier count | Allocation complexity |
|---|---|---|
| **<100 orders/day** | 1–2 | Simple — pick the strongest carrier for your geography |
| **100–1,000/day** | 3–4 | Zone-based allocation rules |
| **1,000–10,000/day** | 4–6 | Zone × category × SLA-tier rules |
| **>10,000/day** | 5–8 | Dynamic allocation engine + carrier-performance feedback loop |

Above 6 carriers, the operational complexity usually outweighs the gain. The sweet spot for most growing D2C brands is 4–6.

## What allocation rules actually matter?

Five rule layers, in priority order.

### 1. Pincode serviceability

Rule: if a destination pincode is not serviceable by Carrier A, route to the next-best carrier that serves it. Foundational; nothing else matters if the order doesn't get delivered.

### 2. Zone × cost

Rule: within serviceable carriers, route to the one with the lowest contracted cost for that zone × weight slab. This captures most of the per-shipment cost saving.

### 3. Category × carrier strength

Rule: for high-return categories (apparel, footwear), prefer reverse-strong carriers. For high-AOV time-sensitive, prefer premium-SLA carriers. Adds 3–5 percentage points of unit-economics improvement.

### 4. Historical SLA on that lane

Rule: weight carrier choice by their 30-day first-attempt success rate on that origin-destination pair. Catches lane-specific carrier issues that average rates don't surface.

### 5. Capacity and SLA caps

Rule: if a carrier has hit a daily volume cap or is showing degraded SLA on the day, divert overflow to the next carrier. Critical during festive peaks.

## How do you build a zone-based allocation matrix?

A practical 5-zone × N-carrier matrix.

For each zone (Local, Zonal, Metro, ROI, Special), rank your contracted carriers by cost. Then rank by historical SLA reliability for shipments to that zone. The default allocation per zone is the carrier that wins on cost; the fallback is the next-strongest carrier on cost+SLA blended.

| Zone | Primary (cost-driven) | Secondary (reliability fallback) | Tertiary (capacity fallback) |
|---|---|---|---|
| Local | Carrier A | Carrier B | Carrier D |
| Zonal | Carrier A | Carrier C | Carrier B |
| Metro | Carrier B | Carrier A | Carrier C |
| ROI | Carrier C | Carrier A | Carrier D |
| Special | Carrier D | Carrier C | Carrier A |

Refresh this matrix monthly based on the previous month's performance data.

For zone-wise pricing inputs across your carrier panel, the [shipping rate calculator](/tools/shipping-rate-calculator) compares 15+ carriers on the same shipment so the matrix is data-driven, not opinion-driven.

## How do you layer category and SLA rules on top?

Three layers stack on the zone matrix:

- **Category override**: high-return categories (apparel, footwear, jewelry) override the cost-primary allocation to use the reverse-strongest carrier for that zone. The cost premium is recovered in lower true cost on returns.
- **SLA override**: orders tagged "priority" (loyalty tier, high-AOV time-sensitive) override default to the premium-SLA carrier for that zone, regardless of cost.
- **COD risk override**: high-risk COD orders (new buyer, low-density pincode, AOV outlier) override to a carrier with strong COD verification and re-attempt workflows.

Most well-run mid-volume brands run 3–5 overrides. More than 8 starts to break operational maintainability.

## How do you operationalize this without drowning in complexity?

Three implementation patterns.

### Pattern 1: manual allocation (small scale)

For brands at <300 orders/day, a simple zone-to-carrier mapping in a spreadsheet works. Ops manually allocates each manifest. Slow but viable.

### Pattern 2: rule-based engine in your OMS

For 300–3,000 orders/day, build allocation rules into your order management system. Each order is routed by code based on zone + category + AOV. Implementation: 2–4 weeks of engineering.

### Pattern 3: aggregator-managed allocation

For 1,000+ orders/day, an aggregator platform manages allocation dynamically — including carrier-specific capacity, real-time SLA, and category-aware routing. No internal engineering required. ShipPrime works this way.

## What metrics should you track to refine the mix?

Six metrics, reviewed monthly.

1. **Cost per delivered shipment by carrier by zone.** Spot drift and renegotiate where needed.
2. **First-attempt delivery rate by carrier by zone.** Drives the SLA fallback rules.
3. **NDR rate by carrier.** Carriers with rising NDR get less allocation until resolved.
4. **RTO rate by carrier × category.** Apparel RTO from Carrier X over time tells you whether the reverse-pickup workflow is healthy.
5. **Customer NPS by carrier.** Customer-facing satisfaction by which carrier delivered.
6. **Capacity headroom.** During festive, you need to know how much daily capacity you can push to each carrier without breaking SLA.

The brands that hit single-digit RTO and predictable D+ have a closed-loop process: measure → adjust allocation → re-measure.

## What's the biggest carrier mix mistake?

Three common ones.

1. **"Cheapest carrier wins" without modeling reverse.** Apparel brands picking the cheapest forward carrier and discovering 30% higher total cost after reverse and RTO is the classic failure.
2. **Sticky single-carrier defaults from early-stage decisions.** A brand that started on one carrier at 50 orders/day and is now at 5,000 orders/day on the same single carrier is leaving 15–20% on the table.
3. **Too many carriers, no rules.** A brand using 9 carriers with no allocation rules just spreads cost without optimizing.

The fix is the same in all three cases: rebuild allocation with explicit zone × category × SLA rules.

## How does ShipPrime handle carrier mix?

ShipPrime allocates each order across 15+ courier partners based on the rules described above — pincode serviceability, zone × cost, category strength, historical SLA, and capacity. The allocation runs dynamically per order, not on a static carrier-default basis.

For ops teams, the dashboard surfaces allocation performance by carrier × zone × category, with monthly drift alerts when a carrier's SLA or cost moves materially. [NDR management](/features/ndr-management) and tracking workflows run uniformly across carriers, so the brand maintains one process regardless of how many carriers are in the mix.

The practical effect: brands typically save 12–20% on true cost per delivered shipment compared to single-carrier defaults, without adding operational complexity.

## Frequently Asked Questions

**Why do D2C brands use multiple courier partners?**
Because no single carrier wins every lane. Multi-carrier allocation optimizes per-zone and per-category economics, reduces single-carrier SLA-breakage risk, and improves the per-delivered cost by 12–25%.

**How many couriers should a D2C brand use?**
At sub-100 orders/day: 1–2. At 100–1,000: 3–4. At 1,000–10,000: 4–6. Above 10,000: 5–8. More carriers add operational complexity faster than gain.

**What's the easiest carrier allocation rule to start with?**
Zone-based cost optimization. For each of the 5 zones (Local, Zonal, Metro, ROI, Special), pick the carrier with the lowest contracted cost. Add category and SLA overrides as the mix matures.

**Should I use an aggregator to manage carrier mix?**
Aggregators eliminate per-carrier integration overhead and provide dynamic allocation across 15+ carriers without internal engineering. For brands below 10,000 orders/day, aggregators usually outperform direct multi-carrier setups on cost and ops complexity.

**How often should I re-evaluate my carrier mix?**
Monthly performance review of cost and SLA by carrier × zone. Quarterly allocation-rule refresh based on the data. Don't change rules weekly — that creates noise — but don't lock in for years.

**What's the biggest risk of single-carrier shipping?**
SLA-breakage risk during festive or operational disruptions, and per-zone cost leakage (paying the loser's rate on lanes where another carrier wins). Both compound over time.

## Closing Thought

Carrier mix is the unsexy but high-impact operational discipline that compounds month after month. Start with zone-based cost rules, layer category and SLA overrides as you scale, and measure performance monthly. A 6-week investment in mix design typically pays back through reduced shipping cost over the rest of the year.

---

Want dynamic carrier allocation across 15+ couriers? [Start a free ShipPrime account](/register) or [see ShipPrime pricing](/pricing).

Carrier mix strategy for Indian D2C brands. How to allocate orders across multiple couriers by zone, SLA, category, and cost — a 2026 playbook.

Carrier Mix Strategy for D2C: How to Allocate Orders Across Couriers

# True Cost Per Shipment for D2C: Rate, RTO, COD, Packing in 2026

True cost per shipment for an Indian D2C brand is rarely the number printed on the courier's rate card. It's the rate plus a stack of compounding costs — RTO, COD handling, packing, reverse, weight disputes, and write-offs — and most brands under-count by 25–45%. That gap is where margin quietly disappears.

This guide walks through the full true-cost calculation, with practical math you can run on your own orders this week.

## What is true cost per shipment?

True cost per shipment is the **fully loaded delivered cost of one successful order**, including:

- Forward freight (base rate + fuel surcharge + GST)
- COD handling fees
- Allocation cost of RTO freight (averaged across delivered orders)
- Reverse pickup cost (averaged across delivered orders)
- Packaging cost (carton, mailer, filler, tape, label)
- Working capital cost on COD remittance delay
- Customer-experience cost (CX time, refunds, replacements)
- Inventory write-offs from RTO/reverse damage

The number that matters for unit economics is total annualized shipping spend divided by total delivered shipments — not the per-shipment rate from your contract.

## Why does the rate card understate true cost?

Six structural reasons.

1. **RTO is not free.** Every RTO costs forward freight + return freight + repackaging + inventory write-off risk. A 10% RTO rate adds roughly 20–25% to per-delivered-order cost.
2. **Reverse pickup is real volume.** A 15% return rate means 15% of forward orders carry an additional reverse freight charge.
3. **COD fees compound.** COD share of 50% + COD fee of ₹40 = ₹20 added to the average shipment cost.
4. **Packaging adds up.** ₹8–₹15 per shipment in cartons, mailers, fillers — easy to overlook on a single shipment, material in aggregate.
5. **Working capital cost on COD remittance.** A D+15 cycle on ₹8 lakh/day pipeline locks ₹1.2 crore; at 12% cost of capital, that's ~₹14 lakh/year.
6. **Weight disputes and surcharges.** Volumetric corrections, fuel surcharge volatility, oversize handling fees rarely modeled at the contract stage.

## How do you calculate true cost per shipment? Step by step.

A worked example for a hypothetical D2C brand at 1,000 orders/day, ₹800 AOV, apparel category.

### Step 1: Forward freight per shipment

Assume average chargeable weight 0.7 kg, average zone mix landing on a ₹55 surface express rate. Add 18% GST = **₹65** per forward shipment.

### Step 2: RTO cost allocated to delivered orders

RTO rate: 12% on COD, 4% on prepaid. COD share: 55%. Blended RTO rate: (0.55 × 0.12) + (0.45 × 0.04) = **8.4%**. RTO cost per RTO event: ₹65 forward + ₹120 return + ₹15 repacking = **₹200**. Per-delivered allocation: (0.084 / 0.916) × ₹200 = **₹18 per delivered shipment**.

### Step 3: Reverse pickup cost allocated to delivered orders

Return rate: 22% of delivered apparel orders. Reverse pickup cost: ₹70 per pickup. Per-delivered allocation: 0.22 × ₹70 = **₹15 per delivered shipment**.

### Step 4: COD handling fee allocated

COD share: 55%. COD fee: ₹40 per COD order. Per-delivered (across all orders): 0.55 × ₹40 = **₹22 per delivered shipment**.

### Step 5: Packaging cost

Carton, mailer, filler, tape, label: ₹10 per shipment. **₹10 per delivered shipment**.

### Step 6: Working capital cost on COD

55% × 1,000 orders × ₹800 = ₹4.4 lakh COD pipeline/day. D+7 cycle = ₹30.8 lakh locked. At 12% cost of capital: ₹3.7 lakh/year = ~₹10/day = **₹0.01 per delivered shipment** (small at this scale).

### Step 7: CX cost from delivery issues

Estimate: 8–12% of orders generate one CX ticket; ₹30 fully loaded cost per ticket. Per-delivered: ~**₹3**.

### Step 8: Total true cost per delivered shipment

₹65 + ₹18 + ₹15 + ₹22 + ₹10 + ₹0.01 + ₹3 = **₹133 per delivered shipment**.

The published rate was ₹55. True cost is 2.4× that. Without RTO + reverse + COD modeling, this brand thinks shipping is 6.9% of AOV; it's actually 16.6%.

## What changes the true cost most?

Six levers, ranked by typical impact.

1. **RTO rate.** Cutting RTO from 12% to 6% saves roughly ₹9 per delivered shipment in this example — 7% margin uplift.
2. **Reverse pickup rate.** Reducing returns from 22% to 16% saves roughly ₹4 per delivered shipment.
3. **COD share.** Shifting 10 points of share from COD to prepaid removes ₹4 per delivered shipment in COD fees and unlocks working capital.
4. **Forward freight per shipment.** Multi-carrier allocation typically saves 10–18% on forward freight — ₹6–₹12 per shipment in this example.
5. **Packaging.** Right-sized cartons and poly mailers can reduce volumetric weight charges by 15–25% on relevant SKUs.
6. **Working capital cycle.** Cutting D+15 to D+2 on COD remittance frees up substantial cash; small per-shipment impact at lower scale, material at scale.

The biggest opportunity for most brands is RTO reduction, followed by carrier mix optimization.

## Should I model true cost per category and per zone?

Yes. The per-category breakdown matters more than the aggregate. Apparel and footwear carry 20–35% return rates that wreck unit economics if not modeled. Beauty and FMCG have low returns but higher COD-rejection risk on new buyers.

Per-zone matters too. Tier-3 ROI costs more per delivered shipment in every line item — higher RTO, longer cycle, higher forward freight. A brand reporting blended 12% shipping-to-revenue might actually be 8% in metros and 19% in Tier-3.

For zone-and-category modeling, the [shipping rate calculator](/tools/shipping-rate-calculator) gives you the rate component across 15+ carriers. You add the RTO and reverse layers from your own historical data.

## What does a healthy shipping-cost-to-revenue ratio look like for D2C?

Directional benchmarks vary by category and AOV:

| Category | Healthy shipping-cost-to-revenue |
|---|---|
| Apparel (₹800–₹1,500 AOV) | 14–18% |
| Footwear (₹1,000–₹2,500 AOV) | 12–16% |
| Beauty / personal care (₹500–₹1,200 AOV) | 10–14% |
| Jewelry fashion (₹500–₹2,000 AOV) | 12–15% |
| Electronics (₹1,500+ AOV) | 8–12% |
| FMCG / nutraceuticals (₹400–₹800 AOV) | 11–15% |
| Home decor (₹800–₹2,500 AOV) | 14–18% |

If your number is outside this band, the gap is usually in RTO, reverse, or carrier mix — not in your contracted rate.

## How does ShipPrime fit into the true-cost calculation?

ShipPrime affects six of the seven cost layers:

- **Forward freight** — aggregator-negotiated rates start at ₹19/500g; typically 10–25% lower than direct list rates for sub-10K-orders/day brands.
- **RTO cost** — automated NDR re-attempt logic typically cuts RTO rates by 25–40%, reducing the per-delivered allocation.
- **Reverse pickup** — competitive reverse pricing via the reverse-strong carriers on the panel.
- **COD handling** — standard COD fees apply; remittance on D+2 cycle reduces working capital cost materially.
- **CX cost** — unified tracking timeline and [NDR management](/features/ndr-management) cut CX ticket volume by 20–35%.
- **Working capital** — D+2 COD remittance unlocks cash that's otherwise locked for D+7 to D+15.

Packaging and inventory write-offs are on you to optimize; the rest is structural.

## Frequently Asked Questions

**What is true cost per shipment for D2C?**
The fully loaded delivered cost of one successful order — forward freight, RTO allocation, reverse pickup, COD fees, packaging, working capital, CX. Typically 1.8–2.5× the published rate-card number for Indian D2C brands.

**How do I calculate my actual shipping cost?**
Total annualized shipping spend (all line items) divided by total delivered shipments. Include RTO freight, reverse pickup, COD handling, packaging, and any working capital cost on COD remittance.

**What's the biggest hidden cost in D2C shipping?**
RTO usually. A 10% RTO rate adds 20–25% to per-delivered cost. Reverse pickup for high-return categories is a close second.

**What's a healthy shipping-cost-to-revenue ratio for D2C in India?**
Varies by category — 10–18% across most D2C categories. Apparel and home decor sit higher (14–18%); electronics lower (8–12%). Outside this band, the gap is usually RTO or carrier mix.

**Can I reduce RTO costs without harming conversion?**
Yes — tight NDR workflows, COD verification on flagged orders, and address validation at checkout reduce RTO without affecting overall conversion. The brands hitting single-digit RTO have automated, not pulled levers that cut buyer experience.

**Does multi-carrier allocation reduce true cost per shipment?**
Yes — typically 10–18% reduction in forward freight, plus another 3–5 percentage points from carrier-specific RTO and reverse-pickup advantages. The total true-cost impact is usually 12–20%.

## Closing Thought

The rate card is just the starting line. True cost per shipment includes everything that touches an order from manifest to refund. Brands that measure and manage all seven layers of cost — not just freight — are the ones whose unit economics survive scale.

---

Want to model true cost across 15+ couriers? [Start a free ShipPrime account](/register) or [see ShipPrime pricing](/pricing).

True cost per shipment is more than freight. Calculate the full economics — rate, RTO, COD, packing, reverse — for Indian D2C brands in 2026.

True Cost Per Shipment for D2C: Rate, RTO, COD, Packing in 2026

# 3PL vs Shipping Aggregator vs In-house Fulfillment for D2C

A fulfillment model decides who picks, packs, ships, and resolves your orders — and which line items on your P&L are fixed, variable, or hidden. For a D2C brand in India choosing between a 3PL, a shipping aggregator, and in-house fulfillment, that decision quietly shapes margins, cash flow, and how fast you can scale during peak weeks.

## What does each fulfillment model actually do?

**Third-party logistics (3PL)** is a single external partner that stores your inventory in their warehouse, picks and packs each order, and hands it off to a courier. You pay storage fees, pick-pack fees, and shipping fees — usually with a minimum monthly commitment. The 3PL operates a WMS (warehouse management system), and you get a dashboard view of stock and orders.

**A shipping aggregator** is a software layer that doesn't store your inventory. It plugs into your store, gives you access to multiple courier partners through one dashboard, picks the best courier per order based on rate and serviceability, and handles AWB generation, tracking, NDR resolution, and COD remittance. You still pack the orders yourself, or in your warehouse, or at a 3PL.

**In-house fulfillment** is when you (or your team) store inventory in a space you control — a garage, a small warehouse, a leased unit — and pack each order before handing it to a courier. You either book each courier directly or use an aggregator to route shipments.

The three models aren't strict alternatives. Many brands run an aggregator on top of in-house packing, and some 3PLs let you bring your own carrier accounts on the side. The real question is *who owns each step* and *which costs become fixed vs variable*.

## How do the three models compare on cost?

The cost stack looks similar at first glance and very different by the time you trace each line item. The table below summarizes where each model places the spend.

| Cost line | In-house | Shipping aggregator | 3PL |
|---|---|---|---|
| Warehouse rent | Yours (₹15–₹80/sq ft/mo by city) | Yours | Bundled into per-order fee |
| Pick & pack labour | Yours (₹15–₹40/order at scale) | Yours | ₹15–₹30/order incl. handling |
| Packaging material | Yours | Yours | Yours or bundled (varies) |
| Courier rates | Direct contracts, volume-dependent | Pooled aggregator rates | 3PL's contracted rates |
| Tech / dashboard | DIY or ad-hoc | Included | Usually included |
| Min monthly commitment | None | Usually none | ₹15,000–₹80,000+ |
| Onboarding time | Zero | Hours to two days | Two to six weeks |
| Switching cost | Low | Low | High (inventory transfer) |
| Cash-flow impact | Per-courier COD cycle (D+2 to D+15) | Aggregator's remittance SLA | 3PL remittance + invoice cycle |

A few patterns stand out. In-house and aggregator setups give you the lowest fixed costs and the fastest exit if a vendor underperforms. 3PLs absorb operational headcount but add a monthly commitment and a layer between you and the courier — useful at scale, expensive too early.

## When does each fulfillment model make sense?

Volume bands aren't strict cutoffs, but they capture the points where each model usually breaks down.

**Under 100 orders/day — in-house with an aggregator.**
At this scale, a 3PL's minimums eat your unit economics. A 200–400 sq ft space, two pickers, and a [multi-courier routing](/features/multi-carrier) layer covers you. You retain product control: custom inserts, hand-written notes, hand-checked QC — assets that compound for an early brand.

**100–500 orders/day — in-house plus aggregator, or a hybrid.**
This is the trickiest band. In-house keeps you nimble; a 3PL starts looking attractive for warehousing once your SKU count climbs. A common hybrid: keep slow-moving SKUs in-house and push fast-moving SKUs to a 3PL closer to your top demand zones.

**500–5,000 orders/day — 3PL or a regional hub model.**
Manual pick-pack at this scale needs six to fifteen people in a single warehouse. Either you run that operation yourself (in-house at scale) or you outsource to a 3PL that already has the pickers, racking, and WMS. Aggregator software still sits on top for courier routing.

**5,000+ orders/day — multi-node, almost always 3PL or owned warehouses.**
At this volume, zone-based shipping cost becomes the dominant lever. Most brands move to two or three regional warehouses (north, south, sometimes east or west) — either through a 3PL with multiple nodes or by building owned capacity.

## What are the hidden trade-offs in each model?

The brochure version of each model is clean. The reality has wrinkles.

- **3PLs charge you for what you don't see.** Storage overage, additional pick fees beyond a tier, returns processing, and "exception handling" can collectively add 8–18% to the per-order quote. Read the line items, not just the headline rate.
- **Aggregators are only as good as their courier panel.** Fewer than ten couriers usually means dead pincodes and forced routing to a single carrier in some regions. Breadth matters: ShipPrime, for example, runs 15+ courier partners across 18,700+ pincodes.
- **In-house breaks during festive weeks.** A pick-pack team built for 200 orders/day can't ramp to 800 overnight. Plan staffing six to eight weeks before Diwali or BFCM — or pre-stock a 3PL as overflow.
- **Switching a 3PL is painful.** Moving inventory between 3PLs takes two to four weeks of partial downtime and usually a one-time transfer fee. Negotiate exit terms when you sign in, not when you leave.

If you want to model the per-order economics of switching, you can [compare slab rates](/tools/shipping-rate-calculator) before committing.

## How do you transition between fulfillment models without breaking ops?

The most common transitions are in-house to 3PL (scaling up) and 3PL to in-house with aggregator (cost cuts). Both work, but rushing the cut-over usually does more damage than running both for a few weeks.

1. **Freeze new SKUs at the old node for two weeks before cut-over.** Don't fight a transition while also adding inventory complexity.
2. **Move ABC analysis first — top 20% of SKUs to the new node.** They represent 70–80% of orders. Once they're stable, follow with the rest.
3. **Run dual-fulfillment for one to two weeks.** Route a portion of orders to the new node while the old one handles the rest. Watch order-to-ship SLA, NDR rate, RTO rate, and customer-reported issues.
4. **Reconcile rate cards in writing.** Storage rates, per-order pick fees, return handling — get every line item documented before you stop shipping from the old node.
5. **Unify the tracking experience.** Customers shouldn't see two different tracking flows for the same brand in the same week. Aggregators help here because the branded tracking page is consistent across couriers.

## How ShipPrime fits in this picture

ShipPrime is a shipping aggregator — not a 3PL. You keep your inventory wherever it makes sense for your business, and ShipPrime layers over the top to handle courier selection, AWB generation, NDR management, COD remittance, and customer tracking. The platform connects to 15+ courier partners across 18,700+ pincodes, with rates starting at ₹19 per 500 g and D+2 COD remittance — which usually compares well against direct courier contracts and 3PL-bundled rates at the same volume.

If you're running in-house fulfillment today and want to add multi-carrier routing without changing how you pack, the Shopify and WooCommerce integrations get you live in hours. If you've already signed up with a 3PL, you can still use ShipPrime as the shipping layer on top — your 3PL packs, ShipPrime routes — as long as your 3PL contract allows you to bring your own carrier panel.

## How do I decide between a 3PL and a shipping aggregator?

A 3PL takes inventory and operations off your plate at the cost of fixed monthly commitments and a layer between you and the courier. An aggregator keeps fulfillment in your hands and gives you software plus multi-courier reach with no monthly minimum. The simpler heuristic: if your bottleneck is pick-pack labour or warehouse space, lean 3PL. If your bottleneck is shipping cost, courier serviceability, or COD cash flow, lean aggregator.

You don't have to pick one for the whole journey. Most D2C brands in India start in-house with an aggregator, add 3PL nodes regionally once they cross 500 orders/day, and keep the aggregator running as the shipping layer across both. The decisions are sequential, not exclusive.

## Frequently Asked Questions

**Is a 3PL cheaper than an aggregator?**
Per-order, a 3PL is usually pricier because it bundles labour and warehousing into the fee. A 3PL becomes cheaper than in-house only once you cross the labour-and-rent threshold where running your own warehouse costs more than the 3PL's pick-pack fee. An aggregator is software, not warehousing, so it competes on shipping rates and operational efficiency — not on storage cost.

**Can I use a shipping aggregator if I run my own warehouse?**
Yes — that's the most common setup. The aggregator sits between your order management system and the courier network. You pack orders in your warehouse, the aggregator picks the right courier per order based on rate and serviceability, and handles tracking, NDR, and COD remittance.

**What's the minimum monthly volume to justify a 3PL?**
Usually around 4,000–6,000 orders/month. Below that, 3PL minimums and per-order pick fees outpace what in-house labour would cost you. Above that, the math flips — 3PL pick-pack is more efficient than what you can build alone.

**Do I lose data control when I move to a 3PL?**
Partially. The 3PL owns inventory location, packing visibility, and pick performance. A good 3PL exposes this through dashboards and APIs, but the underlying data lives in their WMS. An aggregator on top preserves your shipping-side data — AWBs, rates, NDR, RTO — regardless of which fulfillment model sits underneath.

**Can I run both a 3PL and in-house fulfillment for the same brand?**
Yes, and many growing brands do. The typical split: fast-moving SKUs at a 3PL closer to demand, custom or low-velocity SKUs in-house. An aggregator unifies the shipping layer across both nodes so customers see one consistent tracking experience.

**What hidden fees should I watch in a 3PL contract?**
Storage overage charges (per pallet or per sq ft beyond a slab), return-handling fees, "exception handling" charges for damaged or misrouted items, and account management fees. Ask for an itemized invoice template before signing, not after.

## Closing Thought

Fulfillment is not a single decision — it's a series of them, made at different volumes and in different seasons. The brands that get it right rarely commit to one model forever. They start lean, layer software on top, and add infrastructure only when the unit economics demand it.

---

**Ready to add multi-courier routing on top of your current fulfillment setup?** [Start shipping in under 30 minutes](/register) or see [transparent per-shipment pricing](/pricing) — no setup fees, no monthly minimums.

Want more context first? Read [how aggregators reduce logistics costs](/resources/blogs/how-shipping-aggregators-reduce-logistics-costs) or the [D2C guide for India](/resources/blogs/d2c-guide).

Compare 3PL, shipping aggregator, and in-house fulfillment for D2C brands in India — costs, control, and how to pick the right model as you scale.

3PL vs Shipping Aggregator vs In-house Fulfillment for D2C

# 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](/tools/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](/features/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](/features/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](/register) or [see ShipPrime pricing](/pricing).

A practical framework to evaluate courier partners for Indian D2C — pincode coverage, SLA, NDR/RTO, COD, tech, and dispute process. 2026 guide.

ShipPrime Blog