Employed Riders or Gig Riders: What the Difference Actually Does to Your Delivery Numbers

Most D2C brands choose a delivery partner on two numbers: the rate card and the promised SLA. Neither tells you who will be on the bike at 8 pm on a sale day, or whether that rider will still be around next quarter.

That is decided by a variable most ops reviews never examine: whether the rider is an employee or a gig worker. It looks like an HR detail. It behaves like an operating lever, sitting underneath peak capacity, first-attempt delivery, NDR, RTO and SLA adherence.

What is the difference between an employed delivery rider and a gig rider?

An employed rider works for the delivery operator on payroll, with defined shifts, a fixed salary and statutory employee benefits. A gig rider earns per task outside that relationship and decides when, and whether, to log in.

Indian law now draws this line explicitly. The Code on Social Security, 2020 describes gig workers as people who earn outside the traditional employer-employee setup, and the four labour codes took effect on 21 November 2025. Under the codes, aggregators must contribute 1 to 2 percent of annual turnover towards gig and platform worker welfare, capped at 5 percent of what they pay those workers.

Formal recognition gives gig riders a social security route, but it does not create a rostered workforce. For a brand, the defining difference is who controls the shift.

Why does the rider employment model change delivery capacity at peak hours?

Gig capacity is a forecast of voluntary behaviour, while employed capacity is a roster. That distinction bites hardest at the moments brands care about most: evening peaks, sale days and festive weeks.

Some of the best recent Indian data on gig delivery work comes from IDinsight's study of two-wheeler delivery drivers on a location-based platform. Only 23 percent of drivers worked more than 8 hours a day, only 29 percent kept consistent daily hours, and 33 percent worked solely in their free time. Average tenure on the platform was about 13 months.

This is not a criticism of gig workers; flexibility is why many choose the work. But it makes a gig pool's capacity at 8 pm on a Friday a probability, and when every platform needs riders in the same hour, it goes to the highest incentive.

Incentives are also a weaker lever than they look. A study of driver attrition on a last-mile delivery platform, published in Manufacturing & Service Operations Management, found that regular pay does more for retention than subsidy pay, and that the effect of subsidies fades faster as tenure grows.

Speed is set by inventory placement and kept by capacity. When the labour ministry asked quick commerce platforms to drop 10-minute branding in January 2026, the platforms themselves argued that short timelines come from warehouses located close to consumers rather than pressure on riders. Placement sets the ceiling; reliable riders decide whether you reach it. And a missed promise costs more than a slower one kept, as we examined in whether customers want 10-minute delivery or a promise that holds.

How does the rider model affect first-attempt delivery, NDR and RTO?

First-attempt delivery depends on what the rider does at the door, and that behaviour follows accountability. A rider who owns the same area tomorrow has a reason to make the extra call; one with no continuity has a reason to move on.

The clearest evidence comes from research published in Management Science using data from a leading Indian last-mile firm. It examined fake remarks, where an associate records "customer unavailable" without reaching the address. The misconduct created a spillover productivity loss, cutting the next day's successful deliveries by 1.60 percent and first-time-right deliveries by 1.86 percent.

Two cautions. The associates in that study were contractual, and the research does not compare employment models head to head. It shows that rider conduct moves first-attempt numbers, not that any one model eliminates misconduct.

What the employment model changes is the ability to act: auditing NDR reasons rider by rider, retraining, and holding one person accountable for one zone over time. That is the difference between recovering failed deliveries before they become RTOs and simply absorbing them.

The arithmetic of a failed first attempt

Cost per successful delivery = cost per delivery attempt ÷ first-attempt success rate

At an identical cost per attempt, a fleet converting 90 percent of first attempts pays about 1.11 times the attempt cost for every delivered order. A fleet converting 80 percent pays 1.25 times. That is 12.5 percent more per delivered order, before the reverse leg on RTOs. The arithmetic is simplified (it assumes every attempt costs the same), but it shows why the cheaper rate card often loses where it matters.

Does rider tenure improve delivery performance?

Tenure helps, but only inside a managed system. Research on last-mile routing shows that experienced drivers carry tacit knowledge of roads, traffic and parking that optimization models miss, and doctoral research on millions of crowdshipping orders found that driver familiarity improves delivery time performance.

The Management Science study adds a counterintuitive twist: the damage from fake remarks worsened when the associate knew the area well. Familiarity without oversight entrenches bad habits as efficiently as good ones.

That is why SOPs matter more than tenure alone. OTP handover, COD handling, tamper-evident packaging and cold-chain discipline can be written down, but only a fleet that repeatedly trains and audits the same riders can enforce them. On a shared gig pool, or on a grocery app's own fleet, your SOPs become suggestions rather than standards.

When does a gig rider model fit, and when does an employed fleet win?

The right model depends on your order profile, not on ideology. Gig pools absorb unpredictable volume without fixed cost; employed fleets deliver consistency where a failed or mishandled order is expensive.

Read the table as a spectrum. Most brands running fast delivery on their own website sit in the right-hand column for their most important orders.

What should you ask a delivery partner about its riders?

Ask for numbers that expose the rider model, not just the headline SLA. A partner that cannot answer these at rider or cohort level is managing averages, not a fleet.

These questions sit alongside the checks in how to tell whether a fulfilment partner's SLA is actually good and the fulfilment KPIs every D2C ops lead should track.

How Zippee builds rider consistency into fulfilment infrastructure

Zippee onboards its delivery partners as full-time employees, not gig workers, because the metrics above are infrastructure outcomes rather than HR outcomes. The same riders work the same dark store zones, are trained on each brand's handling SOPs, and stay accountable for first-attempt outcomes over time.

That fleet runs on Zippee's dark store network, which serves 100+ consumer brands across 21+ cities with 30-minute, 60-minute and same-day delivery. Orders are placed on the brand's own website, so the customer relationship stays with the brand and its handling standards stay standards.

The rider model is a delivery metric in disguise

Brands spend months tuning inventory placement and delivery promises, then hand the final stretch to a workforce model they never examined. That model decides whether capacity shows up at peak, whether failed attempts get recovered, and whether your SOPs survive contact with the doorstep. Measure it like any other input.

If you’re ready to turn your fulfillment into a competitive advantage, join our waitlist.