BEST
Journal of Applied Electrical & Science Technology Ae University of PGRI Adi Buana Surabaya p-ISSN 2715-2871 e-ISSN 2714-5247 Design and Construction of a Pharmacy Sales Information System (Case Study: Hero Farma Pharmac.
Sanggita Erinne Widyastami Suwito Faculty of Computer Science Duta Bangsa University Surakarta.
Indonesia sanggita82@gmail.
Agustina Srirahayu Faculty of Computer Science Duta Bangsa University Surakarta.
Indonesia agustina@udb.
Abstract Ai Hero Farma Pharmacy in Boyolali serves more than 40 daily transactions, but still uses manual recording through Microsoft Excel which is prone to human error , data duplication, and delays in reporting.
This study aims to design and build a web-based sales information system to improve the efficiency and accuracy of pharmacy operations.
The research method used is waterfall, which includes needs analysis through interviews and observations, system design using UML, implementation with Laravel 10 and React.
js integrated through Inertia.
js, and testing using the blackbox testing The implementation results show that the system was successfully built with a structured database.
Blackbox testing on 8 main functions and system performance testing.
This web-based information system is proven to be able to replace manual Excel processes , minimize recording errors, increase operational efficiency, and support better managerial decisions to support pharmacy performance.
KeywordsAiinformation systems, pharmacy, sales.
Laravel.
React.
Inertia.
js, blackbox testing INTRODUCTION Hero Farma Pharmacy, located in Boyolali.
Central Java, serves more than 40 daily sales transactions and collaborates with more than 10 drug However, the process of recording transactions, managing stock, and generating sales reports is still done manually using Microsoft Excel by the admin or pharmacist.
The reports are then sent to the pharmacy manager or owner .
This manual approach is prone to human error, such as data duplication and inaccurate recording .
Furthermore, daily reports take up to several hours each day to create, and monthly reports take an additional one to two days.
This situation directly impacts operational efficiency and delays the managerial decision-making process .
A similar situation was also found in previous research .
, which stated that the use of Excel in drug stock management is prone to data inconsistencies and reporting delays.
Fatkhurochman and Nusa Persada .
added that manual systems are unable to support the real-time transaction needs of the pharmacy Several previous studies have shown that implementing a web-based information system can be a solution to these obstacles.
Rahmadani and Harris.
stated that a web-based information system can improve Nibras Faiq Muhammad Faculty of Computer Science Duta Bangsa University Surakarta.
Indonesia nibras_faiqmuhammad@udb.
transaction recording accuracy and facilitate real-time stock monitoring.
Research by Sasongko et al.
also demonstrated the success of an integrated sales system in managing stock data and financial reports at the Central Farma Tayan Pharmacy.
Furthermore, several other studies concluded that digital systems expedite the recording process and improve the quality of customer service .
flexible information systems that support realtime needs , the Laravel-Inertia approach is considered Inertia.
js, w h e n combined with Laravel, simplifies communication between server-side and modern front-end frameworks.
This integration eliminates the need to create separate APIs, thereby speeding up the development cycle and providing a seamless user experience .
This research aims to design and develop a webbased sales information system and financial reports at Hero Farma Pharmacy.
This system is expected to improve operational efficiency and data recording accuracy, as well as minimize manual recording errors through real-time access .
The web platform was chosen because it does not require additional installation and can be accessed through various devices .
System data is managed using MySQL, with the user interface built using React.
js for interactive displays .
, and Laravel as the backend with a ModelView-Controller (MVC) pattern and routing features.
System development follows a systematic waterfall approach and is appropriate for the specified needs .
II.
METHODS
This research applies several methods to support success in designing and developing a pharmacy sales information system, as explained in the following section:
Method of collecting data Data collection methods are used to obtain data relevant to the research problem.
The data collection techniques applied include:
Primary data was obtained directly from research subjects through interviews and field observations at Hero Farma Pharmacy.
In-depth interviews and observations were conducted with the pharmacy staff to empirically identify problems .
Secondary data, obtained through literature studies from various supporting sources, such as 80iC BEST.
Vol.
No.
02, 2025
BEST
Journal of Applied Electrical & Science Technology Ae University of PGRI Adi Buana Surabaya p-ISSN 2715-2871 e-ISSN 2714-5247 scientific journals, articles, and other literature studies related to information systems, pharmacy System Development Methods This research uses the Waterfall system development method, which was chosen because it has a structured and easily controlled workflow .
This method consists of five stages:
System Requirements Analysis This stage involves identifying and gathering observations, and literature review.
The needs analysis is conducted using the PIECES (Performance.
Information.
Economy.
Control.
Efficiency.
Service.
approach to evaluate the weaknesses of the current manual system and detail the requirements of the system to be both functionally and nonfunctionally.
This stage is the result of observing business processes and will be tailored to user requirements .
System Design At this stage, the system is designed using the Unified Modeling Language (UML).
The design includes use case diagrams and activity diagrams to visualize the system flow of key features such as product management, sales transactions, and Implementation The system was developed as a web-based The Laravel framework served as the backend , while React.
js served as the frontend .
Both were integrated using Inertia.
js, with the database managed using MySQL.
This approach enabled an interactive, responsive, and structured Testing Testing was conducted using the Black Box Testing method, which aims to ensure that system functions operate according to specifications without the need to review the program code.
The techniques used include equivalence partitioning.
and boundary value analysis , which have proven effective in detecting errors and have been used in various information systems studies .
addition, quantitative system performance testing was also conducted to evaluate the results of system implementation on pharmacy operational Maintenance The maintenance phase is carried out after the system is implemented, including bug fixes , system adjustments based on user feedback, feature updates as needed, and performance monitoring to ensure the system remains optimal and relevant.
RESULTS AND DISCUSSION
From the results of the research on the Hero Farma Pharmacy sales information system, namely:
System Requirements Analysis A system requirements analysis was conducted using the PIECES (Performance.
Information.
Economy.
Control.
Efficiency.
Service.
approach to identify weaknesses in the manual system previously used at Hero Farma Pharmacy .
Data were collected admin/pharmacists, and warehouse employees, as well as direct observation of the sales process, stock management, and transaction reports.
Parameter Performance Information Economy Control Efficiency Services Table 1PIECES Analysis Old System The process of transactions and is slow because it has to be input manually in Excel and there is often duplication or incorrect data Stock information and sales reports It takes more time to summarize data, correct errors.
There are no access rights settings, so changed without activity logs.
Recording reporting takes a long time and is prone to human Customer service is slow due to long transaction times.
receipts are often written manually.
New System Fast and automatic Stock information and sales reports are always updated accessed in realtime.
Save time, paper costs, and reduce recording errors.
There are access rights for users .
dmin, warehouse, owne.
transaction activity control and stock Automatic reporting process, easy to operate system, supports faster audit and Faster more accurate drug System Design The system design was carried out using the UML ( Unified Modeling Language ) method to visualize functional requirements, activity flows, and system UML was chosen because it can visualize actor-system interactions, business processes, and 81iC BEST.
Vol.
No.
02, 2025
BEST
Journal of Applied Electrical & Science Technology Ae University of PGRI Adi Buana Surabaya p-ISSN 2715-2871 e-ISSN 2714-5247 entity relationships in an organized and easy-tounderstand manner .
The diagrams used include:
Use Case Use case diagrams are used to describe the relationship between actors .
dmin/pharmacists, warehouse employees, and owner.
with general system functionality, such as managing products, conducting transactions, and accessing reports.
database and presents the user with a list of The system then displays the complete product list.
Activity Diagram Manage Product Data Figure 3Activity Diagram Manage Product Data Figure 1Use Case Diagram .
Activity Diagram Activity diagrams are used to visualize the workflow sequence of an activity involving interactions between actors and features within a This facilitates understanding of the system's workflow.
Activity Diagram View Product Data In this process, the user logs in to the system and then selects a menu to manage products.
The user can choose the Create.
Edit, or Delete action If the user selects create, the user inputs new product data and the system saves it to the If the user selects edit, the user selects a product, changes the data, and then the system updates the database .
If the user deletes , the user selects a product and confirms the deletion, and then the system deletes the product from the .
Sales Transaction Activity Diagram Figure 2Activity Diagram View Product Data In the activity diagram , the actor or user first logs into the system.
After successfully logging in , the user selects a menu to view product data.
The system then retrieves product data from the 82iC BEST.
Vol.
No.
02, 2025
BEST
Journal of Applied Electrical & Science Technology Ae University of PGRI Adi Buana Surabaya p-ISSN 2715-2871 e-ISSN 2714-5247 Figure 4Activity Diagram Sales Transaction In this activity diagram , the user logs into the After successfully logging in , the user selects the transaction/POS menu.
The user enters product and customer data.
The system then calculates the total transaction, saves the transaction data to the database, and asks if a receipt is desired.
If so, the system creates a receipt and sends it to the printer.
Finally, the system displays a completion or success message.
Activity Diagram View Report Figure 5Activity Diagram View Report For this process, the user logs in and then selects the report menu.
The user selects the reporting timeframe, whether weekly, monthly, or yearly.
The system then retrieves the report data, displays it on the screen, and provides the option to export the report in PDF or Excel format .
If exported, the system provides a download link.
The system then displays a success .
Class Diagram Class diagrams are used to represent data structures and relationships between entities in a system in an organized manner.
The following is an illustration of a class diagram for a pharmacy sales information 83iC BEST.
Vol.
No.
02, 2025
BEST
Journal of Applied Electrical & Science Technology Ae University of PGRI Adi Buana Surabaya p-ISSN 2715-2871 e-ISSN 2714-5247 Figure 8Dashboard Page Displays a summary of key data such as total products, low inventory, daily sales, and revenue.
30-day sales graph is available to monitor sales trends, as well as a list of recent transactions.
There's also a navigation menu to product, category, supplier , report, and POS pages.
Product Page Figure 9Product Page Figure 6Class Diagram Implementation Login Page The product page displays a complete list of pharmacy products with categories, stock, status, and action options .
Search, filter , and add product buttons are available for entering new products.
Transaction Page Figure 7Login Page Users are required to enter an email and password that corresponds to their respective access rights to be able to enter the system.
Dashboard Page Figure 10Transaction Page The transaction/POS page displays a list of products, a shopping cart, payment details, payment method options, and a save button .
Sales Report Download 84iC BEST.
Vol.
No.
02, 2025
BEST
Journal of Applied Electrical & Science Technology Ae University of PGRI Adi Buana Surabaya p-ISSN 2715-2871 e-ISSN 2714-5247 Table 1Product Data Entry Page Test Case Add product with valid data Input Fill in all The entered does the column Columns are not all filled Add products by inappropriate data Figure 11Sales Report Download The downloaded sales report displays a sales summary, such as total sales, number of transactions, number of items sold, and best-selling products, as well as the average transaction.
During the development process, technical challenges were encountered in the integration between Laravel and Inertia.
js, particularly with data synchronization between components.
These issues were resolved through adjustments to state management and prop structure documentation.
For users, brief training was required, as the transition from a manual system to a web-based system required The scientific contribution of this research lies in the use of modern technology in a pharmaceutical information system.
The Laravel-Inertia-React approach, rarely used in pharmacy systems, demonstrated higher efficiency, a more interactive interface, and supported more real-time business The system performance evaluation also provided quantitative evidence of performance improvements, which can serve as a benchmark for the development of similar systems in the healthcare Testing Blackbox Testing Blackbox testing method in this study uses equivalence partitioning and boundary value analysis techniques to verify the functions of the Hero Farma Pharmacy sales information system.
Add products with empty columns Test Case Show product list Input Search valid keywords Keywords are according to the data The keyword Search don't exist Login with empty Login with blank Login incorrect data Expected Output Login successful.
Displays AuUsername Ay Displays AuPassword requiredAy Displays message AuLogin failedAy Displays Success Displays requiredAy Auall Success Expected Output Showing Displaying the searched product Status Success Displays AuProduct foundAy Success Success Table 3Product Page Updates Test Case Update with valid data Update product by filling in incorrect Update with empty columns Input Fill in all The entered does the column Columns are not all filled Expected Output Product data has Displays Status Success Displays requiredAy Auall Success Expected Output Product Status Success Success Table 4Delete Product Test Case Delete Product Input Table 2 Login Page Testing Input Username & Password according to Username is password is Username is password is Incorrect Username & Password Status Success Table 2Read Product Page Test Case Login with valid Expected Output Product added Table 5Transaction Page Status Success Test Case Normal Sales Transaction Success Success Success Transactions with quantity exceeding Transactions without selecting a Input All Data filled in exceeds Empty Expected Output Transaction successful, stock receipt printed Displays Auinsufficient stockAy Displays Auselected product does not existAy Status Success Success Success Table 6Report page Test Case Input Expected Output Status 85iC BEST.
Vol.
No.
02, 2025
BEST
Journal of Applied Electrical & Science Technology Ae University of PGRI Adi Buana Surabaya p-ISSN 2715-2871 e-ISSN 2714-5247 Reports can only be owner/manager Download PDF and Excel reports The report page does not appear if it is not owner/leader PDF and Excel files Success Success Input Monthly sales chart Expected Output Displays Displays chart per month Status Success Success System Performance Testing System performance testing was conducted to evaluate the effectiveness of the sales information system on pharmacy operational efficiency and This testing was conducted using a quantitative approach, comparing conditions before and after the implementation of the web-based system.
Table 9 System Performance Testing Parameter Average time per Daily report Duration of Recording error rate Maximum number of services per Percentage of pending Before the System (Exce.
After System (Web-base.
Change (%) A 2 minutes Faster A A 2 hours A 15 minutes Faster A A 5 hours A 30 minutes Faster A A 10 Ae 15% per A 1% Accuracy A 90% 10 Ae 12 20 Ae 30 A 5 minutes Regularly check the server and network Fix existing bugs or errors.
Regular hardware checks to keep the system running IV.
Table 7Dashboard Page Test Case Dashboard view Based on the research results, the sales information system developed for Hero Farma Pharmacy is able to replace the previous manual system that was slow and prone to errors with a web-based system that is automated, fast, and controlled.
The application of the PIECES analysis method and system design using Unified Modeling Language (UML) showed significant improvements in operational time efficiency, transaction speed, stock data accuracy, and strengthened security through user access rights management.
The implementation of features such as dashboards, product management.
Point of Sale (POS) transactions, and realtime reporting has been proven to support pharmacy business processes more effectively.
The results of blackbox testing ensured that all functions run as needed, while system performance testing showed a significant increase in operational efficiency and accuracy.
Therefore, routine system maintenance is still necessary to ensure the system remains optimal and relevant to the development of pharmacy needs in the future.
REFERENCES