This is a real-world client project developed to manage the client’s charity collection operations across three institutes. The client has a large donor network, with donors organized under different collectors based on their geographic areas. The system brings donor management, collector assignments, promised donations, wallet management, and collection history together in one centralized platform.
The application was designed around the client’s actual operational workflow rather than as a simple data-management or CRUD application. It provides administrators with control over collectors and their collection capacity while allowing them to keep track of every donor, promised contribution, completed collection, and wallet transaction.
The system provides a centralized donor management interface where administrators can maintain donor records and associate each donor with the appropriate collector.
Donor information can be searched and managed using details such as:
This allows the client to handle a large donor base while maintaining a clear relationship between each donor and the collector responsible for them.
Collectors are organized according to specific geographic areas.
The administrator can create collectors and assign them to particular areas, then associate donors with the appropriate collector. This creates a structured collection network where each collector knows which donors they are responsible for.
The system also allows administrators to manage collector information and monitor their overall collection activity from the administrative interface.
One of the important business features is the collector wallet system.
Each collector has a wallet that is controlled by the administrator. The wallet represents the amount available to that collector for completing collection operations.
Administrators can:
The wallet provides an additional layer of control over the collection process and helps the organization keep track of collector-level financial activity.
The platform separates promised donations from completed collections.
When a donor promises to make a contribution, the collector can record the promised collection along with the date when the donor expects to provide the donation.
For example, if a donor promises to donate a certain amount next month, that amount is recorded in the promised collection system but does not immediately affect the collector’s wallet.
Promised collections have their own dedicated view, allowing collectors and administrators to see upcoming commitments and the expected collection dates.
When the collector actually receives the promised donation, the collection is processed through the normal collection workflow. At that point, the corresponding amount is deducted from the collector’s wallet.
This gives the client a clear distinction between:
Promised → Awaiting Collection → Collected → Wallet Updated
Every completed collection can be tracked through the collection history.
The client can review collection activity and keep a record of completed donations rather than relying on manual records or separate spreadsheets.
This helps administrators understand:
Alongside collection history, the system maintains wallet-related information so administrators can understand how each collector’s wallet is being used.
This makes it possible to monitor the relationship between wallet balance, completed collections, and collector activity.
The client manages collection operations for three institutes through the same platform.
Instead of maintaining separate systems for each institute, the application provides a centralized environment where the organization’s collection data and operational workflow can be managed from one place.
This makes the system particularly useful as the client’s donor and collection network grows.
React · Node.js · Express.js · Sequelize · MySQL
