What a delivery fee really needs to cover

A delivery fee looks simple to a customer: one number at checkout. Behind it is a chain of work that can include preparation, pickup waiting, travel, support, payment processing, and sometimes a failed delivery.

For an operator, the useful question is whether the revenue associated with an order covers the costs that order creates. Start with a small worksheet you can explain to your team before building a more elaborate model.

Separate basket value from delivery revenue

The money collected at checkout is not automatically yours to spend on delivery. Some of it may belong to the merchant. Identify the delivery fee, any agreed merchant contribution, and any other revenue that actually belongs in your calculation.

Write down how promotions are funded. A customer discount paid by the merchant has a different effect on your delivery contribution from the same discount funded entirely by the operator. Make the funding arrangement explicit rather than leaving it hidden in a campaign total.

Use a completed-order worksheet

The following example is hypothetical and is included to show the calculation. It is not a suggested fee, payout, or profitability forecast.

An operator-funded ₹15 offer would take that contribution to minus ₹2. The worksheet still excludes fixed costs such as office expenses, regular salaries, and subscriptions. Use your own records and accounting treatment to decide which costs belong in each category.

Count the work that does not end in a completed order

A cancelled order can still involve preparation, rider travel, support time, or a payment adjustment. Record these cases rather than assigning every unsuccessful order a cost of zero.

Likewise, a failed delivery may involve a return journey or another attempt. Keep the reason visible: an incorrect address, an unreachable customer, a service boundary mistake, and a damaged order need different operational responses.

Review the costs of these incidents across the operating period. A worksheet for a smooth order is useful, but it does not describe the whole business if difficult orders are excluded.

Test the difficult parts of the service area

Distance is one input. Time spent reaching the shop, waiting for collection, finding a building entrance, and completing the handoff also matters when reviewing rider work.

Compare actual order journeys by area and operating window. If a particular zone regularly creates long collection waits, a higher distance fee may not address the underlying problem. You may need better preparation updates or a different assignment routine.

Before introducing a new pricing rule, test how it appears at checkout. Make any distance charge, minimum order condition, or promotion limit understandable before payment. A fee that surprises the customer can create support work of its own.

Review offers as experiments

Give each offer a purpose, a funding source, a duration, and a review date. Decide what you want to learn: whether people try the service, return without the offer, or order at a different time.

Look at completed orders and the contribution remaining after the offer, alongside cancellations and support issues. Avoid celebrating order volume without checking what those orders required to fulfil.

• Identify which checkout revenue belongs to the delivery operation.
• Record payouts and other variable costs using actual data.
• Include unsuccessful orders in the operating-period review.
• Make promotion funding and limits explicit.
• Check that customers understand the price before payment.

A clear worksheet gives operations, support, and commercial teams a shared starting point. Explore Delivery Stack to discuss how your delivery rules and order records should work together.