Restaurant in-house web app

Scope of Work Application to be built using React Native Web Application for a restaurant User accounts with different rights (Administrator, Restaurant Manager, Waiters/Waitresses and Kitchen) Each user (Admin, manager, waiters and waitresses) is identified by First name, Surname, username, auto-generated password, random 4-digit employee ID code and Ghana mobile number (the restaurant manager’s mobile number for example). The Kitchen is to be identified simply by a username, auto-generated password, an employee ID code and a Ghana mobile number (the restaurant manager’s number for example). We propose to set the restaurant manager’s mobile number for all users as the number will only be used for password reset requests (except for the administrator). Because employees can change regularly, there is no point to insert different mobile numbers basically. One mobile number to be set to receive all password resets if needed except for the administrator access account). Backend to allow, the administrator and the restaurant manager account to re-generate passwords for users, edit user accounts info (First name, Surname and mobile number). If administrator becomes locked out or the restaurant manager becomes locked out, then each can click on reset password and the system should send a sms with a password to use to be able to re-login. The backend should also allow the admin or the restaurant manager to generate usage reports (table orders, purchase types i.e. in GHS cash, mobile money or card payment). Waiter/Waitress The waiter or waitress logs into the web app, can select items from the food menu and the drinks menu while receiving instructions from the customer(s) sitting at the restaurant table. Once done with the selection of items, he/she clicks on send to the kitchen. Kitchen One of the Kitchen staff logs into the web app, sees the different incoming table orders. For each order, the kitchen staff needs to click on ‘Accept’, the web app will move the order to ‘Being prepared’, once complete, one of the kitchen staff needs to click on ‘Ready to Serve’. The Ready to Serve would alert the waiter/waitress that would have taken the original order asking him/her to collect the food order and serve it to the table. Waiter/Waitress Once the customer(s) are done with their food and drinks and they request for the bill. The waiter/waitress that’s been attending to them should be able to click on ‘Payment Request’. The payment options would be Cash (in Ghana Cedis), Mobile Money or via Card Payment. The customer will have to be notified prior to paying via mobile money or card that a payment charge of % would be added on top and if they are happy to pay it. If not, then they can pay cash. If change needs to be given to the customer, then the waiter/waitress should click on ‘Change Required’ and then enter the amount of cash the customer gave for the app to auto calculate the amount of change that needs to be handed over to the customer. Payment collected > Waiter/waitress needs to click on a button stating ‘Payment Collected’ whether its in cash or digital. Restaurant Manager The restaurant manager will have the same backend panel rights as the administrator and will also be able to view ongoing orders and incoming payments at any given time. 2. Long term scope Restaurant Tables and Beacons and guest Android/iOS app hence the recommendation to look at building with React native from the start for scope 1 to avoid development sylos. Guest app to allow end user registration as optional and offer takeaway capabilities in future. -- Link to customer menu: [login to view URL]