“I’ll tip when it gets delivered” sounds reasonable from the customer’s side. You want to see the service first. I understand that. The problem is that I have to decide whether to take the work before I can provide the service.

That timing gap is the part that gets lost in a lot of tipping arguments. We’re talking about the same money at two different points in the process.

I can’t put an intention into the calculation.

When I look at an offer, I’m comparing the pay I’m shown with the time and mileage involved. An extra payment that might arrive later isn’t something I can safely use to cover those costs now.

From my experience, saying a tip will come later doesn’t always mean one arrives. That doesn’t make every customer dishonest. It does mean that hoping for a later tip is different from evaluating the offer in front of me.

A customer might have every intention of handing over cash. Another might forget. Another might decide against it. Before accepting the job, I can’t know which situation I’m looking at. I still have to decide whether the work is financially reasonable.

The question before acceptance is: can I afford to take this job on the offer I can see?

That’s why drivers use the word “bid.”

I use that word to explain the decision, not to pretend there’s a formal auction running in the app. Where an upfront tip is reflected in the offer, it can affect whether a driver sees the job as worthwhile.

Spark’s own guidance distinguishes estimated tips from confirmed tips. Its offer guidance also says tips can change before confirmation. So I’m not claiming the initial number is an unconditional promise. I’m explaining why the information available at acceptance matters.

A later tip is still appreciated.

This isn’t an argument against cash or an extra thank-you after a good delivery. It’s an explanation of why a driver may pass on a low offer even though a customer would have tipped later.

It also isn’t a promise that an upfront tip buys a specific delivery time or guarantees perfect service. Store issues, traffic, availability and app decisions can affect the order. A real service problem still deserves an honest response through the platform.

We need to be looking at the same decision.

Customers are often asking, “Was the service good enough to deserve extra?” Drivers evaluating an offer are asking, “Does this cover the work I’m about to do?” Until both sides recognize that difference, we’ll keep answering different questions.

That’s what I want this site to make visible. Not a demand to trust every driver blindly. An invitation to understand the decision a driver has to make before your groceries reach the door.

Platform reference

Spark Driver’s guide to offers and estimated tips ↗

Platform information reviewed October 30, 2026. This is independent commentary, not an official Spark publication.
Put yourself in the driver’s seat ↗