VISVESVARAYA TECHNOLOGICAL UNIVERSITY

JNANASANGAMA, BELAGAVI – 590018

Mini Project
Report on
AGRICULTURE BASED MANAGEMENT SYSTEM

Bachelor of
Engineering in
COMPUTER SCIENCE AND ENGINEERING
Submitted by
1BG19CS009 AKSHAT SAXENA
V SEMESTER
Dr. Sreevidya R C
Associate Professor, Dept. of CSE
BNMIT,Bengaluru

B.N.M. Institute of Technology

An Autonomous Institution under VTU,
Approved by AICTE, Accredited as Grade A Institution by NAAC.
All eligible UG branches – CSE, ECE, EEE, ISE & Mech. Engg. are Accredited
by NBA for academic years 2018-19 to 2021-22 & valid upto 30.06.2022
Post box no. 7087, 27th cross, 12th Main, Banashankari 2nd Stage, Bengaluru-560070, INDIA
Ph: 91-80-26711780/81/82 Email: [email protected], www.bnmit.org

Department of Computer Science and Engineering

Febraury-2022
 B.N.M. Institute of Technology
An Autonomous Institution under VTU,
Approved by AICTE, Accredited as Grade A Institution by NAAC.
All eligible UG branches – CSE, ECE, EEE, ISE & Mech. Engg. are Accredited
by NBA for academic years 2018-19 to 2021-22 & valid upto 30.06.2022
Post box no. 7087, 27th cross, 12th Main, Banashankari 2nd Stage, Bengaluru-560070, INDIA
Ph: 91-80-26711780/81/82 Email: [email protected], www.bnmit.org

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CERTIFICATE
Certified that the mini project work entitled Agriculture based Management System carried out by

Mr. AKSHAT SAXENA (1BG18CS009), is a bonafide student of V Semester, BNM Institute of

Technology in partial fulfillment for the award of Bachelor of Engineering in COMPUTER

SCIENCE AND ENGINEERING of Visvesvaraya Technological University, Belagavi during the

year 2021-22. It is certified that all corrections / suggestions indicated for Internal Assessment have

been incorporated in the report deposited in the departmental library. The project report has been

approved as it satisfies the academic requirements in respect of mini project work prescribed for the

said degree.

Dr. Sreevidya R C Dr. Sahana D. Gowda

Associate Professor Professor and HOD
Department of CSE Department of CSE
BNMIT, Bengaluru BNMIT, Bengaluru

Name and Signature

Examiner 1:

Examiner 2:
 ABSTRACT

Khet Express: An Agriculture based Management System is an online website that helps buyers
to shop for their desired Fruits and vegetables sitting comfortably at home along with their
family. These days people want to explore as many options and are mostly interested in getting
things delivered at home without them going outside. Buyers would not want to face external
factors or buy bad products from any vegetable seller, customers rather feel buying fresh
products online is better than offline. So, this management system works as a boon to both the
farmer and the customer. The sellers can put up all the available products online along with the
required details, buyers can make orders, know what they have ordered, etc. On the other side, it
allows the users to have their own accounts where they can log into or register into the website
and check the products, add it to the cart, place order, view the cart in order to decide about it
again, and logout safely when they are done. Khet Express System will make better connection
among Farmers and Buyers ensure quality food. It will also Standardize and increase efficiency
of Agro-culture process
The completion of this project brings with a sense of satisfaction, but it is never complete without
thanking the persons responsible for its successful completion.

I take this opportunity to express our profound gratitude to Shri. Narayan Rao R Maanay, Secretary,
BNMIT, Bengaluru for his constant support and encouragement. I would like to express my special
thanks to Prof. T. J. Rama Murthy, director, BNMIT, Bengaluru and S Y Kulkarni, Additional
Director, BNMIT, Bengaluru for their constantguidance towards our goals and professions. I extend
my deep sense of sincere gratitude to Dr. Krishnamurthy G.N, Principal, BNMIT, Bengaluru, for
providing us facilities required for the project. I would also like to thank Prof Eishwar Maanay,
Dean Administration, BNMIT,Bengaluru, for providing us useful suggestions required for the project.
I express my in-depth, heartfelt, sincere gratitude to Dr. Sahana D. Gowda, Professor and HOD,
Department of Computer Science and Engineering, BNMIT, Bengaluru, for her valuable suggestions
and support.I extend my heartfelt, sincere gratitude to Dr. Sreevidya R C, Associate Professor,
Department of Computer Science and Engineering, BNMIT, Bengaluru, for completion of the project.
Finally, I would like to thank all the faculty members of Department of ComputerScience and
Engineering, BNMIT, Bengaluru, for their support. I would like to thank our family and friends for
their unfailing moral support and encouragement.

AKSHAT SAXENA
1BG19CS009
CONTENTS PAGE NO.
ABSTRACT I
ACKNOWLEDGEMENT II
1. INTRODUCTION 1
1.1 Overview of Database Management System 1
1.2 Problem Statement 2
1.3 Objectives of the Project 2
1.4 Background Study 2
2. Software Requirement Specifications 3
2.1 Hardware Requirements 3
2.2 Software Requirements 3
2.3 Front-end Tools 3
2.4 Back-end Tools 3
3. SYSTEM DESIGN 4
3.1 Schema Diagram 4
3.2 ER Diagram 5
3.3 Overview of GUI 5
3.4 Normalization 6
4. IMPLEMENTATION 8
4.1 Table creation 8
4.2 Description of Table 12
4.3 Populated Tables 15
4.4 SQL Triggers & Stored Procedures 17
4.5 Database connectivity 18
4.6 Modules 20
5 RESULTS 22
6 CONCLUSION AND FUTURE ENHANCEMENTS 30
FIG NO. FIGURE NAME PAGE NO.
3.1 Schema Diagram 4
3.2 E-R Diagram of KhetExpress 5
4.1 Description of Blogdata table 12
4.2 Description of BlogFeedback table 12
4.3 Description of Buyer table 13
4.4 Description of Farmer table 13
4.5 Description of Fproduct table 14
4.6 Description of Likes table 14
4.7 Description of mycart table 15
4.8 Description of Transaction table 15
4.9 Values of Blogdata table 15
4.10 Values of BlogFeedback table 16
4.11 Values of Buyer table 16
4.12 Values of Farmer table 16
4.13 Values of Fproduct table 16
4.14 Values of Likes table 17
4.15 Values of Transaction table 17
4.16 Trigger Implementation 18
4.17 Workflow of System 20
4.18 Modules of Khet Express 21
5.1 Home Page 22
5.2 Registration Page 22
5.3 Login Page 23
5.4 Profile Page 23
5.5 Add product Page 24
5.6 Update profile Page 24
5.7 Home2 Page 25
5.8 About Page 25
5.9 Catalogue Page 26
5.10 My cart Page 26
5.11 Transaction Page 27
5.12 Transaction successful Page 27
5.13 Blog View Page 28
5.14 Blog Write Page 28
5.15 Logout Page 29
 INTRODUCTION

1.1 Overview of Database Management System

A Database is a collection of related data organized in a way that data can be easily accessed,
managed and updated. Any piece of information can be a data, for example name of your school.
Database is actually a place where related piece of information is stored and various operations
can be performed on it. A DBMS is a software that allows creation, definition and manipulation
of database. DBMS also provides protection and security to database. It maintains data
consistency in case of multiple users. The database system can be divided into four components:
● The database system can be divided into System developer and End users.
● Database application: Database application may be Personal, Departmental, Enterprise
and Internal.
● DBMS: Software that allow users to define, create and manages database access.
● Database: Collection of logical data. Functions of database management system:
1. Provides Recovery services.
2. Provides utility.
3. Provides data Independence.
4. Provides a clear and logical view of the process that manipulates data.
Advantages of DBMS: ● Segregation of application program ● Minimal data duplicity ●
Reduced development time and maintenance need ● Easy retrieval of data
Khet Express is the farmer system where they can plan, monitor and analyze the activity of the
farmers production system. It manages farmer operation with one system and organizes data in
one place. It helps smart farmers become even smarter. This creates in partnership with growers
and buyers. It inspires farmer to produce and buyers to consume fresh goods. Khet Express
System will make better connection among Farmers and Buyers ensure quality food. It will also
Standardize and increase efficiency of Agro culture process.
1.2 PROBLEM STATEMENT
Design a project where farmers and buyers can create their accounts, they can buy or sell the
products including fruits, vegetables, and grains using this website. They can also review the
products and add a brief/blog regarding the same.

1.3 OBJECTIVES OF THE PROJECT

The specific objectives of the project include:
● To provide qualitative foods to the buyers.
● Implementing an automated/online Khet Express system.
● To inspire farmer to produce quality goods and supply to the buyers.
● Eco-friendly farming system.
● It is focused on studying the existing system of Agro Culture and to make sure that the
peoples are getting quality fresh goods.
● Less effort and less labor intensive, as the primary cost and focus primary on creating,
managing, and running a secure quality food supply.
● Increasing number of buyers as individuals will find it easier and more convenient to buy
goods. Easy management.

1.4 BACKGROUND STUDY

India is fourth largest agriculture sector in the world. Agriculture sector provides employment to
over two third population of the country. Not only this, agriculture is major source of income for
more than 75% Indians. Although agriculture is of great significance to the national economy yet
the condition of Indian farmers and other individuals depended on the sector is unfortunate.
Creating a Database Management System like Khet Express can help Farmer’s plan, monitor and
analyze the activity of the production system. It manages the organization of data in one place. It
also helps farmers to become smart. It will also Standardize and increase efficiency of Agro
culture process.The basic tools used to build websites are HTML, CSS and PHP. HTML
describes the elements used in the given website, CSS is used for styling the website and PHP is
an open-source, interpreted, and object-oriented scripting language that can be executed at the
server-side. This allows us to access the MYSQL database which we will be using as the back
end to store the data about the Khet Express website.
 SYSTEM REQUIREMENTS

2.1 SOFTWARE REQUIREMENT SPECIFICATION (SRS)

Requirement analysis for web application encompasses three major tasks: formulation,
requirements gathering and analysis modelling. During formulation, the basic motivation and
goals for the web application are identified, and the categories of users are defined. In the
requirements gathering phase, the content and functional requirements are listed, and interaction
scenarios written from end-user’s point-of-view are developed. This intent is to establish a basic
understanding of why the web application is built, who will use it, and what problems it will
solve for its users.

​ Hardware requirements:

Processor: 11th Gen Intel(R) Core (TM) i7-1165G7 (Minimum i3)

Clock speed: @ 2.80GHz (Minimum 1.8 GHz)
Screen resolution: 1920 X 1080 (1024 X 768 recommended)
RAM: 16 GB (Minimum 2 GB)
Disk space: 1TB SSD (Minimum 15 GB HDD)
Input Output Console for interaction

​ Software requirements:
● Oracle SQL*Plus Release 11.1.0.6.0/MYSQL.
● Visual Studio Code IDE.
● Windows 7 or higher.
● Google chrome Browser (Chrome has an extensive compatibility list with many modules
and hence is preferred by many web developers)
● PhpMyAdmin.
● Chrome dev tools (for inspections and verifications of element placement).

​ Front end tools used: HTML, CSS.

​ Back-end tools used: PHP, MYSQL.

 SYSTEM DESIGN

System design is the process of defining the architecture, modules, interfaces and data for a
system to satisfy specific requirements. System design could be seen as the application of system
theory to product development. There is some overlap with the disciplines of systems analysis,
systems architecture and systems engineering.

3.1 SCHEMA DIAGRAM

A database schema is the skeleton structure that represents the logical view of the entire
database. It defines how the data is organized and how the relations among them are associated.
It formulates all the constraints that are to be applied on the data. A database schema defines its
entities and the relationship among them. It contains a descriptive detail of the database, which
can be depicted by means of schema diagrams. It’s the database designers who design the
schema to help programmers understand the database and make it useful.
3.2 ER DIAGRAM
An entity–relationship model describes interrelated things of interest in a specific domain of
knowledge. A basic ER model is composed of entity types and specifies relationships that can
exist between instances of those entity types. Consequently, the ER model becomes an abstract
data model that defines a data or information structure which can be implemented in a database,
typically a relational database.

3.3 Overview of GUI

GUI is a program interface that takes advantage of the computer's graphics capabilities to make
the program easier to use. Well-designed graphical user interfaces can free the user from learning
complex command languages. On the other hand, many users find that they work more
effectively with a command-driven interface, especially if they already know the command
language.
Hypertext Markup Language (HTML) is the standard markup language for creating web pages
and web applications. With JavaScript it forms a triad of cornerstone technologies for the World
Wide Web. Web browsers receive HTML documents from a web server or from local storage and
render them into multimedia web pages. HTML describes the structure of a web page
semantically and originally included cues for the appearance of the document.
Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a
document written in a markup language like HTML. CSS is a cornerstone technology of the
World Wide Web, alongside HTML and JavaScript. CSS is designed to enable the separation of
presentation and content, including layout, colors, and fonts. This separation can improve content
accessibility, provide more flexibility and control in the specification of presentation
characteristics, enable multiple web pages to share formatting by specifying the relevant CSS in
a separate .css file, and reduce complexity and repetition in the structural content.

3.4 Normalization
Normalization is a process of analyzing the given relation schema based on their functional
dependencies and primary key to achieve desirable properties of minimizing redundancy and
minimizing insert, delete, update anomaly. The normalization process takes a relation schema
through a series of tests to certify whether it satisfies a certain normal form. The normal form of
a relation refers to the highest normal form condition that it meets, and hence the degree to which
it has been normalized.
Normalization rules are divided into the following normal form:
1. First Normal Form
2. Second Normal Form
3. Third Normal Form
4. Boyce-Codd Normal Form
3.4.1 First Normal Form

The first normal form states that the domain of an attribute must include only atomic (simple,
individual) values and that the value of any attribute in a tuple must be a single value from the
domain of the attribute. Consider the relations of the Khet Express System, all the relations are in
1NF as they have neither any multivalued attributes nor composite attributes. Hence the relations
are said to be in 1NF.
3.4.2 Second Normal Form
Second normal from is based on the concept of full functional dependency. A functional
dependency X -> Y is a full functional dependency if removal of any attribute A from X means
that the dependency does not hold anymore. A relation schema R is in 2NF if every nonprime
attribute A in R is fully functionally dependenton the primary key of R.
3.4.3 Third Normal Form
The third normal form is based on the concept of transitive dependency. A relation schema R is
in 3NF if it satisfies 2NF and no non-prime attribute of R is transitively dependent on the
primary key. A relation schema R is in 3NF if every nonprime attribute of R meets both of the
following conditions:
● It is fully functionally dependent on every key of R.
● It is non-transitively dependent on every key of R.

The relations used in this database are fully functionally dependent on its key attribute and do not
hold any transitive dependencies. Hence all the relations are in 3NF.
4.1 Table Creation
In the tables, data is organized in row and column format. The rows represent a unique record
and the columns represent the attributes of a given table. The tables provide the overall structure
of the different tables that are used; showcasing the various attributes and the respective data
types.

CREATE TABLE `blogdata` (

`blogId` int(10) NOT NULL,
`blogUser` varchar(256) NOT NULL,
`blogTitle` varchar(256) NOT NULL,
`blogContent` longtext NOT NULL,
`blogTime` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE
current_timestamp(),
`likes` int(10) NOT NULL
);

CREATE TABLE `buyer` (

`bid` int(100) NOT NULL,
`bname` varchar(100) NOT NULL,
`busername` varchar(100) NOT NULL,
`bpassword` varchar(100) NOT NULL
`bhash` varchar(100) NOT NULL,
`bemail` varchar(100) NOT NULL,
`bmobile` varchar(100) NOT NULL,
`baddress` text NOT NULL,
`bactive` int(100) NOT NULL
);
CREATE TABLE `farmer` (
`fid` int(255) NOT NULL,
`fname` varchar(255) NOT NULL,
`fusername` varchar(255) NOT NULL,
`fpassword` varchar(255) NOT NULL,
`fhash` varchar(255) NOT NULL,
`femail` varchar(255) NOT NULL,
`fmobile` varchar(255) NOT NULL,
`faddress` text NOT NULL,
`factive` int(255) NOT NULL,
`frating` int(11) NOT NULL,
`picExt` varchar(255) NOT NULL,
`picStatus` int(10) NOT NULL
);
CREATE TABLE `fproduct` (
`fid` int(255) NOT NULL,
`pid` int(255) NOT NULL,
`product` varchar(255) NOT NULL,
`pcat` varchar(255) NOT NULL,
`pinfo` varchar(255) NOT NULL,
`price` float NOT NULL,
`pimage` blob NOT NULL,
`picStatus` int(10) NOT NULL
);

CREATE TABLE `mycart` (

`bid` int(10) NOT NULL,
`pid` int(10) NOT NULL,
`fproduct_pid` int(255) NOT NULL
);
CREATE TABLE `transaction` (
 `tid` int(10) NOT NULL,
`bid` int(10) NOT NULL,
`pid` int(10) NOT NULL,
`name` varchar(255) NOT NULL,
`city` varchar(255) NOT NULL,
`mobile` varchar(255) NOT NULL,
`email` varchar(255) NOT NULL,
`pincode` varchar(255) NOT NULL,
`addr` varchar(255) NOT NULL
);
ALTER TABLE `blogdata`
ADD PRIMARY KEY (`blogId`);
ALTER TABLE `blogfeedback`
ADD KEY `f6` (`blogId`);

ALTER TABLE `buyer`

ADD PRIMARY KEY (`bid`);

ALTER TABLE `farmer`

ADD PRIMARY KEY (`fid`),
ADD KEY `fid` (`fid`),
ADD KEY `fid_2` (`fid`),
ADD KEY `fid_3` (`fid`);

ALTERTABLE`fproduct`
ADD PRIMARY KEY (`pid`),
ADD KEY `fid` (`fid`);

ALTERTABLE`transactio
n` ADD PRIMARY KEY
(`tid`),
ADD KEY `f4` (`bid`),
ADD KEY `f5` (`pid`);
ALTER TABLE `farmer`
MODIFY `fid` int(255) NOT NULL AUTO_INCREMENT;

ALTER TABLE `blogfeedback`

ADD CONSTRAINT `f6` FOREIGN KEY (`blogId`) REFERENCES `blogdata` (`blogId`) ON
DELETE CASCADE;
ALTER TABLE `fproduct`
ADD CONSTRAINT `f3` FOREIGN KEY (`fid`) REFERENCES `farmer` (`fid`) ON DELETE
CASCADE;

ALTER TABLE `mycart`

ADD CONSTRAINT `f2` FOREIGN KEY (`pid`) REFERENCES `fproduct` (`pid`) ON
DELETE CASCADE;

ALTER TABLE `transaction`

ADD CONSTRAINT `f4` FOREIGN KEY (`bid`) REFERENCES `buyer` (`bid`) ON
DELETE CASCADE,
ADD CONSTRAINT `f5` FOREIGN KEY (`pid`) REFERENCES `fproduct` (`pid`) ON
DELETE CASCADE;
4.2 Table Description

Desc blogdata;

In the above figure, the structure of the Blogdata table is given to provide the details regarding
the blog written by the user of the website.

Desc buyer;

In the above figure, the structure of the Buyer table is given to provide the buyer personal details
like Name, Username, Password, Email, Mobile number, Contact Address.
desc farmer;

In the above figure, the structure of the Farmer table is given to provide the Farmer personal
details like Name, Username, Password, Email, obile number, Contact Address.

desc fproduct;

In the above figure, the structure of the Fproduct table is given to provide the Product details like
Name of the product, Category of the product, Price, Description and the Image of the product.
 desc mycart;
Desc mycart;

In the above figure,the structure of the mycart table is given to provide the cart details

In the above figure, the structure of the mycart table is given to provide the cart details.

Desc transaction;

In the above figure, the structure of the Transaction table is given to provide the Checkout details of
the transaction like the Buyer Id, Product Id, Name of the buyer, Mobile, Email and Address where
the products are to be delivered.

4.3 Populated Tables

select * from blogdata;

select * from buyer;

select * from farmer;

select * from fproduct;

select * from mycart;

select * from transaction;

 4.4 SQL Triggers and Stored Procedures
4.4.1 Trigger
A database trigger is procedural code that is automatically executed in response to certain events
on a particular table or view in a database. The trigger is mostly used for maintaining the
integrity of the information on the database. Triggers execute when a user tries to modify data
through a data manipulation language (DML) event. DML events are INSERT, UPDATE, or
DELETE statements on a table or view.

4.4.2 stored procedure

A stored procedure is a set of Structured Query Language (SQL) statements with an assigned name,
which are stored in a relational database management system as a group. If a query has to be written over
and over again, instead of having to write that query each time, it can be saved as a stored product and can
be executed just by calling the procedure. In addition, parameters can also be passed to the stored
procedure. Therefore, depending on the need, the stored procedure can act accordingly.

CREATE DEFINER=`root`@`localhost` PROCEDURE `product`() NOT DETERMINISTIC CONTAINS

SQL SQL SECURITY DEFINER SELECT `pid`,`product`,`pinfo`, `pimage`, `price`, `pcat`
FROM `fproduct` order by fid ASC

4.5 Database Connectivity

A Database connection is a facility in computer science that allows client software to talk
todatabase server software, whether on the same machine or not. A connection is required tosend
commands and receive answers, usually in the form of a result set. PHP has a pretty straight
forward method to working with MySQL databases.
There are five steps to make PHP database interaction:
1. Create a connection
2. Select database
3. Perform database query
4. Use return data
5. Close connection

PHP CODE
<?php
session_start()
//1. Create a database connection
$conn=mysql_connect('localhost','root','');
if($conn) echo "Connection Successful";
//2. Select a database to use
$db=mysql_select_db(‘KhetExpress’,$conn);
If($db) echo "Database selected!";
//3. Perform database query
$sql="Select * from buyer";
If(mysql_query($sql,$conn) echo "Rows selected";
$result = mysql_query($sql,$conn);
//4. Use returned data
While($row=mysql_fetch_array($result)
{
echo $row['username']; echo $row['email'];
}
//5. Close the
connection
mysql_close($conn);
?>
4.6 Modules
The below flowchart explains how the system runs in the real world. The system can be easily
implemented under various situations. Reusability is possible as and when required in this
application. There is flexibility in all the modules which makes the task of the user easier.
The first-time users are required to register to this site else the user will not be able to access the
features of the site. After successful registration, the user can log in to his account and view the
Catalogue and place orders
 RESULTS
Home Page: The below figure of the home page shows the first page of the application. The user
can go straight into the login page using this screen or go straight to registration using the
register tab.

SignUp: The below figure of the starting of registration page shows the various options the user
can register under like as a buyer or as a farmer.
Login Page: The below figure of the Login page shows the Username and Password fields for
which the user has to provide his/her credentials in order to login to the platform.

Profile Page: : The below figure of the Profile shows the various options the user can use to
Update their profiles, Access the main menu or Upload the Product in the Database.
Add product Page: The below figure of the Product addition page shows the various details to be
given in order to Upload the Product in the Database.

Update Profile Page: The below figure of the Update profile page shows the various details to be
given in order to update the Profile in the Database.
Home2 page: This is alternative to the main index page.

About Page: This provides us the Information regarding the project.

Catalogue Page: The below figure of the catalogue page provides us the different products which
can be added to the cart along with a quantity input box.

View Cart Page: The below figure shows the MyCart page which gives us the brief of the
products user added in his/her cart

.
Transaction Page: The below figure shows the transaction page where the Delivery details are to
be updated.

Transaction Successful Page: The below figure shows that the transaction is done successfully.
Blog View Page: In the below figure, the structure is given to provide the details regarding the
blog written by the user of the website. Users can give the blogs either upvotes or comments.

Blog Write Page: The below figure shows the Blog Write page where people can write the blogs
and upload it in the database.
Logout Page: The below figure shows that user got logged out successfully.
 CONCLUSION AND FUTURE ENHANCEMENTS
Conclusion
The proposed Management System provides a user-friendly and helpful means of booking and
purchasing Agro-products online without any confusion or problems that might occur usually.
Thus, the site modifies the usual way of service booking and thus creates a new platform for the
people to utilize and reap the benefits offered. This project reduces the efforts of both buyer and
farmer. This is also a more trustable and accurate way of handling data as there is a high risk of
data loss or data corruption in keeping offline records, thus improving data redundancy. Thus, we
can say our project is a very trustable and accurate type of data management for Agriculture data
management and will be very helpful in the real world.
The project teaches us the essential skills like:
● Understanding database handling and query processing.
● Implement, analyze and evaluate the project developed for an application.
● Demonstrate the working of different concepts of DBMS.

Future Enhancements
Due to time constraints, some features are not implemented yet and will be implemented soon.
We have not yet included a Billing System and Payment Gateway. A feedback module can be
incorporated in order provide feedback of the vegetables, fruits or cereals purchased by a buyer.
Furthermore, we are providing services on web platforms. The app version of the system might
come in near future. The bill details have to be entered by admin manually, we will automate this
in the future versions. There is also going to be some improvement in our user interface and we
are going to make it more user-friendly and attractive.