Greencart
  • Executive Summary
    • Chapter 1
    • Chapter 2
    • Chapter 3
    • Chapter 4
    • Chapter 5
    • References
  • Greencart Final AVP
Powered by GitBook
On this page
  1. Executive Summary

Chapter 4

PreviousChapter 3NextChapter 5

Last updated 19 days ago

Methodology, Result, and Discussions

This chapter presents the results of the system testing and implementation phase, detailing the procedures undertaken to validate functionality, promote sustainability, and ensure user reliability. It outlines the testing methodologies applied, evaluates performance outcomes, and incorporates feedback from users and stakeholders. Through these elements, the chapter highlights how Greencart contributes to environmental sustainability by minimizing packaging waste, encouraging the use of reusable materials, and fostering active customer participation. The findings not only demonstrate the system’s current efficacy but also reveal opportunities for refinement and innovation to enhance long-term impact and operational efficiency.

Greencart is an online shopping platform designed to embed eco conscious practices into the delivery process. Central to its model is a structured system that minimizes single use packaging by implementing size based wrapping protocols and photo documentation prior to dispatch. Each shipment includes a user-friendly unwrapping guide to facilitate the correct handling and return of packaging materials. The platform actively monitors the volume of bubble wrap used, tracks returned materials, and automates the issuance of discount vouchers to incentivize sustainable behavior. Returned materials, whether verified through customer uploaded videos or in-person assessments by logistics personnel are then repurposed for future deliveries, promoting a circular approach to packaging.

During the implementation phase, rigorous testing was conducted to ensure the system performed as intended across technical and user centric dimensions. The methodology encompassed unit testing of core modules (e.g., item-size detection, packaging allocation), integration testing across customer, logistics, and administrative workflows, and system testing to evaluate end to end transaction processes. Additionally, user acceptance testing provided valuable insights from actual users, reinforcing the platform’s usability and reliability. The results affirm Greencart effectiveness in reducing packaging waste, improving delivery logistics, and motivating returns through transparent tracking and reward systems. Participants reported that instructions were clear and return procedures straightforward, while logistics personnel acknowledged the system’s role in streamlining the management of reusable packaging. Nonetheless, the testing phase also identified areas for improvement, such as enhancing the video based validation process for returns and developing better engagement strategies for users in remote locations. These findings inform future development efforts aimed at scaling Greencart’s environmental and operational benefits.

Requirements Analysis

Figure 15.1 Level 15 Data Flow Diagram (Explosion)

Figure 15.1 illustrates the structured process through which delivery feedback is submitted and reviewed within the system. The process begins at the “Submitting Delivery Review” stage (15.1), where the customer provides feedback regarding their delivery experience. Upon submission, the system records the review alongside the corresponding order status, ensuring that feedback is contextually linked to specific transactions. The process then advances to the “Reviewing Customer Feedback” stage (15.2), during which logistics personnel assess the content of the customer's input. This evaluation enables the logistics team to gauge service quality, recognize positive performance, and identify areas requiring improvement. By integrating this feedback loop into the system's workflow, Greencart fosters a culture of continuous improvement, promoting responsive service and reinforcing its commitment to user satisfaction and sustainable logistics practices.

Functional Requirements

Functionality

F1: The system shall provide users with the ability to create an account by entering their first name, last name, username, and password. F2: The system shall support role-based registration, enabling users to register as a customer, online seller, logistics personnel, or delivery driver.

F3: The system shall require administrative approval for online sellers, which is granted upon submission and verification of all necessary documentation.

F4: Upon successful login, the system shall automatically redirect users to the appropriate dashboard corresponding to their assigned role. F5: The system shall enable online sellers to post items for sale by entering relevant details, including item name, category, and accompanying image.

F6: The system shall allow customers to browse and search for items by category, select desired products, place orders, and proceed with secure payment processing.

F7: The system shall enable online sellers to manage order processing. Once confirmed, logistics personnel shall prepare items for shipment, update the package status, upload packaging verification photos, and generate a corresponding waybill. F8: The system shall facilitate payment completion for online sellers and automatically issue a digital receipt containing a tracking number.

F9: The system shall maintain a comprehensive record of all packages handled by logistics personnel and display shipment statuses accordingly.

F10: The system shall provide delivery drivers with receiver information, allow them to upload delivery proof in the form of photos, and automatically update the delivery status upon completion. F11: The system shall allow customers to submit a video review post-delivery, receive a discount voucher for future purchases, and provide feedback regarding the condition and safety of the received package.

F12: The system shall display customer-submitted video reviews to logistics personnel, automatically issue discount vouchers based on review validity, and present statistics on the total quantity of bubble wrap collected and redeployed.

Data

D1: User data (first name, last name, phone, address, username, password, role) shall be securely encrypted and stored in the database to ensure user privacy and prevent unauthorized access.

D2: Product data (product name, description, price, quantity, category, images) shall be maintained in a relational database, with images stored securely for efficient retrieval and display.

D3: Shopping cart data (user ID, product details, quantity) shall be dynamically updated to reflect real-time changes and ensure accurate cart management.

D4: Order data (user ID, customer details, payment method, total price, shipping fee) shall be stored to support order processing, auditing, and fulfillment tracking.

D5: Package data (sender and recipient details, item info, pouch size, wrap status, proof of delivery) shall be recorded for monitoring shipments and verifying eco-wrapping compliance.

D6: Waybill data shall include sender and recipient information, shipping status, and tracking number to ensure traceable and transparent delivery.

D7: Payment data (order number, sender name, amount, contact) shall be securely handled and linked with verified payment gateways for transaction integrity.

D8: Shipment data (order ID, customer info, rider ID, delivery status, timestamps) shall be logged for delivery verification and rider coordination.

D9: Coupon data (file details, coupon code, usage status) shall be stored with validation to track discount applications and ensure proper reward allocation.

D10: Pouch stock data (pouch size, bubble wrap rolls, daily consumption) shall be maintained for sustainable packaging inventory tracking and restocking.

D11: Document data (BIR certificate, valid ID) shall be securely stored to verify shop owner legitimacy and platform compliance.

User Interface

The Greencart platform features a sustainability-focused user interface designed to streamline online shopping while promoting environmentally conscious practices. It offers intuitive modules for product browsing, and voucher rewards. The interface supports seamless order placement, bubble wrap return logging, and transparent shipment tracking empowering users to make environmentally responsible choices with ease and efficiency.

UI1: Package Specification

The Package Specification interface streamlines the process of sending and receiving parcels by collecting comprehensive sender and recipient information, including name, contact number, and detailed address. Additionally, the system records essential package details such as item name, weight, quantity, and item value. A unique feature of this interface is the Wrap Image upload function, allowing logistics personnel to capture and upload a photo of the package after it has been wrapped. Alongside the image, a Wrap Status field is included, where personnel can document the quality of the wrapping as "Perfectly Wrapped" or other predefined statuses. This visual verification and status logging provide accountability for packaging quality, ensuring that items are securely packed to minimize damage during transit.

UI2: Shipping Rates Management

Non-Functional Requirements

The Shipping Rates Management interface enables logistics personnel to efficiently manage shipping fees by allowing them to add, edit, and delete shipping rates based on various weight categories and delivery regions. When entering package details in the Package Specification interface, the system automatically calculates the applicable shipping fee based on the sender’s and recipient’s locations, ensuring consistency and accuracy. Additionally, shipping rates can be adjusted to reflect changes in pricing policies or operational costs, promoting flexible and up-to-date fee management. This automated calculation and centralized rate management reduce manual errors and streamline the shipping process.

UI3: Package Management

The Package Management interface provides a comprehensive view of all outgoing and incoming parcels, displaying complete sender and recipient information, including names, contact numbers, and addresses. This centralized display enables logistics personnel to track package details effectively, ensuring accurate delivery coordination. Additionally, the interface categorizes packages based on shipping status, such as "In Transit," "Delivered," or "Pending," allowing for quick monitoring and status updates. By consolidating essential package data in one interface, the system streamlines communication between senders and recipients, reducing delivery errors and enhancing operational efficiency.

The Bubble Wrap Returns Management interface facilitates the processing and tracking of returned bubble wrap from customers. This interface displays the sender’s name, the weight of the returned bubble wrap in kilograms, and provides an option to generate a coupon code based on the returned quantity. Logistics personnel can review and verify the condition of the returned materials, ensuring they meet the required standards for reuse. Once validated, a unique coupon code is created and provided to the customer as a reward for their participation in the recycling initiative. This process not only encourages sustainable practices but also maintains accurate records of reusable packaging materials.

UI5: Coupon Redemption

The Coupon Redemption interface provides customers with a convenient way to view and claim discount coupons generated from returned bubble wrap. Once the logistics personnel verify the returned materials and issue a coupon, the customer automatically receives a notification of the coupon code along with the corresponding discount value. Customers can then apply the coupon during their next purchase to avail of the discount, ensuring a seamless redemption process. The interface also includes a claim button to confirm coupon usage, updating the system to prevent multiple redemptions and maintain accurate coupon tracking.

UI6: Voucher Wallet

The Voucher Wallet interface consolidates all claimed coupons into a centralized voucher section, accessible through a voucher icon. Once a customer claims a coupon from the Coupon Redemption interface, it is automatically added to their Voucher Wallet for easy access. Customers can view all available vouchers, including discount amounts, expiration dates, and usage status. During checkout, the system allows customers to select a voucher to apply the discount to their current order, streamlining the purchasing process and promoting repeat transactions.

UI7: Order Placement with Voucher Application

The Order Placement interface enables customers to place orders and apply discount vouchers seamlessly. When proceeding to checkout, customers can select a voucher from the Voucher Wallet, and the system will automatically deduct the discount amount from the total purchase cost. The interface displays the original amount, discount applied, and the final total, providing clear visibility of the savings. This integration ensures that customers can conveniently use their coupons while completing the order, promoting a streamlined purchasing experience and encouraging repeat use of the recycling program.

UI8: Product Listings and Delivery Reviews

The Product Listings and Delivery Reviews interface organizes products into specific categories, making it easier for customers to browse and select items. Each product post displays detailed information, including the product name, price, available quantity, and packaging type. Additionally, the interface features a Delivery Reviews section, where customers can view feedback from previous buyers regarding delivery quality and packaging condition. This section helps build trust by showcasing transparency in service quality and encouraging other customers to provide their own delivery feedback after receiving their orders.

Non-Functional Requirements

Technical Requirements

T1: Response Time Under 3 Seconds: The system shall maintain an average response time of less than 3 seconds for key user actions, such as product searches, order submissions, and payment processing.

T2: Peak Load Capacity: The system shall handle up to 300 concurrent users without noticeable performance degradation, ensuring stable operations during promotional periods and peak shopping hours.

T3: Data Backup and Recovery: The system shall implement automated daily backups of critical data, including order records, customer profiles, and payment transactions, with a recovery time objective (RTO) not exceeding 2 hours.

T4: Scalability: The platform shall utilize a scalable cloud infrastructure (e.g., AWS, Azure, or InfinityFree) to accommodate growth in user accounts, product listings, and transaction volumes without impacting performance.

T5: Resource Optimization: The system shall be optimized to minimize CPU and memory usage, ensuring smooth performance on devices with lower processing power, such as entry-level smartphones.

Security Requirements

S1: Data Encryption

All sensitive data shall be encrypted both in transit and at rest to safeguard against unauthorized access and data breaches.

S2: Authentication and Authorization

The system shall implement robust authentication mechanisms to verify user identities and enforce role-based authorization to ensure users can access only the data and functions permitted to their roles.

S3: User Role Management

Role-based access control (RBAC) shall be enforced to restrict system actions based on user roles, thereby minimizing the risk of unauthorized operations.

S4: Secure Transaction

All transactional activities shall be conducted over secure HTTPS connections and incorporate validation protocols to prevent data tampering, interception, or leakage.

S5: Security Audits and Vulnerability Testing

The system shall undergo regular security audits and automated vulnerability scans to detect, report, and remediate potential security threats proactively.

Legal Requirements

L1. Compliance with the Data Privacy Act of 2012 (RA 10173)

The system shall adhere to the Data Privacy Act by ensuring secure collection, storage, and processing of personal data, with appropriate measures for consent, access control, and user privacy.

L2. Compliance with the Consumer Act of the Philippines (RA 7394)

Product listings shall be honest and accurate, return policies shall be transparent, and promotional practices shall be fair and compliant with consumer protection standards.

L3. Compliance with the E-Commerce Act of 2000 (RA 8792)

The platform shall support legally recognized electronic transactions and contracts, ensuring secure digital processing in line with national e-commerce regulations.

L4. Compliance with BIR Tax Regulations

All financial transactions shall be properly documented and stored to support the generation of digital receipts and ensure compliance with Bureau of Internal Revenue (BIR) tax reporting requirements.

L5. Compliance with the Intellectual Property Code (RA 8293)

The system shall respect intellectual property laws by protecting its branding elements and ensuring that no copyrighted or trademarked content is used without proper authorization.

User Requirements

To deliver a seamless and eco-conscious shopping experience, GREENCART shall prioritize simplicity, accessibility, and environmental responsibility in its system design. Ongoing enhancements will be informed by user feedback to maintain engagement and satisfaction.

U1: Ease of Use

The system shall feature an intuitive allowing both customers and sellers to navigate the platform, complete transactions, and manage their activities with ease. U2: Accessibility

The system shall be accessible via desktop devices and follow accessibility standards to accommodate all users. U3: Packaging Feedback System

Users shall be enabled to upload unboxing videos and submit evaluations of packaging quality, supporting both quality control and the issuance of eco rewards. U4: Eco-Incentive Program

The system shall incentivize sustainable behavior by encouraging users to return packaging materials in good condition, thereby supporting reuse and recycling initiatives.

U5: Real-Time Order Tracking

Users shall receive real-time updates regarding order status, packaging verification, and voucher issuance through the platform's notification system.

Development and Testing

Development Methodology

Agile methodology was chosen for the development of Greencart to ensure adaptability, continuous improvement, and user centered progress. Its iterative process allowed key features such as packaging validation, eco incentive tracking, and role-based workflows to be built, tested, and improved in short development cycles. Regular stakeholder feedback helped align the system with user needs and sustainability goals, while minimizing risks and ensuring functionality throughout each phase.

Development Phases

1. Requirements Gathering:

The requirements for Greencart were gathered through iterative consultations with stakeholders, including potential users, logistics personnel, and online sellers. These sessions focused on understanding functional needs such as eco incentivized returns, packaging management, and role-based system access. Continuous feedback loops allowed the team to refine priorities and align the platform’s features with the expectations and behaviors of its target users.

2. Design:

The system was designed with a modular and scalable architecture to support maintainability and future expansion. The user interface prioritized clarity and ease of navigation, ensuring that customers, sellers, and logistics personnel could interact with the system intuitively. Design elements such as wireframes, user flows, and prototype interfaces were developed and iteratively refined based on usability testing and stakeholder input.

3. Implementation:

Development was carried out in structured sprints, each focused on building and enhancing core system functionalities. These included the account management module, packaging validation system, eco reward automation, and logistics workflow integration. Best practices such as code versioning, regular peer reviews, and continuous integration ensured high code quality and system consistency.

4. Testing:

  • A comprehensive multi-level testing strategy was employed to validate system performance and usability:

  • Unit Testing: Assessed the reliability of individual components, such as size detection and packaging allocation.

  • Integration Testing: Verified that modules worked cohesively across roles customer, seller, logistics, and admin.

  • System Testing: Evaluated the full end to end transaction process to ensure a seamless user experience and system stability.

  • User Acceptance Testing (UAT): Collected feedback from real users, which was instrumental in fine tuning the platform’s usability and ecological features.

5. Deployment:

The platform was deployed in a controlled, cloud-hosted environment to support scalability and ensure availability. A phased rollout strategy was implemented, allowing the team to monitor performance, identify unforeseen issues, and apply fixes before full scale deployment.

6. Maintenance:

Post deployment, Greencart entered an active maintenance phase, with regular updates driven by user feedback and system monitoring. This included bug fixes, performance enhancements, feature adjustments, and the introduction of new capabilities aligned with Greencart sustainability goals. Security protocols were also routinely updated to safeguard user data and ensure regulatory compliance.

Development Environment

The development of Greencart utilized a structured set of tools and technologies to ensure efficient, scalable, and user-centered development.

1. Programming Languages:

  • PHP: Used for backend development and handling server-side logic.

  • HTML / CSS: Employed for structuring and styling web pages to ensure a clean and responsive layout.

  • JavaScript: Implemented to enhance interactivity and improve user experience on the front end.

2. Development Tools:

  • Notepad++: A lightweight code editor used for writing and editing PHP, HTML, CSS, and JavaScript efficiently.

  • XAMPP: Provided a local development environment, integrating Apache server, MySQL database, and PHP for backend processing.

3. Database:

MySQL: Served as the relational database system to manage and store essential platform data such as user information, order records, and packaging statistics.

4. Hosting:

InfinityFree: A free web hosting service used to deploy the system online for testing, user demonstrations, and accessibility.

5. Operating System:

Windows: All development and deployment tasks were carried out on a Windows-based system, ensuring full compatibility with the selected tools and software.

Testing Procedures

To ensure the functionality, reliability, and sustainability of the Greencart platform, structured testing was conducted throughout development:

1. Unit Testing: Individual components and modules were tested to ensure each functioned correctly in isolation. This included core features like packaging allocation, bubble wrap tracking, and voucher issuance.

2. Integration Testing: The interaction between system components, such as customer, logistics, and administrative workflows, was tested to confirm seamless data flow and system interaction. This included testing the integration of user account management and order processing.

3. System Testing: The complete system was tested against the specified requirements to evaluate its overall performance, security, and usability. Key functions, such as order placement, packaging validation, and return processing, were tested to ensure smooth transactions and effective tracking.

4. User Acceptance Testing (UAT): End-users, including customers and logistics personnel, participated in testing the system. Feedback was collected to validate whether the system met user expectations regarding usability, functionality, and sustainability features.

5. Test Data: Sample data included mock user accounts and product listings, while real-world scenarios focused on actual user interactions to assess system performance.

6. Test Metrics: System stability and reliability were assessed by tracking defect density and the test pass rate.

Implementation Plan

Project Schedule

The implementation of Greencart adhered to a structured project schedule, utilizing a Gantt chart to effectively monitor progress and ensure timely completion of each development phase:

1. Use of Project Management Tools:

A Gantt chart was employed to visualize the project timeline, track key milestones, and maintain adherence to the planned schedule.

2. Key Milestones:

Week 1: Requirements gathering, competitor analysis, and UI/UX design for customer, seller, and logistics interfaces.

Week 2: Development of user registration, authentication, and role-based access for customers, sellers, and logistics personnel.

Week 3: Implementation of product listing features, packaging allocation, and bubble wrap tracking.

Week 4: Integration of packaging verification photo upload, unwrapping guide, and the bubble wrap tracker system.

Week 5: Development of the eco-incentive program, return process for bubble wrap, and reward system.

Week 6: System testing, debugging, and internal quality assurance reviews.

Week 7: User acceptance testing (UAT) with pilot users and incorporation of final feedback.

Week 8: Final adjustments, full deployment, and post-launch monitoring.

3. Resource Allocation:

  • Project Lead: Oversees all development phases, ensuring alignment with objectives and timely completion of deliverables.

  • Developer: Responsible for coding, testing, and implementing features such as user registration, product listing, and packaging allocation.

  • Tester: Conducts system testing, gathers UAT feedback, and verifies the functionality of the bubble wrap tracker and eco-incentive program.

4. Estimated Time and Effort:

Each phase was allocated approximately one week, with daily progress checkpoints. Effort distribution is as follows:

  • Design: 10%

  • Development: 50%

  • Testing and Debugging: 30%

  • Deployment and Final Adjustments: 10%

5. Tracking Progress:

Regular monitoring was conducted to maintain alignment with the schedule. Any delays were addressed through resource reassignment or timeline adjustments. Weekly status reports documented progress, highlighted key milestones, and outlined completed phases.

Resource Allocation

To successfully implement the Greencart platform, various resources are required, including human, hardware, software, and financial resources. These resources ensure smooth development, testing, and deployment while maintaining efficiency and cost-effectiveness.

1. Human Resources:

  • Project Manager

  • Frontend Developer

  • Backend Developer

  • UI/UX Designer

  • System Tester

2. Hardware Resources:

  • Windows-based development machines with at least an Intel i3 processor.

  • Local server setup using XAMPP.

  • Stable internet connection for development, testing, and cloud deployment.

3. Software Resources:

  • Notepad++ for code editing

  • XAMPP for local development and server simulation

  • InfinityFree for web hosting

  • Chrome for cross-browser testing

4. Financial Resources:

  • Domain, hosting, and design tool expenses estimated at PHP 3,000–5,000.

Risk Management

To ensure the successful development, deployment, and sustainable operation of Greencart, potential risks were systematically identified, assessed, mitigated, and continuously monitored.

1. Risk Identification

Technical Risks: Issues with module integration, software bugs, or scalability limitations during peak transaction periods.

Financial Risks: Unexpected costs for cloud storage, third-party fees, or additional server resources for increased user demand.

Operational Risks: Development delays due to limited resources or unforeseen technical challenges in implementing new features.

Security Risks: Data breaches, unauthorized access to verification photos, or vulnerabilities in transaction processing systems.

User Risks: Low user engagement with new features due to unclear instructions or lack of awareness.

2. Risk Assessment

Risk

Likelihood

Impact

Priority

Bugs or errors in packaging module

High

High

Critical

Data breaches

Medium

High

Critical

Budget overruns

Medium

Medium

High

Delayed return validations

Medium

Medium

Medium

Logistics delays in remote areas

Medium

Medium

Medium

3. Risk Mitigation

  • Technical Risks: System bugs, API integration failures, or performance issues under high user load.

  • Financial Risks: Unanticipated expenses related to hosting upgrades, external tools, or feature scaling.

  • Operational Risks: Delays in feature deployment due to limited resources or unforeseen development hurdles.

  • Security Risks: Potential data breaches, unauthorized access, or weak data protection measures.

  • User Risks: Low adoption of packaging return features or minimal user participation in eco-incentives due to lack of awareness or poor usability.

4. Risk Monitoring

  • Weekly Reviews: Regular meetings to assess and update risk management strategies.

  • User Feedback: Continuous input collection to address issues promptly.

  • System Monitoring: Automated tools used to track performance and detect issues.

Communication Plan

Communication Channels

  • Meetings: Virtual and in-person team discussions.

  • Email: For formal updates and documentation.

  • Project Management Tools: Trello for task tracking and progress monitoring.

  • Instant Messaging: Gmail and Messenger for quick updates.

  • Document Storage: Google Drive and GitHub for storing project files.

Communication Protocols

  • Clear agendas and documented meetings.

  • 24-hour email response time.

  • Immediate reporting of critical issues.

  • Regular milestone updates to stakeholders.

Capstone Project Deployment Results

The Greencart system was deployed from April 22, 2025, to May 8, 2025. The deployment involved 3 customers and 1 logistics personnel in Davao City. During this period, user interactions with the platform, including packaging documentation and discount exchanges, were closely monitored in real-world scenarios. Challenges arose due to high customer volume and parcel releases for delivery drivers. Despite these challenges, both participants remained cooperative and engaged, effectively using the system and demonstrating its potential for real-world application.

General Objective: Decrease bubble wrap disposal by 30% per week in customer returns.

Week

Bubble Wrap Returned (kg)

Total Bubble Wrap Distributed (kg)

Returned Bubble Wrap

Week 1

0.7 kg

35 kg

2%

Week 2

0.6 kg

30 kg

2%

Table 4.1 Current System of Returned Bubble Wrap Tracker

Figure 4.5 Returned Bubble Wrap and Incentive List on Logistic Personnel Page

A related study by Karekla and Karademas (2021) highlighted the impact of prosocial incentives in mitigating plastic waste through donation-based rewards, effectively reducing plastic bag use from 32% to 10%. Similarly, the University of the Philippines Diliman (2023) implemented a reusable alternatives program, achieving a 43% decline in single-use plastic over three weeks by offering incentives and discounts. Greencart adopts a similar approach, incentivizing customers to return bubble wrap through app-based tracking and video verification, reinforcing responsible disposal practices.

Table 4.1 and Figure 4.5 provides data on customer returns of bubble wrap collected between April 25 and April 26, 2025. The table details the weight of returned bubble wrap, categorized by return date and verified through video proof submissions. Each kilogram deemed reusable is rewarded with a ₱1 coupon, establishing a tangible incentive for participants while promoting circular waste management.

The Greencart system effectively aligns with its objective of decreasing bubble wrap disposal by 30% per week by systematically tracking returns and integrating digital verification. The collected data reveals consistent customer engagement and precise monitoring, reducing manual tracking errors and supporting previous findings by Karekla and Karademas (2021) and UP Diliman (2023). By merging incentive-based returns with digital validation, Greencart fosters sustainable waste management practices and encourages ongoing participation in environmentally conscious behaviors.

Specific Objective 1: Reduce bubble wrap usage by 10% per month in the logistics company.

Pouch

Total Bubble Wrap Distributed (kg)

Bubble Wrap Roll (Current)

Daily Consumption (m)

Bubble Wrap Roll (Greencart)

small

200

2 meters

11

1 roll

medium

200

2 meters

14

2 rolls

large

200

2 meters

15

3 rolls

xl

200

2 meters

16

4 rolls

Table 4.2 Compared Bubble Wrap Consumption of Current System and Greencart

Figure 4.6 Available Stock History on Logistic Personnel Page

A related study by the IVL Swedish Environmental Research Institute (2024), titled "Review of Life Cycle Cost Analysis for Reusable Packaging for the Automotive Industry," implemented a life cycle cost analysis to compare single-use and reusable packaging in logistics. The study found a 20% reduction in packaging costs and a 31% decrease in carbon footprint through reusable packaging. This method aligns with Greencart objective to reduce bubble wrap usage by 10% per month by optimizing daily consumption and roll distribution.

Similarly, the World-Wide Fund for Nature (WWF, 2024) analyzed reusable packaging systems in their report "Reuse in the Global South: Case Studies," identifying a 20% reduction in plastic waste leakage. Greencart strategy to track daily consumption per pouch size and implement reuse models aligns with this approach, as evidenced by the data in Table 4.2.

To assess the objective, the Greencart system monitored daily bubble wrap consumption, recording the initial and reduced usage for each pouch size. As shown in Figure 4.6, the system tracked data from April to May 2025, noting a consistent reduction in daily consumption across all pouch sizes. The significant decrease in material usage supports the feasibility of achieving a 10% monthly reduction target. The system’s data analysis further emphasizes the importance of tracking consumption patterns to identify high-usage areas and implement targeted reuse strategies.

Specific Objective 2: Reduce defective product deliveries by 30% per week in the logistics company.

Order Id

Receiver

Delivery Date

Logistics_action

(Current)

Wrap Status

(Greencart)

Wrap Image (Greencart)

Customer Review

1001

Rolly@

Apr 01, 2025

Packed

Perfectly Wrapped

📷 IMG_ORD001.png

"Well packed. No damages. Satisfied."

1002

Lito@

Apr 01, 2025

Packed

Perfectly Wrapped

📷 IMG_ORD001.png

"Bubble wrap intact. Smooth delivery."

1003

Jm@

Apr 01, 2025

Packed

Perfectly Wrapped

📷 IMG_ORD001.png

"Bubble wrap intact. Safe delivery."

Table 4.3 Current System Logistics and Greencart Wrap Process

Figure 4.7 System Logistics Wrap Process on Logistic Personnel PageA related study by Escudero-Santana et al. (2022) examined the impact of offering multiple delivery time and location options on reducing service failures, including defective deliveries, in last-mile logistics. In line with this, the proposed Greencart system improves packaging and delivery methods by integrating real-time feedback from customers (as shown in Table 4.3) and visual verification of packaging conditions (Figure 4.7). By utilizing these methods and continuously monitoring customer reviews and packaging conditions, the system aims to reduce defective deliveries, aligning with the study's conclusion that delivery flexibility and optimized logistics handling reduce defect rates in e-commerce.

Similarly, Dunn (2013) explored the importance of packaging integrity in reducing defective product deliveries in e-commerce. The Greencart system directly addresses this issue by providing clear guidelines for packaging integrity and using image-based verification (as shown in Figure 4.7). These features enable Greencart to minimize packaging failures and prevent damage during delivery. The proactive approach to packaging management aligns with Dunn’s findings that better packaging standards lead to fewer defective deliveries.

Furthermore, Wang et al. (2022) investigated the relationship between faster package delivery and reduced product return rates. Greencart takes this a step further by enhancing packaging quality alongside delivery speed, ensuring that products arrive undamaged. This approach mirrors Wang's conclusions that optimizing both delivery speed and product handling results in reduced product returns, thus supporting Greencart’s aim of reducing defective deliveries by 30% per week.

The success of Greencart can be attributed to its systematic tracking of bubble wrap returns, optimized packaging processes, and real-time monitoring of delivery conditions. By integrating automated incentive-based returns and using video verification, Greencart reduces manual tracking errors while encouraging responsible disposal practices. The consistent reduction in bubble wrap usage and defective deliveries demonstrates the platform’s effectiveness in fostering sustainable waste management and enhancing product handling critical factors for e-commerce businesses where packaging integrity directly impacts customer satisfaction and operational efficiency.

In conclusion, the digital transformation facilitated by Greencart aligns with best practices identified in the literature and validates the project's specific objectives. By incentivizing returns and tracking packaging integrity, the system not only reduces waste and defective deliveries but also strengthens environmental and operational sustainability, reinforcing stakeholder trust and contributing to the company’s overall performance.

UI4: Bubble Wrap Returns Management

Figure 4.2 Agile Methodology