ASP.

NET Core-Full Stack-

Inventory WMS:
Back End with REST API, Clean
Architecture, CQRS, Repository &
Front End with Razor Pages,
JavaScript (VueJS)

1st Edition - 2025

© 2025 go2ismail@gmail.com
© 2025 go2ismail@gmail.com

ASP.NET Core – Full

Stack – Inventory WMS:
Back End with REST API, Clean Architecture,
CQRS, Repository & Front End with Razor
Pages, JavaScript (VueJS)

1st Edition - 2025

©2025 go2ismail@gmail.com – 1st Edition

The software and its source code are available for purchase.
Feel free to contact us at the email below:

hi@indotalent.com

©2025 go2ismail@gmail.com – 1st Edition

Contents
1. Introduction .................................................................................................................................... 7
1.1 Technology Stack ..................................................................................................................... 8
1.2 Getting Started Guide ............................................................................................................. 9
2. Technical ............................................................................................................................................ 10
2.1 Full Stack Web Development ...................................................................................................... 10
2.2 Back End ...................................................................................................................................... 11
2.2.1 ASP.NET Core Web REST API................................................................................................. 11
2.2.2 Clean Architecture................................................................................................................ 12
2.2.3 CQRS with MediatR .............................................................................................................. 13
2.2.4 Repository ............................................................................................................................ 14
2.3 Front End ..................................................................................................................................... 15
2.3.1 ASP.NET Razor Pages ............................................................................................................ 16
2.3.2 JavaScript with VueJS ........................................................................................................... 17
3. Functional.......................................................................................................................................... 18
3.1 Introduction to Inventory WMS .................................................................................................. 18
3.2 Sales Modules ............................................................................................................................. 19
3.2.1 Customer Group ................................................................................................................... 19
3.2.2 Customer Category .............................................................................................................. 20
3.2.3 Customer .............................................................................................................................. 21
3.2.4 Customer Contact ................................................................................................................ 22
3.2.5 Sales Order ........................................................................................................................... 23
3.2.6 Sales Report ......................................................................................................................... 24
3.3 Purchase Modules ....................................................................................................................... 25
3.3.1 Vendor Group ....................................................................................................................... 25
3.3.2 Vendor Category .................................................................................................................. 26
3.3.3 Vendor .................................................................................................................................. 27
3.3.4 Vendor Contact .................................................................................................................... 28
3.3.5 Purchase Order .................................................................................................................... 29
3.3.6 Purchase Report ................................................................................................................... 30
3.4 Inventory Modules ...................................................................................................................... 31
3.4.1 Unit Measure ....................................................................................................................... 31
3.4.2 Product Group ...................................................................................................................... 32
3.4.3 Product ................................................................................................................................. 33
3.4.4 Warehouse ........................................................................................................................... 34
3.4.5 Delivery Order ...................................................................................................................... 35

©2025 go2ismail@gmail.com – 1st Edition

 3.4.6 Sales Return ......................................................................................................................... 36
3.4.7 Goods Receive ...................................................................................................................... 37
3.4.8 Purchase Return ................................................................................................................... 38
3.4.9 Transfer Out.......................................................................................................................... 39
3.4.10 Transfer In .......................................................................................................................... 40
3.4.11 Positive Adjustment ........................................................................................................... 41
3.4.12 Negative Adjustment.......................................................................................................... 42
3.4.13 Scrapping ............................................................................................................................ 43
3.4.14 Stock Count ........................................................................................................................ 44
3.4.15 Transaction Report ............................................................................................................. 45
3.4.16 Stock Report ....................................................................................................................... 46
3.4.17 Movement Reports ............................................................................................................ 47
3.5 Utilities ........................................................................................................................................ 48
3.5.1 Booking Group ..................................................................................................................... 48
3.5.2 Booking Resource ................................................................................................................. 49
3.5.3 Booking Manager ................................................................................................................. 50
3.5.4 Booking Scheduler ............................................................................................................... 51
3.5.5 Program Resource ................................................................................................................ 52
3.5.6 Program Manager ................................................................................................................ 53
3.5.7 Program Kanban ................................................................................................................... 54
3.6 Membership ................................................................................................................................ 55
3.6.1 Users..................................................................................................................................... 55
3.6.2 Roles ..................................................................................................................................... 56
3.7 Profiles ........................................................................................................................................ 57
3.7.1 My Profile ............................................................................................................................. 57
3.8 Settings ........................................................................................................................................ 58
3.8.1 My Company ........................................................................................................................ 58
3.8.2 Tax ........................................................................................................................................ 59
3.8.3 Number Sequence................................................................................................................ 60

©2025 go2ismail@gmail.com – 1st Edition

©2025 go2ismail@gmail.com – 1st Edition
1. Introduction

This book serves as a comprehensive guide for developing an Inventory WMS application using
ASP.NET Core within a full-stack development approach. The application is meticulously crafted as a
Visual Studio solution, divided into two major sections: the Back End and the Front End. Each section
plays a crucial role in creating a seamless and efficient inventory management system, offering readers
a deep dive into modern web development practices.

The Back End is built as a Web REST API using ASP.NET Core Controllers. It adheres to the principles of
clean architecture, ensuring a scalable and maintainable codebase. The Command Query
Responsibility Segregation (CQRS) pattern is implemented using MediatR, providing a clear separation
between data modification and retrieval processes. Additionally, the repository pattern is employed to
streamline data access and ensure consistent interaction with the database. Together, these patterns
and principles establish a robust foundation for the application's server-side functionality.

The Front End leverages ASP.NET Core Razor Pages, enhanced with JavaScript and VueJS to create a
dynamic and responsive user interface. To deliver a professional and enterprise-grade experience, the
Syncfusion Community Edition is utilized for advanced controls such as grids, pivot tables, schedulers,
and kanban boards. Notably, Syncfusion Community Edition is free, making it an excellent choice for
developers aiming to build feature-rich applications without incurring additional costs. This
combination of technologies ensures a cohesive and highly functional application that meets the
demands of modern inventory management.

©2025 go2ismail@gmail.com – 1st Edition

1.1 Technology Stack

This application leverages a range of modern technologies to ensure scalability, maintainability, and a
professional user experience. Each tool and framework has been carefully selected to provide an
optimal development and runtime environment for the Inventory WMS system. Below is a list of the
key technologies used in this project:

• Visual Studio Community 2022: An integrated development environment (IDE) used for
building and managing the entire solution.

• Microsoft SQL Server: A robust relational database management system for storing and
managing data.

• ASP.NET Core 9.0: A modern, high-performance framework for building web applications and
APIs.

• C#: The primary programming language used to develop the Back End.

• Clean Architecture: A design principle employed to ensure a clear separation of concerns

and maintainable code.

• CQRS with MediatR: Implements the Command Query Responsibility Segregation pattern to
separate command and query responsibilities, enhancing clarity and scalability.

• HTML / CSS / JavaScript / VueJS: Used to create a dynamic and responsive user interface for
the Front End.

• Syncfusion: A suite of enterprise-grade UI controls, such as grids, pivot tables, schedulers,

and kanban boards, provided under the free Community Edition.

©2025 go2ismail@gmail.com – 1st Edition

1.2 Getting Started Guide

To get started with the source code, ensure your development machine meets the following
prerequisites:

1. A computer running Windows OS.

2. Visual Studio Community 2022.

3. Microsoft SQL Server (Express Edition is sufficient).

Once the development machine meets these prerequisites, follow these steps to run the Inventory
WMS application directly from the source code using Visual Studio Community 2022:

1. Unzip the source code.

2. Open the Inventory WMS solution using Visual Studio Community 2022.

3. Update the DefaultConnection string in the configuration file to point to your Microsoft SQL
Server (SQL Server Express is sufficient).

4. Run the application by pressing F5 or navigating to Debug > Start Debugging. The database
will be automatically created, and the Inventory WMS application will launch in your default
web browser.

Below are the credentials for logging in:

Email: admin@root.com

Password: 123456

The online demo can be accessed through: https://wms-fs-vue.csharpasp.net/

©2025 go2ismail@gmail.com – 1st Edition

2. Technical

2.1 Full Stack Web Development

The solution for this application is designed as an ASP.NET Core full-stack web development project
contained within a single solution with a multi-layered architecture. This architecture ensures clear
separation of concerns and maintainability. The Back End is implemented as a Web REST API developed
using the controller-based approach. It is worth noting that Microsoft currently supports two methods
for building REST APIs: the traditional controller-based approach and the newer minimal API approach.
For this solution, the controller-based method has been chosen as it aligns well with the clean
architecture principles adopted in this project. The clean architecture is further enhanced with the use
of CQRS (Command Query Responsibility Segregation) via MediatR, which ensures clear separation of
commands and queries, and the repository pattern for efficient data access management.

The Front End is built using ASP.NET Core Razor Pages, which generates server-side HTML. To provide
a dynamic and rich user interface experience, VueJS is utilized for handling client-side interactions. This
combination of server-side rendering with Razor Pages and client-side enhancements using VueJS
ensures a seamless and responsive user experience while maintaining simplicity and flexibility in
development.

©2025 go2ismail@gmail.com – 1st Edition

2.2 Back End
2.2.1 ASP.NET Core Web REST API

The solution will produce two applications: an ASP.NET Web REST API and an ASP.NET Web Application.
The Web REST API is developed using ASP.NET Core with a controller-based approach. This approach
leverages controllers primarily for routing API endpoints, ensuring that their responsibility is limited to
directing requests to the appropriate application layer components. By adopting this methodology, the
controllers remain minimalistic, containing only concise and compact code that handles routing logic.

In this design, no business process logic is written in the controllers. Instead, all business operations
are encapsulated within the application layer, which processes incoming requests and returns
appropriate responses. This separation of concerns aligns with the principles of clean architecture,
promoting maintainability and scalability by isolating business logic from the API routing layer.

As a result, the controllers in the Web REST API serve as lightweight entry points, ensuring clarity and
simplicity in the API design. This structure not only streamlines the development process but also
enhances code readability and reusability across the project.

©2025 go2ismail@gmail.com – 1st Edition

2.2.2 Clean Architecture

Clean architecture, introduced by Robert C. Martin, also known as Uncle Bob, provides guidance on
dependency management within a project. The core principle of clean architecture is that the
innermost layers of a system should remain independent and free from dependencies on outer layers.
Following this principle, the solution is structured into multiple projects, each representing a distinct
layer of the clean architecture model. These layers, ordered from innermost to outermost, are Domain,
Application, Infrastructure, and Presentation.

The Domain layer is implemented within the Domain project and focuses on defining the core entities
of the application. The Application layer resides in the Application project and is dedicated to
implementing business processes, referred to as Features, using the Command Query Responsibility
Segregation (CQRS) pattern. This layer leverages MediatR to handle commands and queries effectively.
The Infrastructure layer, contained within the Infrastructure project, manages external dependencies
such as databases and email services.

Finally, the Presentation layer is implemented within an ASP.NET project that serves as both a Web API
and a Web Application. The Web API uses a controller-based approach for routing and interacting with
the Application layer. For simplicity, both the Web API and the Web Application are combined into a
single project. However, this design is flexible enough to allow the separation of these components
into distinct projects that can be deployed on different servers if needed.

©2025 go2ismail@gmail.com – 1st Edition

2.2.3 CQRS with MediatR

The Application layer, encapsulated within the Application project, serves as the core of all business
processes in the solution. This layer is intentionally designed to be thicker than the other layers, as it
consolidates and centralizes all business logic. By doing so, it ensures that the business processes are
well-structured and separated from concerns like infrastructure and presentation.

Business processes within the Application layer are categorized into two primary groups: data retrieval
and data modification. All activities related to data retrieval are organized under the Queries folder,
while those involving data modification are grouped under the Commands folder. This separation
aligns with the Command Query Responsibility Segregation (CQRS) pattern, which simplifies the
architecture by clearly distinguishing between read and write operations.

To streamline the implementation of CQRS, the project leverages MediatR, a third-party library
developed by Jimmy Bogard, who is also known for creating AutoMapper. MediatR provides a
straightforward mechanism to handle commands and queries through a mediator pattern, enhancing
maintainability and reducing dependencies between components in the application. By adopting
MediatR, the Application layer becomes more modular and easier to extend.

©2025 go2ismail@gmail.com – 1st Edition

2.2.4 Repository

The Infrastructure layer serves as the foundation for handling external resources such as databases,
email services, and other third-party integrations. This layer centralizes all code related to external
dependencies, ensuring that resource access is organized and maintainable. By isolating these
operations, the Infrastructure layer enables better separation of concerns and promotes the principles
of Clean Architecture.

For data access to the database, the repository pattern is employed within the Infrastructure layer. The
repository pattern acts as a mediator between the domain and data mapping layers, providing a
consistent and controlled approach to data persistence. This approach is particularly beneficial for the
Command operations in the CQRS architecture, where it ensures that data insertion and modification
follow a standardized and reliable process. By encapsulating database logic within repositories, the
application gains better maintainability and flexibility, as changes to the data access logic can be made
without affecting the higher layers of the application.

On the other hand, Queries are designed to be as simple and fast as possible. To achieve this, direct
access to the database context is granted for read operations, bypassing the repository pattern. This
approach provides the freedom to optimize queries for performance and even allows the flexibility to
replace the underlying technology with alternatives like Dapper for improved speed and efficiency in
data retrieval. By distinguishing the handling of Commands and Queries in this manner, the application
achieves a balance between consistency in data modification and performance in data retrieval.

©2025 go2ismail@gmail.com – 1st Edition

2.3 Front End

The back-end application is implemented as a Web REST API, providing endpoints designed to be
consumed by other programs or systems, rather than directly by human users. These endpoints act as
the backbone of the application, enabling data retrieval, creation, modification, and deletion in a
structured and programmatically accessible manner. The Web REST API ensures that the business logic
and data processing are handled securely and efficiently, while adhering to the principles of clean
architecture and separation of concerns.

On the other hand, the front-end application is a web-based user interface designed specifically for
human users to interact with the system. It bridges the gap between the underlying application logic
and the users by offering an intuitive and user-friendly interface. Through the front-end, users can
perform various tasks, such as viewing data, creating new entries, or modifying existing ones, without
needing to understand the underlying complexity of the back-end processes.

In this architecture, the front-end application acts as both a consumer of the Web REST API and a
provider of a visual and interactive interface for users. It sends requests to the back-end API to fetch
or persist data and then displays the results to the user in an accessible format. At the same time, it
collects user inputs, processes them, and sends them back to the API for further action. This dual role
ensures that the application remains functional and efficient while delivering a seamless experience
for human users.

©2025 go2ismail@gmail.com – 1st Edition

2.3.1 ASP.NET Razor Pages

The front-end is developed using ASP.NET Core Razor Pages, combined with JavaScript and VueJS to
create a dynamic and interactive user experience. Razor Pages is a server-side web framework that
generates HTML on the server and serves it to the client. This approach provides a structured and
predictable way to manage the application’s UI while taking advantage of server-side rendering for
improved performance. By using Razor Pages, each page in the application is tied to a physical file,
making it intuitive to define URL routing based on the file structure. This simplicity significantly
enhances the development process, allowing developers to easily organize and locate code.

Once the server-side-generated HTML is delivered to the browser, VueJS is used to enrich the interface
with client-side interactivity. VueJS, a progressive JavaScript framework, simplifies the creation of user
interfaces by providing a reactive and composable view layer. It enhances DOM manipulation, event
handling, and data binding, allowing developers to add dynamic behaviors to the pages, such as real-
time form validation, interactive menus, and smooth animations, with a more structured and
component-based approach. Moreover, VueJS integrates well with Razor Pages, enabling the front-
end to dynamically interact with the back-end Web REST API for data retrieval and updates without
requiring full-page reloads.

The combination of Razor Pages and VueJS strikes a balance between server-side rendering and client-
side interactivity, resulting in a scalable and user-friendly web application. Razor Pages ensures clean,
maintainable, and structured server-side code, while VueJS provides the flexibility to enhance the user
experience on the client side with its component-based architecture. This hybrid approach ensures
that the front-end not only delivers a robust interface but also remains responsive and engaging for
end-users.

©2025 go2ismail@gmail.com – 1st Edition

2.3.2 JavaScript with VueJS

The front end, as the final application interface, serves two primary purposes: providing a user-friendly
interface for human users and consuming application features exposed through the Web REST API.
JavaScript, powered by VueJS, plays a pivotal role in achieving both objectives efficiently. For the user
interface, VueJS enhances interactivity, enabling the development of a more dynamic and responsive
UI. With VueJS, developers can harness the power of component-based architecture, state
management with Vuex, and reactive data binding. This approach leads to an engaging and seamless
user experience that feels modern and intuitive. VueJS components can be easily reused, ensuring
consistency across different parts of the application, and its templating system makes it
straightforward to manage complex UI logic.

When it comes to consuming application features via the Web REST API, JavaScript and VueJS offer
unparalleled flexibility and simplicity. VueJS natively supports integration with libraries for HTTP
requests like Axios, enhancing the way interactions with the Web REST API are managed. For instance,
a custom Axios integration within VueJS can include interceptors for managing token-based
authentication seamlessly. If a JWT token expires, the interceptor can automatically request a new
token, then retry the original API call. This setup ensures uninterrupted communication between the
front end and back end while maintaining a secure and efficient authentication flow. Vue's reactivity
system also allows for immediate UI updates when API responses are received, providing a smooth
user experience.

Even though the server-side rendering is handled by ASP.NET Core Razor Pages, no direct access to the
application layer is allowed. Instead, all application features are accessed exclusively via the Web REST
API. This separation enforces a clean architectural boundary and ensures that the same Web REST API
can be reused for other front-end implementations, such as native Android or iOS applications. VueJS
supports this architecture beautifully with its ability to be used for SSR (Server-Side Rendering) with
frameworks like Nuxt.js, or as a lightweight client-side framework, thus providing versatility in how the
front end can be developed. This design demonstrates the flexibility and scalability of the architecture,
as it allows the application to evolve beyond a single front-end platform without requiring changes to
the underlying back end.

©2025 go2ismail@gmail.com – 1st Edition

3. Functional
3.1 Introduction to Inventory WMS

Inventory WMS is a full-stack application built using ASP.NET Core. The back end consists of a Web
REST API developed with ASP.NET Core utilizing a controller-based approach, while the front end is a
web application created with ASP.NET Core Razor Pages. This combination provides a robust
architecture, leveraging the strengths of server-side rendering for structured HTML generation and
dynamic client-side interactions using JavaScript and jQuery. Together, these components create a
seamless experience for managing inventory and warehouse operations.

The Inventory WMS application is designed to meet the essential requirements of efficient inventory
and warehouse management. It offers a comprehensive set of features grouped into several key
modules. The Sales Module allows businesses to manage customer orders and sales transactions,
while the Purchase Module handles supplier orders and procurement processes. The Inventory
Module is at the heart of the application, providing tools for stock tracking, warehouse organization,
and inventory adjustments.

In addition to core functionalities, the application includes supplementary modules for enhanced
usability. The Utilities Module offers various tools to assist with day-to-day operations, and the
Membership Module enables the management of user roles and permissions. Finally, the Profile and
Settings Modules allow administrators and users to configure preferences and maintain application
settings. These modular components work together to provide a professional-grade solution tailored
for businesses requiring comprehensive inventory and warehouse management.

©2025 go2ismail@gmail.com – 1st Edition

3.2 Sales Modules
3.2.1 Customer Group

The Customer Group feature is an integral part of the Sales Module. Its primary purpose is to allow
businesses to categorize customers into specific groups, such as Military, Government, Hospitality,
Foundation, Education, and Corporate. By grouping customers in this way, the system provides a
structured approach to managing customer data, enabling businesses to better organize and analyze
their customer base.

This grouping is especially beneficial when creating customer master data. Assigning customers to
predefined groups ensures that relevant insights can be gained during data analysis, particularly for
sales trends, performance reports, and targeted marketing strategies. The Customer Group
functionality empowers businesses to make data-driven decisions and tailor their approach to meet
the unique needs of each customer segment.

©2025 go2ismail@gmail.com – 1st Edition

3.2.2 Customer Category

The concept of Customer Category, as part of the sales module, provides the ability to categorize
customers based on their specific interests or characteristics. This categorization can be customized to
suit the business's needs, with examples such as Startup, Small, Medium, Micro, and Enterprise.
Similar to Customer Groups, Customer Categories play a vital role during the creation of master
customer data, enabling businesses to analyze their customer base more effectively. By classifying
customers into distinct categories, companies can better understand their target market, optimize
their sales strategies, and deliver tailored products or services that align with the specific needs of
each category. This categorization system will also assist in targeted marketing and forecasting,
enhancing overall decision-making.

©2025 go2ismail@gmail.com – 1st Edition

3.2.3 Customer

Customers are a crucial component of the sales module, and the primary objective of the customer
feature is to create a well-structured master customer database. By ensuring that customer data is
collected in an organized manner, businesses can maximize the utility of this data for future analysis
and decision-making. Key information from related features, such as Customer Groups and Customer
Categories, can be incorporated into the master customer record, helping to classify and better
understand each customer’s profile. This comprehensive approach ensures that businesses have a
solid foundation for managing customer relationships.

The master customer data can also be used to record essential customer details, such as full address
information, including street, city, state, zip code, and country. Additionally, it allows businesses to
capture communication details, including phone numbers, email addresses, and social media
accounts. This information is vital for effective customer engagement and communication, enabling
businesses to stay connected with their customers through the preferred channels. By maintaining
accurate and detailed customer records, companies can enhance customer service, streamline
processes, and foster stronger customer relationships.

©2025 go2ismail@gmail.com – 1st Edition

3.2.4 Customer Contact

Customer Contact is a key feature within the sales module, primarily designed to record all contact
persons associated with a specific customer. This functionality helps streamline customer relationship
management by maintaining a clear record of who the primary contacts are for each customer. It
ensures that businesses can easily access the necessary information when they need to reach out to
the right individuals, whether for sales inquiries, support requests, or other business matters.

By utilizing the Customer Contact feature, organizations gain a better understanding of the responsible
parties for each customer, which improves communication efficiency. This becomes especially valuable
when managing multiple accounts, as it eliminates confusion regarding the main point of contact. With
this feature, sales and customer service teams can quickly identify the appropriate person to contact,
ensuring smoother interactions and more effective problem-solving, ultimately enhancing the overall
customer experience.

©2025 go2ismail@gmail.com – 1st Edition

3.2.5 Sales Order

Sales Order is an essential component of the sales module, designed to facilitate the creation of
customer orders. The primary function of this feature is to capture vital information such as the
customer details, order status, and tax information. This helps ensure that all relevant order data is
properly recorded and accessible. Sales orders can be efficiently created, with the ability to easily input
a variety of items, including product descriptions, quantities, and prices, making the process
streamlined and user-friendly.

Once the sales order is completed, it can be generated into a PDF format, allowing businesses to create
a hard copy of the order for physical documentation or customer distribution. This feature simplifies
the sales process by providing a reliable and consistent method for managing customer orders,
ensuring that both the sales team and customers have access to accurate and up-to-date order details.
It also enhances operational efficiency by reducing the need for manual record-keeping and providing
a standardized format for all sales orders.

©2025 go2ismail@gmail.com – 1st Edition

3.2.6 Sales Report

Sales Report is a key feature within the sales module, designed to display sales data in a grid format.
The report groups the information by sales order number, making it easy to track and analyze multiple
orders at once. Below each group, the order details are displayed, providing a clear and concise view
of the sales activities. This organization allows users to quickly identify relevant information without
having to navigate through complex data sets, improving efficiency and accuracy.

Additionally, the grid format can be downloaded as an Excel file, enabling users to perform more in-
depth analysis or generate custom reports. This feature allows businesses to easily export sales data
for further examination, offering flexibility for reporting and decision-making processes. By providing
the ability to download and manipulate the data, the sales report feature supports better insights into
sales performance, trends, and areas for improvement.

©2025 go2ismail@gmail.com – 1st Edition

3.3 Purchase Modules
3.3.1 Vendor Group

The Vendor Group feature is a crucial component of the procurement module. Its main function is to
categorize vendors into specific groups, such as Freelancer, Service Provider, Distributor, Supplier, and
Manufacturer. By grouping vendors in this way, the system helps businesses manage vendor data more
efficiently, providing a clear structure for organizing and analyzing their vendor relationships. This
feature enables businesses to streamline vendor management and improve procurement processes.

Similar to customer grouping, categorizing vendors into predefined groups is particularly useful when
creating vendor master data. It allows businesses to gain valuable insights during data analysis, such
as evaluating vendor performance, optimizing purchasing decisions, and identifying opportunities for
cost reduction. The Vendor Group functionality ensures that businesses can make informed, strategic
decisions that align with their procurement goals and meet the specific needs of each vendor category.

©2025 go2ismail@gmail.com – 1st Edition

3.3.2 Vendor Category

The concept of Vendor Category, as part of the procurement module, allows businesses to categorize
their vendors based on specific characteristics or operational scale. This categorization can be
customized to fit the needs of the organization, with examples such as Small, Local, Medium, Global,
and Large. Similar to Vendor Groups, Vendor Categories are essential when creating vendor master
data, as they provide businesses with the ability to analyze and manage their vendor relationships
more efficiently. By organizing vendors into distinct categories, companies can better understand the
range of suppliers they work with and tailor their procurement strategies accordingly.

Categorizing vendors in this way also helps in strategic decision-making, as it enables businesses to
evaluate their vendors based on size, reach, or geographic focus. This classification system allows
companies to assess vendor performance, streamline purchasing processes, and identify opportunities
for cost optimization or diversification. By grouping vendors into relevant categories, businesses can
also enhance forecasting, risk management, and vendor negotiations, leading to improved overall
procurement outcomes.

©2025 go2ismail@gmail.com – 1st Edition

3.3.3 Vendor

Vendors are a vital component of the procurement module, and the primary objective of the vendor
feature is to create a well-structured master vendor database. By ensuring that vendor data is collected
in an organized manner, businesses can fully utilize this data for future analysis and decision-making.
Essential information from related features, such as Vendor Groups and Vendor Categories, can be
integrated into the master vendor record, helping to classify and better understand each vendor’s
profile. This comprehensive approach ensures that businesses have a solid foundation for managing
vendor relationships effectively.

The master vendor data can also be used to record essential vendor details, such as full address
information, including street, city, state, zip code, and country. Additionally, it allows businesses to
capture communication details, such as phone numbers, email addresses, and social media accounts.
This information is crucial for efficient vendor engagement and communication, enabling businesses
to stay connected with their vendors through preferred channels. By maintaining accurate and detailed
vendor records, companies can enhance procurement processes, streamline operations, and build
stronger vendor partnerships.

©2025 go2ismail@gmail.com – 1st Edition

3.3.4 Vendor Contact

Vendor Contact is a key feature within the procurement module, primarily designed to record all
contact persons associated with a specific vendor. This functionality helps streamline vendor
management by maintaining a clear record of who the primary contacts are for each vendor. It ensures
that businesses can easily access the necessary information when they need to reach out to the right
individuals, whether for procurement inquiries, contract negotiations, or other vendor-related
matters.

By utilizing the Vendor Contact feature, organizations gain a better understanding of the responsible
parties for each vendor, which improves communication efficiency. This becomes especially valuable
when managing multiple suppliers, as it eliminates confusion regarding the main point of contact. With
this feature, procurement teams can quickly identify the appropriate person to contact, ensuring
smoother interactions, faster decision-making, and more effective problem-solving, ultimately
enhancing the overall vendor relationship and procurement process.

©2025 go2ismail@gmail.com – 1st Edition

3.3.5 Purchase Order

Purchase Order is an essential component of the procurement module, designed to facilitate the
creation of purchase requests from vendors. The primary function of this feature is to capture key
information such as vendor details and order status. This ensures that all relevant order data is
accurately recorded and easily accessible. Purchase orders can be efficiently created, with the ability
to input a variety of items, including product descriptions, quantities, and prices, making the process
streamlined and user-friendly for procurement teams.

Once the purchase order is completed, it can be generated into a PDF format, enabling businesses to
create a hard copy for physical documentation or vendor distribution. This feature simplifies the
procurement process by providing a reliable and consistent method for managing purchase orders,
ensuring that both the procurement team and vendors have access to accurate and up-to-date order
details. It also enhances operational efficiency by reducing the need for manual record-keeping and
offering a standardized format for all purchase orders, helping to improve the overall purchasing
workflow.

©2025 go2ismail@gmail.com – 1st Edition

3.3.6 Purchase Report

Purchase Report is a key feature within the procurement module, designed to display purchase data
in a grid format. The report groups the information by purchase order number, making it easy to track
and analyze multiple purchase orders at once. Below each group, the order details are displayed,
providing a clear and concise view of the procurement activities. This structure allows users to quickly
identify relevant information without navigating through complex data, improving efficiency and
accuracy.

Additionally, the grid format can be downloaded as an Excel file, enabling users to perform deeper
analysis or generate custom reports. This feature allows businesses to easily export purchase data for
further examination, offering flexibility for reporting and decision-making. By providing the ability to
download and manipulate the data, the purchase report feature supports better insights into
procurement performance, vendor relationships, and purchasing trends, ultimately helping businesses
improve their purchasing strategies and operational efficiency.

©2025 go2ismail@gmail.com – 1st Edition

3.4 Inventory Modules
3.4.1 Unit Measure

The Unit of Measure (UOM) feature within the inventory module is essential for defining how product
quantities are measured and tracked. It serves as a standardized method to quantify both physical
products and service products, ensuring consistency in inventory management and reporting. Units of
Measure can be used to register the measurement metrics that will be applied to products, allowing
businesses to track items in the most appropriate and efficient way. This helps streamline inventory
processes by providing a clear understanding of how products are counted or quantified, whether by
quantity, weight, length, or time.

The Unit of Measure consists of two key columns: Name and Description. The "Name" represents the
unit itself, such as "unit," "pcs," "meter," or "hour" for service products. The "Description" provides
additional context or details about how that unit is applied. For example, "pcs" could be used for
products sold individually, while "meter" might be used for items measured by length, and "hour"
could apply to service products where time is the key metric. This structure ensures that businesses
can accurately register and manage their inventory, providing better control over stock levels, service
deliveries, and overall operational efficiency.

©2025 go2ismail@gmail.com – 1st Edition

3.4.2 Product Group

The Product Group feature within the inventory module allows businesses to categorize products
based on their specific needs, helping to streamline product management and inventory tracking. By
grouping products into relevant categories such as Device, Storage, Hardware, Software, Service, and
more, businesses can maintain better organization and control over their product offerings. This
classification makes it easier to manage inventory levels, track sales, and optimize procurement
strategies based on different product categories, ensuring more efficient business operations.

The master data for product groups is recorded using two key columns: Name and Description. The
"Name" refers to the specific group, such as "Device" or "Storage," while the "Description" provides
additional context or details about what types of products belong in each group. This structure allows
businesses to clearly define and manage their product groups, ensuring that each product is properly
categorized for easy access and analysis. By using Product Groups, companies can improve inventory
visibility, enhance reporting capabilities, and make more informed decisions regarding stock
management and sales strategies.

©2025 go2ismail@gmail.com – 1st Edition

3.4.3 Product

The Product feature within the inventory module is designed to capture master product data, serving
as a central record for all items managed within the inventory system. When registering a product, key
information such as unit measure, product unit, product group, and product type (whether physical or
non-physical) can be entered. This comprehensive approach ensures that businesses can accurately
track and manage their inventory across different product categories, whether they involve physical
items or services.

By allowing businesses to specify whether a product is physical or non-physical, the system offers
flexibility in managing a wide range of products, including tangible goods like electronics or furniture,
as well as intangible services. This distinction is especially valuable when handling service products, as
it helps separate inventory management for physical stock from service-based offerings, improving
overall inventory accuracy and operational efficiency. The ability to associate products with specific
unit measures and groups further enhances product categorization, making it easier to manage,
report, and analyze inventory in a more organized and streamlined manner.

©2025 go2ismail@gmail.com – 1st Edition

3.4.4 Warehouse

The Warehouse feature within the inventory module is designed to help businesses manage multiple
warehouse locations by capturing master data for each warehouse. This is particularly useful for
businesses that operate with several warehouse facilities and need a structured approach to manage
inventory across various sites. Warehouse data is recorded using two key columns: Name and
Description. The "Name" refers to the specific warehouse location, while the "Description" provides
additional details about the warehouse, such as its function or capacity. This allows businesses to have
a clear overview of their warehouse network, making it easier to track inventory and streamline
logistics.

In addition to non-system warehouses that businesses create, such as their own storage facilities, the
system also includes predefined system warehouses for internal use, such as vendor, customer,
adjustment, scrapping, and stock count warehouses. These system warehouses are important for
performing stock calculations and managing inventory adjustments, ensuring accurate tracking and
reporting of stock movements. By using both non-system and system warehouses, businesses can have
a comprehensive view of their inventory, enabling more effective management, better forecasting, and
improved decision-making regarding stock levels and distribution.

©2025 go2ismail@gmail.com – 1st Edition

3.4.5 Delivery Order

The Delivery Order feature within the inventory module is designed to manage the process of
delivering products to customers after a sales order has been placed. Once a customer places an order,
the internal team follows up by creating a Delivery Order document, using the sales order as a
reference. This ensures that the delivery process is closely tied to the original sales order, allowing
businesses to efficiently track the movement of goods from order to shipment. The Delivery Order
feature captures essential information, such as the sales order number and the warehouse responsible
for fulfilling the delivery, helping to streamline the order fulfillment process.

By recording the sales order and the associated warehouse in the Delivery Order, businesses can
ensure that the correct products are selected from the appropriate warehouse for shipment to the
customer. This functionality helps maintain accurate inventory records and improves operational
efficiency by ensuring that products are dispatched in a timely manner. It also provides a clear
connection between sales orders and the corresponding delivery process, making it easier for
businesses to manage their logistics, monitor delivery progress, and maintain accurate stock levels
throughout the order fulfillment cycle.

©2025 go2ismail@gmail.com – 1st Edition

3.4.6 Sales Return

The Sales Return feature within the inventory module is designed to handle product returns from
customers, allowing businesses to efficiently process returns and maintain accurate inventory records.
The typical flow begins when a customer places an order, which is recorded in the Sales Order. The
next step involves the internal team, often the warehouse team, creating a Delivery Order based on
the sales order, referencing the specific sales order to ensure the correct products are delivered. A
crucial aspect of the Delivery Order is identifying which warehouse will be responsible for dispatching
the products to the customer. This clear process ensures that all relevant details, including product
quantities and shipping locations, are documented.

However, after receiving the products, there may be instances where the customer returns items due
to reasons such as defects or discrepancies in the order. In these cases, the Sales Return functionality
comes into play. The internal team, typically the warehouse operations team, creates a Sales Return
document to record the returned products. This document serves as a formal record of the products
being returned to the company and provides crucial information about the return process, including
the delivery order number as a reference and which warehouse will be responsible for receiving the
returned products.

By accurately capturing the delivery order reference and identifying the warehouse receiving the
returned products, businesses can ensure smooth processing of returns and make the necessary
inventory adjustments. This feature also allows businesses to track returned items, monitor reasons
for returns, and improve customer satisfaction by addressing product issues or discrepancies. Overall,
the Sales Return functionality plays a vital role in maintaining operational efficiency and ensuring that
both customer needs and inventory accuracy are met.

©2025 go2ismail@gmail.com – 1st Edition

3.4.7 Goods Receive

The Goods Receive feature in the inventory module is designed to streamline the process of receiving
products delivered by vendors. This functionality plays a crucial role in recording the arrival of goods
and ensuring that the company accurately tracks inventory levels. When goods are received, the
system captures the relevant purchase order number as a reference, linking the received items to the
original order placed with the vendor. This helps maintain an organized record of incoming goods and
ensures that the items match what was ordered.

In addition to tracking the purchase order, the Goods Receive feature also captures information about
the warehouse that will be responsible for receiving and storing the products. By recording this detail,
businesses can easily identify where the goods should be placed once they arrive, ensuring that
inventory is efficiently managed and that the right products are stored in the appropriate location. This
process enhances operational efficiency and supports accurate inventory management, making it
easier for businesses to track their stock levels and streamline their supply chain operations.

©2025 go2ismail@gmail.com – 1st Edition

3.4.8 Purchase Return

The Purchase Return feature in the inventory module is used when a business needs to return products
that have been previously received from a vendor. This could occur for various reasons, such as
damaged goods, incorrect items, or other issues with the products. The primary function of this feature
is to record the return process, ensuring that the company has an accurate record of which items are
being returned and why. By creating a purchase return document, businesses can track the details of
the returned goods and ensure that the correct items are sent back to the vendor.

One of the key pieces of information captured in the Purchase Return process is the reference to the
original Goods Receive document, which links the returned items to the initial receipt of goods.
Additionally, the warehouse responsible for handling the return is recorded, as this will determine
where the returned products will be processed before being sent back to the vendor. This feature helps
ensure that the return process is organized, and the right products are sent back to the correct vendor,
improving overall supply chain management and vendor relationship handling.

©2025 go2ismail@gmail.com – 1st Edition

3.4.9 Transfer Out

The Transfer Out feature in the inventory module, also known as warehouse-to-warehouse transfer, is
a process that facilitates the movement of goods between two internal warehouses. This is a common
procedure in businesses that have multiple warehouses, such as transferring items from a production
warehouse to a distribution warehouse, or from a quarantine warehouse to the main warehouse. The
Transfer Out process ensures that inventory levels are updated accurately across different locations
and that goods are transferred seamlessly to where they are needed.

During a warehouse-to-warehouse transfer, key information is recorded, including the source

warehouse and the destination warehouse. Additionally, the items being transferred, along with their
quantities, are also tracked to ensure the correct products are moved between locations. This
functionality plays a vital role in maintaining inventory accuracy across various warehouses, supporting
efficient internal logistics, and enabling businesses to manage their stock levels effectively across
different sites.

©2025 go2ismail@gmail.com – 1st Edition

3.4.10 Transfer In

The Transfer In feature in the inventory module is used by the operations warehouse team to record
the receipt of goods that have been transferred from one internal warehouse to another, as part of
the warehouse-to-warehouse transfer process. Once the goods arrive at the destination warehouse,
the team creates a Transfer In document to officially acknowledge and record the receipt of the items.
The Transfer In document references the corresponding Transfer Out document, ensuring that the
transfer process is properly tracked from start to finish.

Key information in the Transfer In process includes the reference to the original Transfer Out
document, which serves as the primary point of reference for the incoming goods. Additionally, the
receiving warehouse is automatically populated with the information from the destination warehouse
noted in the Transfer Out document. This feature streamlines inventory tracking and ensures that the
destination warehouse's stock is updated accurately, completing the warehouse-to-warehouse
transfer cycle and maintaining proper inventory control across multiple locations.

©2025 go2ismail@gmail.com – 1st Edition

3.4.11 Positive Adjustment

Positive Adjustment is a feature in the inventory module that allows businesses to increase the
quantity of a specific product in the stock, effectively adding more units to the existing inventory. This
process is typically used when there is a need to correct stock discrepancies or when additional items
are received but not initially recorded. The primary information captured in a positive adjustment
includes the warehouse, the product being adjusted, and the quantity to be added.

Once the positive adjustment is recorded, the specified quantity is added to the existing stock level of
the product in the designated warehouse. This ensures that the inventory records accurately reflect
the updated stock levels, helping businesses maintain better control and tracking of their product
quantities. Positive adjustments play a vital role in inventory management by ensuring that stock
counts remain accurate and that inventory levels are properly adjusted to reflect actual availability.

©2025 go2ismail@gmail.com – 1st Edition

3.4.12 Negative Adjustment

Negative Adjustment is a feature in the inventory module that allows businesses to decrease the
quantity of a specific product in stock, effectively reducing the inventory count. This process is typically
used when there is a need to correct stock discrepancies, when products are lost, damaged, or
returned, or when items are mistakenly overcounted. The primary information captured in a negative
adjustment includes the warehouse, the product being adjusted, and the quantity to be subtracted.

Once the negative adjustment is recorded, the specified quantity is subtracted from the existing stock
level of the product in the designated warehouse. This ensures that the inventory records are updated
to reflect the accurate stock levels, preventing overstocking and maintaining inventory control.
Negative adjustments are critical for inventory management by ensuring that stock counts are accurate
and that any discrepancies are corrected, helping businesses maintain proper tracking of product
quantities.

©2025 go2ismail@gmail.com – 1st Edition

3.4.13 Scrapping

Scrapping is a feature in the inventory module used to manage the disposal or destruction of damaged
goods. When products are deemed unsellable or no longer usable due to damage, expiration, or other
factors, scrapping allows businesses to remove them from the inventory. This process ensures that
these items are properly accounted for and that stock levels reflect the actual usable inventory. A
dedicated system warehouse is created for scrapping to track the movement of goods being discarded,
ensuring that the reduction in stock is properly recorded.

The key information captured during scrapping includes the warehouse from which the goods are
being removed, the specific product being scrapped, and the quantity of the damaged goods. This
process helps monitor the amount of stock being scrapped and enables businesses to analyze trends,
such as why certain products are consistently being discarded. By tracking scrapping activities,
businesses can identify areas for improvement, whether in product quality, handling processes, or
inventory control, and take corrective actions to minimize losses.

©2025 go2ismail@gmail.com – 1st Edition

3.4.14 Stock Count

Stock count is a process in the inventory module that involves physically counting the existing stock in
the warehouse. This physical count is then recorded in the system to ensure that the inventory records
are accurate. The stock count helps businesses verify the actual quantities of products available in the
warehouse and ensures that the system's stock levels match the physical stock. Any discrepancies
between the system's recorded stock and the physical count are identified during this process.

If a difference is found between the system stock and the physical count, an automatic adjustment is
made to correct the discrepancy. This adjustment can either increase or decrease the stock levels
based on the physical count. The source and destination for this adjustment are typically the
warehouse system designated for stock counting, ensuring that the system's records are updated
accordingly. The final stock count figures become the official stock levels, ensuring that the system
accurately reflects the physical stock in the warehouse. This process guarantees that inventory records
are aligned with actual stock, helping to maintain accurate and reliable inventory management.

©2025 go2ismail@gmail.com – 1st Edition

3.4.15 Transaction Report

The Transaction Report in the inventory module provides a comprehensive overview of all inventory
transactions within the system. This report presents data in a tabular format, displaying essential
information such as the product involved, transaction date, transaction number, quantity, and
transaction type. The transaction type is clearly labeled as either "Plus," indicating an increase in stock
within the warehouse, or "Minus," which shows a reduction in stock. The report also specifies the
module that initiated the transaction, such as Delivery Order, Goods Receive, Adjustment, and others.
This allows users to track and monitor the source and destination of inventory movements across
various processes.

Furthermore, the report provides valuable insights into the flow of goods between warehouses,
whether physical or system-based. For example, a Delivery Order shows the movement of products
from a physical warehouse to a system warehouse, such as the customer warehouse. Similarly,
Scrapping transactions reflect a transfer from a physical warehouse to a system warehouse named
"Scrapping." The report also captures warehouse-to-warehouse transfers, where inventory moves
between two physical warehouses. By including all these details, the Transaction Report helps
businesses monitor inventory flow, understand stock movements, and ensure accurate inventory
management across all warehouse locations.

©2025 go2ismail@gmail.com – 1st Edition

3.4.16 Stock Report

The Stock Report in the inventory module provides a real-time snapshot of the actual stock available
at a specific point in time. This report is dynamic and can change when generated at different times,
reflecting the most up-to-date inventory status. It serves as a critical tool for businesses to monitor
stock levels and assess inventory availability. The report is presented in a tabular grid format, making
it easy to read and analyze. Users can export the data to Excel for further analysis, allowing them to
manipulate the data and generate insights tailored to their specific needs.

The primary information displayed in the Stock Report includes the product name, warehouse name,
and the actual stock quantity at the time the report is generated. This layout ensures clarity and
enables businesses to quickly identify inventory levels across various warehouses. By having a real-
time, accurate view of stock quantities, businesses can make informed decisions on restocking, order
fulfillment, and overall inventory management. The ability to export the data further enhances the
report’s usefulness, providing flexibility for deeper analysis and reporting.

©2025 go2ismail@gmail.com – 1st Edition

3.4.17 Movement Reports

The Movement Report in the inventory module provides a detailed overview of product movements,
both in terms of quantity and transaction types. This report is essential for tracking the flow of
inventory, offering insights into how products are being added to or removed from stock across
different warehouses. The data is presented in a pivot table format, with products and warehouses as
the primary rows, while transaction categories are displayed as columns extending horizontally. This
format allows users to easily analyze which transactions occurred for a specific product in a particular
warehouse and the corresponding quantities involved.

Transaction categories in the Movement Report typically include adjustment, stock count, delivery
order, goods receive, purchase return, and sales return. By summarizing these categories in a pivot
format, the report provides a clear and concise view of all inventory activities for each product and
warehouse. This enables businesses to identify patterns, trends, and potential issues in inventory
management. The Movement Report is a powerful tool for maintaining control over stock movements,
helping organizations ensure accuracy and transparency in their inventory operations.

©2025 go2ismail@gmail.com – 1st Edition

3.5 Utilities
3.5.1 Booking Group

The Booking Group feature in the utilities module allows businesses to create and manage master data
for booking groups. These booking groups serve as categories that can be used when managing
booking resources, providing an organized way to group related resources. For example, booking
groups can include categories such as Electronics, Rooms, and Vehicles, helping users quickly identify
and allocate the appropriate resources for specific needs.

Each booking group is recorded with two key pieces of information: the name of the booking group
and a description providing additional context or details about its purpose. By organizing resources
into booking groups, businesses can streamline their resource management processes, improve
efficiency, and ensure clarity when assigning or reserving resources. This feature is particularly useful
in environments where multiple types of resources are managed and tracked.

©2025 go2ismail@gmail.com – 1st Edition

3.5.2 Booking Resource

The Booking Resource feature in the utilities module allows businesses to define resources that can be
booked for various purposes. When creating a booking resource, users must assign it to a specific
booking group, enabling better categorization and analysis of the resources. For instance, if the
resources are rooms such as "Studio One," "Studio Two," "Conference One," and "Conference Two,"
they can be grouped under the "Room" booking group. This categorization ensures that resources are
organized and easily accessible based on their type.

Another example is when the resources are vehicles such as "Audi One," "Audi Two," "BMW One," and
"BMW Two." These resources can be grouped under the "Vehicle" booking group. By associating each
resource with a booking group, businesses can efficiently manage their resources, streamline the
booking process, and perform detailed analysis of resource usage across categories. This feature is
essential for organizations that rely on effective resource allocation and utilization.

©2025 go2ismail@gmail.com – 1st Edition

3.5.3 Booking Manager

The Booking Manager in the utilities module is a feature designed to record and manage scheduling
agendas for booking resources effectively. It allows users to capture essential details such as the
location, start time, end time, the specific booking resource being scheduled, and the status of the
booking—whether it is "Done," "In Progress," or "Draft." This feature ensures that all bookings are
organized and can be easily tracked, helping businesses manage their resources more efficiently.

The Booking Manager is presented in a tabular grid format, providing a clear and structured overview
of all booking entries. Additionally, the grid can be exported to an Excel file, enabling further analysis
or offline use. This export functionality is particularly useful for generating reports, reviewing booking
trends, or sharing scheduling data with other team members. The Booking Manager is an essential
tool for organizations requiring streamlined resource scheduling and tracking capabilities.

©2025 go2ismail@gmail.com – 1st Edition

3.5.4 Booking Scheduler

The Booking Scheduler in the utilities module is a visual representation of the schedule managed
through the Booking Manager. It provides a dynamic grid view that allows users to see booking
timelines for resources at a glance. The scheduler offers multiple viewing options, including timeline
day, timeline week, timeline work week, timeline month, and agenda views. These flexible display
modes make it easier to identify which resources are actively booked on specific dates, helping users
plan and allocate resources efficiently.

By integrating with the Booking Manager, the Booking Scheduler ensures that all scheduled bookings
are accurately reflected in the grid. This visual approach provides a more intuitive way to track
bookings compared to the traditional tabular grid. Users can quickly identify booking overlaps,
resource availability, and scheduling gaps, streamlining the resource management process. The
Booking Scheduler is an invaluable tool for organizations that require an at-a-glance overview of their
resource usage and scheduling activities.

©2025 go2ismail@gmail.com – 1st Edition

3.5.5 Program Resource

The Program Resource feature in the utilities module is designed to create and manage a master list
of program resources. These resources serve as foundational data that can later be utilized within the
Program Manager. By recording program resources in this module, businesses can define and
categorize the assets or items needed for various programs, ensuring consistency and accuracy across
operations. Key details captured in the Program Resource include the resource name and description,
making it easier to identify and reference them during program planning and execution.

Once program resources are recorded, they can be linked to entries in the Program Manager. In the
Program Manager, users can specify which program resources are being utilized, track their status (e.g.,
Draft or Confirmed), and assign priority levels, such as Low, High, or Critical. This structured approach
ensures that resource allocation is well-documented and prioritized based on program requirements,
improving the efficiency and reliability of program execution.

©2025 go2ismail@gmail.com – 1st Edition

3.5.6 Program Manager

The Program Manager in the utilities module is a tool designed to effectively manage work programs
by recording their status and priority. Users can select program resources that have been previously
registered in the Program Resource module, ensuring proper allocation and tracking of necessary
assets. The Program Manager provides a structured tabular grid view, where key details such as
program name, resource, status, and priority (e.g., Low, High, or Critical) are displayed. This grid can
also be exported to an Excel file for further analysis or reporting, enabling businesses to evaluate
program performance and trends more effectively.

In addition to the tabular grid view, the Program Manager includes a Kanban-style interface for a more
visual representation of program statuses. This Kanban view helps users track the progress of work
programs as they move through various stages, such as Draft, In Progress, or Completed. The pivotal
layout of the Kanban board makes it easier to manage workflows, prioritize tasks, and monitor progress
at a glance, ensuring efficient program execution and better collaboration among team members. This
dual-view capability enhances the usability and functionality of the Program Manager, making it a
versatile tool for project and program management.

©2025 go2ismail@gmail.com – 1st Edition

3.5.7 Program Kanban

The Program Kanban in the utilities module is a visual representation of the Program Manager in a
Kanban view format. In this view, statuses such as Draft, Confirmed, On Progress, Done, and Cancelled
are displayed as pivot columns, while cards beneath these columns provide detailed information about
each work program, including its description and priority level (Low, Medium, High, Critical).

To enhance clarity, a colored sidebar is added to each card, visually distinguishing the priority levels,
making it easier for users to identify and manage tasks at a glance. This intuitive layout simplifies
workflow tracking and prioritization, ensuring efficient management of work programs.

©2025 go2ismail@gmail.com – 1st Edition

3.6 Membership
3.6.1 Users

The User Management feature in the membership module is designed to empower administrators
with tools to efficiently manage users within the system. Through this feature, administrators can add
new users, ensuring they are properly registered and assigned initial roles. Additionally, administrators
have the ability to edit user details, such as updating names, changing roles, or resetting passwords,
to ensure user information stays accurate and up-to-date.

This feature also allows administrators to block users when necessary, providing control over who has
access to the system. By offering comprehensive user management capabilities, this module ensures
that user accounts are well-maintained, roles are properly assigned, and security measures are upheld,
creating a robust and organized user management process.

©2025 go2ismail@gmail.com – 1st Edition

3.6.2 Roles

The Roles page in the membership module displays a list of all the roles available within the system.
These roles define the permissions that can be assigned to users, ensuring they have the appropriate
access to system features and functionalities. Administrators can manage these roles by adding new
ones or removing existing ones, tailoring them to the organization's needs. These roles can then be
assigned or unassigned to specific users through the User Management menu, providing flexibility and
control over user access within the system.

©2025 go2ismail@gmail.com – 1st Edition

3.7 Profiles
3.7.1 My Profile

The My Profile section in the Profiles module allows currently logged-in users to manage and update
their personal information within the system. Through this feature, users can make changes such as
updating their name, changing their password for security purposes, and uploading a new avatar to
personalize their profile. This functionality ensures that users have control over their personal data
and can keep their profile information up to date with ease.

©2025 go2ismail@gmail.com – 1st Edition

3.8 Settings
3.8.1 My Company

The My Company section within the Settings module provides a dedicated space for managing specific
information about the company using the system. This feature allows administrators to update
essential company details, ensuring that all records and documents generated by the system reflect
accurate and up-to-date information. Key fields include the company's name, a brief description, the
currency used for transactions, and the complete address, such as street, city, state, zip code, and
country. Additionally, communication details like phone number and email address can also be
configured in this section.

The information entered in the My Company section is prominently utilized in the headers of printable
documents, including PDF exports. This ensures that every document created through the system has
a professional appearance and accurately represents the company’s identity. By maintaining
comprehensive and precise company details, businesses can streamline their branding and
communication efforts while ensuring consistency across all system-generated documentation.

©2025 go2ismail@gmail.com – 1st Edition

3.8.2 Tax

The Tax section within the Settings module is designed to manage the master data for tax rates used
in various transactions, such as sales orders and purchase orders. This feature allows businesses to
define and maintain accurate tax information, ensuring compliance with applicable regulations and
simplifying the application of tax rates during transactions. The primary fields in the tax master data
include the tax name, the tax rate expressed as a percentage, and a description providing additional
details about the tax.

By maintaining a centralized repository of tax rates, the Tax section helps streamline the transaction
process by automatically applying the correct tax rates based on the defined data. This reduces manual
errors and ensures consistency in tax calculations across all transactions. With the ability to manage
and update tax details easily, businesses can adapt to changing tax regulations efficiently and maintain
accurate financial records.

©2025 go2ismail@gmail.com – 1st Edition

3.8.3 Number Sequence

The Number Sequence section within the Settings module is used to monitor and track the numbers
used when creating documents such as sales orders or purchase orders. This feature ensures that all
document numbers are generated in a systematic and consistent manner, preventing duplicates and
ensuring proper record-keeping. The information captured in the number sequence report includes
the entity name, the prefix and suffix applied to the document number, and the last used count, which
shows the most recent number assigned.

The report generated by the number sequence feature is available for download in Excel format,
making it easy for users to review and analyze the document numbering history. Importantly, this
report is read-only, meaning no editing can be performed, ensuring the integrity of the number
sequence. This functionality is crucial for businesses to maintain a clear and auditable trail of
document numbers, which aids in tracking and preventing errors in document creation across various
processes.

Thank You!

©2025 go2ismail@gmail.com – 1st Edition