Online Food Ordering System

INDRA GANDHI NATIONAL OPEN UNIVERSITY

A Project proposal on

“Online Food Ordering System”

Name: - Aditya Bhardwaj

Enrolment Number: - 197988876

Under Guidance

Of

Mr. Ujjal Chanda

IGNOU

BCA

Year of Submission: 2021

Page 1
 INDEX
Content Pages
1. Introduction………………………………………………………. 3
2. Objectives………………………………………………………….. 3-4

3. Project Category…………………………………………………

(3.1).RDBMS………………………………………………………. 4

(3.2).OOPS………………………………………………………….. 5-6

4. Analysis

(4.1).E-R diagram (Entity Relation Diagram)………………… 7

(4.2). DFD (Data Flow Diagram)…………………………………… 8-13

(4.3). SRS (Software Requirement Specification)…………. 13-18

(4.4). Data Dictionary…………………………………………………… 19-21

5. Module
(5.1).Module Description………………………………………………… 21-22

(5.2).Testing……………………………………………………………………. 22-23

(5.3).Process logic…………………………………………………………… 24-26

(5.4).Gant Chart………………………………………………………………. 27

(5.5).Effort Chart…………………………………………………………….. 27

6. Tools /Platform

(6.1). Hardware/Software Requirement specification…… 28

7. Type of Project…………………………………………………………………………………28

8. Limitation and Future Scope……………………………………………………………..29

Page 2
1. INTRODUCTION
Online food ordering website is a web-based software that helps to order food
online. In this software the customer will easily able to order food online. It allows
the customer to register initially with minimum details and will let them check the
menu items before ordering, adding them to cart and submitting the order. This
website will contain different types of food varieties available to user to buy
through online.

For example: - south Indian, north Indian food, ice creams etc. After adding
product to cart users can easily make payment by selecting available payment
option and pay amount.

2. Objectives
The main objectives of the project on online food ordering system is to manage
the details of food item , category , customers , order , confirm order.

 It manage all the information about food item, payment, confirm order
food item.
 The purpose of the project is to build a web application to reduce the
manual work for managing the food item, category, payment, customers. It
tracks all the details about the customer order, confirm order.

Drawback of existing system:-

Online food ordering software is supported to remove and some in some cases
reduce the challenges faced by this existing manual system.
This web application is planned to reduce as possible errors in ordering food
manually.
In manual existing system restaurants are storing the data in manual way they
have large number of customer daily that is why they need the help of online food
ordering system to maintain and store the records accurately. It’s hard to keep
record of day to day transaction and menu with manual process .In manual

Page 3
system customers can’t get the full list of menu by ordering by call but by online
food ordering system customers can look through the whole menu.

3. PROJECT CATEGORY
3.1(RDBMS)
An RDBMS is a DBMS designed specifically for relational databases. Therefore,
RDBMS are a subset of DBMS.
A relational database refers to a database that stores data in a structured format,
using rows and columns. This makes it easy to locate and access specific values
within the database. It is "relational" because the values within each table are
related to each other. Tables may also be related to other tables. The relational
structure makes it possible to run queries across multiple tables at once.
While a relational database describes the type of database an RDMBS manages,
the RDBMS refers to the database program itself. It is the software that executes
queries on the data, including adding, updating, and searching for values. An
RDBMS may also provide a visual representation of the data. For example, it may
display data in tables like a spreadsheet, allowing you to view and even edit
individual values in the table. Some RDMBS programs allow you to create forms
that can streamline entering, editing, and deleting data.
Most well known DBMS applications fall into the RDBMS category. Examples
include Oracle Database, MYSQL, Microsoft SQL Server, and IBM DB2. Some of
these programs support non-relational databases, but they are primarily used for
relational database management.
Examples of non-relational databases include Apache HBase, IBM Domino, and
Oracle No SQL Database. These types of databases are managed by other DMBS
programs that support No SQL, which do not fall into the RDBMS category .

(3.2) OOPS:-
I choose the project category oops because objects are the most important part
of the real problem. It allows users create the objects that I want and then create
methods to handle those objects. Manipulating these objects to get results is the
goal of Object Oriented Programming.

Page 4
Object-Oriented Programming popularly known as OOP, is used in a modern
programming language like Java.

Core OOPS concepts are: -

1) Class
The class is a group of similar entities. It is only a logical component and not the
physical entity. For example, if you had a class called “Expensive Cars” it could
have objects like Mercedes, BMW, Toyota, etc. Its properties (data) can be price
or speed of these cars. While the methods may be performed with these cars are
driving, reverse, braking etc.

2) Object
An object can be defined as an instance of a class, and there can be multiple
instances of an object in a program. An Object contains both the data and the
function, which operates on the data. For example - chair, bike, marker, pen,
table, car, etc.
3) Inheritance
Inheritance is an OOPS concept in which one object acquires the properties and
behaviour of the parent object. It’s creating a parent-child relationship between
two classes. It offers a robust and natural mechanism for organizing and structure
of any software.
4) Polymorphism
Polymorphism refers to the ability of a variable, object or function to take on
multiple forms. For example, in English, the verb “run” has a different meaning if
you use it with “a laptop,” “a foot race, and” business. Here, we understand the
meaning of “run” based on the other words used along with it. The same also
applied to Polymorphism.
5) Abstraction
An abstraction is an act of representing essential features without including
background details. It is a technique of creating a new data type that is suited for
a specific application. For example, while driving a car, you do not have to be
concerned with its internal working. Here you just need to concern about parts
like steering wheel, Gears, accelerator, etc.

Page 5
6) Encapsulation
Encapsulation is an OOP technique of wrapping the data and code. In this OOPS
concept, the variables of a class are always hidden from other classes. It can only
be accessed using the methods of their current class. For example - in school, a
student cannot exist without a class.
7) Association
Association is a relationship between two objects. It defines the diversity between
objects. In this OOP concept, all objects have their separate lifecycle, and there is
no owner. For example, many students can associate with one teacher while one
student can also associate with multiple teachers.
8) Aggregation
In this technique, all objects have their separate lifecycle. However, there is
ownership such that child object can’t belong to another parent object. For
example, consider class/objects department and teacher. Here, a single teacher
can’t belong to multiple departments, but even if we delete the department, the
teacher object will never be destroyed.
9) Composition
A composition is a specialized form of Aggregation. It is also called "death"
relationship. Child objects do not have their life cycle so when parent object
deletes all child object will also delete automatically. For that, let’s take an
example of House and rooms. Any house can have several rooms. One room can’t
become part of two different houses. So, if you delete the house room will also be
deleted.

Advantages of OOPS:

• OOP offers easy to understand and a clear modular structure for programs.
• Objects created for Object-Oriented Programs can be reused in other
programs. Thus, it saves significant development cost.
• Large programs are difficult to write, but if the development and designing
team follow OOPS concept then they can better design with minimum
flaws.
• It also enhances program modularity because every object exists
independently.

Page 6
 E-RDIGRAM

FOOD
Has
USER_NAME FOOD_ID
PICTURE
PASSWORD NAME
CATEGORY
ADMIN DISCOUNT ORDER
ADDED RATE
CATEGORY
MANAG
E
PICTURE
SHIPPING_ADDRESS
MANAGE

STATUS NAME

ORDER HISTORY MANAGE ADDRESS

NAME
TOTAL_COST EMAIL_ID
ORDER_NAME MANAGE
GENDER
ORDER_DATE
CUSTUMER
IMAGE
NAME
MESSAGE
CITY

EMAIL_ID
GENERATE COUNTRY
PHONE

DELETE EMAIL_ID
MESSAGE
CAT_ID

FOOD_ID
ORDER
MESSAGE_DATE
RATE
ADDRESS TOTAL
NAME
QTY

DILEVERY HAS
CONTACT

Page 7
4.2. DFD (Data Flow Diagram)

0-LEVEL DFD

ONLINE
RESTURANT FOOD ORDERING
SYSTEM

REQUEST OF ORDERING
RESPONSE
VIEW
REQUEST ORDER

ADMIN USER

Page 8
 1 LEVEL DFD (ADMIN)
ADMIN
SELECT
LOGIN
VEIW
SAVE ORDER ADD
CATOGRY
ORDER DETAILS

SEARCH
MEMBER
SAVE SAVE

MEMBER DETAILS CATEGORY DETAILS

UPDATE
PRODUCT VIEW
REQUEST
MESSAGE
ADD
SAVE PRODUCT

PRODUCT HISTORY SELECT LOG OUT

SAVESAVE

LIST OF PRODUCT DETAILS

MEMBERS MESSAGE DETAILS

MEMBER DETAILS

Page 9
2 LEVEL DFD (USER)

REQUEST
USER LOGIN GIVE
FEED BACK
VIEW

SAVE
VIEW
MY
ORDER FEEDBACK

DILEVERY
DISPLAY BOY CHANGE
DETAILS

ORDER
INFO DISPLAY

DILEVERY
BOY
BILL

ORDERING

DILEVERY BOY

Page
10
2ND LEVEL DFD (ADMIN)

REQUEST LOGIN REQUEST

ADMIN
LOGOUT

VIEW
VIEW

VIEW
VIEW
VIEW
ORDER
MESSAGE
VIEW
DISPLAY BILLS

ORDER DISPLAY
INFO DISPLAY

BILLS
MESSAGER

ORDER

CHANGE

Page
11
 4.3. SRS (SOFTWARE REQUIREMENT SPECIFICATION)
(4.3.1) INTRODUCTION
([Link]) DOCUMENT PURPOSE: -
This document presents a detailed explanation of the objectives, features, user
interface and application of Online Food Ordering System in real life. It will also describe
how the system will perform and under which it must operate. In this document it will
be also shown user interface. Both the stakeholders and the developers of the system
can benefit from this document.

([Link]) PRODUCT SCOPE: -

This system will help to manage and run the restaurant business systematically. In this
management system, we will provide an app that can be used by the customers to order
food. Customers can also give feedback through this app. So that owner of the restaurant
can evaluate the whole system. This will ultimately lead to hire less waiters and create an
opportunity to appoint more chefs and better kitchen place to serve food faster. Customers
can also make payment through debit or credit cards using POS which will be integrated
with the management software. Customers can see current discount facility of the
restaurant. Customers can also see the calorie chart which will increase consciousness
about their health. All the information about daily expenses and profit will be saved in the
system. Also the required information’s about employees will be saved in the system which
can be only accessed by the system admin.

([Link]) Intended Audience and Document Overview:-

This document is intended for different types of readers such as restaurant owner, system
designer, system developer and tester. By reading this document a reader can learn about
what the project is implemented for and how it will present it’s basic ideas.
This document has a sequential overview of the whole project so if a reader reads the document
from top to bottom; he will get a clear idea about the project.

([Link]) Definition, Acronyms and Abbreviations: -

We will also use bold letter to emphasis main topics and for all the major functions of the system.
Underline will represent hyperlink. Italic will represent acronyms and useful notes.
We will use some acronyms through this document. Abbreviations and definition of some useful
terms we will use are given below :

Page
12
 TERM DEFENITION
SYSTEM ADMIN System admin is a person who is responsible for managing the
whole system and who has full access to the system

SYSTEM USER
A person who is using or operating the system but with a
limited privilege

DATABASE A person who is using or operating the system but with a

limited privilege

FIELD A cell within a form.

SOFTWARE REQUIREMENT A document that completely describes all of the functions of a

SPECIFICATION proposed system and the constraints under which it must
operate. For example, this document

STAKE HOLDER Any person who is involved in the development process of

the software.

POINT OF SALE(POS) A point of sale system is either a stand-alone machine or a

network of input and output devices used by restaurant
Employees to accomplish their daily activities including food
and beverage orders, transmission of tasks to the kitchen and
other remote areas, guest-check settlement, credit card
transaction processing, and charge posting folios.

RMS Restaurant Management System

(4.3.2) General Description
([Link]) PRODUCT PROCPECTIVE:-
The Restaurant Management System helps the restaurant manager to manage the restaurant
more effectively and efficiently by computerizing meal ordering, billing and inventory control.
The system processes transaction and stores the resulting data. Reports will be generated from
these data which help the manager to make appropriate business decisions for the restaurant. For
example, knowing the number of customers for a particular time interval, the manager can decide
whether more waiters and chefs are required. Moreover, easily calculate daily expenditure and
profit.

Page
13
The whole management system is designed for a general Computerized Digital Restaurant, So that
any restaurant owner can get it and can start automated process to his restaurant.

([Link]) PRODUCT FUNCTIONALITY: -

Whole functions will perform through this order.

 Take Order
 Serve Food
 Payment
 Available Good
 Required Goods
 Customer Information
 Customer Review

([Link]) USER AND CHARACTERISTICS:-

The Restaurant Management System has five active actors and one cooperating
system. The customer can access the system through wifi connection and order food. The
Chef can see the order and after preparing the food he will tell the system that the food is
ready. The waiter can get the confirmation of food from the chef through the system and
deliver it to the right table. The cashier can access the system and receive the payment
from customers. The Admin can edit the price, count total earning and expenditure.

([Link]) OPERATING INVIROMENT OPERATING SYSTEM:-

Better environment Windows 10.

Language: - C#
It is need to use Smartphone to place food order in this system. Which will running on
Android Operating System. (We will provide the android app to place order with the
system.) Whole system should be covered by WiFi connection and a display for Chef in
kitchen.

([Link]) Design and implementation constraints

There are some constraints which costs more for the system. If those constraints can overcome
then this whole system will perform best. They are-
1. IOS App and Windows App.
2. Information flow or data flow can be controlled and more effective.
3. Faster server system such as LINUX server.
4. Bengali language for Bangladesh and Other language for other countries.
5. C# can be use for more security.

Page
14
([Link]) USER DOCUMENTATION

It will provide specific guidelines to a user for using the online food ordering system.
Furthermore a Video (Slide Show) will be provided which will represent the whole system
function and how it works.

([Link]) ASSUMPTION AND DEPENDENCIES

If this system have IOS and Windows app then customers who use such kind of smartphone
(windows and ios) will be more benefited. If there are more Tablets for each tables the
whole system performance will be better. For more secure system it is beneficial to use CC
camera a TV.

(4.3.3) Specific Requirement

([Link]) EXTERNAL INTERFACE REQUIREMENT

There are many types of interfaces as such supported by this software system
namely; User Interface, Software Interface and Hardware Interface.

([Link])User Interfaces

The user interface will be implemented using any android Smartphone app browser. This
interface will be user friendly .So that every kind of customer can place the food order
easily. Customers can also give feedback through it easily with some demo comment or if
they are keen to write their review by own they can do it

([Link]) Hardware Interfaces

There shall be logical address of the system in IPv6 format.

([Link]) Software Interfaces

The system shall communicate with the Configuration to identify all the available components to
configure the product. The system shall communicate with the content manager to get the product
specifications.
([Link]) Communications Interfaces
Communication function required the Internet protocol version 6 and it will follow HTTPS. It will
use FTP for whole system with local server. And email communication to device to device of the
system.

Page
15
 (4.3.4)FUNTIONAL REQUIREMENTS
Food Order via App
Customer can order food with the app but it needs specific wifi connection.

Take Order
The chef will take the order and if it is available to make then he will confirm the order and start
to prepare food.

Serve Food
When the food is ready to be served then the chef will alert the waiter. After serving the food
the waiter will insure the order as served.

Payment
The cashier will receive the payment if the customer is a member he or she will get
discount.

Available Good
The Chef will add what goods are available and the admin can see that data.

Required Goods
The chief will add what goods are required.

Customer Information
The customer will be get registered and be the member of special customer.

Customer Review
Customer can give overall review about the food and services.

([Link]) BEHAVIOUR REQUIREMENTS

Use Case View
The use cases for each of the actors are described in this section.

Customer Use Case

Use case: Order Food

Description The Customer can order food and see their payment receipts and pay.

Page
16
Description
The admin can see the orders of customers and checks whether this order can be taken or not
and then confirms the order and starts preparing the food. When the food is ready the admin
alerts the waiter to serve the food. He can also edit what ingredients are available and what
ingredients are demanded.

Waiter Use Case

Use case: Serve Food

Description
The waiter can see the food orders and the ready foods in the kitchen to be served. After
serving the food the waiter will mark the order as served.

Cashier Use Case

Use case: Take Payment
Description
The Cashier can only take payment from the customer and save it into the system database
with respect to the food item and also check if the customer is eligible.

([Link]) Performance and Requirements

 The product will be based on local server.
 The product will take initial load time.
 The performance will depend upon hardware components.
 Payment system will be fully secure through POS system.
 Different database for employee.
([Link])Safety and security requirement

 The source code developed for this system shall be maintained in

configuration management tool.

 The whole system is secured. Only Admin can access all the data.

 This system will use HTTPS. Because of this protocol this is more secure.

 This system will use secured POS system.

Page
17
(4.4) DATA DICTIONARY

TABLE NAME:-Admin

Field name Data type Allow null Description

Username Varchar(50) No PK
Password Varchar(100) No Alphanumeric
character

TABLE NAME:- Category

Field name Data type Allow null Description

CAT_ID Int(50) No PK
CAT_NAME varchar(100) No Category name

TABLE NAME: - food

Field name Data type Allow null Description

Name Varchar(50) No
CAT_ID Int(50) No FK
FOOD_ID Int(50) No PK
Rate Varchar(50) No
Discount Int(50) No
Description Varchar(50) No
Picture Varchar(10) No
TABLE NAME: - SIGN_UP

Field name Data type Allow null Description

Name Varchar(50) No
Address Varchar(50) No
City Char(20) No
State Char(20) No
Phone Int(10) No
Email_id Varchar(50) No PK
Password Varchar(50) No
Confirm Varchar(50) No
password
Country Char(50) No
Image Vharchar No
Gender Char(30) No
Security_ques Varchar(50) No
Security_ans Varchar(50) No

Page
18
 TABLE NAME:-VIEW_ORDERS

Field name Data type Allow null Description

EMAIL_ID Varchar(50) No Fk
CAT_ID Varchar(30) No
FOOD_ID Varchar(20) No
Rate Int(10) No
Qty Int(50) No
Total Int(10) No

TABLE NAME: - DILIVERY OPTION

Field name Data type Allow null Description

Name Varchar (50) No Pk
Contact Int (10) No
Address Varchar(300) No

TABLE NAME:-CREDIT CARD

Field name Data type Allow null Description

Holder name Varchar(30) No Pk
Card name Varchar(30) No
Company varchar(30) No
Expiry Int(30) No
TABLE NAME:- ORDER HISTORY

Field name Data type Allow null Description

Order_id Varchar(50) No Pk
Order_name Varchar(50) No
Shipping address Varchar(50) No
Total cost Int(10) No
Status Varchar(50) No
Order date Date No

Page
19
TABLE NAME: - MESSAGE

Field name Data type Allow null Description

Name Varchar(50) No
EMAIL_ID varchar(50) No pk
Phone Int(10) No
Message Varchar(100) No
Message date Date No
Delete Char(10) No

5. MODULE
(5.1)MODULE DISCRIPTION

There are two main modules of online restaurant food ordering system.

 Admin
 User

ADMIN: - The main function of admin is to manage the

whole software. Admin will also view customer order payment details. Admin will able to use
these modules which are following: -

 LOGIN: - Login module accepts login username and password. In a login module admin
of the system can access the whole software.
 ADD CATEGORY: - In this module admin will able to add category to provide good
service to customer while addition of category admin will have to fill the form such as
category name, category picture etc…
 ADD FOOD: - In this module admin will add food while addition of food admin will have
to fill the form such as food name, choose category, rate, discount etc…
 UPDATE PRODUCT: - In this module admin will update the added item.
 VIEW ORDER: - In this module admin view the order given by the customer.
 VIEW MESSAGE: - In this module admin view the message uploaded by the customer on
the portal.
 LOG OUT: - In this module user signup from the website.

Page
20
USER: - First of all user registered on the website and then user will able to use various type
of services related with ordering food. The services are as follows: -

 SIGNUP: - In this module user register on the website and then able to login with their
register username and password while registering on the website user will have to fill
the form such as name address, city, phone, email, state etc……
 LOGIN:- Login module accepts login username or password of the user which allow user
to enter into the website and use various services related for the ordering food.
 ORDER FOOD:- In this module user order food with their own choice while ordering the
food user will have fill the form such as select item.
 ADD TO CARD:- In this module user will able to view the such as food name, rate,
quantity, total price etc….
 PAYMENT OPTION:- In this module admin will choice payment option such as COD(cash on
delivery) ,credit card, debit card, while.
 ORDER HISTORY:- This modules allows see the order history such as order number, shipping
address, total cost, status, order rate etc.
 LOGOUT:- In this module user signup from the website.

5.2 Testing procedural

Testing:- Testing is a process of executing a software or program again and again with the
purpose of finding errors in it. When software is implemented, it has errors. The errors in
software are usually known as bugs. The main and initial errors in software are usually known
as bugs. The main and initial purpose of software testing is to find out the errors or bugs in a
developing software. Software testing is mandatory and required phase in software
development where the main purpose is to deliver accurate reliable and efficient software. So,
it is needed for my website to deliver good software.

Unit Testing:- UNIT Testing is defined as a type of software testing where individual units/
components of a software are tested.

Unit Testing of software applications is done during the development (coding) of an application.
The objective of Unit Testing is to isolate a section of code and verify its correctness. In
procedural programming, a unit may be an individual function or procedure. Unit Testing is
usually performed by the developer.

In SDLC, STLC, V Model, Unit testing is first level of testing done before integration testing. Unit
testing is a WhiteBox testing technique that is usually performed by the developer. Though, in a
practical world due to time crunch or reluctance of developers to tests, QA engineers also do
unit testing.

Page
21
Module Testing:- A group of related programs that achieve a single task in an application
is usually known as a module. Testing a complete module, a collection of related program units
to check if the module is working properly as a whole and producing the desired output is
known as module testing. Module testing may fall under the category of white box testing as
well as black box testing.

Page
22
5.3 PROCESS LOGIC CHART
 ADMIN
 Process logic chart(login)

If valid Open admin panel

Login Login

Invalid

Display
message
Fig No.1 (Login)

 Process logic chart(category)

If valid Successfully
NAME added
ADD CATEGORY Category

Invalid

Failed
Fig no.2 (Add category)

 Process logic chart(food)

Unique
Name Added
Food successfully
 Add food
Not unique

Failed

Page
23
 Fig No.3 (Add food)

Unique
Food name Order
View order View viewed
order
Not unique

Not
viewed

Fig No.4 (view order)

Open
If valid history page
Name Order
Order history history

Invalid
Fig No.5 (Order history)

Display
message

View Open
Unique
massage message
page
View View
massage message Not unique

Display
message

Page
24
Fig No .6(View message)

Page
25
 Customer

Customer If valid
details
Registered
Sign up Sign up

If invalid

Display
message

Fig No.7 (sign up)

Open costumer
Username & If valid panel
password
Login
Login
Invalid

Display
message

Fig No.8 (Login)

Successfully
Unique ordered
Select
Order food Order food
Not unique

Failed

Fig No.9 (Order Food)

Page
26
 5.4. GANT CHART
PROJECT PLANNING

Project
Development SEP 2021 OCT 2021 NOV DEC 2021 JAN FEB 2022
Stages 2021 2022
Requirements
Analysis
20 days
Planning

10days

Analysis
25days
Design

22DAYS
Coding

28days
Testing

24days
Implementation

15days

5.5 EFFORT CHART

LEARNER

75%

GUIDE

25%

Page
27
6. TOOLS AND PLATFORM
(6.1). Hardware/software Requirement specification
HARDWARE Requirement

PROCESSOR Intel(R) Core(TM) i3-6006U CPU@, 2.00GHZ

1.99GHZ
RAM 4.00GB(3.88GB usable)
HARD DISK 1 TB
KEYBOARD Multimedia
TOUCH PAD YES
Display Type LED Display screen
SIZE 15.6”

Software Requirement

OPERATING SYSTEM WINDOWS 10

FRONT END [Link] With C#
BACK END MS SQL SERVER
LANGUAGE C#
SCRIPTING LANGUAGE HTML/XML/JAVA SCRIPT
EDITING TOOL NOTEPAD/MS WORD
IAMGE EDITING TOOL MS PAINT
WEB BROWSER IE

7. PROJECT Place

(7.1) Are you doing this project for any industry /client? Mention Yes/No. If Yes,
Mention the Name and Address of the Industry or Client.

Ans.:- No

Page
28
Limitation and Future Scope:

 Late Deliveries:
With food ordered online some time it takes a lot of time to deliver to the required place as it depends upon
the distance from which it is ordered, as a matter of fact this technological ease has made the current
generation a bit complaisant, while ordering something online it should be kept in mind that the food should
be ordered from the nearest possible outlet so it may reach you in few minutes or else you got to wait long
for the delivery. So, it’s better to be smart enough to order properly by deciding the area rather than reaching
unknowingly and then keep on waiting.

Price Differences:
Well it is not a big problem as far as the delivery thing is concerned, but yes, the price does differ while
ordering some services are found to be free of cost, but some restaurants use to charge extra money for
delivery of food at your place. This price ranges from 3-15$ depending upon from how far you are being
served moreover it is also observed that there is some unusual rise in prices of the online available food
items this may be due to the inclusion of taxes but all in all it is considered as a change and indirectly as a
disadvantage.

Social Interaction:
Having lunch/dinner in a restaurant is quite a fascinating stuff, the ambiance, the social interaction and the
experience of all these things rejuvenates the hunger in you but sitting in your couch and ordering food is a
comforting but complacent approach back to back where people would not enjoy the benefits of reaching
out to other places and enjoying the delights of the social interaction with different environment.

Quality of food:
This is one of the few reasons which has made people reluctant to order food online, sometimes it happens
when food is found to be of low standards then shown or said about. People often go berserk over this, and
they flood your customer’s feedback page with all the possible words which you don’t want to listen about
your brand.

Page
29