Feature Requests

In the provider application: Automatically assign offer preferences to all suppliers who have just created an account so that they can be informed of all personalized requests. Make sure that the client also sees all previous old vacancies. On the customer application: Make sure that the customer and the supplier can communicate directly from the personalized offer. this will therefore prevent the customer from leaving. on the provider's profile in order to initiate the discussion. do this directly in the personalized offer page. Give the provider the opportunity to create a service billing invoice once he and the customer have agreed on all the details in the chat. The invoice will be generated directly according to the payment method activated by default by the administrator. NB: the amount of the invoice may differ from the price of the actual service displayed on the supplier's profile. The supplier must also, before initiating the invoice, give all the details and a capture of his conversation with the customer as proof for the administrator. Administrator: In order to better manage the translation pane, give the possibility to add banners according to each available language (a banner to save for English, French, German, etc... ) Make the default language banner mandatory and leave the others optional Facebook instagram facebook instagram Add an option, advertising, to allow the provider to highlight its service in the form of advertising (Facebook, instagram, x) He pays for a defined period according to the amounts that the administrator will have defined for each term.

Dynamic Provider Document (KYC) Configuration — Admin Controlled The document/KYC requirement system should be configurable from the Admin Panel instead of being fixed. Admin Panel Requirements Admin must be able to create and manage document requirements dynamically, including: Add new document type Edit existing document type Delete/disable document type For each document type, admin must be able to configure: Document Name Example: Aadhaar Card, PAN Card, Police Verification, Trade License, etc. Number of Image Upload Fields One image (front only) Two images (front & back) Image Field Labels Example: Image 1 Name → Front Side Image 2 Name → Back Side Document ID Number Requirement Enable/Disable ID number input field Example: Aadhaar number, PAN number Mandatory / Optional Toggle Mark document as compulsory or optional Category-Based Requirement (Optional Enhancement) Admin can assign document requirements based on provider category Example: Electricians require License Carpenters do not Interior contractors require GST/Registration Provider App Behavior During registration/KYC submission: Providers see document upload fields dynamically based on admin configuration Providers upload images and enter ID numbers (if required) After submission: Documents cannot be edited Any change request requires admin approval Purpose This flexible system allows document requirements to be updated without changing code and supports different verification needs for different provider types. This should replace the fixed document upload structure currently in the provider app. want documents verified in 3 statuses like this? Pending Review Approved Rejected (with reason) Rules: Documents cannot be edited after submission Any modification must require admin approval

There are two possible options for this: Admin-based setting Provider-based setting But your system is currently fully provider-based, so I will explain it in that way. Provider-Based Time Slot Settings In the provider panel and app, you can create a new page called Time Slot Settings. I will explain the advance booking system. You can design and implement it in your own way. At a minimum, the following fields are required: Slot Duration This field defines the duration of each slot. Example: If the provider sets 1 hour, slots will be shown every 1 hour. If the provider sets 5 minutes, slots will be shown every 5 minutes. Break Time (in minutes) This field defines the gap between slots. Example: If slot duration is 1 hour, slots will normally show as: 9:00, 10:00, 11:00 If the provider sets a 30-minute break, slots will show as: 9:00, 10:30, 12:00 Booking Delay (in hours) This controls how much delay is required for same-day bookings. Example: If the current time is 1:00 PM And the provider sets a 1-hour booking delay The first available slot will be shown from 2:00 PM This is a mandatory field. At least this option is required. Multiple Bookings (Optional) Provide an Enable / Disable option. If enabled, show a field where the provider can set the number of allowed bookings (e.g., 1, 2, 3, 4). Example: If set to 2, the same time slot (e.g., 9:00 AM) can be booked twice. After two bookings, that slot will be blocked and the next slot (10:00 AM) will be shown. This is useful for providers who have multiple workers, so they can handle more than one job at the same time. Working Hours This option already exists in your system. All these options are already implemented in my website ( brobookme.com ). You can check it for reference.

One more important point—this is crucial and useful for everyone. In your provider panel, you already have a Visiting Charges field. I suggest adding one more field called Minimum Booking Amount. Minimum Booking Logic Example: Visiting charges: ₹150 Minimum booking amount: ₹500 If a user books services below ₹500, the visiting charge (₹150) will be applied. If a user books services ₹500 or above, the visiting charge will be removed automatically. Implementation Notes You need to: Add one additional field in the provider panel (Minimum Booking Amount). Store this value in the database. Add simple logic in the frontend and cart page to calculate and apply or remove the visiting charge. Visiting charges logic is already implemented everywhere, so this is only a small extension of the existing system. Benefits This gives more control and flexibility to providers. It prevents low-value bookings, which are often not worth the provider’s time. Many providers cancel such bookings, which negatively affects the platform. This is especially useful in India, where low-value bookings are common. Users who book low-value services can still proceed by paying a visiting fee, which fairly covers travel costs. Industry Reference This concept already exists in many platforms: Zomato Food delivery apps Grocery delivery platforms Amazon (minimum order / delivery fee logic) This feature helps both users and providers and improves overall booking quality.

Hi Team, I would like to request a Loyalty Points / Rewards system in the eDemand app to increase repeat customers and boost bookings. ✅ How it should work Customers earn loyalty points on every successful booking/payment Example: 1 point = ₹1 or 0.1 Points should be added only after booking marked as completed Customers can redeem points in next booking as discount Admin should control: Points per ₹ spent (or %) Minimum redeem limit (ex: 50 points) Maximum redeem limit per order (ex: 10% of bill) ✅ Where to show points Customer App: Wallet / Profile section Checkout screen (Redeem Points option) History (Earned & Used points) Admin Panel: Loyalty settings section Customer points list Transaction logs Partner Panel/App (optional): Show points used in booking invoice/order details ✅ Benefits Increase customer retention + repeat bookings Encourages higher cart value Improves brand loyalty Please consider adding this as a core feature. Thank you 🙌

I need a configuration in the system to set a delay for booking slots to appear after a specific number of hours. Currently, if the present time is 11:42 a.m., the booking system shows now the next available slot at 12:00 p.m. but we need to show after 4 hours Examples: If I set a 4-hour delay, the earliest available slot should be 4:00 p.m. (present time + 4 hours). If I set a 2-hour delay, the earliest available slot should be 2:00 p.m. (present time + 2 hours). Feature: Show Available Slots for Today or Tomorrow Objective: If no available slots are present for today, the system should automatically display the available slots for the next day (tomorrow). The system should operate within the service hours (9:00 AM to 6:00 PM), and any slots outside this window should not be shown. Key Features: Service Hours: Start Time: 9:00 AM End Time: 6:00 PM The system should only offer slots within this time frame. Available Slots Filtering: Today’s Availability: When a customer accesses the booking system, show available slots for today (if there are any). If there are no available slots for today, automatically display available slots for tomorrow (next day) within the same service hours (9:00 AM to 6:00 PM). Slot Calculation: Current Time Check: The system needs to check the current time to determine available slots for today. If no slots are available today, the system will skip to the next day (tomorrow) and show the available time slots (starting from 9:00 AM) for that day. Slot Presentation: If today has no available slots due to the "Limit late bookings" or time of day, only show tomorrow’s available slots. Ensure that the available slots are filtered correctly by considering both: The current time and the Limit late bookings restriction (e.g., 4 hours). The service hours (9:00 AM to 6:00 PM). No Booking Outside Service Hours: Any times outside the service hours of 9:00 AM to 6:00 PM should never be displayed to the customer. Behavior When Slots Are Full: If all slots for today are unavailable (due to being fully booked or restricted by the Limit late bookings), the system will not show any slots for today and will move directly to the available slots for tomorrow. Example Scenarios: Scenario 1: Available Slots for Today Current Time: 2:00 PM, Limit late bookings: 4 hours. Available slots for today: 6:00 PM (since it's within service hours and after the Limit late bookings). Available slots for tomorrow: 9:00 AM, 10:00 AM, etc. Scenario 2: No Available Slots for Today Current Time: 5:00 PM, Limit late bookings: 4 hours. No available slots for today because the next available time would be after service hours (6:00 PM). Available slots for tomorrow: 9:00 AM, 10:00 AM, etc. Scenario 3: After 6:00 PM (End of Service Hours) Current Time: 7:00 PM. Limit late bookings: 4 hours. No slots available for today. Available slots for tomorrow (starting from 9:00 AM). Backend Considerations: Database: The database should store the available time slots for each day, within the service hours (9:00 AM to 6:00 PM). The system should calculate available slots based on the current time and the “Limit late bookings” setting. Time Slot Calculation: If the current time is within service hours and slots are available for today, display them. If there are no available slots for today, display available slots for tomorrow starting from 9:00 AM. Make sure to adjust the system logic for the transition between days (e.g., the transition from today to tomorrow after 6:00 PM). No Overlapping Times: Ensure that time slots do not overlap with existing bookings and only show slots that are actually available. User Interface Behavior: Available Slots for Today: The customer will see the available time slots for today based on the current time and the "Limit late bookings." No Slots for Today: If there are no slots available for today, only tomorrow’s available slots will be shown. Example UI: Available Slots for Today: 6:00 PM Available Slots for Tomorrow: 9:00 AM, 10:00 AM, etc. End Result: Customer Experience: Customers will see a seamless flow of available slots, starting with today’s available slots if any, and automatically moving to tomorrow’s slots if no slots are available for today. Admin Control: The admin can configure the "Limit late bookings" and ensure that customers only see the available slots in line with service hours (9:00 AM to 6:00 PM).

Create New Review (Admin Access): Allow the admin to create reviews for services or products manually. This can be useful for testing purposes or for responding to reviews that need to be displayed on the platform. The admin should be able to enter a rating (e.g., stars), a review comment, and associate it with a specific user or service. Edit Customer Reviews: Provide an option for admins to edit customer reviews. This can be useful if there's a typo or if a customer updates their review. Admin should be able to modify the rating, comment, and any additional feedback provided by the customer. Delete Reviews: Admins should have the ability to delete any review, whether it's a customer review or an admin-created review. This option can be for removing inappropriate, fake, or spam reviews. Approval Process (Optional): Add a feature where reviews are pending approval before being posted publicly. The admin can review and approve or reject the reviews. Moderation: Admins can also flag certain reviews for further investigation, such as those containing inappropriate language or violating policies. Search & Filter Reviews: Allow the admin to search reviews by user, rating, date, or keywords. Enable filtering options to view reviews from specific dates or services. Notifications: You may want to notify the admin when a new review is submitted, allowing them to take quick action.

example Set a minimum booking amount, e.g., ₹500. If the customer’s booking does not meet this amount, a visiting charge of ₹100 (or another specified amount) will be applied. If the booking meets or exceeds the minimum amount, no visiting charge will be added Logic for Minimum Booking Policy Minimum Booking Amount: Set a minimum booking threshold, e.g., ₹500. If Booking Value < Minimum Threshold: Add a visiting charge (e.g., ₹100) to the final bill. If Booking Value ≥ Minimum Threshold: No visiting charge is added. Display to Customers: Inform customers about the minimum booking requirement and visiting charges upfront during the booking process. Allow admins to: Set or update the minimum booking amount. Adjust the visiting charge. Enable or disable the minimum booking policy dynamically. description can modify UI Workflow: Add a tooltip or note near the pricing summary to notify users. Example: "Minimum booking amount is ₹500. If the booking value is below ₹500, a visiting charge of ₹100 will be applied.

Pricing Logic Condition 1 (First Service): The first service is priced at ₹299. Condition 2 (2 to 5 services): For the 2nd to the 5th service, each additional service costs ₹100. Condition 3 (After 5 services): From the 6th service onwards, each additional service costs ₹80. Examples: 1 Service: Total = ₹299 2 Services: Total = ₹299 (1st) + ₹100 (2nd) = ₹399 5 Services: Total = ₹299 (1st) + ₹100 (2nd) + ₹100 (3rd) + ₹100 (4th) + ₹100 (5th) = ₹699 6 Services: Total = ₹699 (for 5 services) + ₹80 (6th) = ₹779 8 Services: Total = ₹699 (for 5 services) + ₹80 (6th) + ₹80 (7th) + ₹80 (8th) = ₹939

On-Site Description: The technician will visit the customer's location to perform the required service. Examples: Home repairs, appliance servicing, plumbing, etc. Online Description: The service is provided remotely without a physical visit. Examples: Downloadable resources: PDF files, audio files, etc. Professional services: Web design, interior design consultations, or online courses etc. At Store Description: The customer will visit the store or shop to avail of the service. Examples: Device repairs, custom furniture selection, or in-store consultations etc.