Restaurant Chain Management System

Proposal document

PROJECT

RESTAURANT CHAIN MANAGEMENT SYSTEM

P age |1

Proposal document

By: Softqube Technologies

Restaurant Chain Management System

Proposal document

Index
1. Phase-I .......................................................................................................................................................................................... 3 2. Phase-II ......................................................................................................................................................................................... 3 3. Adopted Technology for Development .......................................................................................................................................... 5

P age |2

By: Softqube Technologies

Restaurant Chain Management System

Proposal document

1. Phase-I
1. The web presence needs to be completed, including the home page. 2. The design needs to be high on aesthetics. 3. The home page will have an option for users to register online to stay updated about the launch, happenings regarding the portal 4. This would be a mini-registration, where users could register by just mentioning their name and email. (A verification link is sent back to the users by email). Users will also have option to sign in using facebook and twitter, and also refer the site to their friends 5. Restaurants would also have a provision to leave their contact details for us to contact them offline. 6. Except these functionalities, the normal links and layout.

2. Phase-II
1. Complete user registration module, including the users who have registered earlier, will be send an email whereby they can complete the registration; for news users, the normal registration is followed 2. Users will be able to view the restaurant details online with detailed menu card, reviews, gallery, video snippet, etc. 3. User management module including profile information, account history, etc. 4. Restaurants will be able to leave a lead for us on the portal to do a follow up with them for registration. Categories of restaurant will be order only , delivery only , order and delivery . 5. The initial registration of the restaurant is done by us from the back end (by a category of back-end employees), who would upload all the details including the menu card, detailed menu, logos, gallery, video (if any). 6. Once this is done, the restaurant goes live, and the restaurant owner is provided with a username and password to manage their account online (profile, menu, account statement, order history, coupon history, analytics etc.) 7. Portal Administration Module with user rights and user management (Various categories of users will be there with access to different modules. For example, a customer care agent would not have access to finance module, mailer module, etc.) 8. Order management system needs to be developed, which will 1 interface to begin with The back office agent interface. This could be a desktop based application built on C#.NET, and could use the database from the server online. The other option could be a web based backend interface for the agents, but that would then choke a lot of bandwidth unnecessarily. 9. Order management system will have the necessary user information, in case of a repeat or a pre-registered customer; else, new customer form will have to be filled by the agent to register the user on the portal. Please note, any user who has registered on the portal and has a user id, his data will be available to the agent, but a user who has been ordering on the phone, though his information is also present in the user master, he would not have a username with which he can login. In such case, if the user wishes to register online then when he clicks on register > he gets an option Click here if you have ordered with us before on phone, chances are we would have your record > he then presents his mobile number which is validated in the database and if it s true, his data is pulled and the user registration is populated automatically except the username and the password. (This way you cut down the repetitive registration process for the user as well) 10. Order management system would also have other functionalities including tracking orders, order status, order history, coupons applicable, coupons available, etc.

P age |3

By: Softqube Technologies

Restaurant Chain Management System

Proposal document

11. Coupon Management System > this module will be used to design various customized coupon codes mapped to user accounts, restaurants, menu items, days of the week, month of the year, time of the day, master coupons (applicable to all). This also includes creating rules for coupons, validity, redemption process, etc.) 12. Communication and Newsletter Module (this would include SMS, and Email integration) 13. 2-way SMS module > this module will manage all the keywords and assigned behaviour of the query. We can add/edit/remove keywords and mention the parameter format, it is customizable. 14. Fleet management system > users assigned this role, will have access to the current orders which need to be fulfilled, and the user would be able to track the delivery vehicles and communicate with them through SMS and phone (out of the scope of the portal). 15. Delivery boy management system will have complete records with history of delivery resources. Other random bulleted points are mentioned for better understanding. New order is intimated to the restaurants by the following ways: 1. SMS y New Order y Order Details y Pickup Delivery Boy & Estimated time y Delivered & Payment Received Confirmation y If not delivered then reason 2. Fax 3. Email 4. Web alert / desktop alert (phase II) 5. Call (in case of system delay/failure) InterFAX API 1. Query Back SMS ex. HUNGRY REPRINT <ORDERNO> to 56161 2. Query Back SMS ex. HUNGRY <ORDERNO> to 56161 (to check the status of order) 3. Query Back SMS ex. HUNGRY to 56161 4. Query Back SMS ex. HUNGRY KEBABRI to 56161 (to retrieve restaurant information) Customer facing public interface 1. Web 2.0 Standards 2. Home page will have Search for restaurant on the home page, latest deals, partner restaurants have a microsite for the restaurant 3. Home page menu-check other sites 4. Cross browser compatible 5. Users can browse menu cards/reviews online without registration 6. Users can register and order online, etc. 7. Users can login using their facebook account 8. Users personal information is recorded 9. Features of Social network needs to be implements 10. Feature for users to Follow restaurants, Like restaurants 11. Random Surveys Module 12. Invite your friends facebook 13. My Account 14. Summary of orders 15. Latest deals P age |4 By: Softqube Technologies

Restaurant Chain Management System

Proposal document

16. Restaurants can login and access their menu cards 17. View reviews 18. View account summary day wise, week wise, month wise, parameterized, with visual aids like fusion charts, dundas dashboards, etc, 19. Restaurants can use the widgets to include the menu and the OMS interface on their portal Web-based CRM 1. Feedback system 2. Newsletters 3. Food trends, fads, etiquettes, things to remember while ordering food on phone, 4. Offers 5. Marketing campaigns Web-based Order Management System 1. A dashboard having the following information a. Customer information Name, Phone, Address, Email, DoB, Preferences (Food) b. Recent order transactions c. Search module restaurant locator: location, cuisine, price, offers d. While recording the order, system will assess the order, and show what the customer ordered with this last time e. Top things the customer prefers to eat/order cuisine wise whether available at the restaurant where he s ordering from f. Select mode of payment CoD, Pay on phone (MOTO), Credit card on delivery, etc. g. Order tracking today s orders, recent orders, current status, edit order, cancel order, etc. h. Up sell ex. Ur order amount is 654. Add a dish to it, and get 10% off, etc. Web-based Employee Management System Portal Admin 1. Literally, everything should be relative/parameterized/easily configurable at the top level 2. Ex. SMS gateway, SMS name, Email address, etc,

3. Adopted Technology for Development

y y y y y y y Web Hosting: Technology: Charting tools: Scripting Lang.: Code Behind Lang.: Reporting Tools: Database: Discount ASP.NET (Recommended) or Intranet Microsoft .NET Framework 3.5 Microsoft .NET Charting Tools ASP.NET / AJAX / JavaScript / CSS C#.NET 3.5 Crystal 8.5 MS SQL 2008 Yours Truly, Harikrishna Patel harikrishna@softqube.co.in +91-999-80-14314

P age |5

By: Softqube Technologies