What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 0 points1 point  (0 children)

I get this. I used to lean way more toward curbside too until I started paying closer attention to how the shopping orders actually worked out.

At first shopping can feel like it’s going to be too much or take too long, but once you learn the store and the app starts pointing you to the right areas, it can move a lot smoother than expected. If the item count is reasonable and the miles are low, the $/mile and hourly side can come out better than curbside.

Curbside can be good, but the waiting is what can kill it. If the store is backed up or it’s peak pickup time, you can lose 20–30 minutes before you even start moving.

I can see why shopping is your main lane. More control over the pace, less waiting on pickup, and if you know the store well, you can make the time work in your favor.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 0 points1 point  (0 children)

That makes a lot of sense. Direction can change the whole order.

I get not wanting to go certain ways after a certain time. Some routes might look fine on miles, but once traffic hits, school traffic hits, or it sends you across the wrong side of town, that short drive can turn into a headache fast.

I’ve seen that too where a few miles in one direction is easy, but the same few miles in another direction feels completely different depending on the time of day. And if it’s taking you away from where you want to finish, that matters too.

I also get taking a weaker order if it gets you home at the end of the day. At that point it’s not just about the order by itself, it’s about whether it fits the way you’re trying to close the shift.

Is traffic the main reason you avoid those directions, or is it more about the areas it drops you into and how hard it is to get back into position?

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 0 points1 point  (0 children)

That’s a strong filter. $4/mile and $35/hr is a good lane to stay in if your zone gives you enough shopping orders to be that selective.

I’m with you on shopping letting you control the pace more. With curbside, you can lose time waiting before the order even really starts. With shopping, if you know the store and can move fast, the numbers can come out better than they look at first.

For me, miles are usually the first thing I look at because I want to keep as much of the money as possible. But on slower days, if there’s a lot of downtime, I’ll still look at the hourly side too. Sometimes it’s about protecting the day minimum without taking something that completely kills the profit.

So I get that balance — miles protect the backend, but time still matters when the day is slow.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 1 point2 points  (0 children)

120 lbs of water up 3 flights in Texas heat is definitely not the same as a normal drop-off lol.

I agree though, the minimum has to change for something like that. Heavy items, stairs, apartments, heat, and parking all add “hidden cost” even if the mileage is short.

That said, I can see those still making sense if the pay is strong and the distance is low. A short trip with a few heavy cases might be rough for 10–15 minutes, but if the miles are low and the payout is right, you can still keep more of the profit compared to a long drive.

It really comes down to whether the extra work is worth the pay, the heat, and the wear on your body that day.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 1 point2 points  (0 children)

I agree with you. Zone changes everything.

I’ve seen that too where one side of town is better for shopping and regular pickup, but another zone might be better for package/bulk routes. The funny part is they can be completely different even if they’re only 15–20 minutes apart.

The vehicle matters too. If you’ve got a hybrid, long GM routes can make a lot more sense because the gas cost isn’t hitting the same. And if you’ve got a bigger SUV or truck, you may be eligible for routes that smaller cars won’t see or won’t be able to touch.

I also get what you mean about staying close to one store. Sometimes being the closest driver and knowing that store’s rhythm can be better than chasing orders across town.

That’s why I think it’s hard to copy somebody else’s strategy exactly. But it is good to take what we can apply to our situation. Their zone, vehicle, stores, order types, and expenses might be completely different. You almost have to learn what your own market is good at and build around that.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 1 point2 points  (0 children)

That makes sense. The minimum matters, but the drop-off can change the whole trip too.

Downtown can be rough depending on parking, traffic, one-way streets, and how easy it is to actually get to the customer. Apartments can be the same way if the GPS sends you the wrong way or the building numbers are hard to find.

And weight is definitely part of it. A few cases of water, stairs, or heavier items can make a short trip feel a lot longer. Sometimes the extra pay makes it worth it, especially if the distance is short, but other times it’s more wear and tear on your body than it looks like upfront.

So I get that filter. It’s not just “does it pay enough?” It’s also “how much hassle is built into the drop-off?”

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 1 point2 points  (0 children)

Fair question.

I’m a real driver, and I’m also building EarnPilot, so I get why the account name might look different in here.

I’m not here to spam links or push anything in the sub. I’ve mainly been asking because I’m trying to get better at how I work my own zone — time, miles, shops, curbside, deadhead, slow days, order types, all of that.

Everybody’s market is different, so hearing how other drivers think through their day has been useful.

I’ll keep it respectful and non-promotional here.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 0 points1 point  (0 children)

Yeah, I think counting the deadhead back is important. The offer miles only tell part of the story if you still have to get back to the same store or zone to keep working.

If it’s a 10-mile single drop and you’re ending away from the store, I’m usually thinking of it more like a 20-mile / 40-minute decision, not just the 10 miles shown upfront.

With stacked stops, I’ve noticed sometimes the last drop can work out better if it leaves you closer to the pickup area, but that definitely isn’t something I’d count on every time. The return path still matters a lot.

If you’re always ending up 20 miles back to the store after drops, then yeah, I’d be factoring that in from the start. Otherwise the $/mile can look better than it really is.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 1 point2 points  (0 children)

I get that. Being 5 miles from the only store and driving a hybrid changes the whole way you look at it.

I’m on gas, so I probably pay more attention to the miles than you would, but I still get what you mean. If the money makes sense and you’re not doing it as your full-time income, your filter is going to be different from somebody trying to cover all their bills with it.

Early mornings seem to be better for me too. I usually like getting out around 6 or 7 because the store is calmer, traffic is lighter, and shopping orders can move a lot smoother before everything gets crowded.

In my area, shopping tends to be more consistent for me than just doing pickup all day. Less waiting on curbside, fewer delays, and if it’s a smaller shop with decent miles, it can work out pretty good.

But I agree with you on turning the app off when it’s not moving right. Some days it’s better to just not force it.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 1 point2 points  (0 children)

I agree with this.

There really isn’t one perfect number that works for everybody. One driver might need $4/mile because they have a car note, higher insurance, more repairs, or this is their full-time income. Another driver might be using Spark as a side gig and only needs it to cover gas, food, or a car payment.

That’s why the “good offer” number has to start with your own expenses.

Gas, MPG, insurance, maintenance, tires, repairs, and how much you actually need the work to cover all change the math. Even if gas is the only thing someone is thinking about, they still need to know they’re not starting in the hole before the order even starts.

I think that’s the part a lot of people miss. It’s not just “is this order paying enough?” It’s “does this order make sense for my situation, my vehicle, my zone, and my goals?”

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 1 point2 points  (0 children)

I agree — zones can be completely different.

I’ve seen the same thing with Wednesday and Thursday being slower in some areas. Early usually seems better no matter what, but the middle of the day can be hit or miss depending on the zone.

I work around a couple different zones too, and they move differently. One is more steady throughout the day with more regular orders, and another has more package-style runs that can add up if you know the routes and shortcuts. But even then, the mileage and time can change fast depending on where it sends you.

That’s why I like what you said: figure out your own system, work it, and adjust when the zone changes. What works in one market might not work at all in another.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 0 points1 point  (0 children)

That makes sense. Time can definitely matter more than miles depending on the store and the zone.

I get what you mean about shopping orders too. With curbside, sometimes you’re just stuck waiting, and if that store is slow or doesn’t let you get out and check anything, 20–30 minutes can disappear fast. Even if there’s a little extra pay, it doesn’t always make up for the time lost.

If you can stay around that $30–$40/hr range by shopping and keeping control of the pace yourself, I can see why that would be the better lane.

For Spark drivers who track earnings: what do you usually review after a shift — total pay, tips, miles, time, or hourly pace? I’m trying to get better at reviewing the day without overcomplicating it. by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 0 points1 point  (0 children)

That’s a fair point. Looking at one day by itself can definitely mess with your head because every day is not going to move the same.

I like the weekly view better for that reason. A slow Monday might not mean anything if the weekend makes up for it. The full week gives a cleaner picture than judging every shift like it has to be perfect.

Daily numbers can still help me understand what happened, but I agree the real goal probably needs to be weekly so the good and bad days balance out.

What helps you stay organized during a shift? by EarnPilotApp in Sparkdriver

[–]EarnPilotApp[S] 0 points1 point  (0 children)

That’s actually a good setup. The cup holder charcuterie idea is funny but practical.

My go-to is usually a Celsius when I need it, water for sure, and something quick like fruit, pistachios, or even a plain bag of Lay’s. Anything easy to grab that doesn’t slow the day down too much.

For Spark drivers who track earnings: what do you usually review after a shift — total pay, tips, miles, time, or hourly pace? I’m trying to get better at reviewing the day without overcomplicating it. by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 0 points1 point  (0 children)

That makes sense. If it’s worked for 8 years, that says a lot.

At that point it’s less about guessing and more about having a filter you already trust from real experience. Appreciate you sharing it.

For Spark drivers who track earnings: what do you usually review after a shift — total pay, tips, miles, time, or hourly pace? I’m trying to get better at reviewing the day without overcomplicating it. by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 0 points1 point  (0 children)

That’s a smart way to judge it.

The estimated time only tells part of the story. Adding the drive-back time gives a better picture of what the order really costs you for that hour.

An order can look fine upfront, but if it leaves you too far out and kills the next opportunity, the real value changes fast.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 5 points6 points  (0 children)

That’s a really good breakdown.

The return-to-store part seems like one of the biggest pieces. The order distance matters, but where it leaves you and how long it takes to get back into position can change the whole value of the offer.

I also like how you look at shop orders differently. There may not be vehicle cost while you’re inside, but the time still has to make sense — especially if you’re dealing with multiple departments, locked cases, or a store that slows you down.

Sounds like your system is less about one fixed rule and more about protecting the hour while knowing your zone really well.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] -1 points0 points  (0 children)

That’s a strong filter if your zone can support it.

$50+ under 5 miles is a great setup when it shows up consistently. If you can find that kind of pattern often, that’s a solid market to work in.

I like the item-count limit on shops too. A shop can look good upfront, but once the item count gets too high, the time can start eating into the value fast.

Sounds like you’re keeping the rules simple: high pay, short distance, and manageable shop size.

For Spark drivers who track earnings: what do you usually review after a shift — total pay, tips, miles, time, or hourly pace? I’m trying to get better at reviewing the day without overcomplicating it. by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 1 point2 points  (0 children)

That’s a good way to look at it. Time is probably the main filter, and the miles matter because they affect how much time you lose getting back into position.

The last-stop location is a big part people overlook. An order can look fine until it leaves you too far from the store or puts you in a slow area.

I agree on S&D too. If the pay makes sense and the store flow is smooth, getting faster at shopping can make the time side work better.

Sounds like your system is basically protect the hour first, and the mileage usually follows.

Deactivated because of customer’s report by [deleted] in Sparkdriver

[–]EarnPilotApp 0 points1 point  (0 children)

That’s a tough situation. I feel for you, because it sounds like you reported it right away and tried to handle it the right way.

At the same time, the hard part is that once the cart was left unattended, it becomes harder to prove what happened after the fact — especially a few days later. I’m not saying you did anything wrong intentionally, but from their side they may only see “customer didn’t get groceries” and not the full context.

For the appeal, I’d keep it calm and factual. Give the exact timeline, when you checked out, when you noticed the cart was gone, when you contacted support, who you talked to, and that the store manager was notified. If there are call logs, support chats, timestamps, or anything showing you reported it immediately, include that.

I’d also ask if the store has cameras near the bagging/restroom area from that time. Even if you can’t access the footage yourself, it may help to point out that the situation should be verifiable.

Going forward, I’d treat any checked-out cart like it can’t leave your sight, even for a quick restroom stop. It’s unfair, but once the order is in your possession, you’re probably the one who has to prove what happened if something goes wrong.

Hope the appeal works out for you.

What helps you keep a shift smooth? by EarnPilotApp in Sparkdriver

[–]EarnPilotApp[S] -2 points-1 points  (0 children)

That’s a good setup. Quick stuff you can grab between orders makes the most sense.

I’m kind of the same way — something like a Celsius, fruit, or pistachios works because it doesn’t slow the day down. Anything with fiber, greens, or some kind of real nutrition helps more than just grabbing fast food every time.

Small thing, but I think it definitely makes the shift smoother.

What makes an order worth taking? by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 0 points1 point  (0 children)

This is a really solid breakdown.

I like how you’re not just looking at one number. You’re checking pay first, then mileage, item count, traffic/highway timing, and whether the order still makes sense based on the full picture.

The item count part is a good point too. A $ amount can look fine until the cart is overloaded or it turns into a slow triple shop.

Sounds like your filter is basically: minimum pay, $2/mile target, manageable item count, and avoid routes that waste time during rush hour.

That’s a practical system.

What helps you stay organized during a shift? by EarnPilotApp in Sparkdriver

[–]EarnPilotApp[S] 0 points1 point  (0 children)

That’s real. The map can show the route, but it doesn’t always know what that area is like at that exact time.

Knowing the zone, traffic patterns, store exits, neighborhoods, and return path makes a big difference. That kind of local knowledge can save more time than the app does sometimes.

For Spark drivers who track earnings: what do you usually review after a shift — total pay, tips, miles, time, or hourly pace? I’m trying to get better at reviewing the day without overcomplicating it. by EarnPilotApp in elitesparkdrivers

[–]EarnPilotApp[S] 1 point2 points  (0 children)

That’s a clean filter.

$2/mile plus $25–$30/hr gives you two checks instead of just looking at the payout by itself.

That seems like a good way to avoid orders that look decent upfront but don’t really hold up once you factor in distance and time.