Merch4Change: An Integrated Social Commerce & Philanthropic Giving Platform

CO2060 — Software Systems Design Project (2YP)
Department of Computer Engineering · Faculty of Engineering · University of Peradeniya, Sri Lanka


Project Overview


Academic Information & Team

Engineering Team

Registration No Student Name Assigned Role University Email
E/23/050 G.C. Damsiluni Frontend Developer & UI/UX Designer e23050@eng.pdn.ac.lk
E/23/089 M.A.S. Dulshara Database Systems & Infrastructure Engineer e23089@eng.pdn.ac.lk
E/23/343 S.B.N.S. Samarawickrama Backend Systems & API Architect e23343@eng.pdn.ac.lk
E/23/347 S.D.M.P. Sandanayake Team Leader & Full-Stack Systems Engineer e23347@eng.pdn.ac.lk

Table of Contents

  1. Executive Summary & Problem Statement
  2. The Merch-to-Impact Closed-Loop Architecture
  3. Multi-Sided Stakeholder Roles
  4. Functional Capabilities & Subsystems
  5. System Process Workflows & Flowcharts
  6. System Architecture & Engineering Design
  7. Security Architecture & Concurrency Safeguards
  8. Quality Assurance & Verification Methodology
  9. Project Milestones & Strategic Roadmap
  10. References & Technical Resources

1. Executive Summary & Problem Statement

1.1 Problem Domain

Contemporary digital retail and philanthropic fundraising operate in distinct silos, leading to three systemic inefficiencies:

  1. Philanthropic Friction: While digital consumers exhibit strong demand for socially responsible consumption, conventional donation funnels are disconnected from day-to-day purchasing activities, producing high friction and drop-off rates.
  2. Asymmetric Information and Verification Deficits: Grassroots charitable institutions face profound credibility challenges. Lacking standardized verification channels, legitimate causes struggle to gain public trust and funding.
  3. Unrealized Corporate Social Responsibility: Independent brands and creators lack turn-key software infrastructure to demonstrate direct social impact within their existing sales funnels.

Figure 1: Architectural Problem Domain Figure 1: Systemic market deficits and structural friction separating consumer commerce from philanthropic funding.

1.2 Proposed Resolution

Merch4Change resolves this structural disconnect through a unified, multi-sided digital platform that connects ethical merchandise purchases directly with transparent philanthropic allocations via an in-app reward coin economy.


2. The Merch-to-Impact Closed-Loop Architecture

The platform operates on a closed-loop micro-philanthropic economy:

Figure 2: The Merch-to-Impact Value Loop Figure 2: The closed-loop Merch-to-Impact value cycle converting retail transactions into verifiable social impact.


3. Multi-Sided Stakeholder Roles

The system is structured around four primary user personas with distinct operational scopes:

Persona Operational Scope & Permissions
Conscious Consumers Discover and purchase curated merchandise, place real-time bids on limited charity auctions, earn Merch Coins, execute atomic cause donations, monitor project funding progress, and engage via community feeds and 24-hour stories.
Brands & Creators Manage branded merchandise storefronts, publish product collections, upload cloud media assets, host timed charity drop auctions, and track verified impact metrics.
Charities & NGOs Submit statutory registration documentation for administrative compliance audits, receive verified status badges, publish milestone-driven campaigns, receive atomic coin donations, and showcase physical headquarters on interactive geospatial maps.
Platform Administrators Review pending non-profit compliance applications, inspect PDF documentation, grant or revoke verification status, audit system financial ledgers, and supervise content moderation.

4. Functional Capabilities & Subsystems

Multi-Vendor Merchandise Marketplace

Timed Auction & Bidding Engine

Closed-Loop Coin Economy & Crowdfunding

Non-Profit Governance & Geospatial Discovery

Social Community & Direct Messaging


5. System Process Workflows & Flowcharts

5.1 End-to-End User Impact Journey

The complete operational flow from initial registration to verified philanthropic delivery:

Figure 3: End-to-End User Impact Journey Figure 3: Sequence of operations from consumer onboarding to charitable impact execution.


5.2 Coin Accrual & Atomic Donation Engine

The reward and donation subsystem is built to ensure strict ledger integrity, preventing double-spending and race conditions:

Figure 4: Coin Generation and Atomic Donation Architecture Figure 4: Algorithmic coin accrual calculations and atomic multi-document transaction pipeline.


5.3 Live Auction & Real-Time Bidding Mechanics

Ensures valid bid increments, active-window verification, and atomic high-bidder reassignment:

Figure 5: Live Auction Engine Figure 5: Auction scheduling, bid increment validation, and winner determination flow.


5.4 Non-Profit Credentialing & Regulatory Audit Pipeline

Rigorous multi-stage vetting process safeguarding donor contributions against unverified entities:

Figure 6: Charity Verification Pipeline Figure 6: Administrative audit pipeline from certificate upload to verified directory indexing.


6. System Architecture & Engineering Design

6.1 High-Level Architecture

Merch4Change employs a modular three-tier client-server architecture:

Figure 7: Multi-Tier System Architecture Figure 7: Multi-tier architectural boundaries spanning client SPA, API gateway, core domain services, and persistence.


6.2 Technology Matrix

Subsystem Selected Technologies Technical Rationale
Presentation Tier React 19, Vite 7, Tailwind CSS 3.4 Modern React compiler optimizations, sub-second module reloads, and utility-first responsive layout structures.
Geospatial & Visuals Leaflet, React-Leaflet, OpenStreetMap High-performance raster map rendering for global NGO headquarters without proprietary API licensing constraints.
Backend Runtime Node.js (>=18.0.0, ES Modules) High-throughput asynchronous event loop well suited for concurrent e-commerce and real-time social workloads.
API Gateway Tier Express.js 4 Robust middleware composition, modular resource routers, and defensive HTTP security headers.
Database & ODM MongoDB Atlas, Mongoose 8 Flexible JSON document schemas accommodating polymorphic profile types, dynamic product attributes, and audit logs.
Session Security Dual-Token JWT (Memory + HttpOnly Cookie) In-memory ephemeral access tokens paired with rotated HttpOnly, SameSite=Lax refresh cookies.
Payment Ingress Stripe Checkout API Fully hosted, PCI-DSS compliant checkout sessions providing secure card processing and webhook notifications.
Media Pipeline Cloudinary REST API, Multer (Memory) In-memory buffering (strict 2MB ceiling) with streaming uploads to Cloudinary CDN, bypassing local disk storage.
Transactional Email Resend API & Nodemailer (SMTP) Multi-provider fallback delivery ensuring reliable OTP transmission during authentication and account recovery.

6.3 NoSQL Document Model & Collection Architecture

The data tier is engineered natively on MongoDB Atlas utilizing Mongoose 8 ODM, leveraging a document-oriented NoSQL paradigm optimized for high-throughput reads, polymorphic user roles, and atomic ledger mutations:

Figure 8: NoSQL Document Model & Collection Architecture Figure 8: MongoDB NoSQL collection schemas, embedded document arrays, and normalized ObjectId references.


7. Security Architecture & Concurrency Safeguards


8. Quality Assurance & Verification Methodology

System reliability is enforced through multi-tier automated test suites:

Figure 9: Quality Assurance Pipeline Figure 9: Quality assurance pyramid spanning unit tests, endpoint integration, concurrency checks, and continuous integration.


9. Project Milestones & Strategic Roadmap

Figure 10: Implementation Milestones & Strategic Roadmap Figure 10: Phased project implementation roadmap from initial release to planned enterprise capabilities.


10. References & Technical Resources


Department of Computer Engineering · Faculty of Engineering · University of Peradeniya
CO2060 — Software Systems Design Project (2YP) · Academic Year 2025/2026