VISVESVARAYA TECHNOLOGICAL UNIVERSITY

Jnana Sangama, Belagavi-590018

A Database Management System Mini Project Report on

“MOBILE STORE MANAGEMENT SYSTEM”
Submitted in Partial fulfillment of the Requirements for the V Semester of the Degree of

Bachelor of Engineering in
Computer Science & Engineering
By
NITHIN C (1CR21CS412)

ADARSH PALANAKAR (1CR21CS400)

Under the Guidance of,

Dr. Sanchari Saha, Assistant Professor, Dept. of CSE

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CMR

INSTITUTE OF TECHNOLOGY
Affiliated to VTU, Approved by AICTE, Accredited by NBA and NAAC with “A++” Grade
ITPL MAIN ROAD, BROOKFIELD, BENGALURU-560037, KARNATAKA, INDIA
CMR INSTITUTE OF TECHNOLOGY
 Affiliated to VTU, Approved by AICTE, Accredited by NBA and NAAC with “A++” Grade
ITPL MAIN ROAD, BROOKFIELD, BENGALURU-560037, KARNATAKA, INDIA

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CERTIFICATE
This is to certify that the Database Management System Project work entitled “MOBILE
STORE MANAGEMENT SYSTEM” has been carried out by Nithin C (1CR21CS412)
and Adarsh Palanakar (1CR21CS400), bona fide students of CMR Institute of Technology,
Bengaluru in partial fulfillment for the award of the Degree of Bachelor of Engineering in
Computer Science and Engineering of the Visvesvaraya Technological University, Belagavi
during the year 2022-2023. It is certified that all corrections/suggestions indicated for the
Internal Assessment have been incorporated in the report deposited in the departmental
library. This Database Management System Project report has been approved as it satisfies the
academic requirements in respect of project work prescribed for the said Degree.

_____________________________ _____________________________
Signature of Guide Signature of HOD
(Dr. Sanchari Saha) (Dr. Shreekanth M Prabhu)
Assistant Professor Professor & HoD
Dept. of CSE, CMRIT Dept. of CSE, CMRIT
External Viva

Name of the Examiners Signature with date

1.

2.

ii
 DECLARATION

We, the students of V semester of Computer Science and Engineering, CMR Institute of
Technology, Bangalore declare that the project work entitled "Mobile Store Management
System" has been successfully completed under the guidance of Dr. Sanchari Saha, Assistant
Professor, Dept. of Computer Science and Engineering, and Mrs. Anjali Gupta, Assistant
Professor, CMR Institute of technology, Bengaluru. This project work is submitted in partial
fulfillment of the requirements for the award of the Degree of Bachelor of Engineering in
Computer Science and Engineering during the academic year 2022-2023. The matter embodied
in the project report has not been submitted previously by anybody for the award of any degree
or diploma to any university.

Place: Bangalore

Date: 12/01/2023
Team members:
NITHIN C (1CR21CS412)

ADARSH PALANAKAR (1CR21CS400)

iii
 ABSTRACT

The title of project is mobile shop management system. The main purpose of our project is to do
smart work and also, we can see that in this era of advanced technology we also have to do work
more smartly that’s why most of the shops need advanced techniques to do their work more
speedily and smartly that’s why storing or collecting important data on paper is not reliable and
also it has chance of missing that paper so we created this for storing most important data like
billing, customer information and product information. It will help to organize mobile shop data
in very systematic way.

Keywords: Management, Information, Billing, Data, Mobile

iv
 ACKNOWLEDGEMENT

I take this opportunity to express my sincere gratitude and respect to CMR Institute of
Technology, Bengaluru for providing me a platform to pursue my studies and carry out the
Database Management System Project.
It gives me an immense pleasure to express my deep sense of gratitude to Dr. Sanjay
Jain, Principal, CMRIT, Bengaluru, for his constant encouragement.
I would like to extend my sincere gratitude to Dr. Shreekanth M Prabhu, HOD,
Department of Computer Science and Engineering, CMRIT, Bengaluru, who has been a constant
support and encouragement throughout the course of this project.
I would like to thank my guide Dr. Sanchari Saha, Assistant Professor and
Mrs. Anjali Gupta, Assistant Professor, Department of Computer Science and Engineering,
for the valuable guidance throughout the tenure of the project work.
I would also like to thank all the faculty members of Department of Computer Science
and Engineering who directly or indirectly encouraged me.
Finally, I thank my parents and friends for all the moral support they have given me
during the completion of this work.

v
 TABLE OF CONTENTS

Contents Page No.

Certificate ii
Declaration iii
Abstract iv
Acknowledgement v
Table of contents vi
List of Figures vii
List of Tables viii
1. Introduction 1
1.1 Objectives
1.2 Scope of Project 1
2. System Requirements 2
2.1 Hardware Requirements 2
2.2 Software Requirements 2
3. Design 3
3.1 Tables 3
3.2 Schema Diagram 9
3.3 ER Diagram 10
4. Implementation 11
4.1 Execution of the project 11
4.2 SQL 11

5. Screenshots 23
5.1 Result Output 23

6. Conclusion and Future Scope 30

7. References 31

vi
 LIST OF FIGURES

Fig 3.1 Schema Diagram Error! Bookmark not defined.

Fig 3.2 ER Diagram 3

Fig 5.1 Admin login screen 10

Fig 5.2 Admin home screen 23

Fig 5.3 Product list Error! Bookmark not defined.

Fig 5.4 Inventory list Error! Bookmark not defined.

Fig 5.5 Order list Error! Bookmark not defined.

Fig 5.6 Sales report Error! Bookmark not defined.

Fig 5.7 Brand list Error! Bookmark not defined.

Fig 5.8 Category list Error! Bookmark not defined.

Fig 5.9 User login Error! Bookmark not defined.

Fig 5.10 User home screen Error! Bookmark not defined.

Fig 5.11 Smart phone screen Error! Bookmark not defined.

Fig 5.12 Accessories screen Error! Bookmark not defined.

Fig 5.13 Product categories Error! Bookmark not defined.

Fig 5.14 User cart Error! Bookmark not defined.

Error! Bookmark not defined.

vii
 LIST OF TABLES

Page No.
Table 3.1 Table Structure for brands table 3
Table 3.2 Table Structure for cart table 4
Table 3.3 Table Structure for categories table 4
Table 3.4 Table Structure for clients table 4
Table 3.5 Table Structure for inventory table 5
Table 3.6 Table Structure for orders table 5
Table 3.7 Table Structure for order_list table 6
Table 3.8 Table Structure for products table 6
Table 3.9 Table Structure for sales table 6
Table 3.10 Table Structure for sub_categories table 7
Table 3.11 Table Structure for system_info table 7
Table 3.12 Table Structure for users table 8

viii
MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 1
INTRODUCTION

In this rapid growing generation, technology is growing day by day. Our project is on mobile
shop management system for manage a mobile shop. In our project we have included billing
system, product, customer management, manage brands, manage sail details. We can add the
details of mobile, tablets, headphones and other products. Need of high speed data access is
necessary in today’s world. Record of employee and records of customers will be safely kept in
database. We can edit the data as well as retrieve the data whenever required. In existing system
details are maintained manually so it takes time to save and modify the data. It becomes very
difficult to maintain the data. So, we have prepared an enhanced system of mobile shop
management. This is a very useful for mobile shop to manage their shop easily.

1.1 Objectives
The specific objectives of the project include:

 To manage the details of Customers, Stock, Mobile, Payment, Sells.

 It manages all the information about Customers, Brands, Sells, Customers.
 The project is totally built at administrative end and thus only the administrator is
guaranteed the access.

1.2 Scope of the project

 This System has large scope for the Mobile Shop Management System& Mobile
Information.
 The System stores all information of the Mobiles.
 System can able to accept user request and manages information like Mobile’s as
well as the Customers and Clients
 System provides the facility of Mobile Information with their Prices.
 System Provide facility of payment and purchase Products

Dept. of CSE,SJBIT 2022-2023 Page 1

MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 2

SYSTEM REQUIREMENTS
The system requirements for a project outline the necessary hardware and software
resources for development, deployment, and operation. It is important to carefully
consider and plan for the system requirements of a project, as the wrong choices can lead
to performance issues, compatibility problems, or other issues that can impact the success
of the project.

2.1 Hardware Requirements

Server-side requirements include:

• Minimum dual core CPU, recommended quad core or above

• Minimum 8GB RAM

• 20GB Hard Drive Space

Client-side requirements are any device that is capable of connecting to the internet and
running a web browser.

2.2 Software Requirements

Server-side software requirements are:

● Client: Operating System

● Web Server: Apache Tomcat

● Database Server: MYSQL Server

● Languages: HTML, PHP, CSS

Client-side software can run on any device that supports an internet connection and a
web browser.

Dept. of CSE,SJBIT 2022-2023 Page 2

MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 3
DESIGN
The design chapter of this project report outlines the process and considerations that went
into the design of the project. This includes the identification of design goals and
objectives, the collection and analysis of data, the development of the system or product
design, and the validation and testing of the design. The design chapter provides a
comprehensive understanding of the project's design, and is based on established
principles and practices.

This project as following tables :

1. BRANDS
2. CART
3. CATEGORIES
4. CLIENTS
5. INVENTORY
6. ORDER_LIST
7. ORDERS
8. PRODUCTS
9. SALES
10. SUB_CATEGORIES
11. SYSTEM_INFO
12. USERS
The table details are as follows:

Table 3.1 BRANDS

Dept. of CSE,SJBIT 2022-2023 Page 3

MOBILE STORE MANAGEMENT SYSTEM

Table 3.2 CART

Table 3.3 CATEGORIES

Table 3.4 CLIENTS

Dept. of CSE,SJBIT 2022-2023 Page 4

MOBILE STORE MANAGEMENT SYSTEM

Table 3.5 INVENTORY

Table 3.6 ORDERS

Dept. of CSE,SJBIT 2022-2023 Page 5

MOBILE STORE MANAGEMENT SYSTEM

Table 3.7 ORDER_LIST

Table 3.8 PRODUCTS

Dept. of CSE,SJBIT 2022-2023 Page 6

MOBILE STORE MANAGEMENT SYSTEM

Table 3.9 SALES

Table 3.10 SUB_CATEGORIES

Table 3.11 SYSTEM_INFO

Dept. of CSE,SJBIT 2022-2023 Page 7

MOBILE STORE MANAGEMENT SYSTEM

Table 3.12 USERS

Dept. of CSE,SJBIT 2022-2023 Page 8

MOBILE STORE MANAGEMENT SYSTEM

3.1 Schema Diagram

Dept. of CSE,SJBIT 2022-2023 Page 9

MOBILE STORE MANAGEMENT SYSTEM

3.2 ER Diagram
The Entity Relationship (ER) diagram is a visual representation of the data model of the
eVoter project. It illustrates the entities, attributes, and relationships between the different
elements of the data model, and provides a clear overview of the organization and
structure of the data. The ER diagram is an important tool for understanding the
underlying data model of the eVoter project, and for identifying the relationships and
dependencies between different data entities. In the following sections, we will examine
the ER diagram in detail and discuss the design and implementation of the data model.

Figure 3.2: ER Diagram

Dept. of CSE,SJBIT 2022-2023 Page 10

 MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 4

IMPLEMENTATION
The implementation section of this project report outlines the steps and processes
involved in the development and deployment of the Mobile Store Management System
project. This includes the selection and configuration of tools and technologies, the design
and coding of the system, the testing and debugging of the system, and the deployment of
the system to a production environment. The implementation chapter provides a detailed
description of the project's implementation, and documents the challenges and successes
encountered during the development process. The purpose of the implementation chapter
is to provide insight into the project's technical execution and the rationale behind the
implementation decisions.

4.1 Execution of the project

To execute the project, first start the Xampp server, run Apache and MySQL, then run the
below commands in the chrome extension:

• Localhost/phpmyadmin

• Create database

• Import tables

• Localhost/mobile_store

4.2 SQL Stored procedures

Table structure for table `brands`

CREATE TABLE brands (

id int(30) NOT NULL,
name varchar(250) NOT NULL,
description text DEFAULT NULL,
status tinyint(1) NOT NULL DEFAULT 1,
date_created datetime NOT NULL DEFAULT current_timestamp()

Dept. of CSE,SJBIT 2022-2023 Page 11

 MOBILE STORE MANAGEMENT SYSTEM

) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO brands (id, name, description, status, date_created) VALUES

(1, 'Apple', 'Apple Company', 1, '2021-08-30 10:33:53');

Table structure for table `cart`

CREATE TABLE cart (

id int(30) NOT NULL,
client_id int(30) NOT NULL,
inventory_id int(30) NOT NULL,
price double NOT NULL,
quantity int(30) NOT NULL,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

Table structure for table `categories`

CREATE TABLE categories (

id int(30) NOT NULL,
category varchar(250) NOT NULL,
description text DEFAULT NULL,
status tinyint(1) NOT NULL DEFAULT 1,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO categories (id, category, description, status, date_created) VALUES

(1, 'Smart Phone', 'Smart Phone Products', 1, '2021-08-30 10:52:25');

Dept. of CSE,SJBIT 2022-2023 Page 12

 MOBILE STORE MANAGEMENT SYSTEM

Table structure for table clients

CREATE TABLE clients (

id int(30) NOT NULL,
firstname varchar(250) NOT NULL,
lastname varchar(250) NOT NULL,
gender varchar(20) NOT NULL,
contact varchar(15) NOT NULL,
email varchar(250) NOT NULL,
password text NOT NULL,
default_delivery_address text NOT NULL,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO client (id, firstname, lastname, gender, contact, email, password,
default_delivery_address, date_created) VALUES
(1, 'Claire', 'Blake', 'Female', '09123456789', 'cblake@gmail.com',
'cd74fae0a3adf459f73bbf187607ccea', 'Sample Address', '2021-08-30 15:32:20');

Table structure for table `inventory`

CREATE TABLE inventory (

id int(30) NOT NULL,
product_id int(30) NOT NULL,
quantity double NOT NULL,
price float NOT NULL,
date_created datetime NOT NULL DEFAULT current_timestamp(),
date_updated datetime DEFAULT NULL ON UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

Dept. of CSE,SJBIT 2022-2023 Page 13

 MOBILE STORE MANAGEMENT SYSTEM

INSERT INTO inventory (id, product_id, quantity, price, date_created, date_updated) VALUES
(1, 1, 15, 74990, '2021-08-30 13:24:01', NULL);

Table structure for table `orders`

CREATE TABLE orders (

id int(30) NOT NULL,
client_id int(30) NOT NULL,
delivery_address text NOT NULL,
payment_method varchar(100) NOT NULL,
order_type tinyint(1) NOT NULL COMMENT '1= pickup,2= deliver',
amount double NOT NULL,
status tinyint(2) NOT NULL DEFAULT 0,
paid tinyint(1) NOT NULL DEFAULT 0,
date_created datetime NOT NULL DEFAULT current_timestamp(),
date_updated datetime DEFAULT NULL ON UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO orders (id, client_id, delivery_address, payment_method, order_type, amount,

status, paid, date_created, date_updated) VALUES
(1, 1, 'Sample Address', 'Online Payment', 1, 75340, 1, 1, '2021-08-30 15:57:01', '2021-08-30
16:06:19');

Table structure for table `order_list`

CREATE TABLE order_list (

id int(30) NOT NULL,
order_id int(30) NOT NULL,

Dept. of CSE,SJBIT 2022-2023 Page 14

 MOBILE STORE MANAGEMENT SYSTEM

product_id int(30) NOT NULL,

quantity int(30) NOT NULL,
price double NOT NULL,
total double NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO order_list (id, order_id, product_id, quantity, price, total) VALUES
(1, 1, 1, 1, 74990, 74990),
(2, 1, 3, 1, 350, 350);

Table structure for table `products`

CREATE TABLE products (

id int(30) NOT NULL,
brand_id int(30) NOT NULL,
category_id int(30) NOT NULL,
sub_category_id int(30) NOT NULL,
name varchar(250) NOT NULL,
specs text NOT NULL,
status tinyint(1) NOT NULL DEFAULT 1,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO products (id, brand_id, category_id, sub_category_id, name, `specs`, status,
date_created) VALUES
(1, 1, 1, 0, 'iPhone Pro Max 12', '<ul class=\\\"techspecs-list\\\" role=\\\"list\\\" style=\\\"margin-
right: 0px; margin-bottom: 0px; margin-left: 0px; padding: 0px; list-style: none;\\\"><li
role=\\\"listitem\\\" style=\\\"margin: 0px; padding: 0px;\\\">Super Retina XDR display</li><li
role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding: 0px;\\\">6.7-inch (diagonal)
all-screen OLED display</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding:

Dept. of CSE,SJBIT 2022-2023 Page 15

 MOBILE STORE MANAGEMENT SYSTEM

0px;\\\">2778-by-1284-pixel resolution at 458 ppi</li></ul><p class=\\\"typography-caption

model-caption\\\" style=\\\"margin: 0.8em 0px 0px; padding: 0px; line-height: 1.33337;\\\">The
iPhone 12 Pro Max display has rounded corners that follow a beautiful curved design, and these
corners are within a standard rectangle. When measured as a standard rectangular shape, the
screen is 6.68 inches diagonally (actual viewable area is less).</p><p style=\\\"margin: 0.8em
0px 0px; padding: 0px; line-height: 1.33337;\\\"><br></p><ul class=\\\"techspecs-list\\\"
role=\\\"list\\\" style=\\\"margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding: 0px;
list-style: none;\\\"><li role=\\\"listitem\\\" style=\\\"margin: 0px; padding: 0px;\\\">HDR
display</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding: 0px;\\\">True
Tone</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding: 0px;\\\">Wide color
(P3)</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding: 0px;\\\">Haptic
Touch</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding:
0px;\\\">2,000,000:1 contrast ratio (typical)</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em
0px 0px; padding: 0px;\\\">800 nits max brightness (typical); 1,200 nits max brightness
(HDR)</li><li role=\\\"listitem\\\" style=\\\"margin: 0.4em 0px 0px; padding:
0px;\\\">Fingerprint-resistant oleophobic coating</li><li role=\\\"listitem\\\" style=\\\"margin:
0.4em 0px 0px; padding: 0px;\\\">Support for display of multiple languages and
characters simultaneously</li></ul>', 1, '2021-08-30 12:19:22');

Table structure for table sales

CREATE TABLE sales (
id int(30) NOT NULL,
order_id int(30) NOT NULL,
total_amount double NOT NULL,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO sales (id, order_id, total_amount, date_created) VALUES

(1, 1, 75340, '2021-08-30 15:57:01');

Dept. of CSE,SJBIT 2022-2023 Page 16

 MOBILE STORE MANAGEMENT SYSTEM

Table structure for table `sub_categories`

CREATE TABLE sub_categories (

id int(30) NOT NULL,
parent_id int(30) NOT NULL,
sub_category varchar(250) NOT NULL,
description text NOT NULL,
status tinyint(1) NOT NULL DEFAULT 1,
date_created datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

NSERT INTO sub_categories (id, parent_id, sub_category, description, status, date_created)

VALUES
(1, 3, 'Batteries', 'Mobile Batteries', 1, '2021-08-30 11:28:40');

Table structure for table `system_info`

CREATE TABLE system_info (

id int(30) NOT NULL,
meta_field text NOT NULL,
meta_value text NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO system_info (id, meta_field, meta_value) VALUES

(1, 'name', 'Mobile Store Management System - PHP');

Dept. of CSE,SJBIT 2022-2023 Page 17

 MOBILE STORE MANAGEMENT SYSTEM

Table structure for table `users`

CREATE TABLE users(

id int(50) NOT NULL,
firstname varchar(250) NOT NULL,
lastname varchar(250) NOT NULL,
username text NOT NULL,
password text NOT NULL,
avatar text DEFAULT NULL,
last_login datetime DEFAULT NULL,
type tinyint(1) NOT NULL DEFAULT 0,
date_added datetime NOT NULL DEFAULT current_timestamp(),
date_updated datetime DEFAULT NULL ON UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO users (id, firstname, lastname, username, password, avatar, last_login, type,
date_added, date_updated) VALUES
(1, 'Adminstrator', 'Admin', 'admin', '0192023a7bbd73250516f069df18b500',
'uploads/1624240500_avatar.png', NULL, 1, '2021-01-20 14:02:37', '2021-06-21 09:55:07');

Indexes for table `brands`

ALTER TABLE brands

ADD PRIMARY KEY (id);

--
Indexes for table `cart’

ALTER TABLE cart

Dept. of CSE,SJBIT 2022-2023 Page 18

 MOBILE STORE MANAGEMENT SYSTEM

ADD PRIMARY KEY (id);

--
Indexes for table `categories`

ALTER TABLE categories

ADD PRIMARY KEY (id);
Indexes for table `clients`

ALTER TABLE clients

ADD PRIMARY KEY (id);

--
Indexes for table `inventory`

ALTER TABLE inventory

ADD PRIMARY KEY (id);

--
Indexes for table `orders`

ALTER TABLE orders

ADD PRIMARY KEY (id);

--
Indexes for table `order_list`

ALTER TABLE order_list

ADD PRIMARY KEY (id);

--Indexes for table `products`

Dept. of CSE,SJBIT 2022-2023 Page 19

 MOBILE STORE MANAGEMENT SYSTEM

ALTER TABLE products

ADD PRIMARY KEY (id);

--
Indexes for table `sales`

ALTER TABLE sales

ADD PRIMARY KEY (id);

--
Indexes for table `sub_categories`

ALTER TABLE sub_categories

ADD PRIMARY KEY (id);

--
Indexes for table `system_info`

ALTER TABLE system_info

ADD PRIMARY KEY (id);
Indexes for table `users`

ALTER TABLE users

ADD PRIMARY KEY (id);

AUTO_INCREMENT for table `brands`

ALTER TABLE brands

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=9;

Dept. of CSE,SJBIT 2022-2023 Page 20

MOBILE STORE MANAGEMENT SYSTEM

AUTO_INCREMENT for table `cart`

ALTER TABLE cart

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;

AUTO_INCREMENT for table `categories’

ALTER TABLE categories

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6;

AUTO_INCREMENT for table `clients`

ALTER TABLE clients

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

AUTO_INCREMENT for table `inventory`

ALTER TABLE inventory

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;

AUTO_INCREMENT for table `orders`

ALTER TABLE orders

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

AUTO_INCREMENT for table `order_list`

ALTER TABLE order_list

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;

Dept. of CSE,SJBIT 2022-2023 Page 21

MOBILE STORE MANAGEMENT SYSTEM

AUTO_INCREMENT for table `products`

ALTER TABLE products

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
AUTO_INCREMENT for table `sales`

ALTER TABLE sales

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

AUTO_INCREMENT for table `sub_categories`

ALTER TABLE sub_categories

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;

AUTO_INCREMENT for table `system_info`

ALTER TABLE system_info

MODIFY id int(30) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=15;

AUTO_INCREMENT for table `users`

ALTER TABLE users

MODIFY id int(50) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
COMMIT;

Dept. of CSE,SJBIT 2022-2023 Page 22

MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 5
SCREENSHOTS
This chapter presents the findings of the Mobile Store Management System project and
discusses the results of the completed project. This includes a collection of snapshots of
the output and an analysis of the results, the implications and conclusions.

5.1 RESULT OUTPUT

Fig 5.1 Admin Login screen

Dept. of CSE,SJBIT 2022-2023 Page 23

MOBILE STORE MANAGEMENT SYSTEM

Fig 5.2 Admin Home Screen

Fig 5.3 Product list

Fig 5.4 Inventory list

Dept. of CSE,SJBIT 2022-2023 Page 24

MOBILE STORE MANAGEMENT SYSTEM

Fig 5.5 Order list

Dept. of CSE,SJBIT 2022-2023 Page 25

MOBILE STORE MANAGEMENT SYSTEM

Fig 5.6 Sales Report

Fig 5.7 Brand list

Fig 5.8 Category list

Dept. of CSE,SJBIT 2022-2023 Page 26

MOBILE STORE MANAGEMENT SYSTEM

Fig 5.9 User login

Fig 5.10 User home Screen

Dept. of CSE,SJBIT 2022-2023 Page 27

MOBILE STORE MANAGEMENT SYSTEM

Fig 5.11 Smart phone screen

Fig 5.12 Accessories Screen

Dept. of CSE,SJBIT 2022-2023 Page 28

MOBILE STORE MANAGEMENT SYSTEM

Fig 5.13 Product Categories

Fig 5.14 User Cart

Dept. of CSE,SJBIT 2022-2023 Page 29

MOBILE STORE MANAGEMENT SYSTEM

CHAPTER 6

CONCLUSION AND FUTURE SCOPE

Conclusion

The “Mobile Store Management System” has been created with the intention of providing a
user with application which will suffice all needs for the details of mobile phones and other
updates.

All the requirements specifications were followed as far as possible and few additional features
were added that can make the application more users friendly and less complicated.

The project “Mobile Store Management System” has been developed with the proper guidance
from the client.

We hope that “Mobile Store Management System” fulfils all the needs in possible manner.

Future scope:

 More of number item details can be inserted into the database.

 It can be integrated with the web for universal access.
 E-payment.
 Upgrading the performance for better & faster search.
 System will be portable with shared database.

Dept. of CSE,SJBIT 2022-2023 Page 30

MOBILE STORE MANAGEMENT SYSTEM

Dept. of CSE,SJBIT 2022-2023 Page 31