0% found this document useful (0 votes)
53 views13 pages

Laundry Shop Management System Design

The document outlines a proposed capstone project for developing a console-based Laundry Shop Management System aimed at automating order processing and improving operational efficiency. It addresses the challenges faced by small laundry shops using manual logbooks, such as errors in order tracking and billing disputes, and proposes a digital solution that includes features like customer management, order tracking, and transaction history. The project aims to enhance service quality, reduce workload for staff, and provide valuable insights for business decision-making.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
53 views13 pages

Laundry Shop Management System Design

The document outlines a proposed capstone project for developing a console-based Laundry Shop Management System aimed at automating order processing and improving operational efficiency. It addresses the challenges faced by small laundry shops using manual logbooks, such as errors in order tracking and billing disputes, and proposes a digital solution that includes features like customer management, order tracking, and transaction history. The project aims to enhance service quality, reduce workload for staff, and provide valuable insights for business decision-making.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Republic of the Philippines

UNIVERSITY OF EASTERN PHILIPPINES


University Town, Northern Samar
Web:[Link]; Email: uepnsofficial@[Link]

Laundry Shop Management with


Stack-Based Transaction
History

BSIT-2A

Submitted by:
Achilles Pyrrhus A. Rosales
Justine Mae G. Delorino

December 15, 2025


II. PROPOSED CAPSTONE TITLE

Laundry Shop Management with Stack-Based Transaction History

III. BACKGROUND OF THE STUDY

Small laundry shops currently use manual logbooks to


record customer information, orders, and payments, making
daily operations slow and prone to errors. During busy hours,
staff struggle to track multiple orders simultaneously, often
resulting in misplaced items, forgotten pickup dates, and
pricing disputes due to calculation mistakes. Searching for
specific customer orders requires time-consuming manual
searching through handwritten pages, and there is no
organized system to track order status from drop-off to pick
up. The absence of proper record-keeping also makes it
difficult to identify regular customers or generate business
reports for decision-making. A digital management system is
urgently needed to automate order processing, maintain
accurate records, track order status in real-time, and
provide quick access to customer and transaction information,
ultimately improving service quality and operational
efficiency.
IV. STATEMENT OF THE PROBLEM

General Problem

The absence of an automated laundry shop management


system results in inefficient order processing, inaccurate
record-keeping, time-consuming manual calculations, and
difficulty tracking customer orders and transaction history.

Specific Problems

• Manual order processing and price calculation are time-


consuming and prone to human errors, especially during peak
hours when multiple customers drop off or collect laundry
simultaneously, leading to incorrect billing and customer
disputes.
• No centralized digital system exists for storing and
organizing customer information, order details, and
transaction records, forcing staff to search through multiple
handwritten notebooks and ledgers to locate specific customer
orders or verify pickup dates.
• Difficulty tracking order status in real-time (pending, in
progress, ready for pickup, claimed) results in confusion
about which orders need attention, missed pickup
notifications, and customers arriving to collect laundry that
is not yet ready.
• Inability to quickly search and retrieve customer order
history when customers inquire about previous transactions,
total spending, or service preferences, making it impossible
to provide personalized service or identify loyal customers.
• Manual record-keeping provides no transaction history or
backup mechanism, making it impossible to recover lost
information, reverse incorrect entries, or generate business
reports for revenue analysis and decision-making.

V. OBJECTIVES OF THE STUDY

General Objective

To develop a console-based Laundry Shop Management


System that automates order processing, organizes customer
and transaction data, tracks order status efficiently, and
improves overall operational workflow using data structures
and algorithms.

Specific Objectives

• To design a user-friendly console interface for laundry shop


operations that allows staff to efficiently manage customer
registration, order creation, price calculation, and status
updates without extensive technical training.
• To develop array-based data storage mechanisms for
organizing customer information (ID, name, phone) and order
details (order ID, service type, weight, price, status,
pickup date) that enable quick data retrieval and
manipulation.
• To implement search algorithms (linear search) that allow
staff to quickly find customer records by ID or name, and
locate orders by customer, status, or order ID, reducing
search time from minutes to seconds.
• To create automated price calculation functions that compute
total order cost based on selected service type and laundry
weight, eliminating manual calculation errors and ensuring
consistent pricing across all transactions.
• To integrate stack-based transaction history that records
all system activities (customer additions, order creations,
status updates) and provides a chronological log of
operations for review and accountability.
• To develop order status tracking functionality that clearly
monitors each order's progress through different stages
(Pending → In Progress → Ready → Claimed), enabling staff to
quickly identify which orders need attention.
• To generate comprehensive reports including revenue
summaries, service type analysis, and customer order
histories that provide business insights for decision-making
and performance evaluation.

VI. PROJECT SCOPE

The Console-Based Laundry Shop Management System will include


the following components and functionalities:

Features

Customer Management:

• Customer registration with unique ID generation


• Customer information storage (ID, name, phone number)
• Customer search by ID or name
• View all registered customers
• Customer profile display with order history count
Order Management:

• New order creation with automatic ID generation


• Service type selection (Wash Only, Wash & Dry, Wash Dry
& Fold, Full Service)
• Automated price calculation based on weight and service
type
• Order status tracking (Pending, In Progress, Ready,
Claimed)
• Order status updates and modifications
• Pickup date setting and tracking
• Complete order details viewing
• Order receipt generation

Search and Filter Functionality:

• Search orders by customer ID


• Search orders by status (Pending, In Progress, Ready,
Claimed)
• Linear search algorithm implementation
• Real-time data retrieval

Reporting and Analytics:

• Revenue summary report (total, completed, pending)


• Service type analysis report (orders per service,
revenue per service)
• Individual customer summary (total orders, total
spending)
• Business performance statistics

Transaction History:

• Stack-based activity logging (LIFO implementation)


• Complete transaction history viewing
• Chronological record of all system operations
• Activity timestamps and descriptions

Additional Features:

• Price list display with service rates


• Dashboard with key statistics (total customers, orders,
revenue)
• Input validation for all data entry
• User-friendly menu navigation system
Users

Primary Users:

• Laundry shop staff/cashiers (main operators)


• Laundry shop owners/managers (for reports and oversight)

System Administrator:

• Technical staff for system maintenance and data


initialization

Modules

The project will be structured into six key sections


(modules):

1. Customer Management Module

• Add new customer


• View all customers
• Search customer by ID or name
• Display customer information

2. Order Management Module

• Create new order


• View all orders
• Update order status
• View order details
• Order receipt display

3. Search and Filter Module

• Search orders by customer


• Search orders by status
• Filter and display results

4. Reports Module

• Revenue summary generation


• Service type report
• Customer spending summary
• Statistics calculation and display

5. Transaction History Module

• Transaction logging (stack operations)


• History viewing
• Activity tracking

6. Utility Module

• Price list display


• Dashboard statistics
• Main menu navigation

Functions

Data Storage Functions:

• Store customer data in arrays (IDs, names, phones)


• Store order data in parallel arrays (8 arrays for order
attributes)
• Maintain counters for customers and orders

Processing Functions:

• Calculate total price (weight × service rate)


• Generate unique customer IDs (C001, C002, ...)
• Generate unique order IDs (O0001, O0002, ...)
• Calculate pickup dates (current date + 3 days default)
• Update statistics (total revenue, order counts)

Search Functions:

• Linear search for customer by ID


• Linear search for customer by name (substring matching)
• Linear search for orders by customer ID
• Linear search for orders by status

Display Functions:

• Format and display customer lists in tabular format


• Format and display order lists with columns
• Display individual customer details
• Display individual order details
• Show dashboard with statistics
• Present reports with calculated summaries

Stack Operations:

• Push transactions to history stack


• Display transaction history (convert stack to array)
• Maintain chronological activity log

Validation Functions:

• Validate numeric input (service selection, weight)


• Check array capacity before insertion
• Verify customer existence before order creation
• Validate status selection (1-4 options)

Processes Covered

The system encompasses the entire lifecycle of a laundry


order:

Customer Registration Process:

1. Generate unique customer ID


2. Input customer name and phone
3. Store in customer arrays
4. Log transaction to history
5. Display confirmation

Order Creation Process:

1. Verify customer exists


2. Select service type from menu
3. Input laundry weight
4. Calculate total price automatically
5. Set pickup date
6. Generate unique order ID
7. Store order in arrays with "Pending" status
8. Log transaction to history
9. Display order receipt
Order Status Update Process:

1. Search for order by ID


2. Display current status
3. Select new status from options
4. Update order status in array
5. Log transaction to history
6. Display confirmation

Customer Search Process:

1. Input search term (ID or name)


2. Perform linear search through customer arrays
3. Display matching customer(s)
4. Show "not found" message if no match

Order Search Process:

1. Select search criteria (by customer or by status)


2. Perform linear search through order arrays
3. Display matching orders in table format
4. Show count of results found

Report Generation Process:

1. Traverse order arrays


2. Calculate required statistics (sums, counts, averages)
3. Format data in readable tables
4. Display summary information

Transaction Logging Process:

1. Create transaction description string


2. Push to transaction history stack (LIFO)
3. Maintain chronological activity record
VII. PROJECT DELIMITATIONS

The Console-Based Laundry Shop Management System will NOT


include the following features and functionalities:

• User Interface: Graphical UI, web interface, mobile app,


or touch screen capabilities – console-based only
• Data Management: Database system, file storage, cloud
backup, or data export features – uses in-memory arrays
only
• Payment Features: Payment processing, cash register
integration, receipt printing, or financial transaction
handling
• Communication: SMS notifications, email alerts,
automated reminders, or marketing messages
• Hardware Integration: Barcode scanners, weighing scales,
receipt printers, or other peripheral devices
• Security: User login, password protection, data
encryption, or role-based access control
• Multi-User: Concurrent access, network capabilities, or
real-time synchronization across devices
• Advanced Features: Customer portal, online booking,
loyalty programs, inventory tracking, employee
management, or multi-branch support
• Integration: Third-party APIs, accounting software,
payment gateways, or external system connections
• Capacity Limits: System limited to 100 customers and 200
orders due to fixed array constraints
• Data Persistence: Data does not save permanently;
information resets when program closes
• Deployment: No production deployment, pilot testing, or
real-world implementation – academic demonstration only

VIII. SIGNIFICANCE OF THE STUDY

These are the people will benefit from the Laundry Shop
Management with Stack-Based Transaction History System:

• To Laundry Shop Owners/Managers:

- Owners gain automated reports showing revenue, popular


services, and customer trends that support informed
business decisions. The centralized system provides
operational oversight with complete transaction history
for accountability.

• To Laundry Shop Staff/Employees:

- Staff benefit from automated price calculations that


prevent errors and instant searches that eliminate
manual notebook browsing. The organized system reduces
work stress and speeds up service during busy periods.

• To Customers:

- Customers receive faster service with accurate billing


and systematic tracking that prevents lost items. The
professional experience builds trust and satisfaction.
• To Small Business Community:

This system demonstrates that small businesses can


achieve digital transformation affordably without
expensive software. The implementation serves as a
practical model for other service-oriented businesses.

• To Future Researchers and Computer Science Students:

- This research shows practical application of


fundamental data structures (arrays, stacks) and
algorithms (linear search) in solving real business
problems. The documented implementation guides future
capstone projects in business automation.

Common questions

Powered by AI

The use of stack-based transaction history in the proposed system improves operational accountability by maintaining a chronological log of all activities performed within the system. Each transaction involving customer additions, order creations, and status updates is recorded in a Last In, First Out (LIFO) manner. This allows staff and managers to view previous operations and actions taken within the system to verify past activities or audit the handling of transactions . The capability to review a chronological activity log enhances transparency and accountability since every change or entry can be traced back to its source and timestamp.

The system’s order management functionality supports efficient workflows by automating the creation and management of orders. The system allows for automatic order ID generation, service type selection, and automated price calculations based on service type and laundry weight. It enables staff to update and track order statuses (Pending, In Progress, Ready, Claimed) quickly and accurately. By organizing order details and status tracking in a digital format, the system reduces manual errors and speeds up operation during service peaks . Staff can focus on customer service rather than administrative work, improving speed and accuracy.

The Laundry Shop Management System described is limited by its reliance on a console-based interface and in-memory data storage without any database or cloud backup. This means the system lacks a graphical user interface, payment processing features, communication functions such as SMS or email alerts, and hardware integration like barcode scanners. Also, it does not support multi-user access or role-based security features. As such, the system is not suitable for real-world deployment due to capacity limits (100 customers and 200 orders), lack of data persistence, and no production deployment plans . These limitations prevent the system from being scalable or suitable for handling larger volumes of transactions or users in a real-world laundry business.

The system’s reliance on linear search algorithms for retrieving customer and order data affects its efficiency, especially during peak times when responsiveness is crucial. Linear search iterates through elements one by one; therefore, search time increases linearly with the number of entries. During peak times, this can lead to delays in accessing customer or order information as opposed to more efficient search algorithms, such as binary search, which could offer logarithmic performance. Although linear search is simple to implement, its inefficiency with larger datasets can be a bottleneck, making real-time data retrieval slower . This limits the system's ability to quickly handle large volumes of transactions and inquiries, potentially impacting service speed and customer satisfaction during busy periods.

The limitations concerning capacity and data persistence significantly affect the long-term viability of the system. With a capacity constraint of 100 customers and 200 orders due to fixed array sizes, the system is unsuitable for scaling as the business grows beyond these limits. Additionally, the lack of data persistence — wherein data resets every time the program closes — poses a serious issue for long-term data management and reliability. Without persistent storage, there is no continuity of data between sessions, leading to potential loss of critical business information and decision-making insights. These constraints make the system more of an academic exercise than a practical, deployable solution for operational laundry businesses seeking to sustain and expand operations .

The system design reflects the implementation of fundamental data structures and algorithms taught in computer science by utilizing arrays and stacks. Arrays are used to organize and store customer and order data, allowing efficient data retrieval and manipulation via linear search algorithms. The design employs linear search for locating customer records and orders, which showcases basic algorithmic understanding. The stack-based transaction history demonstrates the use of LIFO for systematically recording and reviewing chronological order entries . These elements highlight practical applications of core computer science concepts, providing a simplified yet effective solution to the management of data and operations within a small enterprise.

The proposed Laundry Shop Management System facilitates better business decision-making by providing automated reports and business analytics. It generates comprehensive reports that include revenue summaries, service type analyses, and individual customer spending histories. Managers and owners can use this data to identify popular services, track business performance, and understand customer behavior and preferences. The centralized digital system provides operational oversight and aids in strategic planning by offering insights into revenue generation and customer trends . By delivering organized and accessible data, the system helps decision-makers make informed choices to optimize operations and improve service offerings.

Without a database, the Laundry Shop Management System ensures data integrity through structured use of arrays to store customer information and order details. Each customer is assigned a unique ID, and data is organized into multiple parallel arrays to maintain consistency and ease of access. The use of structured naming conventions and array capacity checks before insertions prevent data overlap and corruption . Transactions are logged in a stack-based system ensuring a consistent format and chronological order. Through input validation functions, the system maintains data integrity by verifying data entries for correctness before storage.

The proposed system addresses the problem of tracking order status by implementing a clear and detailed order status tracking functionality. It monitors each order through various stages: Pending, In Progress, Ready, and Claimed. Staff can update order statuses in real-time, allowing for quick identification of orders that require attention. This organized tracking prevents confusion over which orders need to be processed and mitigates issues such as missed pickup notifications or customers arriving for orders not yet ready . The ability to update and view order statuses systematically through console commands ensures efficient management of laundry operations.

The Laundry Shop Management System potentially enhances customer experience through improved accuracy and reliability in service delivery. By automating price calculations and maintaining digital records of orders, the system minimizes billing errors and misplacements, thus increasing billing accuracy. Real-time order tracking ensures customers receive timely updates on order status, reducing inconvenience caused by unexpected delays or errors. This systematic approach fosters increased trust and satisfaction among customers, as services run smoothly and customer inquiries can be addressed promptly . However, since it remains console-based and lacks features such as notification alerts, its direct impact on customer interactions might be limited compared to more integrated systems.

You might also like