Edgar Ordering: No. We need the ability to charge a per-mile rate. That method just charges a flat rate for everything within a radius. We need to able to define a base delivery fee of $4.99 for everything under 4 miles and then a $1.25 per mile over 4 miles. So 5 miles would be a $6.24 delivery fee. 6.5 miles would be $8.12. 10.2 miles would be $12.74, etc.

Kyle: I used this feature with Jungleworks but it got very expensive very fast with the google maps api. Now with Ordering I use the geofences. We deliver up to 18 miles out from a restaurant and we set a base fee for 3 miles then the delivery fee goes up each mile after 3. The only downside is you cant get precise charges but for my use case it's not necessary as it charges the full extra mile. so if they're 3.2 miles away it will charge for the 4 mile geofence.

Also due to the geographic area i am in I couldn't use the circle radius. There are some areas that might b 2 miles away (as a bird flies) but take 10 driving miles to get to. So i used a third party website to generate KML files and I just uploaded them into Ordering. Works great!

Derrick Hayworth: Thanks for the response! We don't pay anything with our current solution, but our volume might be lower than yours. API usage is low enough to not exhaust the credits they give you. We charge actual mileage driven as well. It would just be nice to continue doing what we're doing so as to not confuse our customers/drivers.