2.o Food Ordering System Final Report
2.o Food Ordering System Final Report
ON
“FOOD ORDERING SYSTEM”
By
IN PARTIAL
FULFILLMENT FOR THE AWARD OF
Under
The Guidance of
Submitted to the
By
IN PARTIAL
FULFILLMENT FOR THE AWARD OF
Under
The Guidance of
Submitted to the
CERTIFICATE
This is certifying tha Mr.Premkumar Peter Patole,
Mr.Suraj Rajput Meshram,Mr Jitendra Sanjay Shinde and Mr. Umar
Rahimuddin Siddique class B.C.S. 3nd year has completed project
synopsis on “FOOD ORDERING SYSTEM” for B.C.S.
3nd year successfully during the academic year 2023-2024.
Date:
DECLARATION
Computer Science with specialization in Computer. This project report has not
been submitted to any other university or institution for award of degree.
The presentation of this project has given me the opportunity to express my gratitude
to all those who have made it possible for me to accomplish this project.
I thank to our college management for giving me this opportunity to undergo a project
study program in their esteemed organization.
I am special thanks to my project guide Mrs. Ankita Rathod Mam, for giving an
Opportunity to do this project work.
I would like to specially thank to Miss. Sujata Suradkar Mam and Miss. Sandhya
Arak.
I express my gratitude to the project Guide, HOD Mr. Vinod Pawar Sir and Principal
Mr. A. S. Paithane Sir for his valuable guidance and assistance in taking me through
the project.
Our proposed system is an online food ordering system that enables ease
for the customers. It overcomes the disadvantages of the traditional queueing
system. Our proposed system is a medium to order online food hassle free from
restaurants as well as mess service. This system improves the method of taking the
order from customer. The online food ordering system sets up a food menu online
and customers can easily place the order as per their wish. Also with a food menu,
customers can easily track the orders. This system also provides a feedback
system in which user can rate the food items. Also, the proposed system can
recommend hotels, food, based on the ratings given by the user, the hotel staff will
be informed for the improvements along with the quality. The payment can be
made online or pay-on-delivery system. For more secured ordering separate
accounts are maintained for each user by providing them an ID and a password.
1
INDEX
2
INTRODUCTION
The online food ordering system sets up a food menu online and customers can
easily place the order as per they like. Also with a food menu, online customers can
easily track the orders. The management maintains customers database, and improve
food delivery service. The Restaurant management systems motivate us to develop the
system. There are various facilities provided so that the users of the system will get
service effectively. Also, the system considers Restaurants as well as Mess facility to the
customers. Again, the idea comes that mostly mess users are person who are shifted for
various reason in new cities. So, they are interrelated. Increasing use of smart phones is
also considered as a motivation, so that any users of this system get all service on single
click. Another motivation can be considered as the system will be designed to avoid
users doing fatal errors, users can change their own profile, users can track their food
items through GPS, users can provide feedback and recommendations and can give
ratings, it will give appropriate feedbacks to Restaurants / Mess service providers.
Due to lack of a full fledge application that can fulfill the customer requirements
by providing him food from restaurants as well as from mess service, there is a need for
the system. This proposed system will be used by the people who keep shifting from
cities to cites. As well as, it will be useful for the students studying in different cities.
The proposed system will provide the flexibility to the Customers/Users to order
from either Restaurants or Mess. It will also provide Recommendations to the customers
from the restaurants/mess owners uploaded on a daily basis. In the proposed system,
there will be no limitation on the amount of order the customer wants. Also, same
application can be used as a Startup Business for the developers. It will provide real
time customers feedback and ratings along with the comments to the restaurants/mess
owner. It gives appropriate feedbacks to users, so if there is any error happened, then
there will be a feedback dialog toward users.
The proposed system is designed to avoid users doing fatal errors and
inappropriate action. Scope of proposed system is justifiable because in large amount
peoples are shifting to different cities so wide range of people can make a use of
proposed system. The system/interface will take input from the user. The major
attributes that will give input to the dataset is: name, address, email-Id, mobile no, other
3
personal related values, etc. The output will include user/customer’s Order, Bill,
Feedback and Payment options. Initially there will be 10 to 12 restaurants and mess
services considered inside 2 to 3 areas.
The reason why to choose this project is the idea behind project that is to solve
problem of people which they are facing when they shift to different city. The system is
not only for user but also for provider who provides food service. This system is for
making efficient communication between consumer and producer of the food system
which will then leads to the ideal and effective system.
4
OBJECTIVE
5
customer data and payment information, as well as compliance with regulations
such as data protection laws and food safety standards, building trust and
confidence among customers.
10. Adaptability and Scalability: Food ordering systems should be designed to be
adaptable and scalable, capable of accommodating changes in customer demand,
technological advancements, and business growth without compromising
performance or reliability.
By achieving these objectives, food ordering systems can contribute to the overall
success and sustainability of restaurants in today's competitive food industry landscape.
6
NEED OF FOOD ORDERING SYSTEM
Expanded Choices: Online food ordering systems provide customers with access to a
wide range of restaurants and cuisines beyond their immediate vicinity, opening up a
world of culinary options and catering to diverse tastes and dietary preferences.
Transparency and Control: These systems offer transparency and control to customers
by providing detailed menus, pricing information, and customization options,
empowering them to make informed choices and tailor orders to their liking.
Order Tracking: Many online food ordering systems incorporate order tracking features
that allow customers to monitor the status of their orders in real-time, from preparation
to delivery or pickup, providing peace of mind and reducing uncertainty.
Efficiency and Accuracy: By automating the ordering process, online food ordering
7
systems improve efficiency and accuracy, reducing errors associated with manual order
taking and minimizing wait times for both customers and restaurants.
Scalability and Growth: For restaurants, online food ordering systems offer
opportunities for scalability and growth by reaching a wider audience, attracting new
customers, and increasing sales through digital channels, without the constraints of
physical space or location.
8
GOALS OF THE SYSTEM
The goals of an online food ordering system typically revolve around enhancing
customer satisfaction, improving operational efficiency, and driving business growth.
Here are some common goals:
1. Increase Sales Revenue: One of the primary goals is to increase sales revenue
by providing customers with a convenient and accessible way to order food.
This includes attracting new customers, encouraging repeat business, and
upselling additional items through personalized recommendations and
promotions.
2. Enhance Customer Satisfaction: The system aims to enhance customer
satisfaction by offering a seamless and user-friendly ordering experience. This
includes providing a wide selection of menu items, easy navigation, quick
checkout processes, and reliable delivery or pickup options.
3. Improve Order Accuracy: Another goal is to improve order accuracy by
minimizing errors associated with manual order taking. The system should
allow customers to specify their preferences, dietary restrictions, and special
instructions accurately, reducing the likelihood of mistakes in the fulfillment
process.
4. Optimize Operational Efficiency: The system aims to optimize operational
efficiency within restaurants by streamlining order processing, reducing wait
times, and optimizing resource allocation. This includes automating tasks such
as order management, inventory tracking, and delivery routing.
5. Expand Customer Reach: An important goal is to expand the customer reach by
reaching new demographics and geographic areas through online channels. This
includes leveraging digital marketing strategies, social media integration, and
partnerships with third-party delivery services to attract a broader audience.
6. Drive Customer Engagement: The system seeks to drive customer engagement
through features such as personalized recommendations, loyalty programs, and
feedback mechanisms. Engaged customers are more likely to return for future
orders and recommend the restaurant to others.
7. Enable Data-Driven Decision Making: The system aims to collect and analyze
data on customer behavior, ordering patterns, and sales trends to inform
9
decision-making processes. This includes identifying popular menu items,
forecasting demand, and adjusting pricing strategies based on market dynamics.
8. Ensure Security and Compliance: Another goal is to ensure the security of
customer data and payment information, as well as compliance with regulations
such as data protection laws and food safety standards. This includes
implementing secure payment gateways, encryption protocols, and robust data
privacy measures.
9. Differentiate from Competitors: The system aims to differentiate the restaurant
from competitors by offering unique features, value-added services, and
exceptional customer experiences. This includes staying abreast of industry
trends, incorporating customer feedback, and continuously innovating to stay
ahead of the competition.
10. Achieve Long-Term Sustainability: Ultimately, the goal of the online food
ordering system is to contribute to the long-term sustainability and growth of
the restaurant business. This includes building brand loyalty, fostering positive
relationships with customers, and adapting to evolving market dynamics to
remain relevant in the competitive landscape.
Ease of Access:
The application was developed to serve mass population. That is why the user interface
of the application is kept simple.
10
USER REQUIREMENT
11
their order history, reorder favorite items with ease, and save customized
preferences for future orders, saving time and effort when placing subsequent
orders.
10. Feedback and Support: Users value opportunities to provide feedback on their
ordering experience, including ratings, reviews, and suggestions for
improvement. The system should also offer responsive customer support
channels to address any issues or inquiries promptly.
By incorporating these user requirements into the design and development of the
food ordering system, businesses can create a solution that delivers a satisfying and
seamless experience for their customers, fostering loyalty and repeat business.
12
PROJECT DESIGN
Designing an online food ordering system involves several key components and
considerations. Here's a high-level overview of the project design:
1. System Architecture:
- Client-Side Application: This includes the user interface (UI) components
accessible to customers for browsing menus, placing orders, and taking
deliveries.
- Server-Side Application: This handles business logic, processing orders,
managing user accounts, and interfacing with databases.
- Database Management System (DBMS): Stores information such as user
accounts, menu items, orders, and transaction history.
2. User Interface (UI) Design:
- Homepage: Features a search bar, featured items, promotions, and links to
different sections of the website (e.g., menu, order tracking, account).
- Menu Page: Displays categories of food items, individual menu items with
descriptions, prices, and options for customization.
- Cart and Checkout: Allows users to review their selected items, customize
quantities, apply discounts or promotional codes, select delivery/pickup options,
and complete transactions securely.
- Order Tracking: Provides real-time updates on the status of orders, including
confirmation, preparation, out for delivery, and delivered/pickup ready.
- User Account Management: Enables users to create accounts, login/logout,
update profile information, view order history, save favorite items, and manage
preferences.
3. Backend Development:
- User Authentication: Implements secure authentication mechanisms (e.g., JWT
tokens) for user login and session management.
- Order Processing: Handles order placement, updating order status, generating
order confirmations, and sending notifications to users and restaurant staff.
- Menu Management: Supports CRUD (Create, Read, Update, Delete) operations
for managing menu items, categories, and prices.
- Payment Integration: Integrates with payment gateways (e.g., Stripe, PayPal)
13
for secure online transactions, including authorization, capture, and refund
functionalities.
- Order Management: Manages order queues, assigns orders to delivery drivers
(if applicable), and generates reports on order metrics and performance.
4. Database Design:
- User Database: Stores user account information, including usernames,
passwords (hashed), email addresses, delivery addresses, and order history.
- Menu Database: Contains information about menu items, including names,
descriptions, prices, categories, and availability status.
- Order Database: Tracks order details, such as order ID, customer ID, item IDs,
quantities, timestamps, delivery/pickup information, and status updates.
5. Integration and Testing:
- API Integration: Ensures seamless communication between the client-side
application, server-side application, and external services (e.g., payment
gateways).
- Testing: Conducts unit tests, integration tests, and end-to-end tests to verify the
functionality, reliability, and security of the system.
- Deployment: Deploys the system to a production environment, configuring
servers, databases, and network infrastructure for scalability, reliability, and
performance.
6. Maintenance and Support:
- Monitoring and Logging: Implements monitoring tools and logging
mechanisms to track system performance, detect errors, and troubleshoot issues.
- Updates and Upgrades: Regularly updates the system to incorporate new
features, address security vulnerabilities, and improve overall user experience.
- Customer Support: Provides ongoing support to users, addressing inquiries,
feedback, and technical issues promptly and effectively.
14
PROJECT PLANNING
15
Incremental Model:
The Incremental build model is a method of software development where
the model is designed, implemented and tested incrementally (a little more is
added each time) until the product is finished. It involves both development and
maintenance. The product is defined as finished when it satisfies all of its
requirements. This model combines the elements of the waterfall model with the
iterative philosophy of prototyping.
The product is decomposed into a number of components, each of which
are designed and built separately (termed as builds). Each component is
delivered to the client when it is complete. This allows partial utilization of
product and avoids a long development time. It also creates a large initial capital
outlay with the subsequent long wait avoided. This model of development also
helps ease the traumatic effect of introducing completely new system all at once.
The incremental model contains following phase:
System Analysis: It is first stage of process model. This provides primary
analysis of the system Requirement and data gathering. Its process of gathering
data to understand the nature of software. The engineer must understanding the
information domain for software as well as required function behavior
performance and interface.
System Design: As per analysis of system will be designed. It includes designing
of template of website. Software design is multi step process that focus is on four
attribute of the programmer attribute, Data structure, Software architecture,
Interface representation Process design translate requirement into graphical
16
represent four coding of software.
System Coding: Design of system is implemented in this phase. The system
design translates into computer untestable language into this step. This step is
also knows as programing step.
System Testing: After coding each module is tested using different methods.
After the coding of the system all statement have been tested in this step. The
goal of testing to UN curves the requirement design and coding error.
Risk Management:
Risk Identification:
During the analysis of our whole application, we discovered some of the
risks that could affect this website while developing and also while using. These
are those risks:
a. Technological Risk
b. Economical Risk
c. Political Risk
Risk Analysis:
Here is the description of how the above mentioned risks were to affect
this application:
a. Technological Risk: First of all, this application requires web browser
that supports JavaScript and flash. The most common problems are low
processor configuration, low buffer memory, low speed etc...
b. Economical Risk: This project is intranet application there is no extra
economic changes are there. This project is totally cheapest.
c. Political Risk: There are many political risks such as wrong information
about any place in city, images that are not permitted to show, also
permit of all private organization which information 1 includes in our
intranet application. During the risk analysis process, each identified risk
is considered in turn and a judgment made about the probability and the
seriousness of the risk. It relies on the judgment and experience of the
project manager.
17
Risk Probability Effects
Financial Problem Low Catastrophic
S/W component which should be reused contain Moderate Serious
defects
Changes to requirements which require major Moderate Serious
design
Required training for staff is not available Moderate Serious
The rate of defect repair is underestimated Moderate Tolerable
The time required to develop the S/W is High Serious
underestimated
Risk Planning:
Here is how we deal with all the above said risks:
i. Technological Risk: To avoid this risk, I planned that use
JavaScript whenever it must be required and avoiding use of
flash.
ii. Economical Risk: There is no need to solve economical risk.
Because there is no problem about economical problem.
iii. Political Risk: Permitting of the organization to display or
advertisement information is solves this problem. The risk which
might be uncounted after setting up the server is Shown in the
table below. All the applications have different internal and
external risks. Internal risks basically comprise with hardware
failure, server down, power interruption for which the solution is
specified. External risks are associated with the application like
virus, hacking and the corruption of files. The solution is
mentioned in the table below, which is again not much difficult to
handle if proper risk planning is done.
18
3 Power Internal Low Low UPS
Interruption
4 Virus External High Serious Antivirus
5 Hacking External Low Moderate Firewall
6 File Corruption External Moderate Serious Backup
Risk Transfer:
Risk transfer means causing another party to accept the risk, typically by
contract or by hedging. Insurance is one type of risk transfer that uses contracts.
Other times it may involve contract language that transfers a risk to another party
without the payment of an insurance premium. Liability among construction or
other contractors is very often transferred this way. On the other hand, taking
offsetting positions in derivatives is typically how firms use hedging to
financially manage risk.
Some ways of managing risk fall into multiple categories. Risk retention
pools are technically retaining the risk for the group, but spreading it over the
whole group involves transfer among individual members of the group. This is
different from traditional insurance, in that no premium is exchanged between
members of the group up front, but instead losses are assessed to all members of
the group.
The planning by which the risks cannot occur is:
➢ Interact with all branches.
➢ Authorize carefully and creating new safe security system for that.
➢ Make new security for natural threats.
19
SOFTWARE REQUIREMENTS
Hardware Feasibility
❖ Processor: 1.8 GHz to 2.2 GHz
❖ RAM: Minimum 1 GB RAM or above
❖ Storage: Minimum 500 MB or above
Software Feasibility
❖ Front End: XML
❖ Back End: PHP
❖ Tool: XAMMP, Visual studio code
❖ Database: MySQL
➢ User Interface:
o GUI is provided by the software which is self-explanatory.
o User friendly forms, menus and options are contained by the
software.
o Designing of the product have to be studied by the developer.
Software gives warnings with necessary assistance to the clients.
➢ Performance Requirements:
o Good memory space is required. Should be Error-free.
o Large amount of data should be handled easily.
➢ Safety Requirement:
o Backups can be done regularly.
o End user, who have their own username and password, have only
the right to open the software
20
FEATURES OF THE PROJECT
The features of a food ordering system can vary depending on the specific
requirements of the project and the target audience. However, here is a list of common
features that are typically included in a food ordering system:
2. Browse Menus:
• Display restaurant menus with categories, item descriptions, prices, and
images.
• Facilitate easy navigation and search functionality for users to find
specific dishes or cuisines.
3. Order Placement:
• Provide intuitive interfaces for users to add items to their cart, customize
orders (e.g., toppings, quantities), and proceed to checkout.
• Support multiple payment options, including credit/debit cards, digital
wallets, and cash on delivery.
4. Order Tracking:
• Enable real-time order tracking, allowing users to monitor the status of
their orders from preparation to delivery or pickup.
• Provide notifications and updates on order progress, estimated delivery
times, and delivery personnel details.
21
6. Restaurant Management:
• Provide an interface for restaurant owners or administrators to manage
menu items, prices, availability, and promotions.
• Allow restaurants to set business hours, delivery zones, and minimum
order requirements.
7. Delivery Management:
• Integrate with third-party delivery services or provide in-house delivery
management tools for restaurants.
• Optimize delivery routes, assign orders to delivery personnel, and track
delivery status in real-time.
23
ADVANTAGE AND DISADVANTAGE ADVANTAGE
Advantage:
24
dynamics, technological advancements, and consumer preferences, providing
restaurants with flexibility and agility to stay competitive in the industry.
Disadvantage:
25
crowded marketplaces.
10. Limited Accessibility: Not all restaurants may have the resources or
infrastructure to adopt online food ordering systems, limiting accessibility
for users who prefer to order from specific establishments that do not offer
online ordering options.
26
TESTING
Alpha Testing:
Acceptance testing is also sometimes called alpha testing. Be spoke systems are
developed for a single customer. The alpha testing proceeds until the system developer
and the customer agree that the provided system is an acceptable implementation of the
system requirements.
27
Beta Testing:
On the other hand, when a system is to be marked as a software product, another
process called beta testing is often conducted. During beta testing, a system is delivered
among a number of potential users who agree to use it. The customers then report
problems to the developers. This provides the product for real use and detects errors
which may not have been anticipated by the system developers.
Unit Testing:
Unit testing is about testing each unit/part of the application independently.
Different fragments and activities in this android application are tested for its
functionality during this phase. Each module is considered independently. It focuses on
each unit of software as implemented in the source code. It is white box testing. The
following unit test cases are run manually on Realme 5 Pro for its correctness.
Integration Testing:
Integration testing aims at constructing the program structure while at the same
constructing tests to uncover errors associated with interfacing the modules. Modules
are integrated by using the top-down approach.
After unit testing each module individually, the code is tested for inter module
navigation. Below are the test cases which test the interaction between different
activities and fragments in the project.
Validation Testing:
Validation testing was performed to ensure that all the functional and performance
requirements are met.
System Testing:
It is executing programs to check logical changes made in it with intention of
finding errors. A system is tested for online response, volume of transaction, recovery
from failure etc. System testing is done to ensure that the system satisfies all the user
requirements.
28
DRAWING
29
Data Flow Diagram:
30
CODING
Home Page:
<?php
include 'components/connect.php';
session_start();
if(isset($_SESSION['user_id'])){
$user_id = $_SESSION['user_id'];
}else{
$user_id = '';
};
include 'components/add_cart.php';
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1.0">
<title>home</title>
</head>
<body>
31
<section class="hero">
<div class="swiper-wrapper">
</div>
<div class="swiper-pagination"></div>
</div>
</section>
<section class="category">
32
<h1 class="title">food category</h1>
<div class="box-container">
</div>
</section>
<section class="products">
<div class="box-container">
<?php
$select_products = $conn->prepare("SELECT * FROM
`products` LIMIT 6");
$select_products->execute();
if($select_products->rowCount() > 0){
while($fetch_products = $select_products-
>fetch(PDO::FETCH_ASSOC)){
?>
<form action="" method="post" class="box">
<input type="hidden" name="pid" value="<?=
$fetch_products['id']; ?>">
<input type="hidden" name="name" value="<?=
$fetch_products['name']; ?>">
33
<input type="hidden" name="price" value="<?=
$fetch_products['price']; ?>">
<input type="hidden" name="image" value="<?=
$fetch_products['image']; ?>">
<a href="quick_view.php?pid=<?= $fetch_products['id']; ?>"
class="fas fa-eye"></a>
<button type="submit" class="fas fa-shopping-cart"
name="add_to_cart"></button>
<img src="uploaded_img/<?= $fetch_products['image']; ?>"
alt="">
<a href="category.php?category=<?=
$fetch_products['category']; ?>" class="cat"><?=
$fetch_products['category']; ?></a>
<div class="name"><?= $fetch_products['name']; ?></div>
<div class="flex">
<div class="price"><span>₹</span><?=
$fetch_products['price']; ?></div>
<input type="number" name="qty" class="qty" min="1"
max="99" value="1" maxlength="2">
</div>
</form>
<?php
}
}else{
echo '<p class="empty">no products added yet!</p>';
}
?>
</div>
<div class="more-btn">
<a href="menu.php" class="btn">veiw all</a>
</div>
</section>
<script src="https://unpkg.com/swiper@8/swiper-
bundle.min.js"></script>
<script>
34
var swiper = new Swiper(".hero-slider", {
loop:true,
grabCursor: true,
effect: "flip",
pagination: {
el: ".swiper-pagination",
clickable:true,
},
});
</script>
</body>
</html>
Registration Page:
<?php
include 'components/connect.php';
session_start();
if(isset($_SESSION['user_id'])){
$user_id = $_SESSION['user_id'];
}else{
$user_id = '';
};
if(isset($_POST['submit'])){
$name = $_POST['name'];
$name = filter_var($name, FILTER_SANITIZE_STRING);
$email = $_POST['email'];
$email = filter_var($email, FILTER_SANITIZE_STRING);
$number = $_POST['number'];
$number = filter_var($number, FILTER_SANITIZE_STRING);
$pass = sha1($_POST['pass']);
$pass = filter_var($pass, FILTER_SANITIZE_STRING);
$cpass = sha1($_POST['cpass']);
$cpass = filter_var($cpass, FILTER_SANITIZE_STRING);
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1.0">
<title>register</title>
</head>
<body>
36
<section class="form-container">
</section>
</body>
</html>
Login Page:
<?php
include 'components/connect.php';
session_start();
if(isset($_SESSION['user_id'])){
$user_id = $_SESSION['user_id'];
}else{
$user_id = '';
37
};
if(isset($_POST['submit'])){
$email = $_POST['email'];
$email = filter_var($email, FILTER_SANITIZE_STRING);
$pass = sha1($_POST['pass']);
$pass = filter_var($pass, FILTER_SANITIZE_STRING);
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1.0">
<title>login</title>
</head>
<body>
38
<section class="form-container">
</section>
</body>
</html>
About Page:
<?php
include 'components/connect.php';
session_start();
if(isset($_SESSION['user_id'])){
$user_id = $_SESSION['user_id'];
}else{
$user_id = '';
};
?>
<!DOCTYPE html>
<html lang="en">
39
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1.0">
<title>about</title>
</head>
<body>
<div class="heading">
<h3>about us</h3>
<p><a href="home.php">home</a> <span> / about</span></p>
</div>
<section class="about">
<div class="row">
<div class="image">
<img src="images/about-img.svg" alt="">
</div>
<div class="content">
<h3>why choose us?</h3>
<p>At our location in Chatrapati Sambhajinagar
(Aurangabad) or online, you will find the best dishes you didn't
know you craved: Delicious Pizza, Cheezy Hamburger, Roasted Chicken
like your mama makes, and many more. Forget about the daily stress
and come relax with us. After tasting any of our menu items, you
will never want to leave!"!</p>
<a href="menu.html" class="btn">our menu</a>
40
</div>
</div>
</section>
<section class="steps">
<div class="box-container">
<div class="box">
<img src="images/step-1.png" alt="">
<h3>choose order</h3>
</div>
<div class="box">
<img src="images/step-2.png" alt="">
<h3>fast delivery</h3>
</div>
<div class="box">
<img src="images/step-3.png" alt="">
<h3>enjoy food</h3>
</div>
</div>
</section>
<section class="reviews">
<div class="swiper-wrapper">
41
<div class="swiper-slide slide">
<img src="images/pic-1.png" alt="">
<p>I like the roasted chicken its just crispy and
delicious.</p>
<div class="stars">
<i class="fas fa-star"></i>
<i class="fas fa-star"></i>
<i class="fas fa-star"></i>
<i class="fas fa-star"></i>
<i class="fas fa-star-half-alt"></i>
</div>
<h3>Kartik Nikam</h3>
</div>
</div>
<div class="swiper-pagination"></div>
</div>
</section>
43
<script src="https://unpkg.com/swiper@8/swiper-
bundle.min.js"></script>
<script>
</script>
</body>
</html>
Menu Page:
<?php
include 'components/connect.php';
session_start();
44
if(isset($_SESSION['user_id'])){
$user_id = $_SESSION['user_id'];
}else{
$user_id = '';
};
include 'components/add_cart.php';
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1.0">
<title>menu</title>
</head>
<body>
<div class="heading">
<h3>our menu</h3>
<p><a href="home.php">home</a> <span> / menu</span></p>
</div>
<section class="products">
<div class="box-container">
<?php
45
$select_products = $conn->prepare("SELECT * FROM
`products`");
$select_products->execute();
if($select_products->rowCount() > 0){
while($fetch_products = $select_products-
>fetch(PDO::FETCH_ASSOC)){
?>
<form action="" method="post" class="box">
<input type="hidden" name="pid" value="<?=
$fetch_products['id']; ?>">
<input type="hidden" name="name" value="<?=
$fetch_products['name']; ?>">
<input type="hidden" name="price" value="<?=
$fetch_products['price']; ?>">
<input type="hidden" name="image" value="<?=
$fetch_products['image']; ?>">
<a href="quick_view.php?pid=<?= $fetch_products['id']; ?>"
class="fas fa-eye"></a>
<button type="submit" class="fas fa-shopping-cart"
name="add_to_cart"></button>
<img src="uploaded_img/<?= $fetch_products['image']; ?>"
alt="">
<a href="category.php?category=<?=
$fetch_products['category']; ?>" class="cat"><?=
$fetch_products['category']; ?></a>
<div class="name"><?= $fetch_products['name']; ?></div>
<div class="flex">
<div class="price"><span>₹</span><?=
$fetch_products['price']; ?></div>
<input type="number" name="qty" class="qty" min="1"
max="99" value="1" maxlength="2"">
</div>
</form>
<?php
}
}else{
echo '<p class="empty">no products added yet!</p>';
}
?>
</div>
</section>
46
<!-- footer section starts -->
<?php include 'components/footer.php'; ?>
<!-- footer section ends -->
</body>
</html>
Order Page:
<?php
include 'components/connect.php';
session_start();
if(isset($_SESSION['user_id'])){
$user_id = $_SESSION['user_id'];
}else{
$user_id = '';
header('location:home.php');
};
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1.0">
<title>orders</title>
</head>
<body>
47
<!-- header section starts -->
<?php include 'components/user_header.php'; ?>
<!-- header section ends -->
<div class="heading">
<h3>orders</h3>
<p><a href="html.php">home</a> <span> / orders</span></p>
</div>
<section class="orders">
<div class="box-container">
<?php
if($user_id == ''){
echo '<p class="empty">please login to see your
orders</p>';
}else{
$select_orders = $conn->prepare("SELECT * FROM `orders`
WHERE user_id = ?");
$select_orders->execute([$user_id]);
if($select_orders->rowCount() > 0){
while($fetch_orders = $select_orders-
>fetch(PDO::FETCH_ASSOC)){
?>
<div class="box">
<p>placed on : <span><?= $fetch_orders['placed_on'];
?></span></p>
<p>name : <span><?= $fetch_orders['name']; ?></span></p>
<p>email : <span><?= $fetch_orders['email']; ?></span></p>
<p>number : <span><?= $fetch_orders['number']; ?></span></p>
<p>address : <span><?= $fetch_orders['address'];
?></span></p>
<p>payment method : <span><?= $fetch_orders['method'];
?></span></p>
<p>your orders : <span><?= $fetch_orders['total_products'];
?></span></p>
<p>total price : <span>₹<?=
$fetch_orders['total_price']; ?>/-</span></p>
<p> payment status : <span style="color:<?php
if($fetch_orders['payment_status'] == 'pending'){ echo 'red';
}else{ echo 'green'; }; ?>"><?= $fetch_orders['payment_status'];
?></span> </p>
</div>
<?php
}
48
}else{
echo '<p class="empty">no orders placed yet!</p>';
}
}
?>
</div>
</section>
</body>
</html>
Contact Page:
<?php
include 'components/connect.php';
session_start();
if(isset($_SESSION['user_id'])){
$user_id = $_SESSION['user_id'];
}else{
$user_id = '';
};
if(isset($_POST['send'])){
$name = $_POST['name'];
$name = filter_var($name, FILTER_SANITIZE_STRING);
$email = $_POST['email'];
$email = filter_var($email, FILTER_SANITIZE_STRING);
$number = $_POST['number'];
$number = filter_var($number, FILTER_SANITIZE_STRING);
$msg = $_POST['msg'];
$msg = filter_var($msg, FILTER_SANITIZE_STRING);
49
$select_message->execute([$name, $email, $number, $msg]);
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1.0">
<title>contact</title>
</head>
<body>
<div class="heading">
<h3>contact us</h3>
<p><a href="home.php">home</a> <span> / contact</span></p>
</div>
50
<!-- contact section starts -->
<section class="contact">
<div class="row">
<div class="image">
<img src="images/contact-img.svg" alt="">
</div>
</div>
</section>
</body>
</html>
51
CONCLUSION
52
REFERENCE
53