I've noticed a lot of requests for changing from radius to actual DRIVING distance which is long overdue for implementation, but I have other requests to add to overall improvement of Delivery functionality.
1) Change from Radius to Driving distance
2) Ability to choose different delivery fees based on groups of postal codes
3) Ability to allow exceptions allowed or disallowed by postal code
4) Ability to chose delivery days based on delivery zone (postal code group)
--Postal code grouping could also easily be replaced with the ability to draw zones--
Context: We operate in Ottawa. We handle our own delivery - nobody else would want to as we deliver HAY, like bundles of hay, not boxed. We currently do a delivery day once a week. Ottawa (Ontario) is just *across the river* from Gatineau (Quebec) which, as you can imagine, limits any route optimization options and creates very difficult to manage delivery zones especially because we charge the delivery fee based on distance (currently stuck using radius). As per current functionality, with our radius maximum set at 60kms, some delivery stops end up being 64kms+ of driving and include crossing an interprovincial bridge (delays), or using a ferry that charges a $13 per cross (costing us $26 for a charged 15$ delivery fee and incredible delays as we wait to be loaded, cross and unloaded). Given that our customer concentration is in Ottawa and not Gatineau for now, we need some flexibility around the delivery aspect here. I have in the past simply contacted these customers to tell them we can't go to their location but this is quite unfair of a practice and has begun to affect our business reputation since these customers are part of target groups that we serve and share their frustrations at being able to order only to have their delivery cancelled.
I feel like this should be able to be taken care of at the system level with tools, API integrations and what is already available out there these days. HELP!
