-
Notifications
You must be signed in to change notification settings - Fork 0
User Story
For Farmers/Brokers (Senders)
- Registration and Profile Setup User Story: As a farmer/broker, I want to create a profile with my business information, so that I can start using the logistics platform.
Acceptance Criteria:
Collect business details, contact information, and produce types.
Allow users to set preferences for shipping frequency and preferred booking times.
- Price Model Setup User Story: As a farmer/broker, I want to see the price per kilometer when I request a rider, so that I can make informed decisions about the cost of transport.
Acceptance Criteria:
Display rider's price per kilometer during the order request process.
Show a summary of the estimated total cost before confirming the order, including any additional fees.
Provide an option to confirm or cancel the order based on the estimated cost
-
Suggestion and Filtering User Story: As a farmer/broker, I want to see prioritized suggestions for truck owners based on my needs, so that I can quickly find suitable transport options. Acceptance Criteria:
Present a list of truck owners with filters such as type of vehicle, price, capacity, rating, and batch or single path order. Allow users to sort and filter results based on their preferences. Provide detailed profiles of truck owners including vehicle types, capacity, and equipment. Farmer should access to full profile data of riders. Show rider ratings as stars (for MVP, collect ratings by phone surveys with customers and farmers and update in an Excel sheet monthly).
Order Request and Matching System User Story: As a farmer/broker, I want to submit a transport request and have the system match my order with other nearby orders, so that I can reduce transportation costs. Acceptance Criteria: I wrote in detail but we can choose main ones
-
Submission of Detailed Transport Requests
Form Fields: Ensure the transport request form includes fields for:
Pickup location (address, zip code)
Delivery location (address, zip code)
Pickup date and time
Delivery date and time
Type of goods (e.g., perishable, non-perishable, fragile)
Quantity and volume of goods
Special handling requirements (e.g., temperature control, fragile handling)
Validation: Validate all fields to ensure completeness and accuracy before submission.
Save and Edit: Allow users to save draft requests and edit them before final submission. Matching Principles and Algorithm
Geographic Proximity: Match orders based on geographic proximity of pickup and delivery locations.
Radius Filter: Implement a configurable radius filter (e.g., within 50 km) to find nearby orders.
Time Windows: Consider the pickup and delivery time windows to ensure compatibility.
Overlap Tolerance: Allow a configurable tolerance for time overlaps (e.g., +/- 2 hours).
Type of Goods: Match orders with similar handling requirements to optimize transport efficiency.
Category Matching: Categorize goods (e.g., perishable, non-perishable) and match within the same category.
Vehicle Capacity: Ensure the combined volume and weight of pooled orders do not exceed the vehicle's capacity.
Capacity Check: Calculate the total volume and weight of matched orders and compare with available vehicle capacity.
3,Display of Potential Cost Savings and Route Details
Cost Breakdown: Display a detailed cost breakdown showing potential savings from pooling orders.
Original Cost: Show the original cost if the order were transported individually.
Pooled Cost: Show the reduced cost when the order is pooled.
Savings: Highlight the total savings amount and percentage.
4,Confirmation of Pooled Transport Details
Detailed Confirmation: Send a detailed confirmation to both the farmer/broker and the rider.
Order Summary: Include an order summary with pickup and delivery details, type of goods, quantity, and handling requirements.
Route Details: Provide the final optimized route with all stops and estimated times.
Cost Breakdown: Include a final cost breakdown showing the pooled cost and savings.
Notifications: Send confirmation notifications via email and SMS to both parties.
Email Content: Provide a comprehensive summary in the email.
SMS Content: Send a concise summary with a link to view full details online.
-
Incentive System User Story: As a farmer, I want to receive vouchers for accepting pooled transport offers, so that I am encouraged to use this cost-saving option. Acceptance Criteria:
Provide a clear explanation of the voucher system when a pooling option is presented. Show present incentives on this orders like 5% discount for next order. Issue vouchers automatically upon acceptance of a pooling offer. Send confirmation of issued vouchers via email and SMS.
-
Payment Options User Story: As a farmer/broker, I want to choose between online or cash payment options, so that I have flexibility in how I pay for transport services. Acceptance Criteria:
Provide an option to select the payment method during the order request process. Offer secure online payment processing. Provide confirmation of cash payment instructions. Payment could be held in SHYFTX's account until delivery confirmation, ensuring reliability and trust.
-
Order Management System User Story: As a farmer/broker, I want to track the progress of ongoing orders and access archived orders, so that I can manage my shipments effectively. Acceptance Criteria:
Provide a dashboard to track ongoing orders with status updates (e.g., accepted, preparing for pickup, in transit, delivered). Allow access to archived orders for reference and record-keeping. Send notifications via email and SMS for order acceptance, rejection, preparation for pickup, and delivery confirmation.
Notifications for Order Status User Story: As a farmer/broker, I want to receive notifications by email and SMS when my order is accepted or rejected, is being prepared for pickup, and when it is delivered, so that I stay informed about the status of my shipments. Acceptance Criteria:
Send confirmation notifications via email and SMS upon order acceptance and rejection. Notify users when it is time to prepare for pickup. Confirm delivery completion through email and SMS notifications.
-
Contract Agreement User Story: As a farmer/broker, I want to sign a standard contract agreement with truck owners, so that I can ensure clarity and compliance with legal requirements. Acceptance Criteria:
Provide a standard contract template during the registration process. Ensure both parties sign the contract before commencing services. Store the signed contract in the user’s profile and send a copy via email to both parties.
For Riders (Truck Owners)
Registration and KYC
User Story: As a rider, I want to complete a registration process that includes KYC and vehicle information, so that I can start receiving transport orders.
Acceptance Criteria:
Collect and verify personal identification (e.g., government-issued ID).
Collect and verify vehicle information (e.g., vehicle type, registration number, capacity, insurance details).
Allow riders to set their price per kilometer during the registration process.
Ensure the profile is saved and can be updated as needed.
-
Order Notifications User Story: As a rider, I want to receive notifications about new orders via the app and SMS, so that I can quickly decide whether to accept or cancel them. Acceptance Criteria:
Send real-time notifications for new orders through the app and SMS. Provide details about the order, including pickup location, destination, and price.
Order Acceptance and Management User Story: As a rider, I want to access load details and status updates for my orders, so that I can manage my transport efficiently. Acceptance Criteria:
Allow riders to accept or cancel orders through the app. Provide access to load details, pickup date, and status updates for each order. Include navigation links to optimized routes for single or batched orders.
Order Management System User Story: As a rider, I want to track the progress of ongoing orders and access archived orders, so that I can manage my deliveries effectively. Acceptance Criteria:
Provide a dashboard to track ongoing orders with status updates (e.g., accepted, preparing for pickup, in transit, delivered). Allow riders to access archived orders for reference and record-keeping. Send notifications via email and SMS for order acceptance, rejection, preparation for pickup, and delivery confirmation.
Notifications for Order Status User Story: As a rider, I want to receive notifications by email and SMS when I accept or reject an order, prepare for pickup, and deliver the order, so that I stay informed about my tasks. Acceptance Criteria:
Send confirmation notifications via email and SMS upon order acceptance and rejection. Notify riders when it is time to prepare for pickup. Confirm delivery completion through email and SMS notifications.
-
Contract Agreement User Story: As a rider, I want to sign a standard contract agreement with farmers/brokers, so that I can ensure clarity and compliance with legal requirements. Acceptance Criteria:
Same for farmers.