Shopping

Rain and peak-hour surcharges on delivery apps: a log

Delivery app surge charges rain and peak hour: keep a small log of fee, time, weather and distance for each order and see when extra fees appear.

Editorial illustration for Rain and peak-hour surcharges on delivery apps: a log

To find out when delivery apps charge extra, keep a log for two weeks with the delivery fee, the time, whether it was raining and the distance for each order. Then compare average fees for rainy and clear orders and for peak and off-peak hours. It is a simple way to see a pattern that the bill alone does not show.

What to log

  • Date and time the order was placed.
  • Weather: clear or rain, in one word.
  • Distance shown for the restaurant or store, if the app gives it.
  • Order value before fees.
  • Delivery fee, plus any separate surge, rain or handling line shown on the bill.

A notes page on your phone is enough: one line per order. If the bill splits fees into several lines, add them into one number and keep the breakdown in a note.

A made-up fortnight

Say ten orders over two weeks look like this. The fees are invented to show the method, not to describe what any app charges.

OrderTimeWeatherDistanceFee
Mon1:15 pmClear2.0 km₹25
Tue8:40 pmClear3.5 km₹35
Wed8:10 pmRain3.5 km₹68
Thu11:00 amClear1.5 km₹20
Fri8:30 pmClear4.0 km₹45
Sat9:00 pmRain4.0 km₹82
Sun1:30 pmClear2.0 km₹25
Mon7:50 pmRain2.5 km₹60
Tue12:30 pmClear3.0 km₹30
Thu9:15 pmClear3.5 km₹38

Reading the log

Add up the rainy orders: 68 + 82 + 60 is ₹210 over three orders, an average of ₹70. The seven clear orders come to ₹218 (25 + 35 + 20 + 45 + 25 + 30 + 38), an average of about ₹31. In this made-up fortnight, a rainy order cost more than twice as much in fees. Distance matters too, so compare like with like: the 3.5 km clear order on Tuesday cost ₹35 while the 3.5 km rainy order on Wednesday cost ₹68.

In a sheet, with weather in column C and fee in column E, =AVERAGEIF($C$2:$C$50,"Rain",$E$2:$E$50) gives the rainy average and =AVERAGEIF($C$2:$C$50,"Clear",$E$2:$E$50) gives the clear one. For time, add a column for peak or off-peak that you decide yourself, say after 8 pm, and use the same function.

What can you do with it?

  1. If rainy-evening fees are high, keep a ready-to-cook meal for rainy days.
  2. If late-evening orders cost more, order earlier or collect.
  3. If longer distances cost more, choose nearer places for routine orders.
  4. If a fee suddenly jumps without a reason you can see, check the bill line by line.

How does this fit with your tracker?

A statement shows only the total you paid, not the fee, so the log is where the fee lives. If you track spending through a tool such as SpendixAI, keep the fee log in a sheet and use the tracker for the total spend by month and merchant. The two together tell you how much you spent and how much of that was avoidable extras.

Add the reason for ordering

One more column helps: why you ordered. Tired, rain, guests, forgot to plan, or offer. After two weeks, count the reasons. If rain is behind several of your costliest orders, the fix is a stocked kitchen on wet days, and it will save more than avoiding any particular hour.

When to stop logging

Two weeks is enough to see a first pattern. Continue for a month if you see something odd, then stop. Keep the table, because a rainy season or a festival week might look different and you can run it again for a fortnight.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports