BlessShipping Web Application Requirements

BlessShipping – Software Requirements Document
Version: 1.0
Date: July 12, 2025
Client: BlessShipping.com
Prepared by: Joseph Wang

1. Project Overview
BlessShipping is a logistics scheduling and delivery notification platform designed for small-scale, restaurant-focused intercity delivery services. The platform will manage pickup and delivery points (restaurants or hubs), schedule recurring delivery bus routes, track delivery confirmation, and send WhatsApp notifications to clients.

2. Technology Stack (Preferred)
Backend Framework: Laravel 12.x


Admin Panel: Laravel Backpack (https://backpackforlaravel.com/)


Database: SQLite (for dev) / MySQL (for production)


Frontend: Laravel Blade (admin only); no public frontend needed now


Messaging API: WhatsApp Business API (via Twilio, 360Dialog, or other providers)



3. Core Features
3.1 Location Management
Each pickup/delivery point (e.g., restaurants or hubs) will have:
Code: e.g. St-Hubert 03


Name: e.g. St-Hubert Restaurant


Address


Contact Phone Number


Admin Panel Requirements:
Create / Edit / Delete / List Locations



3.2 Shipping Route Scheduler (Bus Schedule)
Admin defines recurring delivery trips, such as:
From
To
Departure Time
Arrival Time
Frequency
Contact
St-Hubert 03
St-Jean-Sur-Richelieu 01
Mon–Fri 9:00 PM
Next Day 8:30 AM
Daily
514-586-0001


Routes are recurring and weekly-based


Admin can add notes or contact info



3.3 Delivery Confirmation
When a driver picks up a package: click to confirm on admin panel or mobile


When delivered: click to confirm delivery


Each confirmation is timestamped



3.4 WhatsApp Notification System
After delivery is marked as completed:
System sends automated WhatsApp message to the contact phone associated with the delivery point


Example Message:
"Your shipment from St-Hubert 03 has been delivered to St-Jean-Sur-Richelieu 01. Thank you for using BlessShipping!"
WhatsApp API integration should be modular (e.g., Twilio, 360Dialog, etc.).

3.5 Users & Access Control
Only admin/staff logins are needed for now


Staff can be limited to view/confirm specific routes


No customer frontend at this stage



4. Optional (Phase 2)
Not required now, but to be considered for future:
QR code scanning for package pickup/delivery


GPS check-in by driver


Driver login and mobile-friendly panel



5. Deliverables Required
Fully working Laravel-based admin system


All CRUD panels accessible from /admin


WhatsApp test integration (sandbox OK)


README for local and production deployment


GitHub repo or ZIP delivery



Timeline
Preferred delivery: 2–3 weeks
Project to be delivered with basic test data and ready for future enhancements.