COURIER MANAGEMENT SYSTEM

Submitted by
KOVVURI MAHESH REDDY
(RA2111003011228)

Under the Guidance of

DR.SANDHIA G K

Assistant Professor, Department of Computational Intelligence

In partial satisfaction of the requirements for the degree of

BACHELORS OF TECHNOLOGY
in
COMPUTER SCIENCE ENGINEERING

SCHOOL OF COMPUTING
COLLEGE OF ENGINEERING AND TECHNOLOGY
SRM INSTITUTE OF SCIENCE AND TECHNOLOGY
KATTANKULATHUR - 603203

1
 SRM INSTITUTION OF SCIENCE AND
TECHNOLOGYKATTANKULATHUR-603203

BONAFIDE CERTIFICATE

Certified that this Course Project Report titled “COURIER MANAGEMENT SYSTEM” is the
bonafide workdoneby – KOVVURI MAHESH REDDY(RA2111003011228) of II Year/ IV Sem
B.Tech.who carried out under my supervision for the course 18CSC303J - Database Management
Systems. Certified further, that to the best of my knowledge the work reported herein does not form
part of any other work.

SIGNATURE HEAD OF THE DEPARTMENT

Faculty In-Charge Dr. R Annie Uthra
Dr.SANDHIYA G.K Professor and Head ,
Assistant Professor Department of Computational Intelligence,
Department of Computational Intelligence SRM Institute of Science and Technology
Kattankulathur Campus, Chennai
SRM Institute of Science and Technology
Kattankulathur Campus, Chennai

2
 ABSTRACT

Courier Management System (CMS) is a centralized software solution

that helps courier companies streamline their delivery process from
order booking to final delivery. The CMS is designed to be efficient,
reliable, and cost-effective, providing customers with a high-quality
courier service. The CMS is composed of multiple modules, each of
which performs specific tasks related to courier delivery operations.
The customer management module enables companies to manage
customer details, including their contact information, pickup and
delivery addresses, and payment history. The order management
module allows companies to track courier orders and their status, assign
delivery personnel for each order, and monitor their performance. The
courier personnel management module enables companies to manage
courier personnel details, including their name, contact information,
and delivery performance. The invoice and payment management
module enables companies to generate invoices and receipts for
customers and manage payment information. Finally, the reporting
module enables companies to generate reports on daily, weekly, and
monthly deliveries, providing valuable insights into courier delivery
operations.The CMS is user-friendly and intuitive, with a simple
interface that is easy to use. It is also scalable and customizable,
allowing companies to add or modify features according to their
requirements.

3
 TABLE OF CONTENTS PAGE NO

Chapter 1 Introduction 5

Chapter 2 Requirements 7

Chapter 3 Entity Relationship Diagram 9

Chapter 4 Schema Diagram 12

Chapter 5 Implementation 15

Chapter 6 Screenshots 24

Conclusion 28

References 29

4
CHAPTER 1

Introduction
This Courier Management System Project will have different modules. The login section will

have login facility for the admin and for the user who will operate this system. While taking

orders from its customers, it will take all the details of its customers who is placing the orders

and all the details for the recipient such as its address, name, mobile number. During billing

process system will generate a tracking id for their products. Through this tracking id,

customers or its recipient will able to track their products from any location using internet. It

will provide status of the product after placing orders within 1 minute.

The courier service is one of the solutions of these problems. It is used to send some things to

any person in the world within time. The courier company has number of branches, which are

spread over the country or the world. So that when person wants to send things then he has to

contact at nearest courier service branch. The courier company creates the schedule & gives

internal/external services. The courier service work as destination office or source office.

In modern age, as time increase, needs & requirements of the person are also increased. They

want more facility & try to do their task quickly & within time. But they can not get all the

things at nearest market or area, so they have to import the things from any place in the world.

Within the country, the things can be imported through post service. But it consumes the time

& sometimes problem of damage or missing occur. Where as in the international market, the

one way is shipping. But it also requires more time.

5
Features of Purposed System:

These are the important features of the project Courier Management System:

In computer system of the courier service computation of the rate is easily & quickly

done.

Computer system of the courier service provide fast access.

Using this computerized system, bill issued procedure becomes fast.

In computer system the person has to fill the various forms & number of copies of the

forms can be easily generated at a time.

In computer system, it is not necessary to create the Manifest but we can directly print it,

which saves our time.

It contain better storage capacity.

Accuracy in work.

Easy & fast retrieval of information.

Well designed reports.

Decrease the load of the person involve in existing manual system.

Access of any information individually.

Work becomes very speedy.

Easy to update information.

6
CHAPTER 2

REQUIREMENTS

MODULES

There are several modules that can be included in a courier management system,
depending on the specific requirements of the business. Some of the common
modules are:

1. Order Management Module: This module allows the courier company to

manage orders from customers, including accepting orders, assigning them to
couriers, tracking the status of the order, and handling cancellations or changes
to orders.

2. Courier Management Module: This module manages the courier's information,

including their availability, location, and performance metrics. It also allows the
courier to view and manage their assigned orders, update their status, and
communicate with customers.

3. Delivery Management Module: This module tracks the delivery process,

including the route taken by the courier, delivery time, and proof of delivery. It
also allows customers to track their orders and receive notifications about the
delivery status.

4. Customer Management Module: This module stores customer information,

including their order history, preferences, and contact information. It also
provides tools for managing customer feedback and complaints.

7
5. Billing and Payment Module: This module manages the billing process,
including generating invoices, tracking payments, and handling refunds. It may
also include features for managing discounts, promotions, and loyalty programs.

6. Analytics and Reporting Module: This module provides insights into the
courier company's performance, including key metrics such as delivery times,
order volumes, and customer satisfaction. It may also include tools for creating
custom reports and dashboards.

8
CHAPTER 3

ENTITY RELATIONSHIP DIAGRAM

An Entity–relationship model (ER model) describes the structure of a database with the help
of a diagram, which is known as Entity Relationship Diagram (ER Diagram). An ER model
is a design or blueprint of a database that can later be implemented as a database. The main
components of E-R model are: entity set and relationship set.

What is an Entity Relationship Diagram (ER Diagram)?

An ER diagram shows the relationship among entity sets. An entity set is a group of similar
entities and these entities can have attributes. In terms of DBMS, an entity is a table or attribute
of a table in database, so by showing relationship among tables and their attributes, ER diagram
shows the complete logical structure of a database.

The geometric shapes and their meaning in an E-R Diagram. We will discuss these terms in
detail in the next section(Components of a ER Diagram) of this guide so don’t worry too much
about these terms now, just go through them once.

Rectangle: Represents Entity sets.

Ellipses: Attributes
Diamonds: Relationship Set
Lines: They link attributes to Entity Sets and Entity sets to Relationship Set
Double Ellipses: Multivalued Attributes
Dashed Ellipses: Derived Attributes
Double Rectangles: Weak Entity Sets
Double Lines: Total participation of an entity in a relationship set

9
10
11
CHAPTER 4

ENTITY RELATIONSHIP 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.

An Entity-Relationship Model (ERM) is an abstract and conceptual representation of data.

Entity-relationship modeling is a database modeling method, used to produce a type of
conceptual schema or semantic data model of a system, often a relational database, and its
requirements in a top-down fashion.

In order to create an ER schema you must know three main concepts: entity, attribute and
relationship.

Entity

Entity is the central concept of the Entity-Relationship model. An entity represents a

description of the common features of set of objects of the real world. Examples of entities are
Person, Car, Artist, and Album.

Attribute

An Attribute represents the properties of real world objects that are relevant for the application
purposes.Attributes are associated with the concept of Entity, with the meaning that all the
instances of the entity are characterized by the same set of attributes. In other words, the entity
is a descriptor of the common properties of a set of objects, and such properties are expressed
as attributes.

Relationship
A Relationship represents semantic connections between entities, like the association between
an artist and his/her album, or between an artist and his/her reviews.
The possible values are one and many. Based on their maximum cardinality constraints,
relationships are called

1. "one-to-one", if both relationships roles have maximum cardinality 1,

2. "one-to-many", if one relationship role has maximum cardinality 1 and the other role has
maximum cardinality N,

3. "many-to-many", if both relationships roles have maximum cardinality N.

12
E-R Schema Normalization
E-R includes some concept that are not minimal but which can be specified through the usage
of the three main concepts of the ER Schema. These concepts are:

 Multi value attributes.

Attributes of an object that can take a set of values represented by an entity and a relationship

 Composed attributes.

Attributes with an internal structure (i.e, an address can include different fields), represented
by using an entity and a relationship

 N-ary relationships.

Represented by a central entity and two reports

 Relationships with attributes.

Relationships involving N entities

13
ER SCHEMA DIAGRAM FOR COURIER MANAGEMENT
SYSTEM

14
CHAPTER 5

IMPLEMENTATION

FRONTEND CODE

INDEX.PHP

<?php

require_once "dbconnection.php";
require_once "session.php";

if ($_SERVER["REQUEST_METHOD"] == "POST" && isset($_POST['submit'])) {

$email = $_POST['email'];
$password = $_POST['password'];

$qry = "SELECT * FROM `login` WHERE `email`='$email' AND

`password`='$password'";
$run = mysqli_query($dbcon, $qry);
$row = mysqli_num_rows($run);
if ($row < 1) {
?>
<script>
alert("Opps! plz Enter Your Username and Pswd again..");
window.open('index.php', '_self');
</script> <?php
} else {
$data = mysqli_fetch_assoc($run);
$id = $data['u_id']; //fetch id value of user
$email = $data['email'];
$_SESSION['uid'] = $id; //now we can use it until session destroy
$_SESSION['emm'] = $email;
?>
<script>
alert(" ागत ह आपका ");
window.open('home/home.php', '_self');
// changes made here
</script> <?php

}
}
?>

15
<!DOCTYPE html>
<html lang="en">

<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Login</title>
<link rel="stylesheet"
href="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css">
<style>
body {
background-image: url('images/10.jpg');
background-repeat: no-repeat;
background-size: cover;
}
</style>
</head>

<body>
<h1 align='center' style="margin: 15px; color:seagreen;font-weight: bold;font-
family:'Times New Roman', Times, serif">TYPHOON COURIER SERVICE</h1>
<hr />
<P align='center' style="font-weight: bold;color:orange;font-family:'Times New Roman',
Times, serif">The Fastest Courier Service Ever</P>
<div>
<h5><a href="admin/adminlogin.php" style="float: right; margin-right:40px; color:blue;
margin-top:0px">AdminLogin</a></h5>
</div>
<div class="container" style="margin-top: 60px; width:50%;">
<div class="row">
<div class="col-md-12">
<h2 style="color: #273c75;">Login</h2>
<p style="color:#e84118;">Please Fill Your ⮯⮯</p>
<!-- <?php echo $error; ?> -->
<form action="" method="post">
<div class="form-group">
<label>Email Address</label>
<input type="email" name="email" class="form-control" placeholder="Enter
username/emailId" required />
</div>
<div class="form-group">
<label>Password</label>
<input type="password" name="password" class="form-control"
placeholder="Enter your password" required>
</div>
<div class="form-group">
<input type="submit" name="submit" class="btn btn-primary" value="SignIn"
/>
<button onclick="window.location.href='resetpswd.php'" class="btn btn-
danger" style="cursor:pointer">Reset Password</button>

16
</div>
<p style="color: #e84118;">Don't have an account?⮞➤ <a
href="register.php">Register here</a>.</p>

</form>
</div>
</div>
</div>
</body>

</html>

DBCONNECTION.PHP

<?php

$dbcon = mysqli_connect('localhost','root','','courierdb');

if($dbcon==false)
{
echo "Database is not Connected!";
}

?>

SESSION.PHP

<?php
// Start the session
session_start();

// if the user is already logged in then redirect user to welcome page

if (isset($_SESSION["uid"]) && $_SESSION["uid"] === true) {
header("location: home/home.php");
exit;
}
?>

17
BACKEND CODE
-- phpMyAdmin SQL Dump
-- version 5.0.3
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Dec 31, 2020 at 11:41 AM
-- Server version: 10.4.14-MariaDB
-- PHP Version: 7.4.11

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

START TRANSACTION;
SET time_zone = "+00:00";

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT

*/;
/*!40101 SET
@OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION
*/;
/*!40101 SET NAMES utf8mb4 */;

--
-- Database: `courierdb`
--

--
-- Table structure for table `adlogin`
--

CREATE TABLE `adlogin` (

`email` varchar(50) DEFAULT NULL,
`password` varchar(50) DEFAULT NULL,
`a_id` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `adlogin`
--

INSERT INTO `adlogin` (`email`, `password`, `a_id`) VALUES

('[email protected]', '1215225', 1),
('[email protected]', '1cd18is027', 2);

18
-- Table structure for table `admin`
--

CREATE TABLE `admin` (

`a_id` int(11) NOT NULL,
`email` varchar(50) NOT NULL,
`name` varchar(50) DEFAULT NULL,
`pnumber` int(14) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `admin`
--

INSERT INTO `admin` (`a_id`, `email`, `name`, `pnumber`) VALUES

(1, '[email protected]', 'Prem', 63627862),
(2, '[email protected]', 'Himanshu Soni', 123456789);

--
-- Table structure for table `contacts`
--

CREATE TABLE `contacts` (

`id` int(11) NOT NULL,
`email` varchar(50) NOT NULL,
`subject` varchar(30) NOT NULL,
`msg` varchar(300) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `contacts`
--

INSERT INTO `contacts` (`id`, `email`, `subject`, `msg`) VALUES

(1, '[email protected]', 'delay', 'I have courier 2 weeks ago but its not delivered yet..'),
(2, '[email protected]', 'Delay', 'gjndfjkgnhdfjkgn');

--
-- Table structure for table `courier`
--

CREATE TABLE `courier` (

`c_id` int(11) NOT NULL,
`u_id` int(11) DEFAULT NULL,
`semail` varchar(50) DEFAULT NULL,
`remail` varchar(50) DEFAULT NULL,

19
`sname` varchar(50) DEFAULT NULL,
`rname` varchar(50) DEFAULT NULL,
`sphone` varchar(20) DEFAULT NULL,
`rphone` varchar(20) DEFAULT NULL,
`saddress` varchar(50) DEFAULT NULL,
`raddress` varchar(50) DEFAULT NULL,
`weight` int(11) DEFAULT NULL,
`billno` int(11) NOT NULL,
`image` text DEFAULT NULL,
`date` date NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `courier`
--

INSERT INTO `courier` (`c_id`, `u_id`, `semail`, `remail`, `sname`, `rname`, `sphone`,
`rphone`, `saddress`, `raddress`, `weight`, `billno`, `image`, `date`) VALUES
(7, 4, '[email protected]', '[email protected]', 'love', 'himanshu', '06362786223', '6526652',
'KR puram,Bangalore,Karnataka', 'Boys hostel of Cambridge institute of technology,j', 2, 22,
'cddd.jpeg', '2020-12-06'),
(8, 4, '[email protected]', '[email protected]', 'love', 'gyanshu', '06362786223',
'06362786223', 'KR puram,Bangalore,Karnataka', 'Boys hostel of Cambridge institute of
technology,j', 2, 3263, 'fc.png', '2020-12-06');

--
-- Table structure for table `login`
--

CREATE TABLE `login` (

`email` varchar(50) DEFAULT NULL,
`password` varchar(50) DEFAULT NULL,
`u_id` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `login`
--

INSERT INTO `login` (`email`, `password`, `u_id`) VALUES

('[email protected]', '12345', 1),
('[email protected]', '12345', 4);

--
-- Table structure for table `users`
--

20
CREATE TABLE `users` (
`u_id` int(11) NOT NULL,
`email` varchar(50) NOT NULL,
`name` varchar(50) DEFAULT NULL,
`pnumber` int(14) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `users`
--

INSERT INTO `users` (`u_id`, `email`, `name`, `pnumber`) VALUES

(1, '[email protected]', 'prem', 56665),
(4, '[email protected]', 'LOVE RAJ', 2147483647);

--
-- Indexes for dumped tables
--

--
-- Indexes for table `adlogin`
--
ALTER TABLE `adlogin`
ADD KEY `a_id` (`a_id`);

--
-- Indexes for table `admin`
--
ALTER TABLE `admin`
ADD PRIMARY KEY (`a_id`),
ADD UNIQUE KEY `email` (`email`);

--
-- Indexes for table `contacts`
--
ALTER TABLE `contacts`
ADD PRIMARY KEY (`id`);

--
-- Indexes for table `courier`
--
ALTER TABLE `courier`
ADD PRIMARY KEY (`c_id`),
ADD UNIQUE KEY `billno` (`billno`),
ADD KEY `u_id` (`u_id`);

--
-- Indexes for table `login`

21
--
ALTER TABLE `login`
ADD KEY `u_id` (`u_id`);

--
-- Indexes for table `users`
--
ALTER TABLE `users`
ADD PRIMARY KEY (`u_id`),
ADD UNIQUE KEY `email` (`email`);

--
-- AUTO_INCREMENT for dumped tables
--

--
-- AUTO_INCREMENT for table `admin`
--
ALTER TABLE `admin`
MODIFY `a_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;

--
-- AUTO_INCREMENT for table `contacts`
--
ALTER TABLE `contacts`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;

--
-- AUTO_INCREMENT for table `courier`
--
ALTER TABLE `courier`
MODIFY `c_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=10;

--
-- AUTO_INCREMENT for table `users`
--
ALTER TABLE `users`
MODIFY `u_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;

--
-- Constraints for dumped tables
--

--
-- Constraints for table `adlogin`
--
ALTER TABLE `adlogin`

22
ADD CONSTRAINT `adlogin_ibfk_1` FOREIGN KEY (`a_id`) REFERENCES `admin`
(`a_id`);

--
-- Constraints for table `courier`
--
ALTER TABLE `courier`
ADD CONSTRAINT `courier_ibfk_1` FOREIGN KEY (`u_id`) REFERENCES `users`
(`u_id`) ON DELETE CASCADE;

--
-- Constraints for table `login`
--
ALTER TABLE `login`
ADD CONSTRAINT `login_ibfk_1` FOREIGN KEY (`u_id`) REFERENCES `users`
(`u_id`) ON DELETE CASCADE;
COMMIT;

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

END OF IMPLEMENTATION CODE OF THE PROJECT

23
CHAPTER 6
SCREEN SHOTS OF GUI

Figure 6.1 Home Page for signup

Figure 6.2 Login Page

24
Figure 6.3 Main Administration

Figure 6.4 Report page for client

25
 Figure 6.5 Tracker Page

Figure 6.6 Report view page for manager

26
Figure 6.7 Delivery Boy Page

Figure 6.8 Manager Dashboard

27
CONCLUSION

System development is also considered as a process backed by engineering

approach. We have tried to incorporate & develop new particles for our education
particles have been followed not during the but coding but also during the
analysis, design phases & in documentation.

Courier agency is considered as an expansion of business relations. It contributes

a lot by
providing quick & fast services of sending documents letters (formal & informal
both) to
business as it enables any business to flourish

Following modification or upgrades can be done in system.

1) More than one company can be integrated through this software.
2) Web services can be used to know exact delivery status of packets.
3) Client can check the repacked delivery status online.
4) Distributed database approach in place of centralized approach

28
References and Bibliography:
http://www.bluedart.com/

http://www.xamppserver.com/en/

http://www.php.net/

http://youtube.com/

http://www.tutorialspoint.com/mysql/

https//apache.org/docs/2.0/misc/tutorials.html

29