+zzzzzf

The Development of Point-of-Sales and Inventory System for Food Hub Garden in

Culianin, Plaridel, Bulacan

An Undergraduate Project Management 1 Submitted in Partial Fulfillment of the Requirements

for

Bachelor of Science in Information Systems

Researchers:

Cruz, Robelyn L.

Llaneta, Ian M.

Reyes, Kevin Patrick C.

Gerazo, Jenilyn C.

Richwell Colleges, Incorporated

January 2025
Table of Contents

Page

List of Tables ...................................................................................................................... i

List of Figures ..................................................................................................................... i

Software Methodology

Introduction......................................................................................................................... 1

Planning Phase..................................................................................................................... 5

System Analysis Phase........................................................................................................ 8

System Design Phase........................................................................................................... 15

References........................................................................................................................... 50
 LIST OF TABLES

Table Page

1 Gantt Chart …………………………………………………………………….... 3

2 RACI Matrix ……………………………………………………………………. 6

3 Data Dictionary …………………………………………………………………. 13

LIST OF FIGURES

Figure Page

2 Scrum Development Cycle.…………....…….………………….…………..…... 4

1 Use Case Diagram ……………….……..………………………….…………… 10

3 Functional Decomposition Diagram.……..………………………….………..... 11

4 Data Flow Diagram Level 0-Context Diagram………….……………………… 15

5 Data Flow Diagram Level 1…………………………………...…………...….... 16

6 Data Flow Diagram Level 2…………………………………….………....……. 17

10 Entity Relationship Diagram ……………………………...………….……….... 23

11 Register Account………………………………………………………………... 24

12 Login Account…………………………………………………………………... 25

13 Logout Account…………………………………………………………………. 26

14 View Employee Profile…………………………………………………………. 27

15 Reset Password…………………………………………………………………. 29

i
16 Manage Payment…………………………………………………...................... 30

17 Process Sales……………………………………………………………………. 31

18 View History Sales Transaction.………………………………………………... 32

19 Manage Inventory………………………………………………………………. 33

20 View Inventory Data……………………………………………………………. 34

21 Monitor Stock Levels…………………………………………………………… 35

22 Generate Report…………………………………………………………………. 36

23 Export Report……………………………………………………………………. 37

24 Wireframe………………………………………………………………………... 38

i
 SOFTWARE METHODOLOGY

Introduction

The modern food industry is a very competitive and ever-evolving field, with growing

consumer expectations for additional products and improved food safety, quality, and shelf-life

variety and use of sustainable, eco-friendly, and green production methods. However,

conventional as processing methods alter the structure and conformation of food products, they

may have an impact on sensory quality attributes like appearance, color, taste, and texture. Thus,

food researchers and the food industry should continuously look for more sophisticated solutions

and technologies, such as innovative processing and analytical procedures, to meet the

continuously rising customer demands for high-quality food items (Echegary et al., 2022). The

current era of the food industry is marked by increased interconnectedness and the use of new

technologies, particularly digital innovations like blockchain, cloud computing and analytics, and

artificial intelligence (AI), as well as other innovative techniques like the Internet of Things

(IoT), smart sensors, autonomous robotics, and 3D food printing (Chowdhury et al., 2022).

These advanced technologies have sped up automation and digitization in practically every

business, including the food sector, improving intelligent food quality management and quick,

online, and on-site monitoring.

Nowadays, Point of Sale (POS) systems are widely used in developing nations.

due to the fact that they offer quick and easy methods of conducting business. Therefore, it

1
becomes crucial for them to ensure the software quality given the high volume of clients in

supermarkets and the more competitive business environment in developing nations. Since user

interfaces are closely related to cashier behavior, customer happiness, and market revenues,

usability is emphasized among other software quality factors for point-of-sale (POS) software.

In the Philippines, the shift towards automated Point of Sale (POS) systems and

Inventory Management has become increasingly prevalent. Major retail chains and businesses

across the country are embracing technology-driven solutions to enhance operational efficiency,

customer service, and overall business performance. The implementation of POS systems is not

only viewed as a modernization strategy but also as a means to stay competitive in the evolving

retail sphere.

One essential business tool that has revolutionized traditional cash registers with creative,

tech-driven solutions is a point-of-sale (POS) system. Modern point-of-sale (POS) systems

provide more than only sales processing, in contrast to previous systems (Rivera, 2023). They

can handle staff schedules and clock-ins, track inventory across several selling avenues, and

collect data for company insight and individualized customer support. Inventory management

and automated point of sale (POS) systems are becoming more and more common in the

Philippines. Technology-driven solutions are being adopted by large retail chains and companies

across to improve customer service, operational effectiveness, and overall business performance.

POS system deployment is not simply seen as both as a modernization approach and as a way to

maintain competitiveness in the rapidly evolving retail industry.

2
 Most current trends include with the reporting capabilities of point-of-sale systems,

employee can keep a close check on sales, earnings, and costs such as cost of products sold.

Real-time, easily readable information is provided to you through POS reports. Staff always have

the data they need to make informed business decisions, no matter where they are. They may

also keep an eye on Key Performance Indicators like average customer sales, stock turnover, and

sell-through rate with POS system. They may use this insight into your company's performance

to pinpoint areas that are doing well and those that require improvement. In any case, this

knowledge will help you make the necessary changes to help business stay profitable and

competitive. The accounting process can be made more efficient with the use of a point-of-sale

system. With a POS system, you can print reports and, in many cases, import data directly with

your accounting software, eliminating the need for accountants to sort through numerous receipts

like they would with an old-fashioned cash register (Chavan, 2023).

Furthermore, according to Sneh Chavan, & S. D. Bhoite (2024), as a result of technology

advancements and altering consumer tastes, the retail business is undergoing considerable

changes. These include self-service kiosks, point-of-sale (POS) systems, and inventory

management tools, which enhance customer experience and streamline operations.

The researchers of this study observed that at Food Hub, the Point of Sale (POS) system

relies on human tracking for order processing and stock control instead of inventory

management. With this arrangement, the system may concentrate entirely on processing sales,

3
transactions, and client information, with staff members managing inventory monitoring

manually.

Point of Sale (POS) systems are technical cornerstones that are driving a paradigm

change in modern corporate transactions, yet they face many challenges to their smooth

functioning (Khattab, 2022). Connectivity issues, security flaws, and operational complexities

are just a few of the many challenges facing POS systems, which call for careful handling and

innovative solutions. These issues have a complex impact on POS systems' dependability, data

security, and general effectiveness, underscoring the necessity of taking preventative action

when negotiating these complications in modern business. Transactions are disrupted by

fluctuating connectivity, which highlights the necessity of dependable internet or backup systems

to guarantee continuous operations. Strong security measures are necessary to maintain

consumer data and stop breaches due to the constant threat landscape. To protect sensitive data,

this calls for strict security procedures and encryption techniques. Regular system upgrades and

patches are crucial for boosting security and functionality. Updates must be carefully planned in

order to prevent interruptions during busy business hours and guarantee continuous functioning.

User experience is hampered by complex interfaces, which highlights the necessity for personnel

to receive thorough training and have user-friendly designs.

The traditional way retailer keeps their sales and inventory details is in spreadsheets

which are not effective anymore when the size of the shop gets bigger. This is because more

items will be made available in a larger quantity, thus tracking the sales made with inventory

level in the shop would be complicated and time consuming for the retailer. Besides, the

4
situation gets worst when the retailer does not have proper method to determine items purchased

by their customers. (Acosta, D., Alquizar, et al, 2020).

Since staff members must manually enter data about stock flow, Food Hub is prone to

human error and inefficiencies in tracking stock levels in the absence of automated inventory

management. This might cause delays or inaccurate restocking. However, as staff members have

more control over the tracking procedure and are able to quickly adjust to changes, the lack of an

integrated inventory management system may also provide some flexibility. The manual

technique may be advantageous for smaller businesses with low inventory, when the complexity

of computerized inventory tracking may not be required, regardless of the possibility of errors.

Because it eliminates the need for expensive inventory software, the manual nature of the POS

system may also result in reduced initial expenses. Food Hub must, however, rely on accurate

and prompt manual tracking in order to avoid stockouts, overstocking, or inventory

inconsistencies.

The main objective of point-of-sale system is to provide retailers and merchants a

centralized retail and sales management interface(s). A registered user can, at any moment,

oversee their store. It is a completely self-sufficient unit. This system has been developed to offer

systematic and thorough management of the store, documentation, and overviews, among other

tasks. It additionally contains a transaction system that guarantees every item a customer buys

are instantly recorded in the inventory. To access the POS system, users need to enter their login

credentials and password for transaction purposes. Process, as well as the addition and removal

5
of data. The point-of-sale system features a catalog of products, amount, and cost. In

comparison, the transaction procedure involves inputting details like the name of the item, its

price, and the quantity, along with the payment obtained from the customer. (Khalid, 2022).

The system aims to enhance operational efficiency, improve accuracy in monitoring

inventory, and generate reliable financial reports. Additionally, it seeks to strengthen inventory

management, speed up transaction processes, and support decision-making and competitive

performance through the use of digital accounting systems, as highlighted by Lutfi et al. (2022).

Additionally, the researcher’s objective is to implement a point-of sales and inventory

system for Food Hub Garden to reduce manual monitoring of products. This means the business

updates the inventory by physically counting the inventory items on a frequent basis is no longer

needed. Manual inventory systems are time consuming, as the business owner must keep track of

inventory sales on a daily basis, while updating the system manually at the end of the day will be

eliminated.

This project significantly helps the business by implementing an automated inventory

system along with point-of-sales (POS) solution. It solves problems like human errors, slow

manual stock monitoring, and incorrect inventory records. The system updates stock levels in

real time, reducing mistakes and keeping track of inventory accurately. The POS integration,

sales data is automatically recorded, saving time and avoiding errors from manual entry. This

makes managing inventory faster and more reliable while ensuring products are always available

6
for customers. The improved process helps the business make better decisions, avoid

overstocking or running out of stock, and keep customers satisfied. Therefore, the project boosts

efficiency, saves resources, and supports the business’s long-term success.

The researchers propose addressing the problem of manually monitoring inventory in

Food Hub's Point of Sale (POS) system by implementing an automated inventory management

system. This system would align inventory levels with sales information instantly, minimizing

the chances of human mistakes and inefficiencies. The researchers suggest training personnel to

efficiently utilize the automated system to facilitate seamless integration and precise data entry.

Furthermore, incorporating notifications for low inventory can assist in avoiding stock shortages,

while keeping detailed logs of stock transactions can improve decision-making. For smaller

operations, the researchers recommend beginning with a simple, budget-friendly software

solution customized to the business's particular requirements to strike a balance between

efficiency and cost.

7
Software Methodology

Figure 2. Scrum Agile Methodology

The researcher will use scrum agile methodology to develop the POS system with

inventory management system for Food Hub Garden.

The aims and objectives that must be met after the project is finished are described in the

initiation phase. During this stage, team members' tasks will be assigned and stakeholders will be

identified. Everything that the iterations will process will be included in the planning phase.

Starting with the most important component, the team will divide the work into several

iterations. The planning phase's iterations will constitute the implementation phase; development

8
won't go on to the following iteration until the current one is complete. The implementation

phase's testing will take place during the review phase. Following each iteration, the system will

be tested to get user input. Furthermore, the deployment phase will be the last stage of project

development and provide the client with the finished product, guaranteeing that it is operational.

Planning Phase

3.1 Gantt Chart

Table 1. Scrum Gantt Chart

9
 Table 1 shows the proposed project's complete timeline and scheduled activities,

organized using a Scrum Gantt chart. Considering the important milestones and sprint cycles

stated, this chart offers a visual representation of the project schedule. It will be expected that the

reconstruction will be accomplished in three months, from November to January. In order to

ensure efficient time management and adhere to Scrum principles, each task phase is carefully

planned, allowing for the timely delivery of the final product.

3.2 RACI Matrix

10
 Table 3. RACI Matrix

Table 3 shows the assignment of roles and responsibilities for each team member such as

Responsible, Accountable, Consulted, and Informed. This chart clearly defines who is

responsible for what, which can help reduce miscommunication. It allows to demonstrate that the

11
right people are involved at the right times, which can help improve transparency and prevent

misunderstandings. To ensure that the project development minimize delays, there is a single

person who is accountable for each task.

System Analysis Phase

4.1 User Stories

1. Owner/Manager

1.1. Login

As an Owner/Manager, I want to log in to the system using my username and password,

so that I can securely access and manage all features of the system.

Acceptance Criteria

 Username and password requests must be generated through the system

 Credentials must be checked against stored data by the system.

 The system must allow complete access to all functions following successful

authentication.

1.2. Generate Reports

As an Owner/Manager, I want to generate various reports, so that I can analyze business

performance and make informed decisions.

12
Acceptance Criteria

 The system must provide options to generate sales, inventory, and staff performance

reports

 Reports must be available for different time periods (daily, weekly, monthly)

 The system must provide reports be exportable to formats like PDF and Excel

1.3. View Sales Data

As an Owner/Manager, I want to view sales data, so that I can monitor the entire sales

performance and trends.

Acceptance Criteria

 The system must display sales data on a dashboard

 Data must include total sales, number of transactions, and top-selling products.

 The system must allow filtering sales data by date range

1.4. View Inventory Data

As an Owner/Manager, I want to view inventory data, so that I can monitor and oversee

stock levels and the uptime movement of products.

Acceptance Criteria

 The system must display current stock levels on a dashboard.

 The system must provide details on inventory movement (in-going and outgoing).

 The system must alert when inventory product is no longer available or low.

13
1.5. Manage Inventory- include

As an Inventory Manager, I want to manage the inventory, so that I can keep the

inventory data accurate and up-to-date.

Acceptance Criteria

 The system must allow adding new products with details like name, category, quantity.

and price.

 The system must allow updating existing product details.

 The system must allow deleting products from the inventory.

 The system must provide confirmation prompts for critical actions like deletions.

1.6. Update Stock Level

As an Inventory Manager, I want to update stock levels, so that I can ensure accurate tracking

of inventory.

Acceptance Criteria

 The system must allow manual updates to product stock levels.

 The system must automatically update stock levels upon sales transactions.

 The system must provide alerts when stock levels are low.

 The system must log all stock level changes for auditing purposes.

2. Cashier

2.1 Login

14
 As a Cashier, I want to log in to the system using my username and password, so that I

can securely access sales processing features.

Acceptance Criteria

 The system must prompt for a username and password.

 The system must validate credentials against stored data.

 Upon successful authentication, the system must grant access to sales processing features

2.2 Sales Processes

As a Cashier, I want to manage the sales process, so that I can efficiently process the

entire customer transactions online or not.

Acceptance Criteria

 The system must allow scanning product barcodes to add items to the sale.

 The system must support manual entry of product details if scanning fails.

 The system must calculate totals, apply discounts, and generate receipts.

 After a sale is completed, the system needs to automatically update the inventory levels.

4.2 Use Case Diagram

15
 Figure 1. Use Case Diagram

Figure 1 illustrates the Food Hub Garden Point-of-Sales and Inventory System is used by

two main users—Owner and Cashier—to make business tasks easier. The Owner can use all

features, like logging in, processing sales, managing inventory, updating stock, viewing sales and

inventory data, and creating reports. This helps them manage transactions, stock, and business

16
performance. The Cashier has limited access to tasks like logging in, processing sales, updating

stock, and checking inventory, which allows them to handle daily transactions. The system helps

reduce mistakes, keep track of the business, and make better decisions.

4.3 Functional Decomposition Diagram (FDD)

Breaking Down High-Level Functions into Detailed Sub-Functions

Figure 3. Functional Decomposition Diagram

17
 Figure 3 shows the breaking down of key functions of the Food Hub Garden sales and

inventory system into four main areas: account management, report, sales, and inventory

management. Each area includes specific tasks, such as user registration, processing payments

(Cash, Credit Card, GCash), managing stock, and generating/exporting sales and inventory

reports. This structured breakdown ensures clarity and detailed organization for system

functionality.

4.4 Data Dictionary

Table 3. Employee Table Data Dictionary

18
 Table 3 illustrates the structure of the Employee Table, which includes essential

employee details like EmployeeID (Primary Key), name, contact information, and position. The

role area classifies staff into Admins, Cashiers, or Inventory Managers, guaranteeing that the

system accurately corresponds with duties and supports user-role-specific functions.

Table 4. Sales Table Data Dictionary

Table 4 illustrates the structure and relationships within the Sales Table of the Food Hub

Garden Sales and Inventory System. This table connects sales transactions through key fields

such as SalesID (Primary Key) and ProductID (Foreign Key). It outlines the details of each sale,

19
including the product name, quantity sold, and price, linking inventory information to transaction

data.

Table 5. Product Table Data Dictionary

PRODUCT

Table 5 illustrates the Inventory Table, emphasizing the arrangement of product

information. The ProductID (Primary Key) distinctly identifies every item, whereas attributes

such as ProductName, Category, Price, and Quantity preserve detailed stock information. This

table connects inventory management with sales processes using common identifiers. This table

links inventory management to sales processes through shared identifiers.

System Design Phase

20
5.1 Data Flow Diagram (DFD)

Figure 4. Level 0 Data Flow Diagram

Figure 4 illustrates how three main users—inventory manager, cashier, and admin—interact with

the system. Each user has specific processes, such as managing inventory, processing sales,

generating reports, logging in/out, and viewing data. Arrows indicate the flow of information

between users and the system. This diagram provides a high-level overview of the system's

functions and user interactions.

21
Figure 5. Level 1 Data Flow Diagram

22
Figure 5 highlights the various responsibilities and tasks assigned to each stakeholder while

illustrating the relationships between the different elements of a Functional Decomposition

Diagram (FDD). A clear, hierarchical breakdown of complex procedures into smaller, easier-to-

manage components is provided by this diagram. It ensures that the responsibilities of each

stakeholder are well-defined and in line with the larger goals through highlighting how their

roles fit into the workflow as a whole. The methodical approach promotes improved

understanding, working together, and responsibility among all process stakeholders.

Figure 6. Level 2 of Account Data Flow Diagram

23
An employee management system's data flow diagram (DFD), shown in Figure 6, illustrates how

users and system operations interact. The administration, cashier, and inventory manager are key

stakeholders who enter data into different processes.

The Employee entity serves as an important data store. The processes are listed as

follows: 1.1 Register User, where the admin enters user data to make new employee records; 1.2

Login, that allows users to log in and confirm their credentials; 1.3 Logout, which allows users to

exit the system; 1.4 Reset Password, which enables users to change their passwords; and 1.5

View Employee Profile, which gives users access to employee information. Data flows among

actors, processes, and the employee entity, ensuring effective system management of employee-

related data.

24
 Figure 7. Level 2 of Sales Data Flow Diagram

Figure 7 shows Level 2 Data Flow Diagrams (DFDs) for a system's sales processes.

There are three primary processes shown: 2.1 Process Sales, in which the admin enters and looks

at sales information to update the sales entity; 2.2 Managing Payment, in which the cashier

enters payments and has them validated before updating the sales record; and 2.3 View Sales

Transaction, which gives the manager and cashier access to and monitoring of sales transactions.

These procedures provide efficient data transfer, validation, and changes to the Sales transaction.

Figure 8. Level 2 of Inventory Data Flow Diagram

25
 Figure 8 demonstrates Level 2 Data Flow Diagrams (DFDs) for a system's inventory

processes. Three essential processes are as follows: 3.1 Manage Inventory, in which the admin

enters data to update the inventory entity; 3.2 Monitor Stock Levels, which enables the manager

and inventory manager to keep an eye on inventory and receive notifications when stock levels

change; and 3.3 View Inventory Data, which allows the administrator and inventory manager to

view inventory records and receive alerts indicating important updates. Data accessibility, stock

monitoring, and effective inventory management are all maintained using these processes.

Figure 9. Level 2 of Report Data Flow Diagram

Figure 9 represents a Level 2 Data Flow Diagram (DFD) for a system's Report process.

The two main tasks that are managed by the manager are 4.1 Export Report and 4.2 Generate

Report. After entering data from the Sales and Inventory entities, the manager can create relevant

26
reports in 4.1 Generate Report. The created reports are exported in 4.2 Export Report so that the

admin can use them further and make effective use of the data that was received from Sales and

Inventory. The development, retrieval, and exporting of reports for monitoring and making

decisions are demonstrated in this flow.

5.2 Entity Relationship Diagram (ERD)

Product

Figure 10. Entity Relationship Diagram

Figure 10 illustrates three tables such as Employee, Sales, and Inventory. The Employee

table includes Employee ID (primary key), name, position, and contact details. The Sales table

contains Sale ID (primary key), Employee ID (foreign key), product sold, quantity, and sale date,

linking sales to employees. The Inventory table holds Product ID (primary key), product name,

quantity, and price, tracking available stock. The relationships connect the Sales table to the

27
Employee table via Employee ID and to the Inventory table through product information,

ensuring efficient management of employees, sales, and inventory.

5.3 Flow Chart

Figure 11. Register Account

Figure 11 outlines the steps involved in the user registration process. The process begins

with the system displaying a registration screen where the user is prompted with the question,

28
"Already have an account?”. If the user answers Yes, they are redirected to the login process

(marked as point A). If the response is No, the user proceeds to input their credentials (e.g.,

username, password, and other required details). Once the information is entered, the system

securely stores the data. The registration process then ends successfully. This approach ensures

that new users can create accounts while offering returning users the option to skip registration

and log in instead.

Figure 12. Login Account

29
 Figure 12 illustrates the login procedure, which validates user credentials for system

access. The process starts by displaying the login screen, prompting users to enter their

credentials, such as username and password. The system then moves to validate the credentials.

At this stage, it checks whether the user’s account exists in the database and if the account is

found Yes, the login is deemed successful, and access is granted. If the account is not found No,

the system marks it as an invalid account, and the process ends. This ensures that only authorized

users with valid credentials can access the system, enhancing security and preventing

unauthorized access.

30
 Figure 13. Logout Account

Figure 13 represents the logout process, ensuring that user sessions are securely

terminated. The process starts when the user clicks the logout button. The system then displays a

confirmation prompt, asking if the user wants to log out. If the user selects No, the logout request

is canceled, and the user is redirected back to the previous page. The process ends here. If the

user selects Yes, the system proceeds to end the session and displays the login page, indicating a

successful logout. This flow ensures that users have the option to confirm logout and that

sessions are securely closed to maintain system security.

31
Figure 14. View Employee Profile

32
 Figure 14 illustrates the process of viewing employee profiles, a feature accessible to

system administrators. The flow begins with the admin logging into the system. After successful

authentication, the admin proceeds to select an employee profile from the list of available

profiles. Once the selection is made, the system retrieves and displays the employee profile

containing relevant information such as name, role, and contact details. The process then

concludes. This ensures that administrators can efficiently access and manage employee details,

providing a structured way to view personnel information as needed.

Figure 15. Reset Password

Figure 15 shows the password reset process begins with the display of the login page. If

the user selects the "Forgot password" option, they are prompted to enter their username. The

system then validates the provided username. If the username is invalid, the system prompts the

user to re-enter it, and the process ends. However, if the username is valid, the system prompts

the user to enter a new password. Once the new password is entered, the system confirms the

password reset, and the process successfully concludes.

33
 Figure 16. Manage Payment

Figure 16 shows the outlines of steps involved in the Manage Payment process. The

process begins with the system displaying the order list. At this point, the user is prompted with

the question, “Proceed to payment or remove product?”. If the user selects No, they can choose

to remove a product by selecting the item and clicking the Remove button. The process then

ends. If the user selects yes, they proceed to the payment process. The user begins by selecting a

payment option and choosing their preferred payment method. Once the payment details are

provided, the system processes the payment and displays a payment confirmation message. The

process then ends successfully.

34
Figure 17. Process Sales

35
 Figure 17 illustrates the workflow for processing sales in a system. The process starts

when the user accesses the display sales system interface. From here, the user proceeds to Select

Product to initiate the transaction. Once a product is chosen, it is added to the order list through

the Add product to order list step. After the product is successfully added, the system updates

and displays the product on the order list for user confirmation or review. The process concludes

at the END point, ensuring that the product selection and order list are managed in a systematic

and organized manner, facilitating smooth sales operations.

Figure 18. View History Sale Transaction

36
 Figure 18 represents the process of viewing historical sales transactions in the system.

The flow begins at the START point, where the system displays the Sales Transaction interface.

The user then proceeds to Select Date Range to filter the transactions. From here, the system

evaluates whether a transaction exists within the selected range, represented by the decision point

Is transaction exist. If the answer is yes, the system proceeds to display the history transaction,

and the process ends. If the answer is no, the system notifies the user that no transaction was

found, and control returns to the Sales Transaction display interface, concluding the process.

Figure 19. Manage Inventory

37
 Figure 19 shows how to manage an inventory system with three main options: adding,

updating, or removing products. To add a product, you enter its details, and the system saves it.

To update a product, you select an existing item, modify its details, and save the changes. To

remove a product, you simply select it, and the system removes it, ensuring the inventory stays

current and accurate.

Figure 20. View Inventory Data

Figure 20 explains how to view inventory data. The process starts with the system

displaying the inventory interface. The user selects the specific inventory data they want to view,

and the system displays it. The process ends after the requested data is shown.

38
 Yes

Figure 21. Monitoring Stock Levels

Figure 21 defines the process of monitoring stock levels within an inventory system. It

starts with displaying the inventory system, where the user can access stock information. The

system checks "Is there enough stock?" a decision point. If yes, the process proceeds to monitor

ongoing stocks and generate updated stock reports. If no, the system sends an alert to notify the

need for restocking or attention.

39
 Figure 22. Generate Report

Figure 22 demonstrate that the process begins by accessing the report system. If the user

opts to generate a report, they proceed by selecting the report, entering parameters, and

generating the report. Otherwise, they are returned to the previous page, ending the process.

40
 Figure 23. Export Report

Figure 23 shows once the report is displayed, the user can choose an export format (PDF,

Word, or Excel). If they confirm the export, the system marks it as "Export confirmed" and ends

the process. If they decline, the system redirects to the report display, and the process ends.

41
5.4 Wireframe

Figure 24. Register Account

Figure 24 illustrates the registration interface of the Food Hub Garden Sales and

Inventory System. This wireframe highlights the user-friendly design for creating a new account.

It includes fields for inputting essential details such as name, email, phone number, and role

selection (e.g., Admin, Cashier, Inventory Manager), ensuring secure and streamlined

onboarding.

42
 Figure 25. Login Account

Figure 25 shows the login screen for the Food Hub Garden Sales and Inventory System.

The wireframe contains fields for inputting an email address and password, as well as role

selection and choice for saving login details and using the password recovery feature. It provides

a seamless and safe access point for system users.

43
 Figure 26. Reset Password

Figure 26 illustrates the reset password interface. This wireframe provides users with a

secure process to recover their account access by entering their registered email or phone

number. It includes fields for role choice and creating a new password, ensuring account

recovery is both efficient and secure.

44
 Figure 27. Sales Management

Figure 27 displays an "Order List" interface within the Food Hub Garden Sales and

Inventory System. The chart includes details of products added to an order, such as SaleID,

SaleDate, ProductID, ProductName, Quantity, and Price. The sum Amount of the order is

showed at the bottom, summing up to 1130. The two buttons, Remove Product and Proceed

Payment, are

specified for managing the order. The right side of the screen features multiple empty product

structure slots and a search bar for searching products. This wireframe represents the stage in

which the order is ready for payment processing.

45
 Figure 28. Payment Process

Figure 28 demonstrates the same "Order List" with a pop-up for the payment method.

Through the Cancel and Process Payment buttons to cancel the transaction or continue with the

payment, this dialog box displays three payment options: cash, credit/debit card, and GCash.

After choosing a payment, a Notice window confirming the successful completion of the

transaction is shown. The confirmation is closed and the interface is returned with the "Payment

Successful" message and a "Done" button.

46
 Figure 29. Sales History

Figure 29 display the Food Hub Garden Sales and Inventory System interface in the

transaction section with an active alert. Key metrics, including Total Sales (1100) and Total

Customer (24), are visible, along with a line graph for sales revenue trends. The sales history

table shows transaction details, but an alert pop-up overlays the interface, stating no sales

transaction found. The pop-up includes a Back button, while the background interface remains

dimmed, drawing attention to the notification.

47
 Figure 30. Inventory Management

Figure 30 shows the user interface design for a Food Hub Garden Sales and Inventory

System. The interface is divided into several functional sections, including current stocks, out-of-

stock, and stock cost panels for managing inventory. On the left, there is an add/update Products

section with input fields for Product Name, Category, Quantity, and Price, along with buttons to

Add, Update, or Remove items. To the right, an available stocks table displays product details

such as product ID, product name, category, quantity, and price. A dropdown filter labeled all

categories and a search bar are provided for easy navigation. The design also includes a comment

overlay and basic navigation tabs like Home, Inventory, View Data, Profile, and Logout, making

it an organized and user-friendly system for inventory management.

48
 Figure 31. Add Product

Figure 31 illustrates the Food Hub Garden Sales and Inventory System's Inventory

module. The ADD/UPDATE PRODUCTS area below lets users enter product information such

Product Name, Category, Quantity, and Price. It also has buttons to Add, Update, and Remove

products to help with inventory management. In the first stage, if you added a product, a

49
confirmation dialog box with the options Yes and No will show up and ask, "Do you want to

save added product?" The second step displays a notification that reads, "Product Saved

Successfully!" and an OK button to end the message after confirmation. When adding products

to the inventory system, this flow guarantees a straightforward and effective procedure.

Figure 32. Remove Product

Figure 32 present that users can manually delete products with zero stock using the delete

Out-of-Stock option in the inventory system interface, which keeps the product list current and

correct. Customers can keep a clear picture of the products that are available, inventory

management is made easier, and product listings are less cluttered thanks to this functionality.

50
 Figure 33. Inventory Report

Figure 33 represent the overall report of inventory data within the business using charts.

It can be monthly, weekly or daily performance report of the business.

51
 Figure 34. Sales Report

Figure 34 shows all the sales transactions within the company; it may vary on daily,

weekly, and monthly revenue. It also shows the best-selling product on ranking, which it can use

to make decision-making. This type of report can show trends that impact sales operations. There

is also visual graphic and chart to easily understand the data.

52
 Figure 35. Export Report

Figure 35 demonstrates that the user allows to export the report, and the export format

will appear, such as PDF, Word, or Excel. Upon choosing the format, there will be a

53
confirmation button. After that, the “Report Export Successfully” will show, and you may click

the “Ok” button to end the task.

References

54
Hassoun, A., Jagtap, S., Garcia-Garcia G. et al., Food quality 4.0: From traditional approaches to

digitalized automated analysis, Journal of Food Engineering (2022)

https://doi.org/10.1016/j.jfoodeng.2022.111216

Sneh Chavan, & S. D. Bhoite (2024). Cloud-Powered Retail Management Study: Elevating

Business Operations with Cloud based POS Solutions over In-house POS. CSIBER International

Journal, Vol. 2 https://www.siberindia.edu.in/journals/

Asrani, H., Vishwakarma, S., Asrani, D., & Asrani, K. (2024). Point of Sale Systems.

International Journal of Innovative Research in Computer Science & Technology (IJIRCST),

12(1), 358-364.

https://doi.org/10.55524/CSISTW.2024.12.1.63

Waghmare, N., & Chavan, S. (2020). A conceptual study of P.O.S. (Point of Sale) system,

improving profitability of Food & Beverage Department in a restaurant. International Journal of

Creative Research Thoughts (IJCRT), 8(6), 3350. https://www.ijcrt.org

Khalid, S., & Mand, N. (2022). Point of Sale System. Department of Computer Science,

Government Degree College Wari (Dir Upper), Khyber Pakhtunkhwa, Pakistan. Retrieved from

https://ssrn.com/abstract=4368998

55
56