Laravel Backend Customization
Budget: ₹1,500 – ₹12,500 INR
I need a developer skilled in Laravel, Flutter, and MySQL for a quick 3-day customization task.
Requirements:
- Backend customization using Laravel
- MySQL database structure changes, including both creating and altering tables
Ideal Skills:
- Proficiency in Laravel, Flutter, and MySQL
- Experience with database structure modifications
- Ability to meet a tight 3-day deadline
Please provide examples of similar work and confirm your availability.
1. Admin Can Place New Service Orders from the Backend
If a service order is received through a phone call, the admin can manually place the order using the backend system to ensure it is properly recorded and processed.
2. Booking Status Flow
The system should support the following status options for each booking:
Pending
Awaiting
Confirmed
Started
Booking Ended
Rescheduled
Completed
Cancelled
Once a particular status is assigned to a booking, the same status cannot be applied again to prevent duplication and maintain accurate service tracking.
3.Booking Section – Calendar-wise Scheduled Service Details
In the Booking section, service orders should be displayed based on the selected calendar date, including both current and previously uncompleted orders.
For example:
If there are 10 scheduled orders for today, and
There are 4 orders from yesterday that were not marked as completed or rescheduled,
Then upon selecting today’s date, the system should display a total of 14 orders (10 today’s + 4 pending from
yesterday).
4. Adding Additional Charges from the Backend
There should be an option to add additional charges to a current booking from the backend.
For example:
If a customer requests extra services during the visit, or
If the work takes significantly more time or effort than expected,
the technician may charge an extra amount. This additional amount should be recorded and added to the booking from the backend to ensure accurate billing and transparency.
5. Hide Customer Mobile Number After Order Completion or Cancellation
Once an order is completed or cancelled, the technician should no longer have full access to the customer's mobile number. For privacy and security reasons, the system should hide the last 5 digits of the number.
For example:
If the number is 9876543210, it should be displayed as 98765XXXXX after the order status is marked as Completed or Cancelled.
6.Frontend Booking Flow – City Selection and Mobile Number Login Enhancement
In the frontend, when a user starts the booking process, they first select their city. After selecting services and proceeding to the cart, the system currently prompts the user to log in via mobile number.
This flow is already in place, but some improvements are needed, such as:
Ensuring a smoother transition between city selection, service selection, and login.
Avoiding repeated login prompts if the user has already logged in once.
Making the mobile number login process more user-friendly and seamless.
Requirements:
- Backend customization using Laravel
- MySQL database structure changes, including both creating and altering tables
Ideal Skills:
- Proficiency in Laravel, Flutter, and MySQL
- Experience with database structure modifications
- Ability to meet a tight 3-day deadline
Please provide examples of similar work and confirm your availability.
1. Admin Can Place New Service Orders from the Backend
If a service order is received through a phone call, the admin can manually place the order using the backend system to ensure it is properly recorded and processed.
2. Booking Status Flow
The system should support the following status options for each booking:
Pending
Awaiting
Confirmed
Started
Booking Ended
Rescheduled
Completed
Cancelled
Once a particular status is assigned to a booking, the same status cannot be applied again to prevent duplication and maintain accurate service tracking.
3.Booking Section – Calendar-wise Scheduled Service Details
In the Booking section, service orders should be displayed based on the selected calendar date, including both current and previously uncompleted orders.
For example:
If there are 10 scheduled orders for today, and
There are 4 orders from yesterday that were not marked as completed or rescheduled,
Then upon selecting today’s date, the system should display a total of 14 orders (10 today’s + 4 pending from
yesterday).
4. Adding Additional Charges from the Backend
There should be an option to add additional charges to a current booking from the backend.
For example:
If a customer requests extra services during the visit, or
If the work takes significantly more time or effort than expected,
the technician may charge an extra amount. This additional amount should be recorded and added to the booking from the backend to ensure accurate billing and transparency.
5. Hide Customer Mobile Number After Order Completion or Cancellation
Once an order is completed or cancelled, the technician should no longer have full access to the customer's mobile number. For privacy and security reasons, the system should hide the last 5 digits of the number.
For example:
If the number is 9876543210, it should be displayed as 98765XXXXX after the order status is marked as Completed or Cancelled.
6.Frontend Booking Flow – City Selection and Mobile Number Login Enhancement
In the frontend, when a user starts the booking process, they first select their city. After selecting services and proceeding to the cart, the system currently prompts the user to log in via mobile number.
This flow is already in place, but some improvements are needed, such as:
Ensuring a smoother transition between city selection, service selection, and login.
Avoiding repeated login prompts if the user has already logged in once.
Making the mobile number login process more user-friendly and seamless.