FlexShark guide
How to Compare Amazon Flex Blocks After Travel and Costs
Compare two worked Amazon Flex block examples using total time, travel costs and service fees, then turn your own results into station and pay filters.
A higher advertised block amount does not always leave you with more for each hour of your day. Compare the offer with the time you expect to spend reaching the station, delivering and getting back to where you need to be. Then subtract the costs you expect to incur.
This guide uses hypothetical numbers to show the calculation. They are not typical earnings, a prediction of your route, or a recommended rate. Use your own records: the exact delivery route and finish time may not be known when an offer appears.
Start with the same calculation for every offer
Estimated remainder = block payment minus driving costs, tolls, parking and any applicable service fee.
Estimated amount per hour = estimated remainder divided by total time committed.
Total time includes your trip to the pickup station, the delivery block and the journey to your next destination. Avoid counting the same minutes twice: if your block-time estimate already includes waiting at pickup, do not add that wait again.
Your driving-cost estimate can include more than fuel. Decide whether it also includes vehicle wear, servicing and other costs, then use the same method when comparing offers. The examples below are before tax and omit costs you have not entered; the result is an estimate, not take-home income.
Worked example: the higher payout can be the weaker choice
Suppose Offer A pays AUD 120 for an advertised three-hour block. You estimate another hour for travel to the station and back, making four hours in total. Your estimated driving costs are AUD 20. For illustration, assume a service fee of AUD 4.20 applies and there are no additional tolls or parking charges.
The estimated remainder is 120 - 20 - 4.20 = AUD 95.80. Dividing by four hours gives AUD 23.95 per hour.
Offer B pays AUD 105 for an advertised two-and-a-half-hour block at a closer station. You estimate half an hour of additional travel, AUD 10 of driving costs and an illustrative service fee of AUD 3.68. Its estimated remainder is 105 - 10 - 3.68 = AUD 91.32. Across three hours, that is AUD 30.44 per hour.
Offer A leaves a little more money in this example, but Offer B uses an hour less of your time. Which matters more depends on your availability. Neither calculation promises that the route will finish on time or that another block will be available afterwards. Check the current FlexShark pricing for which fees actually apply to your account.
Test how sensitive the result is to a longer route
Repeat your calculation with an extra 30 minutes or a higher travel-cost estimate. In Offer B, adding 30 minutes changes the estimated hourly result to about AUD 26.09, even before adding any extra driving cost. A narrow margin can disappear if the route ends far from home.
Rather than assuming the best finish location, record the range you have actually experienced for each station. If you do not yet have that history, keep the uncertainty visible and review the result after delivery.
Turn the comparison into practical filters
Station filters are a starting point for controlling unpaid travel. Keep stations that you can realistically reach and evaluate each one using your own completed-block records. FlexShark cannot infer your full vehicle costs or guarantee a route's final destination from the block payment alone.
The FlexShark filter screenshot and worked settings example show where station, payment and duration rules fit. Use minimum payment and duration together. A minimum total amount does not by itself guarantee a minimum hourly result. Also check the permitted block days and start times: a financially attractive offer is still unsuitable if it overlaps another commitment.
Search schedules and delivery times are separate controls. A search window determines when the software checks for offers, not when you will deliver them. The setup guide explains how those controls work together.
Review estimates against completed blocks
For each completed block, record the station, payment, advertised duration, actual time committed, distance and costs. Compare the estimate you made before accepting with the result afterwards. This helps you see whether a station's travel overhead or a particular time of day is consistently different from your assumption.
Change one filter at a time so you can understand its effect. Raising every threshold at once may leave no matching offers; lowering every threshold may accept work you did not intend to do. For the wider decision about using automation, read when an Amazon Flex bot is useful.