CHAPTER 1

INTRODUCTION

1.1 OVERVIEW

The Grocery Management System (GMS) is a user-friendly, robust, and ef cient software
solution speci cally designed to manage the complex operations of a modern grocery store. Grocery
stores typically deal with a large number of products, dynamic pricing, frequent stock changes, and
customer interactions. Managing all these manually results in inef ciencies, errors, and poor
customer service.

This system automates key business processes such as product management, inventory
tracking, billing, and reporting. It acts as a centralized platform that integrates the core activities of
a grocery store, helping the store owner and staff manage the day-to-day operations with greater
control, accuracy, and ease.

Traditionally, grocery store operations involved pen-paper ledgers, or at best, Excel sheets
for inventory and billing. These methods lack real-time updates, are prone to human error, and do
not scale with growing business needs. GMS solves these issues by providing digital automation,
data consistency, and time-saving features that enhance both the owner’s ef ciency and the
customer’s experience.

1.2 PURPOSE OF THE PROJECT

The purpose of the Grocery Management System is to:

◦ Eliminate manual record-keeping practices in grocery shops

◦ Minimize billing errors and reduce customer wait time
◦ Keep track of stock levels and reorder points automatically
◦ Enable sales and profit tracking with real-time insights
◦ Improve overall business productivity with automation
Key Objectives

◦ To design an interactive, secure platform for grocery store staff to manage products
◦ To implement a billing system that generates accurate invoices and stores sales
history

1
fi
fi
fi
fi
 ◦ To ensure data consistency through an integrated MySQL database
◦ To allow administrative control for monitoring inventory and business performance

The proposed system ensures that grocery operations are reliable, systematic, and less
dependent on manual effort. It supports daily operations while also preparing the store for growth
and scalability.

1.3 SCOPE OF THE PROJECT

This project is suitable for:

◦ Retail grocery shops

◦ Supermarkets
◦ Mini-marts
◦ Provision stores

Functional Scope Includes

◦ Product management: Add/edit/delete product entries with barcode, expiry date, and
stock quantity
◦ Inventory management: Real-time stock level tracking and low-stock alerts
◦ Customer billing: Select multiple items, auto-calculate discounts/taxes, and generate
printed receipts
◦ Sales history: View transaction logs with filter options by date, customer, or product
◦ Reporting module: Generate daily/weekly/monthly reports for sales, stock, and
revenue
◦ Admin module: User access control, backup, and data reset options.

1.4 SIGNIFICANCE OF THE PROJECT

Implementing this system in a grocery store leads to several long-term benefits, including:
• Improved Accuracy: Eliminates human errors in pricing, billing, and stock records.
• Faster Operations: Reduces billing time and improves customer checkout experience.
• Real-Time Monitoring: Admins can view inventory and sales trends any time.

2
 • Data Security: Sensitive data such as sales history and customer details are stored
securely in the database.
• Business Growth Support: Easily adaptable to growing inventory and customer base.
• Decision-Making: Managers can use analytical reports to make stock purchasing and
pricing decisions.

GMS makes the store smarter and more competitive by transforming traditional operations
into a digital workflow. It empowers even small retailers to operate like modern supermarkets.

3
 CHAPTER 2
LITERATURE SURVEY
2.1 INTRODUCTION

In the era of digital transformation, even traditional sectors like grocery retail are embracing
technology to streamline daily operations. The grocery industry, especially in local and medium-
scale stores, faces unique challenges such as managing a wide variety of products, keeping track of
expiry dates, processing bulk billing, managing stock levels, and offering timely service to
customers. Historically, these operations were handled using pen-paper logs, physical registers, or at
best, Excel sheets — which are highly error-prone, time-consuming, and difficult to scale.

The need for a centralized, efficient, and easy-to-use digital system has grown significantly.
Small retailers often cannot afford high-end cloud software due to pricing or may not have stable
internet for web-based platforms. This creates a clear need for a lightweight, standalone grocery
management system that automates essential tasks without the complexity or cost of enterprise
solutions.

Literature surveys for this project involved studying various tools already available in the
market, understanding their limitations, and identifying gaps specific to local retail environments.
This chapter explores existing software tools, the role of databases in grocery systems, key
technological frameworks, and a comparative analysis between current systems and our proposed
model. Additionally, it reviews key academic and industry research articles on digital grocery
automation and outlines how this system bridges the identified gaps in cost, complexity, and
customization.

With increasing competition in the retail market, store owners must focus not only on
managing their resources effectively but also on delivering faster and more reliable services.
Adopting a grocery management system backed by robust database architecture and simplified UI/
UX design is no longer a luxury but a necessity. The findings of this survey lay the foundation for
the development of the proposed Grocery Management System (GMS) – a scalable, affordable, and
practical solution that enhances daily operations, improves data handling, and helps store owners
make informed business decisions.

4
2.2 EXISTING SYSTEMS IN GROCERY RETAIL

Grocery stores, especially in India and other developing regions, have traditionally operated
using manual systems such as notebooks, ledgers, and occasionally Excel spreadsheets. These
systems, while simple, are not scalable and lack the efficiency needed for modern retail demands.
As the volume of products, customers, and transactions increases, managing everything manually
becomes impractical. Manual record-keeping also increases the risk of data duplication, pricing
errors, and inventory mismatch, which directly affects customer satisfaction and business
performance.

In recent years, several digital systems and platforms have been introduced to help retailers
automate their business operations. Some of the commonly known tools include Tally ERP, Zoho
Inventory, Busy Accounting Software, and POS (Point of Sale) systems. While these tools offer
various features like product tracking, billing, and reporting, many are either too expensive, too
complex, or lack customization options for small grocery retailers.

For example, Tally ERP is widely used for financial accounting, but its learning curve and
lack of real-time inventory visibility make it less suitable for a grocery store’s daily operations.
Similarly, Zoho Inventory and cloud-based POS solutions offer strong features but often require
stable internet connections, monthly or yearly subscriptions, and IT support for setup and
maintenance. This is not ideal for local shops operating on low budgets, with limited staff and
technical knowledge.

Furthermore, these tools are generally not built to handle grocery-specific scenarios like:
• Product-wise batch tracking and expiry date management
• Discount handling based on item category or quantity
• Handling loose items sold by weight (e.g., rice, dal, oil in kg/litre)
• Multi-language support for native-language shopkeepers (e.g., Tamil)

Due to these constraints, a significant portion of grocery shop owners still rely on partially
digital systems — such as Excel for stock entry and hand-written bills for customers — leading to
operational delays, customer dissatisfaction, and business inefficiencies.
5
 Our proposed Grocery Management System (GMS) is designed specifically to address these
limitations. It combines the simplicity of a manual system with the power of automation, offering
product entry, stock tracking, billing, and reporting — all in a single, easy-to-use platform. Most
importantly, it eliminates the recurring cost burden by working completely offline and locally via
tools like XAMPP and MySQL, which are open-source and free to use.

Thus, the current state of existing systems reveals a huge gap in availability of affordable,
customizable, and easy-to-implement software for small grocery businesses. This project aims to fill
that gap effectively.

2.3 COMPARATIVE ANALYSIS OF EXISTING TOOLS

With the growing need for digitization in grocery retail, several software tools have emerged
to assist in daily operations. These tools vary in terms of pricing, features, ease of use, and technical
requirements. A comparative study of commonly available solutions reveals their strengths,
limitations, and suitability for local, small-to-medium grocery shops. Below is a detailed
comparison of the most prominent systems currently used in grocery retail:

Table 2.1 - Comparative Analysis

Feature/ Manual Tally ERP Zoho POS Systems Proposed

Criteria System Inventory GMS
Inventory No Limited Advanced Moderate Real-time
Tracking
Billing Manual Accounting Item-based Quick Billing Fast &
Automation Custom
Expiry Date Limited Rare Supported
Not Available Not Tracked
Handling
Sales Manual Financial only Filterable
Customizable Visual
Reporting Reports
Ease of Use Easy Complex Moderate Moderate Simple UI
Internet No No Yes Yes No
Required
Initial Setup Low Medium-High High Medium Low (Free
Cost Tools)
6
 Recurring None None Subscription Monthly Plan None
Cost
Target Users Small Shops Accountants Enterprises Chains/ Local Kirana
Cashiers Stores

Analysis & Observations

• Manual Systems: While easy and cheap, they fail in scalability, speed, and data accuracy.
No backup, no reporting.
• Tally ERP: Great for financial accounting, but not designed for real-time inventory and
expiry management. Needs accounting knowledge.
• Zoho Inventory: A full-featured, cloud-based tool. Works well for large stores but requires
constant internet and payment plans, which may be impractical for small shops.
• POS Systems: Common in supermarkets but require staff training, subscription payments,
and technical support. Not easily customizable for local business needs.
• Proposed GMS: Designed specifically for small grocery shops. It offers essential features
like product entry, stock tracking, billing, expiry management, and reporting. Most importantly, it
works offline, has no recurring costs, and uses free, open-source tools like PHP and MySQL.

This comparative analysis clearly shows that most commercial tools either target large
enterprises or require ongoing payments and technical expertise, which are not viable for small
vendors. Our GMS fills this gap with an accessible, localized solution that requires minimal
training, supports day-to-day grocery operations, and offers long-term sustainability without hidden
costs.

2.4 ROLE OF DATABASE IN GROCERY SYSTEMS

In any digital application, particularly in retail domains like grocery management, the
Database Management System (DBMS) is the backbone that ensures proper data handling, retrieval,
and storage. A grocery store deals with hundreds of items, daily sales transactions, pricing changes,
stock levels, and customer preferences. Storing all of this in paper registers or spreadsheets becomes
unmanageable as the business scales. Thus, implementing a robust relational database system
becomes essential to automate, secure, and streamline the operations.

7
 Our Grocery Management System (GMS) uses MySQL, an open-source relational DBMS
that provides the flexibility and performance required for real-time data operations. Every module
in the system — from product listings to billing and reporting — relies heavily on a well-structured
database schema to ensure consistency, integrity, and speed.

Key Entities Managed by the Database

• Product Table: Stores details like product name, brand, price per unit, quantity in stock,
manufacturing and expiry date, and product ID (primary key).
• Billing Table: Captures details of each transaction, including products purchased,
quantities, total price, applied discounts, and timestamp.
• User Table: Stores login credentials and role-based access information for admins/staff.
• Stock Log Table: Tracks the movement of products in and out of the store (inventory
control).

Why MySQL is Suitable for GMS

• Structured Data Handling: MySQL supports schema-based design, allowing for strict
data formats and validation (e.g., numeric values for quantity and price).
• Relational Integrity: The database can use foreign keys to maintain relationships (e.g.,
linking bills to products purchased), ensuring data consistency.
• Fast Querying: With indexed fields, even large inventories can be searched or sorted
quickly, helping in fast billing operations.
• Security: Admins can limit access using user privileges in MySQL, reducing the risk of
data misuse or leaks.
• Backup & Recovery: Data can be backed up via export options in phpMyAdmin or
automated SQL scripts, ensuring disaster recovery.

DBMS Features That Enhance Grocery Systems

Table 2.2 - DBMS Features

Feature Impact on GMS

Atomicity Ensures complete billing or complete rollback
Consistency Prevents data con icts across modules
Isolation Handles multiple users without data clashes

8
fl
 Durability Sales data is stored safely even after crashes
Data Redundancy Control Ensures duplicate entries are avoided

In addition to these features, MySQL supports auto-incremented IDs, triggers, and stored
procedures which can further optimize large-scale operations like stock restocking alerts, expired
item removal, and daily sales calculation.

In conclusion, a DBMS is not just a data storage mechanism but a critical component that
enhances the functionality, accuracy, and reliability of the Grocery Management System. With
MySQL integrated via PHP and XAMPP, our system delivers a smooth user experience and helps
shop owners manage their business efficiently — all while keeping the backend data secure,
optimized, and organized.

2.5 SECURITY IN GROCERY DATABASE MANAGEMENT SYSTEMS

Security is one of the most critical aspects of any information system, especially in domains
like retail and grocery management where sensitive data such as pricing, stock values, and user
credentials are involved. In a digital grocery management system, protecting the confidentiality,
integrity, and availability of data is a top priority. Without proper security mechanisms, the system
may become vulnerable to unauthorized access, data breaches, manipulation of sales records, or
deletion of critical inventory data — leading to operational chaos and loss of trust.
The Grocery Management System (GMS) integrates multiple security features at both the
application layer (frontend/backend) and the database layer to ensure robust protection of business
data.

Key Security Concerns in a Grocery DBMS

• Unauthorized access to admin dashboard or sensitive modules
• Tampering with product prices or discounts during billing
• Deletion of sales history or transaction logs
• Data loss due to accidental or malicious actions
• Leakage of customer and employee credentials

9
 To address these issues, GMS follows industry-standard security practices that balance ease
of use with strong protective mechanisms.

Major Security Mechanisms Implemented in GMS

1. Role-Based Access Control (RBAC)
• Users are assigned roles such as Admin and Cashier/Staff
• Admin has access to all modules including inventory control, management, and reports
• Staff has restricted access limited to billing and product viewing
• Prevents unauthorized users from performing critical operations
2.Hashed Passwords (PHP & MySQL Integration)
• All passwords are stored in the database using SHA-256 or bcrypt hashing algorithms
• This ensures that even if the database is compromised, raw passwords remain secure
• Passwords are verified using hash comparison, never stored as plain text
3.SQL Injection Protection
• The system uses parameterized queries (prepared statements) in PHP
• This prevents attackers from injecting malicious SQL code to manipulate or delete data
• Validations are applied to all input fields to sanitize user data
4. Session Management
• Each login session is monitored and timed-out after inactivity
• This prevents unauthorized users from accessing the system if a session is left open
• Logout mechanisms clear session variables to avoid session hijacking
5. Database Privileges
• MySQL user permissions are tightly controlled
• Only the application has access to SELECT, INSERT, UPDATE, and DELETE as per need
• Backup and export operations are reserved for Admin roles only
6.Data Backup & Recovery
• Regular backups of MySQL database using phpMyAdmin export or automated cron scripts
• Backups stored offline to prevent data loss from system crashes or corruption
• Data can be restored easily in case of accidental deletion

Optional Future Enhancements:

• Two-Factor Authentication (2FA) using OTP or Email verification
• CAPTCHA on login to prevent brute-force attacks
10
 • Activity Log Module to track every change (who updated what, when)
• SSL/TLS encryption for hosted systems (if converted to online cloud-based version)
In essence, security is not just a feature — it’s a fundamental requirement for a reliable Grocery
Management System.

2.6 CLOUD VS LOCAL SYSTEMS IN GROCERY MANAGEMENT

SYSTEMS

When designing or deploying a Grocery Management System (GMS), one of the most
important architectural decisions is whether to go with a cloud-based solution or a locally hosted
(offline) system. Each approach has its own advantages and trade-offs, depending on the shop’s
size, budget, internet reliability, and technical capacity.
A cloud system is one that stores data and runs the application entirely on remote servers
(like AWS, Google Cloud, or Azure), allowing users to access it via the internet. A local system, on
the other hand, is installed and runs on the shop’s own computer using tools like XAMPP, without
needing a continuous internet connection.
Our proposed GMS is built to function as a local-first system — intentionally designed for
small and medium-sized grocery stores that may not have consistent internet connectivity or the
budget for paid subscriptions.

Why Local Systems are Preferred for Small Grocery Stores

• Unstable Internet: Many local grocery stores, especially in Tier 2/3 cities or rural areas,
do not have reliable internet access. A cloud-based system can become inaccessible during
downtime.
• Cost Sensitivity: Cloud solutions often have ongoing subscription fees. Local systems can
be built using free tools like PHP, MySQL, and XAMPP with no recurring cost.
• Full Data Control: Local systems give shop owners full access and control over their
business data, with no dependency on third-party servers.
• Speed and Simplicity: Since local systems run on the user’s computer, operations like
billing and stock lookup are faster and do not rely on server latency.

When Cloud Might Be a Better Fit:

11
 • Chain stores with multiple branches that need centralized control
• Businesses with dedicated IT teams or managed services
• Shops needing remote access to daily reports from mobile devices
However, these benefits come at the cost of dependency on internet, technical support, and
higher operational expenses.
GMS Decision Justification
The proposed Grocery Management System is developed with local deployment in mind
using XAMPP (which includes Apache, PHP, and MySQL) on a standalone PC or laptop in the
shop. This ensures:
• No downtime during internet failure
• Faster checkout and real-time stock updates
• No risk of data loss due to third-party shutdowns
• Full offline functionality + optional backup for future cloud sync

In conclusion, while cloud systems offer flexibility, local systems are more reliable,
affordable, and practical for everyday grocery retail — especially for businesses that want
independence from ongoing costs or internet dependency. GMS empowers such businesses by
offering a powerful yet simple local solution.

2.7 ROLE OF UI/UX IN GROCERY MANAGEMENT SYSTEMS

In any software application, especially those meant for everyday commercial use like a
Grocery Management System (GMS), the User Interface (UI) and User Experience (UX) are not
just visual elements — they define how effectively and efficiently the system can be used by non-
technical users such as shopkeepers and billing staff.

Unlike enterprise users, grocery shop staff do not usually have IT training. Therefore, a
complicated or cluttered interface will not only delay operations but may lead to frustration and
errors. An intuitive and responsive UI/UX design ensures that the users can focus on their work —
such as billing, inventory updates, or sales review — without needing technical support or long
training sessions.

12
Importance of UI/UX in Grocery Applications
1.Speed and Simplicity in Billing
The billing interface must allow for:
• Fast product search (by name or barcode)
• Quick addition/removal of items to bill
• Auto-calculation of total, tax, and discount
• Print-ready bill in one click
A cluttered UI can slow down the billing process, which directly affects customer waiting
time.
2. Visibility of Stock Levels
The inventory dashboard should:
• Use color codes to highlight low-stock or expired products
• Show category-wise filters (Fruits, Snacks, Grains, etc.)
• Enable one-click edits of product price or quantity
These features allow staff to take action immediately when stock issues arise.
3. Role-Based Dashboards
Different users (Admin vs Staff) should see only what they need:
• Admin: Reports, user management, product settings
• Staff: Billing, product viewing, limited inventory control
This simplifies their workflow and prevents misuse or confusion.
4. Notifications and Alerts
A good UX includes reminders for:
• Products nearing expiry
• Low-stock items
• Daily sales target reports
• Monthly summary alerts
These keep the shop informed without extra effort.

Optional Future Enhancements

• Touchscreen Optimization: For shops using POS touchscreen systems
• Voice Search Integration: For faster product lookup
• Dark Mode: For night use and visual comfort

13
 • Multi-Language UI: Tamil/English toggle for local users

In summary, the UI/UX of a grocery management system directly affects the shop’s speed of
service, staff comfort, and business efficiency. GMS focuses on a clean and simple interface with
smart layouts that reduce effort and training time. When designed well, the UI becomes invisible —
letting users focus on their tasks rather than learning how to use the system.

2.8 INTEGRATION WITH THIRD-PARTY TOOLS AND DEVICES

To improve the efficiency, speed, and customer experience in grocery store operations,
modern Grocery Management Systems (GMS) are often designed with support for external
hardware and tools. These third-party integrations not only automate routine processes but also help
reduce manual effort, minimize billing errors, and support better decision-making.

Our proposed GMS is lightweight, but it is built with flexibility to support the future
integration of various commonly used retail tools, including barcode scanners, thermal printers,
SMS APIs, and mobile applications.

Common Integrations in Grocery Stores

1.Barcode Scanners
• Barcode scanning is one of the fastest and most accurate ways to add items to a bill.
• Instead of manually searching for products, scanning a barcode fetches item name, price,
and updates the stock automatically.
• GMS database can be linked with product barcodes, allowing fast real-time billing and
error-free checkout.
2. Thermal Receipt Printers
• Used to generate instant printed bills for customers.
• Integrated via USB or network ports to the billing system.
• PHP can trigger bill templates in printable formats using JavaScript window.print() or by
generating PDF using libraries like TCPDF.
• Enhances professionalism and customer trust in the store.
3. Inventory Import Tools (Excel/CSV)

14
 • For initial stock setup or mass updates, GMS can be enhanced to support Excel file import.
• Shop owners can update product lists offline and upload to the system.
• Saves time for large inventory entries.
4. SMS/WhatsApp API for Alerts (Future Scope)
• Send SMS for:
• Low stock alerts to owner
• Bill total to customer
• Offers & promotions

Benefits of Integration
• Reduces human errors and improves speed
• Increases daily billing efficiency
• Enhances customer satisfaction with fast checkout and clear receipts
• Automates stock tracking via barcode scanning
• Enables mobile-friendly business control for store owners

In conclusion, integration of third-party tools and devices greatly enhances the practicality
of a Grocery Management System. Even though our proposed GMS is primarily local and
lightweight, it is designed to be flexible and expandable to support the most essential retail
hardware and APIs. This future-ready architecture makes the system scalable without forcing major
redesigns, helping small shops transition toward smart retailing smoothly.

2.9 RESEARCH FINDINGS

As the global retail sector embraces digital transformation, several studies and surveys have
highlighted the measurable impact of automation in small-to-medium retail environments, including
grocery stores. Researchers and business analysts consistently emphasize that the implementation of
management systems significantly enhances operational efficiency, accuracy, customer satisfaction,
and business intelligence.

Various journals, including IEEE, Elsevier, and Springer, along with trade publications like
Economic Times and Business Today, have explored how database-driven systems improve

15
performance in retail. These findings validate the goals of the Grocery Management System (GMS)
and support the need for low-cost, locally deployable solutions for Indian grocery markets.

Key Research Insights

1. Operational Efficiency
Studies reveal that stores using digital inventory systems reduce stock mismatches
by up to 60%. When real-time stock updates are in place, owners can quickly identify shortages,
restock in time, and avoid customer dissatisfaction.
2. Reduction in Billing Time
Automated billing systems have proven to reduce checkout time by 35% to 50%, as
compared to manual or Excel-based processes. Barcode scanning and item search through database
queries improve cashier productivity.
3. Data Accuracy & Loss Prevention
Paper-based records are vulnerable to loss, theft, or damage. DBMS-backed systems
offer secure, retrievable, and well-structured data storage. Research shows that digital systems
reduce pricing and stock errors by over 70%.
4. Business Analytics for Decision Making
Research confirms that owners with access to daily/weekly reports make better
decisions in terms of pricing, promotions, and stock purchases. Database systems generate such
reports instantly, aiding in smarter management.

2.10 GAPS IN EXISTING SYSTEMS AND SCOPE FOR GMS

Although there are several commercial and open-source tools available for retail and grocery
management, a detailed study of these systems reveals multiple gaps, especially when it comes to
small and local grocery shops in India. These businesses often struggle with tools that are either too
generic, too expensive, or too complex for their needs. The lack of tailored solutions leads to
underutilization of digital tools, or worse, a return to manual operations.

Our proposed Grocery Management System (GMS) is designed specifically to address these
gaps — offering a lightweight, cost-free, and scalable platform that meets all the core requirements
of local store owners.

16
Key Gaps in Existing Systems
1. High Subscription Costs
• Most retail software providers follow a Software-as-a-Service (SaaS) model with monthly
or yearly fees.
• Small stores with limited profit margins cannot afford continuous recurring costs.
Example: Tools like Zoho POS or Gofrugal charge ₹1,000+ per month.

2. Internet Dependency
• Cloud-based solutions fail in areas with poor connectivity, making them unreliable.
• Local kirana stores often operate in semi-urban or rural regions where stable internet is a
challenge.
3. Lack of Grocery-Specific Features
• Many systems are built for general retail and do not support grocery requirements like:
• Expiry tracking
• Batch-wise stock
• Loose items sold by weight
• Customizable pricing units (grams, litres, packets)
4. Complex UI and Technical Setup
• Tools designed for large retail chains include excessive features, confusing dashboards,
and steep learning curves.
• Many require professional setup, training, or IT support, which is not practical for a small
family-run store.
5. Limited Customization
• Most commercial tools offer a fixed layout and modules with no option to modify billing
flow, report formats, or product categories.
• Shop owners have unique workflows that standard tools cannot accommodate.
6.Data Privacy & Vendor Lock-in
• Cloud-based tools store data on third-party servers, creating dependency on vendors.
• If subscription is stopped, access to data may also be lost or restricted.

17
 CHAPTER 3
EXISTING SYSTEM & PROPOSED SYSTEM
3.1 EXISTING SYSTEM OVERVIEW
In most small and local grocery stores, management tasks are handled manually or with
basic digital tools like Excel sheets and calculators. These stores usually record product information
in notebooks, bill customers manually or via calculator, and maintain stock by physical counting.
While this may seem cost-effective in the short term, it leads to inefficiencies, errors, and business
limitations over time.

Major Characteristics of the Existing Manual System:

• Product Entry: Done manually in books or loose sheets
• Stock Tracking: Requires physical counting, often missed or outdated
• Billing: Calculated manually, prone to human errors
• Sales Record: Maintained in notebooks, hard to analyze
• Customer History: Not maintained at all
• Reports: Not available or require effort to compile manually

Drawbacks of the Existing System

Table 3.1 - Drawbacks of the Existing System

Area Drawback
Inventory Dif cult to track stock levels in real time
Accuracy Manual billing prone to calculation and entry
errors
Time Ef ciency Billing and stock updates take longer,
increasing customer wait time
Reporting No automated way to view daily or monthly
sales
Data Handling Risk of data loss (paper damage, loss of books)
No support for expansion or data-driven
Business Growth
decisions

Due to these limitations, the current manual system is no longer sufficient for modern retail
needs. Shop owners need a smarter, more reliable method to manage operations efficiently.

18
fi
fi
 3.2 PROPOSED SYSTEM OVERVIEW
To overcome the drawbacks of the existing system, the Grocery Management System
(GMS) is proposed. GMS is a complete, standalone software developed using HTML, PHP, and
MySQL hosted locally through XAMPP. It provides automated inventory management, billing,
reporting, and administrative control — all in a lightweight and user-friendly interface.
This system is designed specifically for local Indian grocery stores, keeping in mind cost-
effectiveness, offline access, and ease of use. It replaces manual entry with digital records, enabling
fast and accurate operations while also offering analytical insights for better decision-making.

Features of the Proposed GMS

• Add, update, and delete grocery products
• Real-time stock tracking with alerts for low or out-of-stock items
• Automated billing with GST and discounts calculation
• Secure admin and staff login
• Dashboard showing daily sales, profit, and stock level summary
• Generate downloadable sales reports (daily/weekly/monthly)
• Simple, Tamil-friendly interface for easy adoption (optional future scope)

Benefits of the Proposed System

Table 3.2 - Benefits

Feature Bene t
Digital Inventory Prevents overstock or stockouts, updates in real
time
Speedy Billing Reduces customer wait time, avoids calculation
errors
Data Backup Option to export and save all data regularly
Admin Control Prevents unauthorized access and tracks staff
activity
Reports & Insights Helps in making business decisions and
tracking growth
Scalable Design Easy to add new features like barcode scanning,
offers, etc.

19
fi
3.3 SYSTEM COMPARISON TABLE
Table 3.3 - System Comparison

Criteria Existing System Proposed GMS

Platform Manual / Excel PHP-MySQL (XAMPP
Localhost)
Billing Manual / Calculator Automated & Accurate
Inventory Control Manual Physical Check Real-time Digital Stock
Updates
Report Generation Not Available Auto-generated Daily/Monthly
User Login Not Applicable Admin & Staff Login System
Cost Low (Manual) Zero Recurring Cost
Data Security None Password Protected, Local
Backup
Future Expandability Not Possible Yes – Modules & Mobile App
Ready

20
 CHAPTER 4
HARDWARE AND SOFTWARE REQUIREMENTS

4.1 HARDWARE REQUIREMENTS

The GMS is designed to run on a standard desktop or laptop computer. The minimum
hardware requirement includes a system with at least an Intel i3 processor or equivalent, and a
minimum of 4GB RAM. However, for smoother performance, especially when dealing with larger
product databases or generating daily reports, 8GB RAM is recommended.

Storage space of at least 250GB is sufficient for the operating system, XAMPP server,
application files, and the database. An SSD is preferred over a traditional hard disk for faster
performance. Input devices such as a keyboard and mouse are essential for system navigation. If
available, a barcode scanner and a thermal printer can be connected to improve the speed of billing
and customer service.

A monitor with a clear display resolution is recommended for better user interface visibility.
For consistent usage in regions with frequent power cuts, a UPS backup is also advisable to prevent
data loss during billing operations.

4.2 SOFTWARE REQUIREMENTS

The application is compatible with Windows and Linux-based operating systems. The
recommended environment for running the Grocery Management System includes the XAMPP
server package, which provides Apache (for hosting), PHP (for backend logic), and MySQL (for
database management).

The web pages are developed using standard HTML5 and CSS3 technologies for structure
and design. For development and minor edits, a code editor such as Visual Studio Code or
Notepad++ is ideal. To access the application, a modern web browser like Google Chrome or
Mozilla Firefox is required, as the user interface is designed to be browser-friendly and responsive.

To manage the MySQL database, phpMyAdmin is used — a browser-based GUI tool

included in XAMPP. It allows easy creation of tables, management of records, and database

21
backups. A PDF reader can be used to view exported reports or documentation generated by the
system.

4.3 DEPLOYMENT AND MAINTENANCE ENVIRONMENT

The Grocery Management System is developed and deployed on a local server, ensuring that
the entire application is self-contained. The process involves installing XAMPP, placing the project
folder inside the htdocs directory, and running the application via a browser at localhost. The
MySQL database can be created and managed within phpMyAdmin.

There is no need for internet connectivity for daily operations, making it highly reliable in
offline conditions. However, occasional internet access may be used to download updates or
integrate optional modules such as SMS or email alerts in future versions.

Routine database backups should be taken periodically by exporting data through

phpMyAdmin to ensure safety against accidental data loss.

22
 CHAPTER 5
SYSTEM DESIGN
5.1 BLOCK DIAGRAM

Fig.No.5.1

5.2 SYSTEM ARCHITECTURE

The proposed system follows a three-tier architecture:

1. Presentation Layer (Frontend)
Developed using HTML and CSS, this layer provides web interfaces for Admin, Vendor, and Client.
Users interact through login pages, dashboards, product browsing pages, and order forms.
2. Application Layer (Backend)
PHP handles server-side logic. It processes user requests, performs validation, manages sessions,
and sends SQL queries to the database.
3. Data Layer (Database)
MySQL is used to store persistent data including user credentials, products, categories, shop types,
and order details.

All communication flows from the frontend to the backend, which then interacts with the database
and returns the results to the user interface.

5.3 ENTITY RELATIONSHIP DIAGRAM (ERD)

The ER diagram defines the entities and the relationships between them in the system. Major
entities include:
• User (Vendor / Client / Admin)
23
 • Product
• Category
• ShopType
• Order
Relationships
• A Vendor can add multiple Products
• Each Product belongs to a Category
• A ShopType can have multiple Vendors
• A Client can place multiple Orders
• Each Order contains one or more Products.

5.4 DATA FLOW DIAGRAM (LEVEL 0)

The Level 0 DFD gives an overview of the system
• User (Admin, Vendor, Client) sends request via web interface
• GMS Processor (PHP backend) handles the request
• Database stores or retrieves required data
• Response is sent back to the user (e.g., login success, product list, order status)
This ensures smooth flow of information and task separation.

5.5 DATABASE DESIGN

Each entity is represented as a separate table in the MySQL database
• Users Table: Stores login credentials, role (admin/vendor/client), contact info
• Products Table: Product ID, Name, Price, Quantity, Category ID, Vendor ID
• Categories Table: Category ID, Name
• ShopType Table: Shop ID, Shop Name, Vendor ID
• Orders Table: Order ID, Client ID, Date, Total Amount
• OrderDetails Table: Order ID, Product ID, Quantity, Subtotal
Proper keys (Primary & Foreign) are used to maintain referential integrity between tables.

24
5.6 INPUT AND OUTPUT DESIGN
Input Design
• User login forms (with role selection)
• Product addition form (for vendor)
• Category and shop creation (admin)
• Order placement form (for client)
Output Design
• Product list with filters (category/shop/vendor)
• Order summary with date and amount
• Admin dashboard with total products, vendors, and sales
• Success/failure messages for each transaction
All outputs are designed to be clean, readable, and action-oriented.

5.7 USER INTERFACE DESIGN

UI design prioritizes ease of use, role-based access, and fast performance:

• Admin dashboard: Manage users, shops, and categories
• Vendor dashboard: Manage their products and view orders
• Client dashboard: Browse products and place orders
• Consistent design elements (buttons, input fields, alerts)
• Responsive layout (desktop & mobile support in future scope)

The UI is kept minimal and intuitive so that even users with basic digital skills can operate the
system comfortably.

25
 CHAPTER 6
MODULES

6.1. USER MODULE

The User Module is a key component of the Grocery Management System, designed
specifically for end-users or customers. This module enables users to create their own accounts and
securely log in to the system using their registered credentials. During registration, users are
required to provide basic personal information such as name, contact number, email ID, and
delivery address. Upon successful login, users can access the complete range of features provided
by the platform.

Once logged in, users can browse through a wide variety of grocery products displayed in a
categorized format for easier navigation. Advanced search options and filters are provided to help
users quickly find specific products based on categories, brands, price range, or availability. Each
product listing includes detailed information such as name, description, price, quantity, and image.

Users can add selected products to their shopping cart, where they have the ability to modify
item quantities, remove unwanted items, and proceed to place an order. The system supports a
smooth checkout process with multiple integrated payment options, including credit/debit cards, net
banking, UPI, and digital wallets. After a successful transaction, users receive a digital payment
receipt and order confirmation via email or SMS.

The User Module also provides access to Order History, allowing users to view details of
previous orders and track the status of current orders—whether they are pending, shipped,
delivered, or cancelled. In case of issues, users can request cancellations or return orders directly
from their dashboard.

Another important feature is Profile Management, which lets users update their personal
details such as phone number, delivery address, and preferred notification settings. Users can also
manage their password and communication preferences to ensure a personalized and secure
shopping experience.

26
6.2. VENDOR MODULE

The Vendor Module is an essential part of the Grocery Management System that provides a
dedicated interface for grocery vendors or sellers. This module allows vendors to register
themselves by submitting their business details such as store name, contact information, address,
and a valid ID proof or license. Once the admin approves the registration, vendors can securely log
in to their dedicated portal using their unique credentials.

After logging in, vendors gain access to a wide range of features that enable them to manage
their online grocery store effectively. One of the core functionalities is Product Management,
through which vendors can add new products to the system by providing complete details like
product name, description, price, quantity, category, and images. They also have the ability to
update existing product information or remove products that are no longer available.

Another critical aspect of this module is Inventory Management. Vendors can continuously
monitor the stock levels of each product they’ve listed. When a product’s stock is low or sold out,
the vendor can quickly update the inventory or restock as necessary. This helps avoid situations like
over-selling or customer dissatisfaction due to out-of-stock items.

The Order Management feature allows vendors to receive real-time notifications when a
customer places an order that includes their listed products. Vendors can prepare the orders, pack
the items, and update the order status (e.g., “Ready for Dispatch” or “Shipped”). These updates are
reflected in both the user and admin views to ensure smooth coordination and transparency.

To help vendors make data-driven decisions, a Vendor Dashboard is available that displays
key metrics like total sales, most sold products, order volume, customer reviews, and overall
performance statistics. This centralized dashboard provides insights that help vendors optimize their
product listings and improve customer satisfaction.

27
6.3. ADMIN MODULE

The Admin Module serves as the central control unit of the Grocery Management System,
providing the administrator with full access and authority over the platform’s operations. This
module is designed to ensure the smooth functioning, security, and maintenance of all system
components by giving the admin oversight over users, vendors, products, orders, and reports.
Admins log in using high-privileged credentials that are securely authenticated to prevent
unauthorized access.

Once logged in, the admin can view and manage all registered users and vendors in the
system through the User Management section. They can add new admin accounts, update or delete
user or vendor profiles, and verify vendor registration requests. The admin is also responsible for
monitoring suspicious activities, ensuring secure transactions, and maintaining platform integrity.

The Order Tracking feature in the Admin Module allows administrators to oversee every order
placed on the platform — including orders from all vendors and users. They can track each order’s
status from placement to delivery. In case of issues like delayed dispatch or customer complaints,
the admin can intervene and take corrective actions, such as updating order status, issuing refunds,
or escalating concerns.

Another major function of the Admin Module is Reporting and Analytics. Admins can
generate detailed reports on various parameters such as daily/weekly/monthly sales, product stock
levels, vendor performance, customer activity, and revenue. These reports help in analyzing trends,
forecasting demand, and making strategic decisions to improve business performance.

Moreover, the admin is responsible for System Maintenance, which includes tasks such as
database backups, updating software components, managing server uptime, and setting system
configurations. They can also define roles and permissions, ensuring that each user type (vendor,
user, or admin) only has access to the features relevant to them.

28
6.4. PRODUCT MANAGEMENT MODULE

The Product Management Module plays a crucial role in maintaining and organizing the
entire catalog of grocery items within the Grocery Management System. It provides a structured and
efficient approach for managing product-related data that is accessible to vendors and visible to
users. This module enables vendors to add new products, modify existing ones, and ensure all
product information is up to date and accurate.

When a vendor wants to add a new grocery item to the system, they use this module to input
important details such as the product name, category (like Vegetables, Fruits, Beverages, etc.),
price, quantity, unit of measurement (e.g., kg, litre, packet), description, and an image for visual
identification. This organized input helps users to easily recognize and evaluate products during
their shopping experience.

The Catalog Management functionality ensures that all products are stored in a well-
maintained digital catalog, which is continuously updated as vendors make changes or add new
items. The system allows seamless navigation by categorizing products appropriately, thus
improving the user’s browsing experience. Users can search for specific items or filter based on
category, price, or popularity due to the structured nature of this module.

This module also supports Category Management, where each product can be grouped under
predefined or newly created categories. This is especially useful for maintaining clarity in a large
inventory system and allows the admin or vendors to control how items are grouped and displayed
on the user interface.

In addition, the Product Updates feature enables vendors to modify product prices based on
market conditions, add promotional offers, or edit details like stock availability and product
descriptions. Any changes made through this module are instantly reflected in the user interface to
maintain real-time accuracy.

Moreover, the Stock Status feature integrates with inventory data, allowing both vendors and
users to view whether a product is in stock or unavailable. This minimizes customer dissatisfaction
due to product unavailability and helps vendors manage restocking efficiently.

29
6.5. ORDER MANAGEMENT MODULE

The Order Management Module is a vital component of the Grocery Management System that
oversees the complete lifecycle of customer orders. It ensures that the transition from product
selection to delivery is smooth, transparent, and well-documented. This module connects users,
vendors, and the admin through a centralized order handling process, reducing confusion and
enhancing the overall user experience.

Once a user selects the products they wish to purchase and proceeds to checkout, the order is
created in the system and logged into the Order Management Module. This module immediately
assigns a unique Order ID and stores all related details, such as items ordered, quantities, prices,
total cost, delivery address, and chosen payment method. The user receives confirmation of order
placement, and the vendor is notified in real-time.

The Order Processing feature facilitates the journey of an order through various stages.
Initially, the order status is marked as “Pending.” As the vendor prepares the order, they can update
the status to “Confirmed” or “Processing.” Once the items are dispatched, the status is changed to
“Shipped,” and finally marked as “Delivered” when received by the customer. In cases of
cancellation, the status is marked accordingly. This dynamic status update system provides users
with live tracking of their orders.

The module also includes Invoice Generation, which automatically creates a digital invoice
once an order is confirmed. This invoice includes product details, pricing breakdown, taxes (if
applicable), and the total amount. It is accessible to the user through their profile and can be
downloaded or emailed as a receipt for future reference.

The Order History functionality allows all users—customers, vendors, and admins—to view
previously placed or received orders. Users can track delivery statuses, reorder products from
history, and manage return or cancellation requests. Vendors can analyze completed and pending
orders to manage dispatch schedules. Admins, on the other hand, can monitor the health of the
system, identify delays or disputes, and take corrective actions.

30
6.6. PAYMENT MODULE

The Payment Module is a crucial part of the Grocery Management System that ensures
secure, seamless, and efficient handling of monetary transactions between users and the system. It
supports the final step in the shopping process—converting placed orders into confirmed purchases
through verified payments.

When a user places an order, they are redirected to the payment interface managed by this
module. The system is integrated with a payment gateway that supports multiple payment methods
including credit cards, debit cards, net banking, UPI, and digital wallets. This provides users with
flexibility and convenience to choose their preferred mode of payment.

One of the key responsibilities of this module is Transaction Security. All sensitive user data,
such as card details and banking credentials, are encrypted using advanced security protocols like
SSL (Secure Socket Layer). The payment gateway ensures PCI-DSS compliance, protecting users
from unauthorized access, data breaches, or fraudulent activities. In the event of any disruption
during the transaction (such as connection timeout), the module ensures that no duplicate or partial
payments are processed.

Upon successful completion of a transaction, the module handles Payment Confirmation. It

receives acknowledgment from the payment gateway and updates the order status from “Pending
Payment” to “Confirmed”. Simultaneously, vendors are notified that the order is ready to be
processed. If a transaction fails, users are provided with clear feedback and alternate payment
options.

The module also includes Receipt Generation functionality. After payment confirmation, a
digital receipt is automatically generated and sent to the user’s registered email. This receipt
includes details such as the order ID, transaction ID, payment method, date and time, and a
breakdown of item costs. Users can also download this receipt directly from their profile section for
future reference or reimbursement purposes.

31
 CHAPTER 7
CONCLUSION AND FUTURE ENHANCEMENTS

7.1 CONCLUSION

The Grocery Management System (GMS) was successfully designed, developed, and tested to
address the common challenges faced by small and medium-sized grocery stores in managing
inventory, billing, and order tracking. Through the use of PHP, MySQL, and HTML/CSS, an
offline-first solution was built that is cost-effective, user-friendly, and capable of automating key
store operations.

The system ensures that grocery store owners and staff can:
• Manage product catalogs efficiently
• Track stock availability in real-time
• Handle client orders with minimum error
• Securely log in based on user roles (Admin, Vendor, Client)
• Generate accurate records and reports for sales and inventory

By eliminating manual processes and replacing them with a structured database-driven

approach, GMS increases accuracy, reduces operational delays, and supports better business
decisions. The application was thoroughly tested and validated against functional and non-
functional requirements and proved to be a stable and reliable system.

Overall, the Grocery Management System fulfills its objective of providing an all-in-one
solution for managing a local grocery shop without the need for expensive third-party software or
constant internet access. It empowers small-scale retailers with technology that works for them, not
against them.

7.2 FUTURE ENHANCEMENTS

While the current version of GMS satisfies essential requirements, there are several potential
areas for improvement and expansion in the future:

1. Mobile Application Support

• Develop Android/iOS apps for shop owners and clients to manage/store data remotely.
32
• Use Flutter or React Native for cross-platform deployment.

2. Barcode Scanner Integration

• Add barcode reading to speed up billing and stock updates using scanner input.

3. SMS/Email Notification System

• Notify clients of order confirmations, and vendors of new orders or low stock alerts using Twilio,
Fast2SMS, etc.

4. Printable PDF Bills

• Automatically generate and save bills in downloadable PDF format using libraries like TCPDF.

5. Multi-language UI
• Add support for Tamil or regional languages to make the system accessible to non-English
speakers.

6. Sales Analytics Module

• Include charts, graphs, and filters for tracking monthly trends, best-selling products, and vendor
performance.

7. Advanced Security Features

• Add features like two-factor authentication (2FA), login history, and activity logs.

8. Multi-Branch Support
• Extend the system to support multiple grocery shops with centralized admin access.

33
 APPENDIX

A. SOURCE CODE
-- phpMyAdmin SQL Dump
-- version 5.1.1
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Feb 10, 2022 at 07:03 AM
-- Server version: 10.4.19-MariaDB
-- PHP Version: 8.0.7

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 */;
-- Table structure for table `cart_list`

CREATE TABLE `cart_list` (

`id` int(30) NOT NULL,
`client_id` int(30) NOT NULL,
`product_id` int(30) NOT NULL,
`quantity` float NOT NULL DEFAULT 0
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

-- Dumping data for table `cart_list`

INSERT INTO `cart_list` (`id`, `client_id`, `product_id`, `quantity`) VALUES
(15, 1, 7, 6),
(16, 1, 4, 11),
(17, 1, 1, 5);
-- Table structure for table `category_list`
--CREATE TABLE `category_list` (
`id` int(30) NOT NULL,
`vendor_id` int(30) NOT NULL,
`name` text NOT NULL,
`description` text NOT NULL,

34
 `status` tinyint(1) NOT NULL DEFAULT 1,
`delete_flag` 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;
-- Dumping data for table `category_list`
INSERT INTO `category_list` (`id`, `vendor_id`, `name`, `description`, `status`, `delete_flag`,
`date_created`, `date_updated`) VALUES
(2, 2, 'Sample 101', 'This is a sample Category Only.', 1, 0, '2022-02-09 11:03:40', '2022-02-09 11:05:03'),
(3, 2, 'Sample 102', 'This is a sample Category 102', 1, 0, '2022-02-09 11:05:57', NULL),
(4, 2, 'Category 103', 'Sample Category 103', 1, 0, '2022-02-09 11:06:10', NULL),
(5, 2, 'test', 'test', 0, 1, '2022-02-09 11:06:17', '2022-02-09 11:06:20'),
(6, 1, 'Category 101', 'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut semper leo vitae dui rutrum
ultricies. Etiam sit amet odio lorem. In sit amet cursus justo', 1, 0, '2022-02-09 11:09:36', NULL),
(7, 1, 'Category 102', 'Morbi pellentesque, dolor in sodales pretium, libero leo finibus arcu, vitae pharetra
ligula quam quis enim. Quisque suscipit venenatis finibus.', 1, 0, '2022-02-09 11:09:45', NULL),
(8, 1, 'Category 103', 'Curabitur fermentum, diam ut dictum molestie, eros dolor luctus dolor, in hendrerit dui
sapien vel lorem. Nulla ultrices gravida nisl, id feugiat turpis varius a. In iaculis lorem nisi. Aliquam nec
aliquam ipsum, vitae fermentum dui.', 1, 0, '2022-02-09 11:10:19', NULL),
(9, 1, 'Category 104', 'Phasellus luctus ultricies dui, non euismod massa congue id. Fusce ut nisi convallis,
aliquam dolor consectetur, varius enim. Phasellus dignissim, erat ac ullamcorper lacinia, nibh est auctor
risus, eget ornare est felis et orci.', 1, 0, '2022-02-09 11:10:35', NULL);

-- Table structure for table `client_list`

CREATE TABLE `client_list` (
`id` int(30) NOT NULL,
`code` varchar(100) NOT NULL,
`firstname` text NOT NULL,
`middlename` text DEFAULT NULL,
`lastname` text NOT NULL,
`gender` text NOT NULL,
`contact` text NOT NULL,
`address` text NOT NULL,
`email` text NOT NULL,
`password` text NOT NULL,
`avatar` text DEFAULT NULL,
`status` tinyint(1) NOT NULL DEFAULT 1,
`delete_flag` 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;
35
-- Dumping data for table `client_list`
INSERT INTO `client_list` (`id`, `code`, `firstname`, `middlename`, `lastname`, `gender`, `contact`,
`address`, `email`, `password`, `avatar`, `status`, `delete_flag`, `date_created`, `date_updated`) VALUES
(1, '202202-00001', 'John', 'D', 'Smith', 'Male', '09123456789', 'This is only my sample address',
'[email protected]', '1254737c076cf867dc53d60a0364f38e', 'uploads/clients/1.png?v=1644386016', 1, 0,
'2022-02-09 13:53:36', '2022-02-10 13:42:53'),
(2, '202202-00002', 'test', 'test', 'test', 'Male', '094564654', 'test', '[email protected]',
'098f6bcd4621d373cade4e832627b4f6', 'uploads/clients/2.png?v=1644471867', 1, 1, '2022-02-10 13:44:26',
'2022-02-10 13:44:35');
-- Table structure for table `order_items`
CREATE TABLE `order_items` (
`order_id` int(30) NOT NULL,
`product_id` int(30) NOT NULL,
`quantity` double NOT NULL DEFAULT 0,
`price` double NOT NULL DEFAULT 0,
`date_created` datetime NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
-- Dumping data for table `order_items`
INSERT INTO `order_items` (`order_id`, `product_id`, `quantity`, `price`, `date_created`) VALUES
(1, 1, 3, 1500, '2022-02-10 09:56:49'),
(2, 7, 10, 285.99, '2022-02-10 09:56:49'),
(3, 4, 5, 50, '2022-02-10 10:29:01'),
(3, 3, 5, 125, '2022-02-10 10:29:01'),
(3, 5, 3, 150, '2022-02-10 10:29:01'),
(4, 6, 3, 45.88, '2022-02-10 10:29:01'),
(4, 7, 3, 285.99, '2022-02-10 10:29:01');
-- Table structure for table `order_list`
-CREATE TABLE `order_list` (
`id` int(30) NOT NULL,
`code` varchar(100) NOT NULL,
`client_id` int(30) NOT NULL,
`vendor_id` int(30) NOT NULL,
`total_amount` double NOT NULL DEFAULT 0,
`delivery_address` text NOT NULL,
`status` 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;

--
-- Table structure for table `product_list`
36
--

CREATE TABLE `product_list` (

`id` int(30) NOT NULL,
`vendor_id` int(30) DEFAULT NULL,
`category_id` int(30) DEFAULT NULL,
`name` text NOT NULL,
`description` text NOT NULL,
`price` double NOT NULL DEFAULT 0,
`image_path` text DEFAULT NULL,
`status` tinyint(1) NOT NULL DEFAULT 1,
`delete_flag` 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;
-- Table structure for table `shop_type_list
CREATE TABLE `shop_type_list` (
`id` int(30) NOT NULL,
`name` text NOT NULL,
`status` tinyint(1) NOT NULL DEFAULT 1,
`delete_flag` tinyint(1) NOT NULL DEFAULT 0,
`date_created` datetime NOT NULL DEFAULT current_timestamp(),
`date_updated` datetime DEFAULT NULL ON UPDATE current_timestamp()
)
INSERT INTO `shop_type_list` (`id`, `name`, `status`, `delete_flag`, `date_created`, `date_updated`)
VALUES
(1, 'Dry Goods', 1, 0, '2022-02-09 08:49:34', NULL),
(2, 'Cosmetics', 1, 0, '2022-02-09 08:49:46', NULL),
(3, 'Produce', 1, 0, '2022-02-09 08:50:31', NULL),
(4, 'Anyy', 1, 0, '2022-02-09 08:50:36', '2022-02-09 08:50:57'),
(5, 'Others', 1, 1, '2022-02-09 08:50:41', '2022-02-09 08:50:45');

-- 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;
(1, 'name', 'Multi-Vendor Online Grocery Management System'),

37
B. SCREENSHOT:

Fig.No.B.1 ADMIN LOGIN

Fig.No.B.2 ADMIN DASHBOARD

38
Fig.No.B.3 PRODUCT LIST

Fig.No.B.4 SHOP TYPE

39
Fig.No.B.5 MONTHLY ORDER - REPORT

Fig.No.B.6 VENDAR LIST

40
 REFERENCE

1. Kumar, A., & Singh, R. (2020). Database Management Systems. Pearson Education India.
➤ Reference for understanding relational database concepts used in GMMS.
2. Welling, L., & Thomson, L. (2017). PHP and MySQL Web Development (5th ed.).
Addison-Wesley Professional.
➤ Used for backend development knowledge using PHP and MySQL.
3. Holzner, S. (2014). HTML, CSS & JavaScript All in One. Sams Publishing.
➤ Referred for frontend interface development.
4. XAMPP Official Documentation. (https://www.apachefriends.org/)
➤ Guidance on configuring Apache server, MySQL, and PHP in a local development environment.
5. Stack Overflow. (https://stackoverflow.com/)
➤ Community-driven solutions and debugging help during development.
6. W3Schools. (https://www.w3schools.com/)
➤ Reference for HTML, CSS, JavaScript, and PHP syntax and examples.
7. Bootstrap Documentation. (https://getbootstrap.com/docs/)
➤ Used for responsive web design elements in the GMMS UI.
8. PlantUML Documentation. (https://plantuml.com/)
➤ Used to design UML diagrams like use case, class, and activity diagrams.

41