Multiple Restaurant Ordering and delivery system

Hello, we are based in New Zealand and have been operating a restaurant food delivery service in Auckland for 15 yrs. We are wanting to upgrade our software. We started with our own propriety software and developed it over the years. Recently we moved to a USA managed system –Data Wedge. They are now closing. There are some requirements that are peculiar to NZ. The main one being processing of credit/debit cards online through a gateway that can process to NZ banks. Others include our address and phone number formats. FoodRunner has a web and mobile presence. However, we are currently off-line. Please find our details and requirements are below: We operate two model types on the same site. 1. Food Delivery a. We list multiple restaurant menus in various locations. b. Punters go on-line and after join up, they select their particular restaurant/menu items/delivery time/address details. c. The software analyses the customer address, the restaurant location then from a matrix works out which eateries they can order from in their area and delivery fee. d. Other fee options can be added if required (card or other fees, packaging, etc.). e. The customer pays on-line via credit/debit card. f. The order details including pick-up time, any extra requirements, sale price, etc. (but excluding cost of delivery). These details are auto-sent to the restaurant via SMS plus email or another internet sent on-screen type alert. The restrnt must respond by confirming the order or otherwise. g. At the same time the basic order details (meal items/quantities, pick-up time, customer name and address) is sent to the relevant driver’s smart phone who is delivering in that same zone. A Google map is also sent showing the route from restrnt to delivery destination. h. The driver must confirm: 1. receipt of order 2. on package pickup and 3. on final delivery. i. All the above details that are sent by restrnt and driver are recvd by the dispatch module so that all activity can be monitored. 2. Self-Pickup or Restrnt to Self-Deliver a. As in a. above b. Punters go on-line to select their particular restaurant/menu items/delivery time if restrnt to deliver (RTD) or pickup time for self-pickup (SP) c. If RTD: The software analyses the customer address, the restaurant location then from a matrix works out delivery fee and time. If SP: The software calculates the food price only and gives pick-up time. d. As in d. above e. As in e. above f. As in f. above g. If RTD, then as in g. above -to a nominated smart phone or emailed or data to an in-store application. In addition to the above, the following features are required for both models: • Geographic areas (zones/suburbs) to control and show which restaurants can deliver to which areas • Control of number of orders per zone per 15 mins to prevent driver delays • Quick re-order for repeat customers (address/card details auto populate) • (Optional) Ability for restaurant to enter into system to change their own menus if required • MUST be able to accept NZ credit/debit cards and to pay funds into FoodRunner’s NZ bank account • Corporate accounts payable monthly –charge up (no on-line payment required with order) • Creditors accounting system to allow payment/recon/tracking/history to restaurants • Driver’s details and accounting system managing payments due him/her, including history. • Mobile App and responsive web site • The dispatcher’s module to show real time driver status, order status, etc. • Phone in orders to dispatcher can be entered manually. • All other details as would be expected -such as customer database for email marketing; restaurant details including FoodRunner discount/commission structure; other fees; menu types by cuisine; open/close hours; etc. Could you please give this request your earliest attention as we are set to go immediately if everything is as we require. Thank you.