Parcel Business Software Development

Job ID: 40598153

Budget: ₹1,500 – ₹12,500 INR

I am looking for an experienced software developer to build a application for my parcel business. This software is only for internal use by employees, not for customers.

The main goal is to simplify parcel booking, tracking, customer communication, and parcel delivery verification.

The software should be easy to use, fast, and require minimal training for staff.

Main Features
1. Parcel Ticket Creation
Create a parcel booking within 30–60 seconds.
Auto-generate Ticket/Parcel Number.
Customer Name
Mobile Number
Receiver Mobile Number
Destination
Parcel Type
Weight
Charges
Payment Status (Paid/To Pay)

2. Parcel Status Management
Employees should be able to update parcel status with one click.

3. Customer Notifications (Official WhatsApp Business API)
Whenever the status changes, the customer should automatically receive a WhatsApp message.

Examples:
Parcel Booked
Parcel Dispatched
Parcel Arrived
Out for Delivery
Delivered

SMS support can be optional.

4. OTP Verification Before Delivery
Before handing over the parcel(through android):

Employee clicks "Generate OTP" and get the payment status
Customer receives OTP on WhatsApp (or SMS if needed)
Customer tells OTP to employee
Employee enters OTP
Parcel marked as Delivered only after successful verification

5. Search by:
Parcel Number

6. Dashboard Show:

Today's Bookings
Delivered Parcels
Pending Deliveries
In Transit
Revenue Today
Pending Payments

7. Employee Login
Different user accounts.:
Admin(owner)
staff
middle man(parcel distributor)

Admin can:
Add users
Edit users
Delete users
View reports

8. Reports
Generate reports for:
Daily
Weekly
Monthly
Date Range

Export to:
Excel
PDF

more detailed explanation:
Our business involves transportation—sending parcels from one location to another. First and foremost, we need the software to be extremely simple—like a ticketing system—where we can easily enter the 'from' and 'to' details. We also need fields for the receiver's and sender's mobile numbers.And the type concept, what kind of parcel is it, what is its weight, total cost and the amount that the customer has paid and how much is to be paid, all these things have to be made in the first ticket in your first step.And then, it should be converted into a ticket. We already have the ticket in a printable format; the customer details simply need to be printed onto it. We will provide you with the dimensions and other necessary specifications.And the ticket should be sent to the receiver's WhatsApp number along with the 'order placed' message.At the same time, as soon as our employee updates the status, a message via WhatsApp conveying that update will be delivered to both the receiver and the sender.The next point to consider is that the middlemen at the delivery locations do not have desktop computers; they will need to perform OTP verification using Android devices. Therefore, we need to develop a solution that works on desktops or Chrome browsers but can also be operated by middlemen via their Android mobile phones.And then, as soon as the middleman—who is to hand over the parcel to the customer—enters the ticket number, a receipt should appear showing the cost and payment status; this allows the middleman to know exactly how much money to collect from the customer. Simultaneously, a random OTP will automatically be sent to the customer via WhatsApp, which the middleman will then enter into the Android to complete the verification.Next, we come to the dashboard. The dashboard provides a complete analysis of sales, as well as details on payments received and pending; this information is accessible to the admin and employees.Next, let's look at the roles involved: there are three types of users. First is the admin, who is the owner; second is the employee responsible for issuing tickets; and third is the middleman, who requires OTP verification but does not have access to the ticketing software itself.Regarding the reports, we only need the data for one week—converted into Excel or PDF format—showing the complete history of all tickets issued and all related information.We don't have a specific requirement for offline software only; we are open to using online software as well.which require internet all the time. Now, let's look at the number of users: the owner will use it, two employees responsible for issuing tickets will use it, and five middlemen will also use it.I need the source code ownership, and the software or website should be built using a modules so that future updates can be implemented.I will let you know soon if there are any further updates