Abdul Ahad Doc group 10

Retail & Distribution Management System Supervisor Muhammad Abid Khan Submitted by Muhammad Yousuf Lodhi OST/2/02959/M/BSCS/2021-1 Abdullah Fateh Syed Saif-ur-Rehman OST/2/04691/M/BSCS/2021-1 OST/2/02969/M/BSCS/2021-1 Abdul Ahad OST/2/02976/M/BSCS/2021-1 Department of Computer Science Federal Urdu University of Arts, Sciences and Technology Karachi, Sindh, Pakistan. ©2026.

Federal Urdu University of Arts, Science Technology, Karachi FYP SUBMISSION FORM Muhammad Yousuf Lodhi (OST/2/02959/M/BSCS/2021-1), Abdullah Fateh (OST/2/04691/M/BSCS/2021-1), Syed Saif-ur-Rehman (OST/2/02969/M/BSCS/2021-1), and Abdul Ahad (OST/2/02976/M/BSCS/2021-1), enrolled in BSCS at Department of Computer Science, Federal Urdu University of Arts, Science & Technology, Karachi, do herebydeclare that the project entitled “ResellerCenter PK ERP: A Cloud-Based Multi-Business Retail and Distribution Management System” submitted by us in partial fulfillment of Bscs degree, is my original work, and has not been submitted earlier. I also solemnly declare that it shall not, in future, be submitted by me for obtaining any other degree from this or any other university or institution. The work presented in this report represents our genuine effort and understanding of software engineering principles, database design, web application development, and enterprise resource planning systems. All external sources, ideas, and assistance have been properly acknowledged and cited throughout the document. Student Name : Muhammad Yousuf Lodhi Signature:______________ Student Name : Abdullah Fateh Signature:______________ Student Name : Syed Saif-ur-Rehman Signature:______________ Student Name : Abdul Ahad Signature:______________ Supervisor Declaration I, Muhammad Abid Khan, hereby certify that the Final Year Project (FYP) report prepared under my supervision by, titled ResellerCenter PK ERP: A Cloud-Based Multi-Business Retail and Distribution Management System, has been completed in all respects. The work presented in this project is the student’s bona fide effort. I recommend that this FYP report be accepted in partial fulfillment of the requirements for the award of the BSCS degree. ___________________ Muhammad Abid Khan FYP Supervisor.

ACKNOWLEDGEMENT All praise and gratitude are due to Almighty Allah, the Most Merciful and Most Compassionate, for granting us the strength, patience, and perseverance to complete this final year project successfully. Without His countless blessings and guidance, the completion of this challenging endeavor would not have been possible. We would like to express our deepest and most heartfelt gratitude to our project supervisor, whose unwavering guidance, insightful feedback, and consistent encouragement have been instrumental throughout every phase of this project. His dedication to mentoring us, his ability to simplify complex concepts, and his willingness to make time for our questions played a pivotal role in shaping our understanding and strengthening the quality of our work. Every discussion with him offered new clarity and direction, particularly during challenging phases when technical obstacles seemed overwhelming. We are sincerely grateful for his patience, professionalism, and commitment to ensuring that we not only completed the project but also learned valuable lessons that will benefit our future professional careers. We extend our sincere appreciation to the Department of Computer Science at Federal Urdu University for providing the academic environment, technical facilities, and essential resources that made this project possible. The availability of well-equipped computer laboratories, access to development tools and software, reliable internet connectivity, and library resources empowered us to explore ideas more freely and execute our work more effectively. The department’s commitment to fostering practical learning, research orientation, and innovation created a strong foundation for our academic journey and prepared us well for addressing real-world software engineering challenges. Our gratitude further goes to the faculty members who taught us throughout our undergraduate program. The knowledge and skills imparted through courses in database management systems, software engineering, web technologies, object-oriented programming, data structures and algorithms, and project management equipped us with the technical competencies necessary to conceptualize and implement this comprehensive enterprise resource planning system. The theoretical foundations and practical laboratory sessions prepared us well for undertaking a substantial software development project of this magnitude. We are deeply grateful to our families for their unconditional love, prayers, continuous moral support, and unwavering belief in our abilities throughout our academic journey. Their sacrifices, encouragement during difficult times, and patience during the demanding phases of project development enabled us to dedicate the necessary time and effort to complete this work with quality and dedication. Their constant motivation served as a source of strength and inspiration, helping us overcome obstacles and maintain focus on our goals. We also acknowledge our classmates, peers, and friends whose constant encouragement, constructive conversations, and mutual support were invaluable during the development process. Whether through collaborative brainstorming sessions, shared challenges, technical discussions, or simple words of motivation, their presence contributed meaningfully to our progress and kept us focused and inspired. The collaborative learning environment among peers enriched our understanding and exposed us to diverse perspectives on problem-solving approaches. Finally, we express our appreciation to the small business owners and retail operators who informally shared their operational challenges and requirements during our initial research phase. Their insights into inventory management difficulties, billing inefficiencies, and financial tracking needs helped us understand the practical problems that motivated this project and guided our design decisions to ensure the system addresses genuine business needs. Each of these contributions, whether large or small, played an essential role in shaping the direction, depth, and overall quality of this project. We are grateful to all who supported us on this journey. Muhammad Yousuf Lodhi, Abdullah Fateh Syed, Saif-ur-Rehman, Abdul Ahad.

ABSTRACT Small and medium retail businesses, wholesalers, and resellers in Pakistan routinely face operational challenges arising from fragmented management of core business processes including inventory control, purchase ordering, sales billing, customer relationship management, supplier coordination, and financial accounting. The absence of integrated systems forces business owners to rely on manual record-keeping, disconnected spreadsheets, or basic point-of-sale terminals that lack comprehensive business intelligence capabilities. This fragmentation leads to inventory discrepancies, delayed decision-making due to lack of real-time visibility, difficulty in tracking profitability across product lines, and operational inefficiencies that constrain business growth potential. Traditional enterprise resource planning systems designed for large corporations often prove too expensive, complex, or feature- heavy for small and medium enterprises, creating a significant gap between available solutions and the actual needs of this important business segment. This project addresses these challenges through the design, development, and implementation of ResellerCenter PK ERP, a comprehensive web-based enterprise resource planning platform specifically engineered to serve the operational requirements of small and medium retail, wholesale, and distribution businesses. The system integrates multiple critical business functions into a unified online platform accessible through standard web browsers, eliminating the need for expensive local infrastructure or specialized software installations. Core functionalities implemented include point-of-sale billing with invoice generation for walk-in and registered customers, real-time inventory tracking with automated stock level updates and low-stock alerts, purchase order management for supplier procurement with goods receipt workflows, customer account management maintaining transaction histories and contact details, supplier relationship management tracking payment terms and order histories, expense recording and categorization for operational cost tracking, comprehensive financial reporting including profit and loss statements and sales analytics, multi-user access control supporting differentiated roles such as administrators, managers, and cashiers with appropriate permission levels, and centralized dashboard analytics providing real-time business intelligence through visualizations of key performance indicators. The technical architecture follows a three-tier model comprising a presentation layer implementing responsive user interfaces accessible across desktop and mobile devices, an application layer containing business logic implemented through server-side scripting using PHP programming language, and a data persistence layer utilizing a relational database management system for structured storage of all business entities including products, transactions, customers, suppliers, and financial records. The system design emphasizes modularity, maintainability, and scalability to accommodate growing product catalogs, increasing transaction volumes, and expanding user bases as businesses grow. Security implementations include password-based authentication with cryptographic hashing, session management maintaining secure user states, role-based access control restricting functionality based on user privileges, input validation protecting against common web vulnerabilities, and audit trail logging recording critical business operations for accountability and compliance purposes. The development methodology adopted was the Agile Scrum framework, which facilitated iterative development cycles organized into focused sprints addressing specific functional modules. This approach enabled continuous requirement refinement, regular supervisor feedback incorporation, adaptive response to emerging technical challenges, and incremental delivery of working functionality. Requirements were gathered through analysis of typical retail business workflows, examination of common operational pain points reported by small business owners, and consideration of specific characteristics of the Pakistani retail market including prevalent business practices, preferred transaction methods, and regulatory considerations. Testing procedures encompassed unit testing of individual functions and database operations, integration testing verifying correct interactions between modules such as billing and inventory updates, system testing validating complete business workflows from purchase receipt through sales and financial reporting, and informal user acceptance testing gathering feedback from individuals familiar with retail operations..

The system successfully demonstrates integration of essential enterprise resource planning capabilities within an accessible web-based platform specifically designed for the resource constraints and operational contexts of small and medium businesses. Key achievements include accurate real-time inventory tracking with automatic updates triggered by purchase receipts and sales transactions, comprehensive billing functionality supporting various customer types and payment methods, financial reporting providing actionable insights into profitability and sales trends, multi-user capability allowing business owners to delegate responsibilities while maintaining control through permission management, and responsive interface design ensuring usability across different devices and screen sizes. Evaluation focused on functional correctness of business logic, accuracy of financial calculations and inventory tracking, usability of interfaces for users with varying technical proficiency, and system reliability under typical operational scenarios. Design considerations addressed practical deployment constraints including compatibility with shared web hosting environments commonly used by small businesses in Pakistan for cost-effectiveness, minimal infrastructure requirements beyond standard web hosting with database support, straightforward deployment procedures not requiring specialized technical expertise, and reasonable performance characteristics for typical transaction volumes experienced by target businesses. The system demonstrates that well-designed web-based enterprise resource planning solutions can significantly reduce operational burdens, improve business visibility, and support data-driven decision-making for small and medium enterprises without requiring substantial financial investments or technical expertise. Future enhancement opportunities identified include mobile application development for native smartphone access supporting on-the-go inventory checks and sales entry, integration of online payment gateways enabling digital transaction processing, implementation of artificial intelligence techniques for demand forecasting and inventory optimization, development of e-commerce interfaces allowing businesses to extend sales channels beyond physical locations, barcode scanning integration for faster product identification and transaction processing, advanced analytics incorporating predictive modeling and trend analysis, and multi-location support for businesses operating from multiple branches or warehouses. This project contributes to the understanding of enterprise resource planning system development for small business contexts and demonstrates practical application of software engineering principles in creating solutions addressing genuine operational challenges in developing market environments. Keywords: Enterprise Resource Planning, Point of Sale System, Inventory Management, Retail Management, Web Application Development, Business Intelligence, Multi-User System, Financial Reporting, Three-Tier Architecture, Small Business Solutions Note: Figures represent placeholders for system diagrams including use case diagrams, activity diagrams, sequence diagrams, class diagrams, entity relationship diagrams, system architecture illustrations, and user interface screenshots. Actual diagrams would be inserted during document finalization with appropriate numbering and captions..

Table of Contents Declaration i Supervisor Approval Certificate iii Acknowledgement iv Abstract v 1 INTRODUCTION 1 1.1 Introduction 1 1.2 Problem Statement 2 1.3 Proposed Solution 3 1.4 Background 4 1.5 Motivation 6 1.6 Aim and Objectives 7 1.7 Scope of the Project 9 1.7.1 In-Scope Functionalities 9 1.7.2 Out-of-Scope Elements 10 1.8 Deliverables and Operational Rules 11 1.8.1 Operational Rules and Business Logic 12 1.9 Technologies Used 13 1.9.1 Web Technologies and Frameworks 13 1.9.2 Database Management System 14 1.9.3 Development Tools and Environment 15 1.9.4 Deployment and Hosting Infrastructure 15 2 LITERATURE REVIEW 17 2.1 Introduction 17 2.2 Overview of Enterprise Resource Planning Systems 17.

2.3 Small Business Management Systems 18 2.4 Cloud Computing and Software-as-a-Service Models 19 2.5 Database Design and Management 20 2.6 User Interface Design and Usability 21 2.7 Software Development Methodologies 21 2.8 Limitations of Existing Systems 22 2.9 Research Gap and Justification 23 3 METHODOLOGY 25 3.1 Introduction 25 3.2 Software Development Life Cycle Model Selection 25 3.2.1 Justification for Agile Scrum Selection 25 3.2.2 Scrum Implementation Approach 27 3.3 Requirements Gathering 28 3.3.1 Stakeholder Interviews 28 3.3.2 Observational Studies 29 3.3.3 Analysis of Existing Systems 29 3.3.4 Requirements Documentation 30 3.4 Software Requirement Specification 30 3.4.1 Functional Requirements Specification 31 3.4.2 Non-Functional Requirements Specification 32 3.5 Algorithms and Core Business Logic 33 3.5.1 Sales Transaction Processing Algorithm 33 3.5.2 Inventory Update Algorithm 34 3.5.3 Financial Calculation Algorithms 35 3.5.4 Report Generation Algorithm 36 3.6 Database Design Approach 36 3.6.1 Conceptual Data Modeling 36.

3.6.2 Logical Data Modeling and Normalization 37 3.6.3 Physical Database Implementation 38 3.7 Tools and Development Environment 39 4 SYSTEM DESIGN 41 4.1 Introduction 41 4.2 Overall System Architecture 41 4.2.1 Presentation Tier 41 4.2.2 Application Tier 42 4.2.3 Data Tier 43 4.3 User Roles and Permission Hierarchy 44 4.3.1 Administrator Role 44 4.3.2 Manager Role 44 4.3.3 Cashier Role 45 4.3.4 Permission Enforcement Mechanism 45 4.4 Unified Modeling Language Diagrams 46 4.4.1 Use Case Diagram 46 4.4.2 Activity Diagram 47 4.4.3 Sequence Diagram 48 4.4.4 Class Diagram 49 4.5 Database Entity Relationship Diagram 50 5 IMPLEMENTATION 53 5.1 Introduction 53 5.2 Module-Wise Implementation 53 5.2.1 Sales Module 53 5.2.2 Purchase Module 55 5.2.3 Inventory Module 56.

5.2.4 Accounts Module 57 5.2.5 Reporting Module 58 5.2.6 User Management Module 59 5.3 Interface Design and User Experience 60 5.3.1 Layout and Navigation 60 5.3.2 Forms and Input Validation 61 5.3.3 Feedback and Messaging 62 5.4 Security and Authentication 63 5.4.1 Authentication Mechanisms 63 5.4.2 Authorization and Access Control 63 5.4.3 Input Validation and SQL Injection Preventio 64 5.4.4 HTTPS and Data Encryption 65 5.5 Validation and Error Handling 65 5.5.1 Client-Side Validation 66 5.5.2 Server-Side Validation 66 5.5.3 Database Constraints 67 5.5.4 Error Handling Strategies 67 6 TESTING 69 6.1 Introduction 69 6.2 Testing Strategy 69 6.3 Unit Testing 70 List of Figures.

ABBREVIATIONS AND NOMENCLATURE API Application Programming Interface CRUD Create, Read, Update, Delete CSS Cascading Style Sheets DB Database ERP Enterprise Resource Planning HTML Hypertext Markup Language HTTP Hypertext Transfer Protocol HTTPS Hypertext Transfer Protocol Secure ID Identifier (Primary Key) JS JavaScript MVC Model View Controller ORM Object Relational Mapping PHP Hypertext Preprocessor (Server-side scripting language) POS Point of Sale RBAC Role-Based Access Control REST Representational State Transfer SDLC Software Development Life Cycle SKU Stock Keeping Unit SME Small and Medium Enterprise SQL Structured Query Language UI User Interface UML Unified Modeling Language URL Uniform Resource Locator UX User Experience XSS Cross-Site Scripting.

PROJECT OBJECTIVES Motivation Small and medium retail businesses, wholesalers, and resellers operating in Pakistan face persistent operational challenges that constrain their efficiency, profitability, and growth potential. These businesses typically manage core functions including inventory control, purchase ordering, sales billing, customer relationships, supplier coordination, and financial accounting through manual methods or disconnected systems that lack integration. Inventory tracking often relies on manual counting and paper-based record-keeping, leading to frequent discrepancies between recorded stock levels and actual physical inventory. Sales transactions are recorded using basic cash registers or simple point- of-sale terminals that capture individual transactions but fail to provide integrated views of business performance or automatically update inventory positions. Purchase orders and supplier management occur through informal communications and scattered documentation, making it difficult to track pending orders, manage supplier payment terms, or analyze procurement costs systematically. Customer relationship management remains rudimentary with contact information and purchase histories maintained in notebooks or basic spreadsheets that cannot be easily searched or analyzed. Financial accounting involves manual calculation of revenues, expenses, and profitability, often performed retrospectively at month-end or quarter-end when timely corrective actions are no longer possible. Business owners lack real-time visibility into key performance indicators such as current stock positions, daily sales trends, fast-moving and slow-moving products, outstanding supplier payments, customer purchase patterns, and overall profitability across product categories. This absence of integrated, real-time business intelligence severely hampers decision-making capabilities and prevents businesses from identifying problems early or capitalizing on emerging opportunities promptly. The challenges are compounded when businesses grow beyond single-person operations and need to delegate responsibilities to employees. Without proper systems for role-based access control and audit trails, business owners find it difficult to grant appropriate access to managers or cashiers while maintaining oversight and preventing unauthorized actions. Training new employees becomes time-consuming as they must learn disparate processes scattered across different tools and manual procedures rather than working within a unified system with consistent interfaces and workflows. Existing enterprise resource planning systems designed for large corporations offer comprehensive functionality but prove unsuitable for small and medium enterprises due to high licensing costs that are prohibitive for businesses with limited budgets, excessive complexity with features and processes designed for large organizational structures that overwhelm small business operators, steep learning curves requiring extensive training and often specialized personnel to operate effectively, substantial infrastructure requirements including powerful servers and dedicated IT support that small businesses cannot afford, and lengthy implementation timelines spanning months with significant business disruption during transition periods. This gap between the sophisticated but expensive solutions designed for large enterprises and the basic but inadequate tools available to small businesses creates a significant opportunity for developing integrated enterprise resource planning solutions specifically tailored to the needs, constraints, and operational contexts of small and medium retail, wholesale, and distribution businesses in developing market environments like Pakistan. Desired Aims, Results, and Objectives The primary aim of this project is to design, develop, and deploy a comprehensive web-based enterprise resource planning platform that integrates essential business management functions into a unified, accessible system specifically engineered to serve the operational requirements and resource constraints of small and medium retail,.

wholesale, and distribution businesses. The specific objectives pursued to achieve this overarching aim include the following. The first objective involves conducting comprehensive requirements analysis to understand the operational workflows, pain points, and functional needs typical of small and medium retail businesses. This includes examining common business processes such as product procurement, inventory management, sales transactions, customer interactions, supplier relationships, and financial tracking. Requirements must address both functional capabilities specifying what the system should do and non-functional characteristics including performance expectations, usability criteria for users with varying technical proficiency, security standards protecting business data, and deployment constraints considering typical hosting environments accessible to small businesses. The second objective focuses on designing a scalable three-tier system architecture that separates concerns appropriately. The presentation tier implements user interfaces accessible through standard web browsers across desktop and mobile devices. The application tier contains business logic processing including transaction calculations, inventory updates, permission validations, and report generation implemented through server-side scripting. The data persistence tier utilizes a relational database management system storing all business entities with appropriate relationships, constraints, and indexes ensuring data integrity and query performance. The architecture must support modular development, facilitate independent testing of components, and enable future enhancements without requiring complete system redesign. The third objective involves developing a normalized relational database schema representing all critical business entities including products with specifications and pricing, inventory transactions recording receipts and issues, sales transactions capturing billing details, purchase orders tracking supplier procurement, customers with contact and transaction histories, suppliers with payment terms and order histories, expenses categorized by type and purpose, users with role-based permissions, and financial records supporting profit and loss calculations. The schema must enforce referential integrity through foreign key relationships, prevent data anomalies through appropriate normalization, support efficient querying through strategic indexing, and maintain audit trails for critical business operations. The fourth objective encompasses implementing comprehensive point-of-sale functionality enabling cashiers and sales staff to efficiently process customer transactions. This includes product selection through search and barcode scanning capabilities, quantity specification and price adjustments with proper authorization controls, invoice generation with automatic calculation of totals and taxes, support for various payment methods including cash, credit, and account-based sales, automatic inventory deduction upon sale confirmation, customer selection or walk- in transaction recording, and invoice printing or digital delivery. The implementation must ensure transactional integrity where all related operations succeed together or fail together, maintaining consistency between sales records and inventory positions. The fifth objective addresses inventory management functionality providing real-time visibility into stock positions. This includes maintaining current quantity on hand for each product, recording inventory transactions including purchases, sales, adjustments, and transfers, providing low-stock alerts identifying products approaching reorder thresholds, supporting inventory valuation using appropriate costing methods, enabling stock audits with variance reporting, and tracking product movement histories for analysis. The system must handle concurrent operations correctly, preventing overselling scenarios where multiple transactions attempt to draw from the same stock simultaneously. The sixth objective involves implementing purchase management workflows supporting supplier procurement processes. This includes creating purchase orders specifying products, quantities, prices, and delivery expectations, tracking order statuses through states such as pending, partial receipt, and completed, recording goods receipts updating inventory quantities and valuations, managing supplier information including contact details, payment terms, and transaction histories, tracking pending supplier payments and settlement records, and generating purchase.

analytics identifying procurement costs and supplier performance patterns. These capabilities enable businesses to manage procurement systematically rather than through informal communications and scattered documentation. The seventh objective focuses on customer relationship management functionality maintaining customer accounts and transaction histories. This includes registering customer information with contact details and address records, maintaining transaction histories showing all purchases with dates, amounts, and products ordered, supporting account-based sales with credit limits and payment terms, tracking receivables identifying outstanding customer balances and payment due dates, and providing customer analytics identifying high-value customers and purchase patterns. These capabilities enable businesses to build stronger customer relationships through better service and targeted marketing based on actual purchase behaviors. The eighth objective encompasses expense tracking and financial management capabilities. This includes recording business expenses categorized by type such as utilities, salaries, rent, marketing, and operational costs, tracking payment methods and dates for expense settlements, maintaining supplier payment records for procurement-related expenses, generating profit and loss statements calculating revenues, cost of goods sold, gross margins, operating expenses, and net profitability, and providing financial analytics showing trends over time and comparative analyses across periods. These capabilities provide business owners with clear financial visibility essential for informed decision-making and strategic planning. The ninth objective involves implementing multi-user access control with role-based permissions. This includes user authentication verifying credentials securely through password hashing, session management maintaining secure authenticated states across page navigations, role definition supporting categories such as administrators with full system access, managers with supervisory access to reports and configurations, and cashiers with access limited to sales transactions and basic customer interactions, permission enforcement restricting functionality based on assigned roles, and audit trail logging recording critical operations with user identification, timestamps, and operation details for accountability and compliance purposes. These capabilities enable business owners to delegate responsibilities safely while maintaining oversight and control. The tenth objective addresses dashboard and reporting functionality providing business intelligence through visualization and analysis. This includes real-time dashboard displays showing key performance indicators such as today’s sales, current inventory value, pending purchase orders, low-stock items, top-selling products, and recent transactions, sales reports with filtering by date ranges, product categories, customers, and payment methods, inventory reports showing current positions, movement histories, and valuation summaries, financial reports presenting profit and loss statements and expense breakdowns, and customer reports identifying purchasing patterns and outstanding balances. These reporting capabilities transform raw transactional data into actionable insights supporting strategic and operational decision-making. The eleventh objective involves implementing responsive user interface design ensuring usability across device types. This includes clean, intuitive layouts with logical information organization and clear navigation structures, consistent visual styling throughout the application promoting familiarity and reducing learning curves, responsive design adapting to various screen sizes from desktop monitors to tablet devices and smartphones, touch-friendly interface elements for mobile device interactions, appropriate text sizing and contrast for readability, and efficient use of screen space minimizing scrolling and navigation overhead. These design considerations ensure that the system remains accessible and usable for business owners and staff with varying levels of technical proficiency and across the diverse device landscape typical in developing markets. The twelfth objective encompasses comprehensive testing and quality assurance activities. This includes unit testing validating individual functions, database operations, and calculation logic in isolation, integration testing verifying correct interactions between modules such as coordination between billing, inventory updates, and financial recording, system testing confirming that complete business workflows function correctly from end to end, and informal user acceptance testing gathering feedback from individuals familiar with retail operations evaluating.

usability, completeness, and practical suitability. Testing must identify and resolve defects systematically, validate that implemented functionality meets specified requirements, and ensure system reliability under typical operational scenarios. The final objective involves system deployment and documentation. This includes deploying the application to web hosting infrastructure accessible via public internet, configuring server environments appropriately for security and performance, establishing database instances with backup procedures, preparing technical documentation describing system architecture, database schema, and implementation details, creating user documentation explaining operational procedures for different user roles, and providing deployment guidance for installation in target hosting environments. These deliverables ensure that the system can be effectively operated, maintained, and potentially enhanced in the future..

Chapter #1 INTRODUCTION 1.1 Introduction The landscape of retail and distribution businesses has undergone substantial transformation in recent decades, driven by technological advancements and evolving market dynamics. Small and medium enterprises operating in retail, wholesale, and distribution sectors face increasing pressure to streamline their operational processes, maintain accurate inventory records, track financial transactions with precision, and respond rapidly to market demands. Traditional business management practices, which often rely on manual documentation, spreadsheet- based calculations, and disconnected software tools, have proven insufficient in meeting these contemporary business requirements. Enterprise Resource Planning systems have emerged as comprehensive solutions designed to integrate various business functions into cohesive operational frameworks. These systems enable organizations to automate routine tasks, centralize data storage, facilitate information sharing across departments, and generate analytical reports for informed decision-making. However, many existing ERP solutions available in the market are either prohibitively expensive for small enterprises, excessively complex requiring extensive training, or lack customization capabilities to address specific industry needs. This project addresses these challenges by developing ResellerCenter PK ERP, a webbased enterprise resource planning system specifically tailored for small and medium businesses engaged in retail and distribution activities. The system aims to provide an affordable, user-friendly, and functionally comprehensive solution accessible through cloud infrastructure, eliminating the need for expensive hardware investments or complex installation procedures. By leveraging modern web technologies and database management systems, the platform offers real-time data synchronization, multi-user concurrent access, and cross-device compatibility. The motivation behind this project stems from observed inefficiencies in traditional business management approaches and the recognition of technology’s potential to transform operational workflows. Through systematic analysis of business requirements, careful system design, and iterative development processes, this project endeavors to contribute a practical solution that bridges the gap between sophisticated enterprise systems and the operational realities of small-scale businesses. 1.2 Problem Statement Small and medium enterprises in the retail and distribution sector encounter numerous operational challenges that impede their growth potential and competitive positioning. One of the primary difficulties is the lack of integrated systems for managing diverse business functions. Businesses typically employ separate tools or manual methods for handling sales transactions, maintaining inventory records, tracking supplier orders, managing customer accounts, and recording financial data. This fragmentation results in data inconsistency, duplication of effort, increased likelihood of human errors, and difficulty in obtaining comprehensive views of business performance. Inventory management presents another critical challenge. Businesses struggle to maintain accurate real-time visibility of stock levels, leading to situations where popular items run out of stock unexpectedly or excessive capital remains tied up in slow-moving inventory. Manual inventory tracking methods are labor-intensive, prone.

to recording errors, and unable to provide timely alerts when reorder points are reached. This inefficiency directly impacts customer satisfaction when orders cannot be fulfilled promptly and affects profitability through suboptimal inventory investment decisions. Point-of-sale operations in many small businesses remain paper-based or use basic calculator methods, making transaction processing slow and error-prone. The absence of automated billing systems means that sales data is not immediately reflected in inventory records, financial accounts, or customer purchase histories. This disconnection between sales transactions and backend systems creates significant reconciliation challenges at the end of business periods and makes it difficult for management to access real-time sales analytics. Financial management and reporting constitute another area of difficulty. Business owners and managers require timely access to financial metrics such as daily sales totals, profit margins, expense trends, and overall business profitability. However, when financial data resides across multiple ledgers, notebooks, or disconnected software applications, generating comprehensive financial reports becomes an arduous manual task requiring significant time and effort. This delay in accessing financial insights hampers responsive decision-making and strategic planning. Furthermore, businesses operating with multiple employees face challenges in implementing access control and maintaining data security. Without proper user management systems, there is risk of unauthorized access to sensitive financial information, potential for data tampering, and difficulty in establishing accountability for transactions and system changes. The absence of audit trails makes it challenging to investigate discrepancies or track the sequence of business events. The lack of scalability in traditional systems presents additional constraints as businesses grow. Adding new product lines, expanding to multiple locations, or increasing transaction volumes often requires completely redesigning existing workflows or adopting entirely new systems, resulting in business disruption and substantial migration costs. These limitations discourage business expansion and innovation. 1.3 Proposed Solution To address the multifaceted challenges outlined in the problem statement, this project proposes the development and implementation of ResellerCenter PK ERP, a comprehensive cloud-based enterprise resource planning system designed specifically for the operational requirements of retail and distribution businesses. The proposed solution integrates all critical business functions into a unified platform accessible through web browsers, eliminating the need for multiple disconnected systems and providing seamless data flow across operational domains. The core architecture of the proposed system follows a three-tier model comprising a presentation layer for user interaction, a business logic layer for processing operations and enforcing business rules, and a data persistence layer utilizing relational database management for structured storage and retrieval. This architectural approach ensures clear separation of concerns, facilitates independent module development and maintenance, and provides scalability to accommodate growing business needs. The point-of-sale module forms the operational heart of the system, enabling rapid transaction processing with barcode scanning support, automatic inventory deduction upon sale completion, real-time calculation of totals including applicable taxes, and immediate generation of customer invoices. Sales data captured through this module automatically updates inventory levels, customer purchase histories, and financial ledgers, ensuring data consistency across the system without manual intervention..

Inventory management capabilities provide comprehensive stock tracking functionality with features including product categorization, unit measurement definitions, reorder level configurations, and automatic low-stock alert generation. The system maintains detailed inventory transaction histories recording all stock movements whether through purchases, sales, or adjustments, enabling complete traceability and facilitating stock auditing processes. Dashboard visualizations present inventory status through graphical representations, allowing managers to quickly identify fast-moving products and optimize purchasing decisions. Purchase order management functionality streamlines the procurement process by enabling electronic creation of purchase orders, tracking order statuses from placement through receipt, recording supplier information and transaction histories, and managing supplier payment schedules. Integration between purchase and inventory modules ensures that received goods are automatically added to stock records with proper documentation of receipt dates, quantities, and associated costs. The customer relationship management component maintains comprehensive customer profiles including contact information, transaction histories, outstanding balances, and payment records. This functionality supports both cash transactions and credit sales, with the system automatically updating customer account balances and generating receivable reports. Businesses can utilize this information to identify valuable customers, extend appropriate credit limits, and personalize customer service approaches. Financial management modules provide robust expense tracking, payment recording, and financial reporting capabilities. The system classifies expenses into categories, tracks payment methods, and maintains chronological financial ledgers. Automated financial reports include daily sales summaries, profit and loss statements, expense breakdowns by category, and comparative analyses across time periods. These reports are generated on-demand with current data, eliminating the delays associated with manual financial compilation. User access control mechanisms implement role-based permission systems defining distinct privileges for administrators, managers, and operational staff. Administrators possess complete system access including user management, system configuration, and data backup capabilities. Managers can access reporting functions, perform inventory adjustments, and approve transactions within defined limits. Operational users such as cashiers have restricted access limited to transaction processing functions. This hierarchical access model ensures data security while maintaining operational efficiency. The cloud-based deployment model offers significant advantages including accessibility from any location with internet connectivity, elimination of local server infrastructure requirements, automatic backup and disaster recovery capabilities, and seamless software updates without client-side installations. The responsive design approach ensures optimal user experience across desktop computers, tablets, and mobile devices, accommodating diverse operational environments and user preferences. 1.4 Background Enterprise Resource Planning systems have evolved significantly since their conceptual origins in the 1960s when early material requirements planning systems were introduced for manufacturing inventory management. Over subsequent decades, these systems expanded in scope to encompass broader business functions including financial accounting, human resources, supply chain management, and customer relationship management. The term ”Enterprise Resource Planning” gained prominence in the 1990s as integrated business software packages became commercially available from major software vendors. Traditional ERP implementations were characterized by on-premises installations requiring substantial hardware infrastructure, lengthy implementation timelines spanning months or years, and significant financial investments often beyond the reach of small enterprises. These systems were predominantly targeted at large corporations.

with complex organizational structures and substantial IT departments capable of managing system administration and customization. The advent of cloud computing technologies and Software-as-a-Service delivery models in the early 21st century transformed the ERP landscape. Cloud-based ERP systems eliminated the need for local server infrastructure, reduced upfront capital expenditures through subscription-based pricing models, and accelerated implementation timelines. These developments made enterprise-grade business management systems accessible to smaller organizations previously unable to afford traditional ERP solutions. In Pakistan’s business context, small and medium enterprises constitute a significant portion of the economic landscape, particularly in retail and distribution sectors. These businesses have historically relied on manual record-keeping practices or basic computerization using spreadsheet software. While some businesses adopted standalone accounting software or inventory tracking applications, integrated systems specifically addressing the workflow requirements of Pakistani retail businesses remained scarce. Language barriers, cultural business practices, and cost constraints further limited the adoption of international ERP products. The retail sector in Pakistan has experienced substantial growth driven by urbanization, rising consumer spending, and increasing market competition. Modern retail formats including chain stores, supermarkets, and organized wholesale distribution networks have emerged alongside traditional small-shop retail operations. This diversification has created demand for management systems capable of handling varying business scales and operational complexities. Technological infrastructure development including widespread internet availability, affordable computing devices, and growing digital literacy has created favorable conditions for web-based business applications. The proliferation of smartphones and mobile internet access has particularly transformed how businesses interact with technology, creating expectations for accessible, user-friendly digital solutions. Previous academic research in enterprise systems has extensively documented the benefits of integrated business management platforms including improved operational efficiency, reduced data redundancy, enhanced decision- making through real-time analytics, and better regulatory compliance through systematic record-keeping. However, research specifically addressing ERP requirements of small Pakistani retail businesses and practical implementations tailored to this context remains limited. This project builds upon the theoretical foundations established in software engineering, database design, web application development, and business process management literature. It applies these principles to develop a practical system addressing identified gaps in available solutions for small and medium retail enterprises. The background understanding gained through literature review, market analysis, and stakeholder consultations informed the system requirements definition and guided design decisions throughout the development process. 1.5 Motivation The motivation for undertaking this project stems from multiple converging factors encompassing academic learning objectives, observed real-world business challenges, and the desire to create tangible value through application of acquired technical skills. Throughout our academic curriculum in computer science, we gained theoretical knowledge and practical competencies in software engineering methodologies, database management systems, web technologies, and systems analysis and design. The final year project presented an opportunity to synthesize these diverse knowledge areas into a cohesive, functional system addressing genuine business requirements..

Direct exposure to small business operations through personal observations and interactions with retail business owners revealed persistent operational inefficiencies caused by inadequate management systems. Many small retailers and wholesalers expressed frustration with manual record-keeping burdens, difficulties in tracking inventory accurately, challenges in maintaining customer records, and limitations in accessing timely business performance information. These pain points highlighted a clear need for an integrated solution tailored to their operational realities and financial constraints. The discrepancy between available ERP solutions and the actual needs of small Pakistani businesses served as a significant motivational factor. Existing commercial systems were often excessively feature-rich for small business requirements, complicated to navigate without extensive training, priced beyond reasonable budgets, or lacking in cultural and operational customization appropriate for local business practices. This gap presented an opportunity to develop a streamlined, focused solution specifically addressing the core needs of target users. From a technical perspective, the project offered an intellectually stimulating challenge involving multiple domains of computer science including requirements engineering, database design and normalization, algorithm development for business calculations, user interface design, security implementation, and system testing. The complexity of creating an integrated system where multiple modules interact seamlessly provided valuable learning experiences in managing interdependencies, ensuring data consistency, and implementing transaction management. The potential for creating genuine business impact served as a powerful motivator. Unlike purely academic exercises, this project aimed to produce a functional system capable of actual deployment and operational use. The prospect of contributing a solution that could potentially improve business efficiency for numerous small enterprises, reduce their operational costs, and enable better decision-making provided a sense of purpose beyond academic requirements. Career development considerations also influenced project selection. Enterprise system development represents a significant area within the software industry with substantial demand for skilled professionals. Gaining hands-on experience in designing, implementing, and testing a comprehensive business application enhances employability and prepares team members for professional roles in software development, business analysis, or system implementation. The collaborative nature of the project presented opportunities to develop teamwork skills including task distribution, progress coordination, conflict resolution, and collective problem-solving. Working as a team on a substantial project mirroring real-world software development environments provided valuable preparation for professional workplace dynamics. Technological enthusiasm for web-based application development and cloud computing paradigms further motivated the project direction. The ability to create accessible systems deployable globally without geographic or platform constraints, utilizing modern development frameworks and following contemporary software architecture patterns, aligned with our interests in current technology trends and best practices. 1.6 Aim and Objectives The primary aim of this project is to design, develop, and deploy a comprehensive cloudbased enterprise resource planning system specifically tailored for small and medium retail and distribution businesses, integrating core operational functions including pointof-sale billing, inventory management, purchase order processing, customer relationship management, and financial reporting within a unified, user-friendly web platform. To achieve this overarching aim, the project pursues the following specific objectives:.

Objective 1: Requirements Analysis and Specification - Conduct comprehensive analysis of business processes in retail and distribution operations through stakeholder consultations, observation of existing workflows, and review of similar systems. Document functional and non-functional requirements systematically following Software Requirements Specification standards. Identify key business rules, user roles, data entities, and system constraints that will govern the system design and implementation. Objective 2: System Architecture Design - Design a scalable three-tier system architecture separating presentation concerns, business logic, and data persistence. Define the structural organization of system components, their interfaces, and communication protocols. Select appropriate technological platforms, frameworks, and tools considering factors including performance requirements, development team expertise, deployment environment, and long-term maintainability. Objective 3: Database Schema Design and Implementation - Develop a normalized relational database schema representing all business entities including products, customers, suppliers, transactions, users, and configuration data. Define table structures, establish referential integrity constraints, create appropriate indexes for query optimization, and implement stored procedures or database-level logic where beneficial for data consistency and performance. Objective 4: Point-of-Sale Module Implementation - Develop an efficient transaction processing interface enabling rapid product selection, quantity specification, automatic price and tax calculation, and invoice generation. Implement barcode scanning support for product identification. Ensure real-time inventory deduction upon sale completion and automatic updating of customer account balances for credit transactions. Design receipt formats appropriate for printing or digital distribution. Objective 5: Inventory Management Module Implementation - Create comprehensive inventory tracking functionality including product registration with multiple attributes, stock receipt recording linked to purchases, stock adjustment capabilities for corrections, category-based organization, unit measurement handling, and reorder level monitoring. Implement inventory reporting showing current stock positions, valuation, movement histories, and low-stock alerts. Objective 6: Purchase Management Module Implementation - Develop purchase order creation interfaces, supplier information management, order status tracking, goods receipt recording, and supplier payment handling. Establish integration between purchase module and inventory module ensuring automatic stock updates upon goods receipt. Implement supplier ledger tracking showing outstanding payables and payment histories. Objective7: FinancialManagementandReportingImplementation - Create modules for expense recording, payment tracking, and comprehensive financial reporting. Implement automated calculation of key financial metrics including daily sales totals, gross profits, net profits after expenses, and period-over-period comparisons. Design report layouts providing clear visual representation of financial data suitable for management decision-making. Objective 8: User Management and Access Control Implementation - Develop user authentication mechanisms, role-based permission systems, and activity logging. Ensure that different user categories have appropriately restricted access aligned with their operational responsibilities. Implement password security practices and session management preventing unauthorized access. Objective 9: User Interface Design and Responsiveness - Design intuitive, userfriendly interfaces following established usability principles and considering the technical proficiency levels of target users. Ensure responsive layouts adapting appropriately to various screen sizes from desktop monitors to mobile devices. Implement clear navigation structures, informative feedback mechanisms, and error prevention strategies. Objective 10: System Testing and Quality Assurance - Conduct comprehensive testing at multiple levels including unit testing of individual functions, integration testing of interconnected modules, system testing of.

complete workflows, and user acceptance testing with representative business scenarios. Document test cases, execute tests systematically, identify and resolve defects, and validate that the system meets specified requirements. Objective 11: Deployment and Documentation - Deploy the system to a cloud hosting environment ensuring proper configuration for security, performance, and reliability. Prepare comprehensive technical documentation including system architecture descriptions, database schema documentation, API specifications, and deployment procedures. Create user manuals explaining system functionality and operational procedures for endusers. 1.7 Scope of the Project The scope of this project encompasses the complete lifecycle of software development from initial requirements gathering through system deployment, focusing specifically on core operational modules essential for retail and distribution business management. This section delineates the boundaries of project activities, identifying functionalities included within the project scope while acknowledging limitations and future enhancement opportunities. 1.7.1 In-Scope Functionalities The project includes implementation of point-of-sale transaction processing with product selection interfaces, barcode scanning support, automatic calculation of subtotals, taxes, and final totals, generation of printable invoices, and recording of payment information. Sales transactions automatically update inventory levels, customer account balances for credit sales, and daily sales summaries accessible through reporting modules. Inventory management functionality within scope includes product registration with attributes such as name, category, unit measurement, cost price, selling price, and barcode identifiers. The system maintains real-time stock quantities, records all stock movements including receipts from purchases, deductions through sales, and manual adjustments. Low-stock alert mechanisms notify users when inventory levels fall below configured reorder points. Inventory reports provide stock valuation, movement histories, and category-wise stock summaries. Purchase order management capabilities include supplier registration with contact details and transaction histories, electronic creation of purchase orders specifying products and quantities, recording goods receipts that automatically increment inventory levels, and tracking supplier payment obligations. The system maintains complete purchase histories facilitating analysis of procurement patterns and supplier performance evaluation. Customer relationship management features include customer profile creation capturing contact information and credit limits, transaction history tracking showing all purchases and payments, account balance maintenance for credit customers, and payment recording automatically adjusting outstanding balances. Customer reports identify frequent buyers and customers with outstanding dues. Financial management modules encompass expense recording classified by categories such as rent, utilities, salaries, and miscellaneous operational costs. Payment tracking records cash outflows associated with supplier payments, expenses, and other disbursements. Financial reporting automatically generates profit and loss statements showing revenue from sales, cost of goods sold based on inventory valuations, operating expenses, and net profit calculations. Daily sales summaries, monthly financial comparisons, and expense breakdowns by category support management decision-making. User access control implements role-based permissions with distinct privilege levels for administrators, managers, and operational staff. User authentication through username and password credentials secures system.

access. Activity logging records significant operations including user logins, transaction processing, and configuration changes, providing audit trails for accountability and troubleshooting. Dashboard interfaces provide graphical representations of key business metrics including daily sales trends, inventory status visualizations, top-selling products, recent transactions, and financial summary cards. These visual elements enable quick assessment of business health and identification of items requiring management attention. 1.7.2 Out-of-Scope Elements Certain functionalities, while potentially valuable, fall outside the current project scope due to time constraints, complexity considerations, or being more appropriate for future enhancement phases. Mobile native applications for iOS or Android platforms are not included in the current scope, though the web interface is designed responsively to function adequately on mobile browsers. Advanced inventory features such as batch tracking, serial number management, expiration date tracking for perishable items, and warehouse location management representing physical storage positions within warehouses are deferred to future versions. The current implementation focuses on aggregate inventory tracking suitable for single-location or simplified multi-location scenarios. E-commerce integration enabling online storefronts, shopping cart functionality, payment gateway connectivity, and order fulfillment workflows represents a separate domain beyond the current ERP focus. While valuable for businesses pursuing online sales channels, this functionality constitutes a major additional subsystem more appropriately developed as a subsequent project phase. Artificial intelligence and machine learning capabilities including sales forecasting based on historical patterns, automated inventory replenishment recommendations, customer behavior analysis, and predictive analytics require substantial additional research and development efforts. These advanced features are acknowledged as promising future enhancements but are not implemented in the current version. Human resource management functions such as employee payroll processing, attendance tracking, performance evaluation, and leave management fall outside the primary retail operations focus of this project. Businesses requiring these capabilities would need separate HR management systems or future ERP expansions. Manufacturing-specific functionalities including bill of materials management, production planning, work order tracking, and quality control processes are not applicable to the retail and distribution business context targeted by this project. The system focuses on businesses that purchase finished goods for resale rather than manufacturing operations. Multi-language support and localization features enabling interface translation and region-specific adaptations are not implemented in the initial version. The system interface is developed in English, which is widely understood in the target business environment. Future versions could incorporate Urdu language support and other regional languages based on user demand. 1.8 Deliverables and Operational Rules This project produces multiple tangible deliverables encompassing software artifacts, documentation, and deployment configurations. The primary deliverable is the fully functional web-based ResellerCenter PK ERP system deployed on cloud infrastructure and accessible via standard web browsers. The system comprises frontend interfaces built using web technologies providing responsive user experiences, backend application logic.

implementing business rules and data processing operations, and database structures persisting all business information. Documentation deliverables include this comprehensive final year project report detailing the complete development process from requirements analysis through implementation and testing. The report serves as academic documentation of the project and as reference material for future system maintenance or enhancement activities. Technical documentation artifacts include database schema diagrams with entity relationship representations, system architecture diagrams illustrating component organization and interactions, user interface wireframes showing screen layouts and navigation flows, and API documentation describing interfaces between system components. User-facing documentation includes operation manuals explaining how to perform common business tasks using the system, such as processing sales transactions, recording purchases, generating reports, and managing user accounts. These manuals target endusers with varying technical proficiency levels and use clear language with illustrative screenshots guiding users through operational procedures. Source code constitutes another critical deliverable, organized in structured directories following established coding conventions and including inline comments explaining complex logic. Version control repositories maintain complete development histories enabling tracking of changes, collaborative development, and rollback capabilities if needed. Proper code organization facilitates future maintenance, debugging, and feature additions. Testing artifacts include documented test plans specifying testing strategies and coverage areas, test case collections describing specific scenarios to validate, test execution logs recording results of conducted tests, and defect reports documenting identified issues, their severity levels, resolution actions, and verification outcomes. These testing deliverables provide evidence of quality assurance efforts and guide future testing cycles. 1.8.1 Operational Rules and Business Logic The system operates according to defined business rules ensuring data consistency, enforcing operational constraints, and implementing standard business practices. In pointof-sale operations, the system enforces rules such as mandatory product selection before invoice generation, automatic inventory sufficiency validation preventing sales exceeding available stock, required payment method specification, and automatic calculation accuracy for totals including applicable tax rates. Inventory management rules include uniqueness constraints on product identifiers preventing duplicate registrations, validation of numeric quantities ensuring only positive values for stock additions, mandatory category assignment for organizational consistency, and automated low-stock detection triggering alerts when inventory falls below defined reorder points. Stock adjustments require proper authorization based on user permissions, and all inventory movements maintain complete audit trails recording transaction timestamps and responsible users. Purchase order rules mandate supplier association for every purchase order, require product specifications with quantities and expected costs, enforce order status tracking through defined states including pending, partially received, and completed, and validate goods receipt quantities against original order quantities. Supplier payment recording updates outstanding liability balances and maintains payment histories for financial tracking. Customer account management rules include optional customer association for sales transactions with mandatory association for credit sales, automatic credit limit validation preventing credit transactions exceeding approved limits, comprehensive transaction recording for all customer interactions, and payment application rules.

determining how received payments reduce outstanding balances following first-in-first-out or other configured methodologies. Financial calculation rules implement standard accounting practices including revenue recognition upon sale completion, cost of goods sold determination using inventory valuation methods such as weighted average cost, operating expense categorization for accurate financial statement preparation, and profit calculation as the difference between revenues and total costs. Period-end closing procedures ensure financial data integrity and facilitate accurate comparative reporting across time periods. User access control rules implement hierarchical permission structures where administrators possess full system access including user management and system configuration capabilities, managers have operational access including reporting and supervisory functions but limited ability to modify system settings, and operational users such as cashiers possess restricted access limited to transaction processing within their job responsibilities. All user actions undergo authentication and authorization checks before execution, and security rules enforce password complexity requirements, session timeout policies, and protection against common security vulnerabilities. 1.9 Technologies Used The development of ResellerCenter PK ERP utilized a combination of contemporary web technologies, database systems, and development tools selected based on criteria including functionality requirements, development team expertise, community support availability, cost considerations, and suitability for cloud deployment. This section provides an overview of the technology stack employed without emphasizing specific brand names or versions, focusing instead on the categories and roles of technologies utilized. 1.9.1 Web Technologies and Frameworks The system frontend employs standard web technologies including HTML for structural markup of user interfaces, CSS for presentation styling and layout control, and JavaScript for client-side interactivity and dynamic content manipulation. These foundational technologies ensure broad browser compatibility and adherence to web standards. Responsive design frameworks provide pre-built CSS components and grid systems facilitating the creation of mobile-friendly interfaces that adapt gracefully to various screen dimensions. JavaScript libraries enhance user experience through features such as asynchronous communication with backend services enabling page updates without full reloads, form validation providing immediate feedback on user inputs, dynamic table manipulations for displaying and filtering data sets, and graphical chart rendering for visualizing business metrics. These libraries abstract complex DOM manipulation operations and provide tested, reliable solutions for common interface challenges. The backend application layer utilizes server-side scripting languages capable of processing HTTP requests, executing business logic, interacting with databases, and generating dynamic responses. The selected language provides robust support for web application development including session management, user authentication, data validation, and template rendering. Object-oriented programming paradigms employed in backend code promote code reusability, maintainability, and logical organization of business logic into coherent modules. Web application frameworks provide architectural structures, common patterns, and utility functions accelerating development processes. These frameworks implement modelview-controller or similar architectural patterns separating data models, presentation templates, and control logic. Built-in features typically include routing mechanisms mapping URLs to controller actions, database abstraction layers simplifying data operations, form.

handling utilities, security helpers preventing common vulnerabilities, and templating engines for generating HTML output. 1.9.2 Database Management System A relational database management system serves as the persistence layer storing all business data including product catalogs, customer records, transaction histories, user information, and configuration settings. The selection of a relational database aligns with the structured nature of business data and supports enforcement of data integrity through constraints, relationships, and transactions. The database system provides SQL query capabilities for data retrieval, manipulation, aggregation, and reporting. Indexing mechanisms optimize query performance particularly for frequently accessed tables and search operations. Transaction support ensures data consistency during complex multi-step operations such as sales transactions that update multiple related tables atomically. Backup and recovery features protect against data loss and enable restoration to previous states if needed. Database design follows normalization principles reducing data redundancy and update anomalies while balancing practical performance considerations. Tables represent distinct business entities with primary keys ensuring unique identification. Foreign key relationships establish connections between related entities enforcing referential integrity. Stored procedures or database-level functions encapsulate complex query logic or validation rules executed within the database engine. 1.9.3 Development Tools and Environment Integrated development environments provide code editors with syntax highlighting, autocompletion, debugging capabilities, and project management features facilitating efficient coding processes. Version control systems maintain source code repositories enabling collaborative development, change tracking, branching for parallel development efforts, and merging of code contributions from multiple team members. Database management tools offer graphical interfaces for designing schemas, executing queries, examining data, and performing administrative tasks. These tools complement command-line interfaces providing visual representations of database structures and simplifying common database operations during development and testing phases. Browser developer tools integrated within modern web browsers enable inspection of HTML structures, CSS styling, JavaScript execution, network communications, and console logging. These tools prove invaluable for frontend debugging, performance profiling, and validating that client-side code behaves as intended across different browsers. Testing frameworks support automated execution of test cases validating that code units, modules, and complete system workflows function correctly. These frameworks provide assertion libraries for verifying expected outcomes, test runners executing test suites, and reporting mechanisms summarizing test results. Automated testing complements manual testing efforts and facilitates regression testing ensuring that new changes do not break existing functionality. 1.9.4 Deployment and Hosting Infrastructure Cloud hosting platforms provide server infrastructure for deploying the application, offering virtual machines or platform-as-a-service environments preconfigured with necessary runtime components. These platforms handle infrastructure concerns including server maintenance, security patching, network configuration, and scaling.

capabilities. Domain name services map human-readable URLs to server IP addresses enabling users to access the system through memorable web addresses. Web servers process HTTP requests, serve static files such as CSS and JavaScript resources, and forward application requests to backend processing engines. Configuration of web servers includes setting up virtual hosts, enabling necessary modules, optimizing performance parameters, and implementing security measures such as HTTPS encryption. Database servers host the database management system storing all application data. Proper database server configuration includes memory allocation, connection pooling, backup scheduling, and access control ensuring only authorized application components can modify data. Separation of web and database servers on different machines or in different security zones follows security best practices protecting sensitive data. Backup systems periodically capture database snapshots and application files storing them in secure locations separate from primary servers. These backups provide disaster recovery capabilities enabling system restoration if primary infrastructure experiences failures. Automated backup scheduling and verification processes ensure backup reliability and minimize recovery time objectives. Monitoring and logging tools track system performance metrics, application errors, security events, and user activities. Log aggregation collects messages from various system components into centralized repositories facilitating troubleshooting and security auditing. Performance monitoring identifies resource bottlenecks, slow database queries, or excessive response times enabling proactive optimization..

Chapter #2 LITERATURE REVIEW 2.1 Introduction The literature review examines existing research, published systems, and documented best practices relevant to enterprise resource planning systems, retail management applications, and web-based business software. This review establishes the theoretical foundations underlying this project, identifies the current state of knowledge in related domains, highlights limitations in existing approaches, and justifies the need for the proposed system. Through systematic examination of academic publications, industry reports, and technical documentation, this chapter contextualizes the project within the broader landscape of enterprise systems research and development. 2.2 Overview of Enterprise Resource Planning Systems Enterprise Resource Planning systems represent comprehensive software solutions designed to integrate and automate various business processes across organizational functions. Academic literature traces the evolution of ERP systems from early Material Requirements Planning systems focused narrowly on manufacturing inventory management in the 1960s and 1970s, through Manufacturing Resource Planning systems incorporating broader production planning functions in the 1980s, to contemporary ERP systems encompassing virtually all business operations including finance, human resources, sales, procurement, and supply chain management. Research examining ERP adoption patterns indicates that large enterprises were early adopters of these integrated systems, driven by needs to standardize global operations, consolidate disparate legacy systems, and achieve economies of scale through centralized data management. Studies document implementation challenges including high costs ranging from hundreds of thousands to millions of dollars, lengthy implementation timelines often extending beyond planned schedules, organizational change management difficulties as employees adapted to new processes, and technical complexities requiring specialized expertise. The benefits of ERP systems documented in literature include improved data accuracy through elimination of redundant data entry and centralized validation, enhanced visibility across organizational functions enabling better coordination and decision-making, process standardization reducing variability and errors, and improved regulatory compliance through systematic record-keeping and audit trails. Research also identifies productivity gains from automation of routine tasks and reduction of manual data manipulation efforts. However, scholarly critiques highlight ERP limitations including inflexibility in accommodating unique organizational processes, complexity requiring extensive training and potentially overwhelming smaller organizations, high total cost of ownership encompassing licensing, implementation, customization, and ongoing maintenance expenses, and vendor lock-in creating dependency on specific software providers for support and future enhancements. 2.3 Small Business Management Systems While extensive research addresses ERP systems for large enterprises, literature specifically examining information systems for small and medium enterprises reveals different priorities and constraints. Small.

businesses typically operate with limited financial resources, minimal dedicated IT staff, simpler organizational structures, and greater operational flexibility. Research indicates that traditional ERP systems designed for large corporations are often inappropriate for small business contexts due to feature complexity exceeding actual needs, cost structures incompatible with small business budgets, and implementation approaches assuming organizational resources unavailable in smaller entities. Studies focusing on small business technology adoption identify critical factors influencing acceptance including perceived ease of use, clear demonstration of tangible benefits, affordability with transparent pricing structures, minimal disruption to ongoing operations during implementation, and availability of accessible support resources. Small business owners frequently lack technical expertise and cannot afford extensive training programs, making user-friendliness a paramount requirement. Literature examining retail management specifically addresses operational workflows characteristic of retail businesses including frequent small-value transactions requiring rapid processing, inventory turnover with perishability concerns for certain product categories, customer relationship dynamics balancing personal service with transaction efficiency, and seasonal demand variations requiring flexible inventory management. Research emphasizes that retail businesses prioritize point-of-sale speed and reliability, accurate real-time inventory tracking preventing stockouts, and simple financial reporting showing profitability metrics clearly. Academic research has documented various point-of-sale system designs ranging from basic cash register replacements focused solely on transaction processing through comprehensive retail management systems integrating sales, inventory, customer relationships, and financial reporting. Studies comparing these approaches indicate that integrated systems provide superior value by eliminating manual data reconciliation between separate systems, reducing human error, and enabling analytical insights from consolidated data. 2.4 Cloud Computing and Software-as-a-Service Models The emergence of cloud computing represents a paradigm shift in software deployment and consumption, with substantial academic literature examining its implications for business applications. Cloud computing abstracts physical infrastructure, providing computing resources as on-demand services accessed over the internet. Research categorizes cloud services into infrastructure-as-a-service providing virtual machines and storage, platform-as-a-service offering application development and deployment environments, and software-as-a-service delivering complete applications accessible through web browsers. For business management systems, the Software-as-a-Service model offers multiple advantages documented in literature. Capital expenditure elimination removes upfront hardware and software licensing costs, replacing them with subscription-based operational expenses more manageable for budget-constrained organizations. Rapid deployment accelerates time-to-value as systems become operational within days rather than months-long traditional implementations. Automatic updates ensure users access current versions with latest features and security patches without manual upgrade processes. Accessibility from any internet-connected location supports remote work and multi-location business operations. Research also acknowledges cloud computing concerns including data security risks from storing sensitive business information on external servers, dependency on internet connectivity making systems inaccessible during network outages, potential performance variability due to shared infrastructure resources, and questions about long-term data portability if organizations wish to migrate between service providers. Academic literature recommends risk mitigation strategies including encryption of sensitive data, selection of reputable cloud providers with documented security practices, implementation of local backup procedures, and evaluation of service level agreements defining provider obligations..

Studies examining cloud ERP adoption among small businesses indicate growing acceptance driven by cost advantages and convenience benefits outweighing concerns for many organizations. Research suggests that for small businesses lacking existing IT infrastructure, cloud-based systems represent practical entry points to enterprise-grade business management capabilities previously inaccessible due to financial and technical barriers. 2.5 Database Design and Management Database systems literature provides extensive coverage of relational database design principles, normalization theory, and transaction management essential for reliable business applications. Academic research establishes that properly designed databases form foundations for data integrity, query performance, and system scalability. Normalization theory, developed through decades of database research, provides systematic methods for organizing data structures to eliminate redundancy, prevent update anomalies, and ensure logical consistency. Studies examining database design for business applications emphasize importance of clearly defined entities representing real-world business concepts, relationships establishing connections between related entities, constraints enforcing business rules at the database level, and transactions ensuring atomic execution of multi- step operations. Literature documents common pitfalls including inadequate normalization leading to data inconsistencies, missing constraints allowing invalid data entry, poorly designed indexes causing performance degradation, and insufficient transaction handling resulting in data corruption during concurrent access. Research addressing database security highlights mechanisms including authentication verifying user identities, authorization controlling access to specific data based on privileges, encryption protecting data confidentiality during storage and transmission, and audit logging recording data access and modifications for compliance and forensic purposes. Academic literature recommends defense-in-depth approaches implementing security measures at multiple levels rather than relying on single protective mechanisms. Transaction processing research establishes ACID properties as fundamental requirements for reliable database operations. Atomicity ensures that multi-step transactions either complete entirely or have no effect, preventing partial updates that leave data in inconsistent states. Consistency maintains database integrity constraints before and after transactions. Isolation prevents concurrent transactions from interfering with each other. Durability guarantees that committed transactions persist even in the event of system failures. Implementation of these properties requires sophisticated concurrency control and recovery mechanisms documented extensively in database literature. 2.6 User Interface Design and Usability Human-computer interaction research provides extensive guidance on designing effective user interfaces for business applications. Academic literature establishes that user interface quality significantly impacts user acceptance, productivity, and error rates. Research identifies core usability principles including consistency in interface elements and behaviors across system components, feedback providing clear indications of system status and operation results, error prevention through validation and confirmations rather than correction after mistakes, recognition over recall by making options visible rather than requiring users to remember information, and flexibility accommodating both novice users needing guidance and expert users seeking efficiency. Studies examining business application interfaces emphasize importance of task-oriented design organizing functionality according to user workflows rather than technical system structure. Research indicates users mental models align with business processes they perform daily, making interfaces reflecting these processes more intuitive than those organized by system architecture. Literature recommends iterative design processes involving representative users in prototype evaluation and refinement cycles..

Responsive design research addresses challenges of creating interfaces functioning effectively across diverse device form factors from desktop monitors through tablets to smartphones. Academic publications document approaches including fluid grid layouts adapting to available screen width, flexible images scaling appropriately, and media queries applying different styles based on device characteristics. Research emphasizes that responsive design goes beyond visual scaling to reconsidering information architecture and interaction patterns appropriate for different contexts of use. Accessibility literature highlights requirements for designing systems usable by people with diverse abilities including visual, auditory, motor, and cognitive variations. Academic research establishes that accessible design benefits all users, not only those with disabilities, through clearer information hierarchy, more robust interaction methods, and better compatibility with assistive technologies. Standards and guidelines documented in literature provide specific criteria for accessible web applications including appropriate color contrast, keyboard navigation support, screen reader compatibility, and clear error identification and correction mechanisms. 2.7 Software Development Methodologies Software engineering literature extensively discusses various development methodologies representing systematic approaches to organizing software creation activities. Traditional waterfall methodologies follow sequential phases including requirements specification, system design, implementation, testing, and deployment, with each phase completing before the next begins. Academic research documents waterfall appropriateness for projects with stable, well-understood requirements but highlights inflexibility in accommodating changing requirements and delayed delivery of working software until late in development cycles. Agile methodologies emerged from recognition of limitations in traditional approaches, emphasizing iterative development, continuous stakeholder engagement, adaptability to changing requirements, and early and frequent delivery of working software increments. Literature describing Agile principles articulated in the Agile Manifesto prioritizes individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following rigid plans. Scrum, a specific Agile framework, organizes work into time-boxed iterations called sprints typically lasting two to four weeks. Research documents Scrum practices including cross-functional teams with collective responsibility for deliverables, daily stand-up meetings coordinating team activities, sprint planning defining work to be accomplished, sprint reviews demonstrating completed functionality, and sprint retrospectives reflecting on process improvements. Academic studies indicate Scrum effectiveness in managing complex projects where requirements evolve and stakeholder feedback proves valuable. Literature examining methodology selection criteria indicates that project characteristics including size, complexity, requirement stability, team experience, and organizational culture influence appropriate methodology choices. Research suggests Agile approaches particularly suit projects with evolving requirements, need for rapid feedback, and emphasis on working software demonstrations. Studies document challenges in Agile adoption including cultural resistance to change, difficulties in distributed team coordination, and tensions between Agile flexibility and regulatory compliance requirements in certain industries. 2.8 Limitations of Existing Systems Analysis of existing retail management and ERP systems reveals several limitations motivating the development of alternative solutions. Commercial ERP systems targeting large enterprises incorporate extensive functionality.

spanning numerous business domains including human resources, manufacturing, advanced supply chain optimization, and complex multi-currency accounting. While comprehensive, this breadth introduces unnecessary complexity for small retail businesses whose core needs center on basic inventory tracking, sales processing, and simple financial reporting. The learning curves associated with feature-rich systems often overwhelm small business users, reducing adoption and effective utilization. Cost structures of traditional ERP systems present prohibitive barriers for small enterprises. Per-user licensing fees, implementation service charges, customization costs, annual maintenance fees, and infrastructure requirements accumulate to total ownership costs incompatible with small business budgets. Research indicates that small businesses require predictable, affordable pricing aligned with their financial capacities and return on investment timeframes. Generic business software often lacks customization appropriate for specific industry contexts or regional business practices. Retail businesses operate according to particular workflow patterns, terminology, and regulatory requirements differing from manufacturing or service sectors. Systems designed generically may not accommodate these specificities without extensive customization efforts beyond small business capabilities. Similarly, systems developed for Western markets may not align with business practices, languages, or cultural norms prevalent in other regions. Many existing systems remain desktop-based requiring local installation and limiting accessibility to specific computers. This constraint becomes problematic as businesses expand to multiple locations, as owners require remote access for oversight, or as mobile device usage increases. Literature indicates growing user expectations for anytime, anywhere access to business information, making purely desktop-based systems increasingly outdated. Integration challenges plague businesses using multiple specialized applications for different functions. Separate systems for point-of-sale, inventory, accounting, and customer management create data silos requiring manual transfer of information between applications. This fragmentation increases administrative overhead, introduces data inconsistency risks, and prevents holistic business views. Research emphasizes benefits of integrated systems eliminating these redundancies. 2.9 Research Gap and Justification Comprehensive review of existing literature and available systems reveals a gap in affordable, integrated, user- friendly retail management systems specifically addressing small and medium business needs in developing economy contexts. While extensive research addresses large enterprise ERP systems and substantial commercial offerings exist in this space, proportionally less attention has been directed toward tailored solutions for smaller retailers and wholesalers operating with limited technical resources and tight budget constraints. Academic research examining small business information systems in Pakistani or similar developing country contexts remains limited. Most published studies focus on technology adoption barriers, general digital literacy challenges, or case studies of large corporation system implementations. Practical documentation of system designs, implementation approaches, and effectiveness evaluations for small business ERP in these contexts is scarce in academic literature. The specific combination of requirements characterizing small retail businesses including rapid transaction processing, real-time inventory visibility, simple financial reporting, multi-user access with appropriate controls, and cloud-based accessibility represents a particular system profile. While individual components addressing subsets of these requirements exist, integrated solutions combining all elements in accessible, affordable packages remain less common..

This project addresses the identified gap by developing a focused system specifically targeting core retail business operations without unnecessary feature complexity, employing contemporary cloud-based deployment removing infrastructure barriers, implementing intuitive interfaces appropriate for users with varying technical backgrounds, and following systematic software engineering practices documented through academic research. The project contributes both a practical system potentially benefiting actual businesses and documentation of design decisions, implementation approaches, and evaluation results adding to the body of knowledge in applied enterprise systems development. 2.10 Summary.

Chapter #3 METHODOLOGY 3.1 Introduction The methodology chapter describes the systematic approach adopted for developing ResellerCenter PK ERP system, encompassing the software development lifecycle model selection, requirements gathering procedures, system specification processes, algorithmic approaches for core business logic, database design methodology, and tools utilized throughout development. This chapter provides transparency regarding how the project team organized work activities, made design decisions, and ensured quality throughout the development process. The methodology selection was influenced by project characteristics including evolving requirements, need for stakeholder feedback integration, relatively short development timeframe, and team composition of students with varying specialization areas. 3.2 Software Development Life Cycle Model Selection The selection of an appropriate software development lifecycle model critically impacts project organization, team coordination, requirement adaptation, and delivery predictability. After careful consideration of project characteristics and evaluation of alternative methodologies documented in software engineering literature, the Agile Scrum framework was selected as the primary development methodology for this project. This section justifies this selection through analysis of project requirements and Scrum characteristics. 3.2.1 Justification for Agile Scrum Selection Several factors made Agile Scrum particularly appropriate for this project context. The evolving nature of requirements represented a primary consideration. Initial project conceptualization identified core functionality areas, but detailed specifications for user interface layouts, specific business rules, report formats, and system behaviors emerged progressively as the team gained deeper understanding of retail business operations and stakeholder needs. Traditional waterfall approaches requiring comprehensive upfront requirements specification would have constrained this natural refinement process or necessitated disruptive change management procedures. The value of frequent working software demonstrations aligned well with Scrum’s iterative delivery emphasis. The project supervisor and potential users could provide feedback based on actual functioning modules rather than abstract specifications or design documents, enabling course corrections before substantial development effort was invested in potentially suboptimal directions. This feedback loop proved invaluable in refining user interfaces, adjusting workflow sequences, and prioritizing feature implementation order. The project timeframe of approximately six months from initial planning through final delivery necessitated efficient time utilization and visible progress tracking. Scrum’s sprint structure with defined time boxes, sprint goals, and regular progress reviews provided natural milestones ensuring the team maintained development momentum and identified obstacles promptly. The relatively short sprint durations of two weeks created a sustainable rhythm balancing planning overhead against adaptability..

Team composition comprising four students with complementary skills in frontend development, backend programming, database design, and system testing suited Scrum’s cross-functional team emphasis. Rather than rigidly dividing work according to specializations and creating handoff dependencies, Scrum encouraged collaborative problemsolving where team members contributed across areas as needed while leveraging individual strengths. Daily coordination ensured awareness of interdependencies and facilitated assistance when team members encountered technical challenges. The academic project context differed from commercial development in lacking external client pressure but maintaining accountability to academic supervisors and evaluation criteria. Scrum ceremonies including sprint reviews demonstrating completed functionality and sprint retrospectives reflecting on process effectiveness provided structured opportunities for supervisor engagement and constructive feedback on both technical deliverables and development practices. Compared to waterfall, which would have required committing to detailed specifications before implementation and risked delivering inappropriate solutions if initial understanding proved incomplete, Scrum’s embrace of change enabled progressive refinement. Compared to less structured ad-hoc development approaches sometimes adopted in academic projects, Scrum provided sufficient process discipline ensuring systematic progress and quality maintenance. Compared to Extreme Programming or other Agile variants emphasizing particular technical practices such as pair programming or test-driven development, Scrum offered flexibility in technical implementation choices while maintaining project management structure. 3.2.2 Scrum Implementation Approach The project adopted Scrum practices adapted to the academic context while maintaining core principles. The product backlog, a prioritized list of features and tasks, was initially populated based on requirements gathering activities and then continuously refined throughout the project. Backlog items were expressed as user stories describing desired functionality from user perspectives, acceptance criteria defining when stories would be considered complete, and task breakdowns identifying specific technical activities required for implementation. Sprints were organized as two-week iterations, balancing the need for demonstrable progress against the overhead of sprint ceremonies. At the beginning of each sprint, the team conducted sprint planning meetings where they reviewed the product backlog, selected stories achievable within the sprint duration considering team capacity and story complexity estimates, and defined the sprint goal summarizing the planned accomplishments. This planning ensured that each sprint targeted coherent functionality sets rather than arbitrary collections of disconnected tasks. Daily stand-up meetings, though sometimes conducted virtually due to schedule constraints, maintained team synchronization. Each member briefly reported progress since the previous meeting, planned activities until the next meeting, and any obstacles impeding progress. These meetings typically lasted 10 to 15 minutes, focusing on coordination rather than detailed technical discussions which occurred separately as needed. The daily rhythm kept everyone informed of project status and enabled early identification of emerging issues. Sprint reviews at the end of each two-week cycle demonstrated completed functionality to the project supervisor and sometimes to representative potential users. These demonstrations focused on working software rather than documentation or theoretical descriptions. Feedback received during reviews was captured as new product backlog items, adjustments to existing stories, or confirmations that implemented features met expectations. This frequent validation reduced the risk of substantial rework near project completion. Sprint retrospectives provided opportunities for team self-reflection on development processes, collaboration effectiveness, and technical practices. The team discussed what went well during the sprint, what could be improved, and specific action items for the subsequent sprint. This continuous process improvement mindset.

aligned with Scrum values and enabled the team to adapt working practices as they gained experience and understanding of effective collaboration patterns. Throughout the project, the team maintained a product backlog in digital project management tools allowing story tracking, progress monitoring, and sprint planning. Visual boards displaying stories in states such as to-do, in- progress, and completed provided transparency regarding current work distribution and sprint progress toward defined goals. 3.3 Requirements Gathering Systematic requirements gathering established the foundation for subsequent design and implementation activities. The objective was to develop comprehensive understanding of business operations in small retail enterprises, identify essential system functionality, determine data management needs, and recognize constraints imposed by user technical proficiency, budgetary limitations, and deployment environment characteristics. Multiple complementary techniques were employed to triangulate requirements from diverse perspectives. 3.3.1 Stakeholder Interviews Semi-structured interviews were conducted with owners and managers of small retail and wholesale businesses representing the target user demographic. Interview protocols covered topics including current business processes for sales transaction handling, inventory tracking methods, supplier order procedures, customer account management practices, financial record-keeping approaches, and pain points or inefficiencies in existing methods. Open-ended questions encouraged respondents to describe workflows in their own terms rather than constraining responses to predetermined categories. Interviews revealed common patterns across businesses despite variations in product categories and business scales. Most businesses maintained physical registers or notebooks recording sales transactions manually. Inventory tracking ranged from mental estimations in very small operations through spreadsheet-based logs in somewhat larger businesses. Financial understanding often derived from accumulated cash balances rather than systematic profit-loss accounting. Customer credit was managed informally based on personal relationships with substantial risk of forgotten debts or disputed account balances. Interviewees consistently expressed desires for systems that would save time in daily operations, reduce errors in calculations and record-keeping, provide clearer visibility into inventory status and financial performance, and operate reliably without requiring constant technical support. Concerns were raised regarding costs, learning curves, and data security. These insights informed prioritization of ease-of-use in interface design, focus on core operational functions rather than peripheral features, and emphasis on reliability. 3.3.2 Observational Studies Direct observation of business operations in retail environments complemented interview findings by revealing actual workflows as opposed to described procedures. Observations were conducted in several small retail shops during normal business hours, noting how sales transactions were handled, how inventory was accessed and replenished, how customer interactions occurred, and how record-keeping was performed. Observations highlighted the fast-paced nature of retail transactions, with customers expecting rapid service particularly during busy periods. This observation reinforced requirements for streamlined point-of-sale interfaces minimizing required clicks or data entries. The frequent need to look up product prices emphasized importance of searchable product catalogs and barcode scanning support. The physical space constraints in small shops indicated necessity for compact screen layouts maximizing information density without cluttering..

Observation of inventory management revealed inconsistencies between physical stock and recorded quantities when manual tracking was used, emphasizing the critical importance of automatic inventory deduction upon sales. Observation of supplier deliveries showed varying practices regarding documentation, suggesting need for flexible goods receipt recording accommodating partial deliveries or discrepancies between ordered and received quantities. 3.3.3 Analysis of Existing Systems While the project specifically avoided replicating any particular existing product, analysis of functionality and user interfaces in available retail management systems provided insights into common feature sets, design patterns, and implementation approaches. This analysis included examination of screenshots, documentation, and feature descriptions of various systems accessed through online research, software review websites, and academic case studies. Analysis revealed common modules including point-of-sale, inventory management, purchase order handling, customer relationship management, supplier management, financial reporting, and user administration. Variations existed in terminology, feature depth, and workflow sequences. Some systems emphasized retail-specific features like customer loyalty programs or integrated e-commerce, while others provided more generic business management functionality applicable across industries. User interface analysis identified patterns such as dashboard landing pages displaying key performance indicators, form-based data entry screens with validation feedback, tabular listings of records with search and filter capabilities, and wizard-style workflows guiding users through multi-step processes. These patterns represented evolved solutions to common interface challenges and informed design decisions for the proposed system while avoiding direct copying of any particular product’s appearance or features. 3.3.4 Requirements Documentation Requirements gathered through these activities were systematically documented in structured formats facilitating subsequent design and implementation. Functional requirements specified system behaviors including user interactions, data processing operations, calculation algorithms, report generation, and integration between modules. Each functional requirement was assigned an identifier, descriptive name, detailed specification including inputs, processes, and outputs, and priority classification indicating whether the requirement was essential for minimum viable functionality or represented enhancement for future consideration. Non-functional requirements addressed quality attributes including performance expectations such as response time constraints for common operations, usability criteria such as task completion efficiency and error rate targets, reliability requirements regarding system availability and data integrity, security specifications for authentication and authorization mechanisms, and compatibility requirements regarding supported browsers and devices. Constraints documented environmental or organizational limitations within which the system must operate, including budget constraints limiting commercial software licensing or expensive infrastructure, technical skill limitations of target users affecting interface complexity tolerance, internet connectivity assumptions regarding available bandwidth and reliability, and regulatory compliance requirements if applicable to financial recordkeeping or data privacy. User stories expressed requirements from user perspectives using the format specifying the user role, desired capability, and benefit. For example, a user story might state that as a cashier, the user wants to process sales.

transactions quickly so that customers do not experience delays during busy periods. Acceptance criteria associated with each story defined specific conditions that must be satisfied for the story to be considered complete, providing testable validation criteria. 3.4 Software Requirement Specification The Software Requirement Specification document formalized requirements in standardized format following established software engineering practices. The SRS served as a contractual understanding between stakeholders regarding what the system would accomplish, guided design decisions, provided reference for implementation activities, and established baseline for testing and validation. 3.4.1 Functional Requirements Specification Functional requirements were organized by major system modules aligning with identified business operations. The point-of-sale module requirements specified capabilities including product selection through search interfaces or barcode scanning, quantity specification with validation, automatic price retrieval and total calculation, tax application based on configured rates, payment method recording supporting cash and credit options, invoice generation with printable formatting, and automatic inventory deduction and customer account updates upon sale completion. Inventory management requirements detailed product registration capturing attributes including name, category, description, unit of measurement, cost price, selling price, barcode identifier, and initial stock quantity. Stock movement tracking requirements specified recording of all inventory changes including receipts from purchases, deductions from sales, and manual adjustments for corrections or losses. Reporting requirements included current stock status showing quantities and values, stock movement histories, low-stock alerts based on reorder levels, and inventory valuation reports. Purchase management requirements addressed supplier registration with contact and payment term information, purchase order creation specifying products and quantities, order status tracking through states from pending to completed, goods receipt recording with automatic inventory increment, and supplier payment tracking updating payable balances. Integration requirements specified automatic linkages between purchase receipts and inventory updates ensuring consistency. Customer management requirements included customer profile creation, transaction history tracking showing all purchases and payments, account balance maintenance for credit customers, payment recording reducing outstanding balances, and customer reports identifying frequent purchasers or customers with overdue payments. Financial management requirements encompassed expense recording with category classification, payment tracking for cash disbursements, revenue calculation from sales, cost of goods sold determination based on inventory costs, profit and loss statement generation, and periodic financial comparison reports. Dashboard requirements specified visual presentations of key metrics including daily sales trends, top-selling products, inventory status summaries, and financial highlights. User administration requirements addressed user account creation with role assignment, authentication through username and password, authorization checks enforcing role-based access controls, password management including secure storage and reset capabilities, and activity logging recording user actions for audit trails. 3.4.2 Non-Functional Requirements Specification Performance requirements established acceptable response time targets for common operations. Page load times for main application screens should complete within three seconds under normal network conditions. Transaction.

processing from product selection through invoice generation should require less than thirty seconds for typical transactions involving multiple products. Report generation for standard reports accessing reasonable data volumes should complete within ten seconds. These targets balanced user experience expectations against realistic technical capabilities given target deployment infrastructure. Usability requirements specified that the system must be operable by users with basic computer literacy but without specialized technical training. Interfaces should employ familiar metaphors, provide clear labeling, offer helpful error messages rather than technical error codes, and maintain consistent navigation patterns throughout the application. Task completion should require minimal clicks or keystrokes, and frequently performed operations should be readily accessible. Reliability requirements mandated system availability during business operating hours, graceful handling of error conditions without data loss or corruption, transaction atomicity ensuring complete success or complete rollback without partial updates, and data backup procedures protecting against accidental loss. Database integrity constraints and application-level validations should prevent invalid data entry. Security requirements specified encrypted password storage using industry-standard hashing algorithms, session management preventing unauthorized access through stolen session identifiers, input validation preventing common vulnerabilities such as SQL injection or cross-site scripting, and role-based access controls restricting functionality according to user privileges. Audit trails should record significant operations including user logins, transaction processing, and configuration changes. Compatibility requirements indicated support for modern web browsers including Chrome, Firefox, Safari, and Edge in recent versions. The interface should adapt responsively to various screen sizes from desktop monitors through tablets to smartphones, maintaining usability across form factors. The system should not require installation of browser plugins or other client-side software beyond standard web browsers. Maintainability requirements addressed code organization, documentation, and extensibility. Source code should follow consistent coding conventions, include explanatory comments for complex logic, and be organized in modular structures facilitating understanding and modification. Database schemas should be properly normalized, and system architecture should separate concerns enabling changes to individual components without cascading modifications throughout the system. 3.5 Algorithms and Core Business Logic Several key algorithms implement core business processing logic ensuring accurate calculations, appropriate inventory adjustments, and correct financial tracking. This section describes the algorithmic approaches for fundamental operations including sales transaction processing, inventory updates, financial calculations, and report generation. 3.5.1 Sales Transaction Processing Algorithm The sales transaction processing algorithm coordinates multiple operations that must execute atomically to maintain data consistency. The algorithm begins when the user initiates sale completion after selecting products and quantities. First, the algorithm validates that all selected products have sufficient inventory quantities to fulfill the order, preventing overselling situations. If any product lacks adequate stock, the transaction is rejected with an explanatory message identifying the problematic products. Upon passing inventory validation, the algorithm calculates the transaction financial totals. For each product in the transaction, the extended line total is computed by multiplying the unit selling price by the quantity selected. These line totals are summed to produce the subtotal amount. If applicable tax rates are configured, tax is.

calculated as a percentage of the subtotal and added to produce the final total amount. Discount logic, if implemented, applies percentage or fixed amount discounts according to defined business rules, adjusting the subtotal before tax calculation. Once financial calculations are verified, the algorithm initiates a database transaction to ensure atomic execution. The first database operation inserts a sales transaction record capturing the transaction timestamp, customer identifier if applicable, subtotal, tax, discount, and final total. This record receives a unique transaction identifier serving as the primary key for subsequent related operations. For each product in the transaction, a sales detail record is inserted containing the transaction identifier, product identifier, quantity sold, unit price at time of sale, and line total. Recording the unit price at transaction time preserves historical accuracy even if product prices are subsequently changed, enabling accurate reporting of past transactions. Following successful sales record insertion, inventory quantities are decremented for all sold products. For each product, the algorithm reduces the current stock quantity by the quantity sold. These inventory updates occur within the same database transaction ensuring that if any update fails, all preceding operations are rolled back maintaining consistency. If the transaction involves a credit sale to a customer account, the customer account balance is incremented by the transaction total amount, recording the sale as an amount owed. This balance update also occurs within the transaction scope. Upon successful completion of all database operations, the transaction is committed, making all changes permanent. An invoice is generated containing transaction details formatted for printing or electronic distribution to the customer. Finally, the point-of-sale interface is reset for the next transaction while displaying confirmation of the completed sale. Error handling logic catches exceptions occurring during any stage of the process. If errors occur after the database transaction begins, all operations are rolled back leaving the system in the state before the attempted sale. Error messages inform the user of the problem in understandable terms, enabling corrective action such as adjusting quantities or resolving system issues. 3.5.2 Inventory Update Algorithm Inventory quantities require careful management through various types of transactions including purchase receipts increasing stock, sales decreasing stock, and manual adjustments correcting errors or accounting for losses. The inventory update algorithm ensures that all quantity changes are recorded with complete audit trails enabling traceability and verification. For purchase receipt processing, the algorithm receives input specifying the purchase order identifier, products received, and quantities for each product. The algorithm first validates that the specified purchase order exists and is in an appropriate state to receive goods. For each product in the receipt, the algorithm increments the inventory quantity by the received amount. Simultaneously, a stock movement record is created documenting the transaction type as a receipt, the associated purchase order, the product identifier, the quantity change, the timestamp, and the user who recorded the receipt. This movement record contributes to the inventory audit trail. The purchase order status is updated based on the extent of fulfillment. If all ordered products have been received in full quantities, the order status changes to completed. If some products remain undelivered, the status indicates.

partial fulfillment. This status tracking enables follow-up on pending deliveries and supplier performance evaluation. Sales-related inventory decrements follow the transaction processing algorithm described previously, with the critical distinction that inventory changes occur atomically with sale recording to prevent situations where sales are recorded but inventory is not updated or vice versa. Manual adjustment processing accommodates corrections for discrepancies identified during physical stock counts, recording of damaged goods removed from saleable inventory, or other scenarios requiring inventory quantity modifications. The adjustment algorithm accepts inputs specifying the product, the adjustment quantity which may be positive for additions or negative for removals, and a textual reason explaining the adjustment. The algorithm applies the adjustment to the product’s current quantity, creates a stock movement record documenting the adjustment as a distinct transaction type with the provided reason, and maintains the timestamp and responsible user identity. This careful documentation ensures that manual adjustments do not become avenues for concealing inventory losses or unauthorized removals. Queries of inventory movement histories include adjustments alongside purchases and sales, providing complete visibility into quantity changes. 3.5.3 Financial Calculation Algorithms Financial reporting requires accurate calculation of revenue, costs, and profits according to standard accounting principles. The profit and loss calculation algorithm aggregates data from multiple sources to determine financial performance over specified time periods. Revenue calculation sums the total amounts from all sales transactions within the analysis period. The algorithm queries sales transaction records filtered by timestamp to identify relevant transactions, retrieves the final total amount from each, and computes the sum representing gross revenue before considering costs or expenses. Cost of goods sold determination requires matching sold products with their cost basis. The algorithm processes sales detail records from the analysis period, identifying the products sold and their quantities. For each product, the algorithm retrieves the cost price used for inventory valuation, typically representing the weighted average cost of that product in inventory. The cost of goods sold is calculated by multiplying the quantity sold by the cost price for each product and summing across all products sold during the period. Operating expense aggregation sums amounts from expense records within the analysis period. Expenses may be categorized, enabling breakdowns showing spending by category such as rent, utilities, salaries, and miscellaneous. The algorithm sums expense amounts overall and within categories for detailed reporting. Gross profit is calculated as the difference between revenue and cost of goods sold, representing profit before considering operating expenses. Net profit subtracts total operating expenses from gross profit, representing the final profit after all costs. Profit margin percentages are calculated by dividing profit amounts by revenue and multiplying by one hundred, expressing profitability as percentages facilitating comparisons across periods of different revenue scales. For periodic comparisons, the algorithm executes these calculations for multiple time periods such as consecutive months or quarters, presenting results in comparative tabular or graphical formats highlighting trends, growth, or declines in business performance metrics..

3.5.4 Report Generation Algorithm Report generation algorithms transform raw transaction data into formatted presentations suitable for decision- making. The inventory status report algorithm retrieves current product records, calculates total inventory value by multiplying quantities by cost prices, identifies products below reorder levels, and formats the information in tabular layouts with sortable columns and summary statistics. The sales summary report algorithm groups sales transactions by relevant dimensions such as date, product, category, or customer. For each grouping, the algorithm aggregates quantities sold and revenue generated, sorts results by selected criteria such as highest revenue or most units sold, and presents formatted tables with totals and averages facilitating performance assessment. Customer account reports query customer records and associated transaction histories, calculating current account balances, identifying customers with overdue payments based on configured terms, and formatting outputs showing customer names, contact information, outstanding amounts, and last transaction dates enabling collection follow-up and credit management. 3.6 Database Design Approach The database design process followed systematic methods from conceptual modeling through physical implementation, ensuring that the database structure accurately represents business information, maintains data integrity, supports efficient queries, and provides scalability for future growth. The approach progressed through entity identification, relationship definition, normalization, and physical schema implementation. 3.6.1 Conceptual Data Modeling Conceptual modeling identified major business entities and their relationships at an abstract level independent of implementation details. Key entities identified included products representing items available for sale, customers representing individuals or businesses purchasing products, suppliers providing products for purchase, users representing system operators with distinct roles and permissions, sales transactions recording individual sale events, purchase orders documenting procurement activities, inventory movements tracking stock changes, expenses recording business costs, and payments capturing financial disbursements. Relationships between entities were defined according to business rules. Products belong to categories, establishing a many-to-one relationship where multiple products may share a category but each product has one primary category. Sales transactions are associated with customers through a many-to-one relationship, as multiple transactions may be initiated by the same customer but each transaction involves a single customer or may be anonymous for cash sales. Sales transactions contain multiple products through a many-to-many relationship, resolved through an associative entity called sales details that captures the intersection linking specific products to specific transactions along with quantities and prices at transaction time. Similarly, purchase orders contain multiple products through an associative purchase order details entity. Inventory movements reference products and transactions, capturing the reason and magnitude of quantity changes. Expenses may be categorized through a many-to-one relationship with expense categories. Users have assigned roles through a many-to-one relationship with role definitions..

3.6.2 Logical Data Modeling and Normalization Logical data modeling transformed the conceptual model into a detailed relational schema applying normalization principles to eliminate redundancy and ensure data integrity. The schema design achieved Third Normal Form ensuring that all non-key attributes depend on the entire primary key and nothing but the primary key, eliminating transitive dependencies and update anomalies. The Products table was designed with a primary key product identifier, along with attributes including product name, category identifier as a foreign key referencing the categories table, description, unit of measurement, cost price, selling price, barcode, reorder level, and current quantity. Separating category information into a distinct categories table avoided repeating category names across multiple products and ensured consistent category values. The Sales table included a primary key sales identifier, timestamp, customer identifier as a foreign key referencing customers, user identifier referencing the user who processed the transaction, subtotal, tax amount, discount amount, and final total. The related sales details table contained a composite primary key comprising sales identifier and product identifier, ensuring unique identification of each product within each transaction, along with quantity, unit price, and line total. Storing the unit price in sales details preserved the price at time of sale even if product prices subsequently changed, preventing historical transaction data from reflecting current prices inaccurately. The Purchases table and related purchase details table followed parallel structures to sales, capturing purchase order information and the products ordered. The Inventory Movements table recorded each stock change with attributes including movement identifier as primary key, product identifier, transaction type indicating whether the movement resulted from a purchase, sale, or adjustment, related transaction identifier if applicable, quantity change, timestamp, and user identifier. Customers table included customer identifier as primary key, name, contact information, credit limit, and current account balance. The separation of customer information from transaction records avoided repeating customer details in every transaction record, and maintaining the account balance as an aggregate simplifies balance queries though requiring careful update logic to keep balances synchronized with transactions. Users table captured user identifier, username, password hash, role identifier referencing a roles table, status indicating active or inactive, and timestamps for account creation and last login. Roles table defined role names and associated permissions, enabling centralized permission management where permission changes affect all users with that role without requiring individual user updates. Expenses table recorded expense identifier, date, amount, category identifier, payment method, and description. The separation of expense categories into a distinct table enabled consistent category definitions and facilitated category-based expense analysis. 3.6.3 Physical Database Implementation Physical implementation translated the logical schema into actual database tables with appropriate data types, constraints, and indexes. Primary key constraints were defined on all tables ensuring unique row identification. Foreign key constraints enforced referential integrity between related tables, preventing orphaned records and ensuring that references to related entities remain valid. Check constraints enforced business rules such as requiring positive values for quantities, prices, and monetary amounts. Unique constraints on fields like usernames prevented duplicate account creation. Not null constraints on required fields ensured that essential data was always provided..

Indexes were created on frequently queried columns to optimize search performance. Foreign key columns were indexed to accelerate join operations between related tables. Columns used in search filters such as product names, barcodes, and customer names received indexes improving lookup speeds. Composite indexes were considered for columns frequently queried together, such as date ranges in transaction queries. Database views provided convenient query interfaces for common data retrieval patterns, encapsulating join logic and calculated fields. For example, a sales summary view might join sales and sales details tables, calculate totals, and present results in formats convenient for reporting without requiring application code to repeatedly construct complex queries. Stored procedures encapsulated complex multi-step operations such as sales transaction processing, ensuring that all necessary database operations occurred atomically and consistently. Stored procedure usage also provided performance benefits by reducing network communication between application and database servers and enabling database query optimization. 3.7 Tools and Development Environment The development process utilized various software tools providing functionality for code editing, version control, database management, testing, and deployment. Tool selection considered factors including team familiarity, community support, compatibility with chosen technology stack, and cost given budget constraints typical of academic projects. Code editors with syntax highlighting, auto-completion, and debugging capabilities facilitated efficient development. Integrated development environments provided project management features organizing source files, configuration files, and resources in logical structures. Extensions and plugins added language-specific support, linting for code quality checking, and integration with version control systems. Version control systems maintained source code repositories enabling team collaboration, change tracking, and rollback capabilities. Distributed version control allowed team members to work independently on local copies, commit changes to shared repositories, and merge contributions. Branching capabilities enabled parallel development of different features while maintaining a stable main branch. Commit histories provided documentation of development progression and facilitated identification of when specific changes were introduced. Database management tools offered graphical interfaces for designing schemas, executing queries, viewing data, and performing administrative tasks. These tools complemented command-line interfaces particularly for exploratory data analysis, schema visualization, and quick data modifications during development. Query builders assisted in constructing complex SQL statements, reducing syntax errors. Browser developer tools integrated in modern web browsers enabled inspection of rendered HTML structures, CSS styling, JavaScript execution, network communications, and performance profiling. Console logging facilitated debugging of client-side code. Network inspection revealed API request and response details ensuring proper communication between frontend and backend. Performance profiling identified slow rendering operations or excessive resource consumption. Testing frameworks supported creation and execution of automated test suites validating that code behaved as specified. Unit testing frameworks enabled isolation of individual functions for focused testing. Integration testing frameworks facilitated testing of interactions between components. Test runners executed test collections and reported results summarizing passed and failed tests. Continuous execution of tests during development provided rapid feedback on whether changes introduced regressions..

Project management and issue tracking tools organized tasks, tracked progress, and facilitated team coordination. Backlogs listed pending work items with priorities and effort estimates. Sprint boards visualized current work distribution across team members and task states. Issue trackers recorded bugs, feature requests, and questions requiring resolution. Cloud hosting platforms provided deployment environments for the web application and database. Configuration dashboards enabled management of server instances, database instances, networking, and security settings. Deployment automation tools facilitated pushing updated code from development environments to production servers, reducing manual deployment steps and associated error risks..

Chapter #4 SYSTEM DESIGN 4.1 Introduction System design transforms requirements specifications into detailed blueprints guiding implementation activities. This chapter presents the architectural organization of ResellerCenter PK ERP system, describes the three-tier structure separating presentation, business logic, and data concerns, explains the user role hierarchy and associated permissions, and provides textual descriptions of Unified Modeling Language diagrams representing system structure and behavior. The design decisions documented here aimed to achieve modularity enabling independent development and maintenance of components, scalability supporting growing data volumes and user numbers, security protecting sensitive business information, and usability ensuring that target users can operate the system effectively. 4.2 Overall System Architecture The system architecture follows a three-tier model comprising the presentation tier responsible for user interaction, the application tier implementing business logic and processing, and the data tier managing persistent storage. This architectural pattern provides several advantages including separation of concerns where each tier has distinct responsibilities with well-defined interfaces to other tiers, independent scalability allowing resource allocation to specific tiers experiencing demand, and flexibility in technology selection for each tier based on appropriate criteria. 4.2.1 Presentation Tier The presentation tier encompasses all user interface components rendered in web browsers, implementing the visual layouts, interactive controls, and client-side behaviors visible to system users. This tier is constructed using HTML for structural markup, CSS for styling and layout, and JavaScript for dynamic client-side functionality. User interfaces are designed following responsive principles adapting to various screen sizes from desktop monitors through tablets to smartphones, ensuring usability across device types. Responsive layouts employ fluid grid systems where component widths adjust proportionally to available screen space, flexible images that scale appropriately, and media queries applying different styling rules based on device characteristics such as screen width. Client-side JavaScript enhances user experience through asynchronous communication with the application tier using AJAX techniques, enabling dynamic page updates without full page reloads. Form validation provides immediate feedback on user input errors before submission to the server, reducing round-trip communications and improving responsiveness. Interactive elements such as dropdown menus, modal dialogs, and dynamic table filtering are implemented in JavaScript providing fluid interactions. The presentation tier communicates with the application tier through HTTP requests, sending user inputs and receiving responses typically formatted as JSON data structures. JavaScript code processes these responses, updating the document object model to reflect new data without requiring complete page reloads. This approach creates more responsive interfaces approaching desktop application interaction patterns while retaining the accessibility and cross-platform compatibility advantages of web-based systems..

4.2.2 Application Tier The application tier contains server-side processing logic implementing business rules, coordinating data operations, managing user sessions, enforcing security policies, and generating dynamic responses to client requests. This tier is implemented using serverside scripting technologies running on web application servers. The architecture within the application tier follows the model-view-controller pattern organizing code into three conceptual components. Models represent business entities and encapsulate data access logic, providing object- oriented interfaces to database tables. Controllers receive requests from the presentation tier, coordinate necessary processing including invoking model methods to retrieve or manipulate data, apply business logic, and select appropriate views for response generation. Views are templates combining static HTML structures with dynamic data, rendering final HTML responses sent to clients. Session management tracks authenticated users across multiple requests, maintaining login states and user- specific context. When users authenticate, the application tier creates sessions identified by unique tokens stored in browser cookies. Subsequent requests include these tokens enabling the server to retrieve session information and verify user identity without requiring repeated authentication. Business logic implementation in controllers and helper functions executes operations including input validation ensuring user-provided data meets format and business rule requirements, transaction processing coordinating multi-step operations that must complete atomically, calculation algorithms computing financial totals, inventory adjustments, and report data, and authorization checks verifying that authenticated users have permissions for requested operations based on assigned roles. The application tier interacts with the data tier through database abstraction layers providing object-oriented interfaces to database operations, abstracting SQL query details from business logic code. This abstraction facilitates code maintainability and enables potential database platform changes with minimal impact on business logic. 4.2.3 Data Tier The data tier comprises the relational database management system storing all business information in structured tables with defined schemas, relationships, and constraints. This tier ensures data persistence, enforces referential integrity, provides transaction management supporting atomic operations, and executes queries retrieving and aggregating data for application tier requests. Database tables organized according to normalized schemas represent business entities including products, customers, suppliers, users, transactions, and configurations. Relationships between tables are enforced through foreign key constraints ensuring referential integrity. Primary key constraints guarantee unique row identification. Check constraints enforce domain restrictions such as positive values for quantities and prices. The database engine processes SQL queries submitted by the application tier, utilizing indexes to optimize query execution, maintaining transaction logs supporting rollback and recovery, and managing concurrent access through locking mechanisms ensuring that simultaneous operations do not corrupt data. Query optimization analyzes execution plans, selecting efficient strategies for joining tables, filtering records, and computing aggregates. Database procedures and triggers encapsulate complex operations or enforce business rules at the data tier level. For example, triggers might automatically update aggregate values such as customer account balances when transactions are inserted, ensuring consistency between transactional details and summary balances without requiring application code to explicitly update multiple locations..

Backup and recovery mechanisms protect against data loss through scheduled backup operations capturing database snapshots, transaction log backups enabling point-in-time recovery, and replication configurations maintaining redundant copies of data on separate servers for disaster recovery. These mechanisms ensure business continuity in the event of hardware failures, software defects, or user errors. 4.3 User Roles and Permission Hierarchy The system implements role-based access control defining distinct user categories with specific permission sets aligned to organizational responsibilities. This approach simplifies user administration by grouping permissions into roles and assigning users to appropriate roles rather than managing individual permissions for each user. Role definitions balance operational efficiency by granting necessary access against security requirements limiting access to minimize breach risks and ensure accountability. 4.3.1 Administrator Role Administrators possess comprehensive system access including all operational functionalities plus administrative capabilities unavailable to other roles. Administrator responsibilities include user account management encompassing creation of new user accounts, assignment of usernames and initial passwords, role assignment determining user permission levels, account status management enabling or disabling accounts, and password reset capabilities assisting users who forget credentials. System configuration tasks reserved for administrators include defining product categories, expense categories, tax rates, and other reference data used throughout the system. Administrators may perform any operational function performed by managers or cashiers, enabling administrators to troubleshoot issues, provide user training, or cover operational duties when necessary. Administrators access audit logs reviewing user activities, investigating discrepancies, and ensuring compliance with operational policies. Backup management and system maintenance activities fall under administrator purview, though in cloud-hosted deployments some infrastructure tasks are handled by hosting providers. The administrator role is typically assigned to business owners or senior managers who require complete visibility and control. The number of administrator accounts should be limited to minimize security exposure from compromised credentials. 4.3.2 Manager Role Managers have extensive operational access including most day-to-day business functions but lack administrative capabilities that could alter system configurations or user accounts. Manager permissions include complete access to inventory management functions enabling product registration, stock adjustments, and reorder level configuration. Managers can create and modify customer and supplier records, facilitating relationship management. Sales transaction processing is available to managers, though this function is primarily performed by cashiers. Managers may process sales when assisting with busy periods or training purposes. Comprehensive reporting access enables managers to view financial statements, inventory reports, sales analytics, and customer reports, supporting managerial decision-making and business oversight..

Managers can create purchase orders, record goods receipts, and enter supplier payments, managing procurement processes. Expense recording capabilities enable managers to document business costs. Managers cannot modify user accounts, alter system configurations, or access audit logs beyond viewing their own activity histories. The manager role suits supervisors, senior staff, or business partners requiring operational authority and reporting visibility without full administrative control. Manager permissions balance operational flexibility with appropriate limitations preventing unauthorized system modifications. 4.3.3 Cashier Role Cashiers have restricted access focused on customer-facing sales operations, representing the minimum permissions required for transaction processing. Cashier permissions include point-of-sale access for processing sales transactions, selecting products, specifying quantities, receiving payments, and printing invoices. Cashiers can view product information including prices and current stock levels necessary for informed sales interactions but cannot modify product records. Customer record viewing enables cashiers to access customer information for credit sales and customer service purposes. Cashiers may record customer payments reducing outstanding balances. However, cashiers cannot create or modify customer accounts, limiting potential for unauthorized credit limit changes or account manipulation. Cashiers cannot access financial reports beyond viewing their own transaction histories, protecting sensitive business performance information from disclosure to all employees. Inventory management, purchase order creation, expense recording, and administrative functions are unavailable to cashiers, enforcing operational segregation and limiting potential impacts of compromised cashier accounts. The cashier role is assigned to frontline sales staff, temporary employees, or situations where transaction processing access is needed without broader system exposure. The restricted permission set minimizes training requirements for cashier role users and limits security risks from the typically higher turnover rates in customer- facing positions. 4.3.4 Permission Enforcement Mechanism Permission enforcement occurs at multiple levels providing defense in depth. Clientside permission checking in the presentation tier hides or disables interface elements for which the user lacks permissions, preventing confusion and unsuccessful operation attempts. However, client-side enforcement alone is insufficient as users could potentially manipulate client code to bypass restrictions. Server-side permission verification in the application tier checks user roles before executing operations, rejecting requests for unauthorized actions regardless of client-side interface states. When requests arrive at controller actions, authentication middleware verifies that a valid user session exists. Authorization middleware then checks whether the authenticated user’s role includes permissions for the requested operation. Unauthorized requests result in error responses or redirects to appropriate pages. Database-level security complements application-tier authorization. Database user accounts used by application code have grants limited to necessary operations. Sensitive tables or columns may have additional access restrictions. While application code typically mediates all database access, database-level controls provide additional protection against SQL injection vulnerabilities or unauthorized direct database access..

4.4 Unified Modeling Language Diagrams Unified Modeling Language provides standardized graphical notations for representing software system designs at various abstraction levels. This section describes key UML diagrams documenting system structure and behavior, explaining the content and relationships depicted in each diagram type. 4.4.1 Use Case Diagram Use case diagrams represent system functionality from user perspectives, identifying actors interacting with the system and the use cases representing distinct functional capabilities available to actors. In the context of ResellerCenter PK ERP, actors include Cashier, Manager, and Administrator representing the defined user roles, along with external systems such as potentially future integrations with payment gateways or e-commerce platforms. Major use cases for the Cashier actor include Process Sale representing the complete workflow of selecting products, calculating totals, receiving payment, and generating invoices. View Product Information enables cashiers to look up product details, prices, and availability. Record Customer Payment allows cashiers to apply payments to customer accounts. These use cases reflect the cashier’s primary responsibility of customer-facing sales transactions. Manager actor interacts with broader use cases including Manage Inventory encompassing product registration, stock adjustments, and inventory tracking. Manage Customers covers customer profile creation and modification. Manage Suppliers handles supplier information and relationships. Create Purchase Order and Record Goods Receipt represent procurement workflows. Record Expense documents business costs. Generate Reports produces various analytical outputs for management review. Process Sale is also available to managers, indicated by relationship links to the same use case available to cashiers. Administrator actor accesses all manager use cases plus additional administrative functions represented as Manage Users for user account administration, Configure System for setting business parameters like tax rates and categories, and View Audit Logs for reviewing system activities. Relationships between use cases indicate commonalities and variations. Include relationships show that certain use cases always incorporate others; for example, Process Sale includes Calculate Transaction Total as an essential sub-function. Extend relationships indicate optional behaviors; for example, Process Sale might extend to Apply Discount when discount scenarios occur. Generalization relationships show specialization, such as specific report types like Sales Report and Inventory Report representing specializations of the general Generate Reports use case. The use case diagram provides a high-level overview of system capabilities organized by user roles, facilitating discussions with stakeholders about functional scope and serving as a requirements validation tool ensuring all necessary capabilities are represented. 4.4.2 Activity Diagram Activity diagrams model workflows showing sequences of activities, decisions, and parallel processes. Activity diagrams for ResellerCenter PK ERP illustrate key business processes implemented in the system. The Sales Transaction Processing activity diagram begins with a start node and flows through the sequence of activities performed during a sale. The first activity is Select Products where the cashier or manager searches for and adds products to the current transaction. This activity may repeat multiple times as multiple products are added, represented by a loop in the activity flow..

Following product selection, the activity Calculate Totals computes subtotals, applies taxes, and determines the final amount payable. A decision node checks whether the calculated total is approved by the user. If not approved, flow returns to the Select Products activity allowing modifications. If approved, flow proceeds to the Enter Payment Information activity capturing payment method and amount. Another decision node determines if the payment is cash or credit. For cash payments, the workflow proceeds directly to the Complete Sale activity. For credit sales, a parallel branch verifies that the customer has sufficient credit limit available. If the credit check fails, flow returns to Enter Payment Information to select an alternative payment method. If the credit check passes, flow merges back to Complete Sale. The Complete Sale activity atomically commits the transaction, updating sales records, inventory quantities, customer balances if applicable, and generating the invoice. After successful completion, flow reaches the end node. Error handling is represented through exception flows branching from activities where errors might occur. For example, insufficient inventory detected during Calculate Totals triggers an exception flow informing the user and returning to Select Products for adjustment. Activity diagrams for other processes such as Purchase Order Creation, Goods Receipt Processing, and Report Generation follow similar patterns, depicting sequences of activities, decision points based on conditions, parallel or alternative flows, and appropriate error handling pathways. These diagrams help team members understand process logic and serve as blueprints for implementation. 4.4.3 Sequence Diagram Sequence diagrams depict interactions between system objects over time, showing the sequence of messages exchanged to accomplish specific functionality. These diagrams complement activity diagrams by focusing on object interactions rather than control flow. The Sales Transaction Processing sequence diagram shows temporal interactions between presentation tier objects such as the Point of Sale Interface, application tier objects including the Sales Controller and Inventory Model, and data tier representations such as the Database. The diagram’s vertical axis represents time progressing downward, while horizontal arrangement represents different participating objects. The sequence begins when the User initiates the transaction in the POS Interface. The interface sends a message to the Sales Controller requesting initiation of a new sale. The controller creates a temporary sale object in memory for accumulating selected products. As the user selects products, the POS Interface sends Add Product messages to the Sales Controller including product identifiers and quantities. For each product addition, the controller queries the Inventory Model to verify stock availability and retrieve current prices. The Inventory Model queries the Database, receives results, and returns product information to the controller. The controller adds the product to the in-progress sale and returns confirmation to the interface, which updates the displayed item list and running total. When the user completes product selection, the interface sends a Calculate Total message to the controller. The controller computes subtotals, taxes, and final totals using business logic methods and returns the calculated amounts to the interface for display..