PROJECT DESCRIPTION
Name: A.Mowin
Class:12A
Project Title: Inventory Management System
Project description:Inventory Management System is a simple computer-based
Inventory Management System developed using Python (Frontend) and SQL (Backend).
The purpose of this project is to help a small shop or warehouse keep proper
records of its products, suppliers, stock levels, and daily sales.
This system allows the user to:
Add and update products with details like name, price, category, and quantity.
Store supplier information such as name, contact number, and address.
Record sales transactions and automatically reduce the stock quantity of products
sold.
Generate reports such as daily sales and low-stock alerts, which help in decision-
making.
Front-end:python
Back end:Sql
Flow of execution:
1. Start the Program
.User runs the Python file.
.The main menu is displayed with options like:
Add Product
View Products
Make Sale
Low Stock Report
Exit
2. User Chooses an Option
.The user selects one of the choices. Based on the input, the corresponding
function is executed.
3. Execution of Features
(a) Add Product
.Python asks the user to enter product details (name, category, price, stock,
supplier ID).
.Data is stored in the SQL database (Products table).
.Confirmation message is shown.
(b) View Products
.Python fetches all product records from the SQL database.
.Displays them neatly in the console for the user.
(c) Make Sale
.User enters the product ID and quantity.
.Python checks stock availability in the database.
If stock is available:
.A new entry is made in the Sales and Sale_Items tables.
.Stock quantity in Products table is reduced automatically.
Total bill amount is displayed.
.If stock is insufficient → error message is shown.
(d) Low Stock Report
.Python runs a query in the Products table to check for items with quantity
below 10.
.Displays a list of products that need restocking.
4. Database Operations
.Every user action (add, sale, update) is translated into an SQL query.
.The database ensures data is saved securely and can be retrieved anytime.
5. Exit Program
When the user chooses Exit, the program closes safely.
.All changes made during the session are already committed to the database.
Database structure: The database has four main tables
1. Products Table
Stores information about items available in the shop/warehouse.
Column Name Data Type Description
product_id INT (PK, Auto) Unique ID for each product
name VARCHAR(100) Product name
category VARCHAR(50) Category of product (e.g., Grocery)
price DECIMAL(10,2) Price of the product
stock_qty INT Available quantity in stock
supplier_id INT (FK) Linked to Suppliers table
2. Suppliers Table
Stores supplier information (who provides the products).
Column Name Data Type Description
supplier_id INT (PK, Auto) Unique supplier ID
name VARCHAR(100) Supplier name
contact VARCHAR(20) Contact number
address VARCHAR(200) Address of supplier
3. Sales Table
Stores sales transactions (like invoices).
Column Name Data Type Description
sale_id INT (PK, Auto) Unique sale ID
date DATETIME Date and time of sale
total_amount DECIMAL(10,2) Total bill amount
4. Sale_Items Table
Stores the details of products sold in each sale.
Column Name Data Type Description
sale_item_id INT (PK, Auto) Unique ID for each sale item
sale_id INT (FK) Linked to Sales table
product_id INT (FK) Linked to Products table
quantity INT Quantity sold
price DECIMAL(10,2) Price per unit at time of sale
Table description:
1. Suppliers Table
This table stores details of the suppliers who provide products to the
shop/warehouse.
Each supplier has a unique supplier_id.
Fields include name, contact number, and address.
It helps in identifying which supplier is linked to which product.
2. Products Table
This is the main table of the system.
It stores all the details of products such as name, category, price, stock
quantity, and supplier information.
The supplier_id here is a foreign key that connects each product to its supplier.
It helps in managing stock levels and product details efficiently.
3. Sales Table
This table stores records of all sales transactions (like invoices).
Each sale has a unique sale_id.
It records the date of sale and the total bill amount.
It acts like the main entry point for every sales activity in the system.
4. Sale_Items Table
This table stores details of the individual products sold in each sale.
It links each sale (via sale_id) with the actual products (via product_id).
It contains information about the quantity of each product sold and its price at
the time of sale.
This ensures that every sale can have multiple products, and stock can be reduced
accordingly.
Project members:
A.MOWIN
P.KRISHAANTH
PRASANNA RAM
