gray-mueller / gray-mueller/food-ordering-app-using-android-studio
Clarify Courier Assignment Logic and Enable Dedicated Couriers in Enatega Mulitvendor web.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Issue: Clarify Courier Assignment Logic and Enable Dedicated Couriers
Description:
There is a lack of clarity regarding the logic for courier assignment when multiple orders are involved, particularly in zones or cities with several couriers. It's essential to define how orders are assigned to couriers, whether based on proximity to restaurants or other factors. Additionally, we need to implement a feature that allows for the allocation of dedicated couriers to specific restaurants.
Impact:
Efficiency: An unclear courier assignment logic may lead to inefficiencies in order fulfillment.
User Expectations: Users and restaurant owners expect transparency in how orders are assigned to couriers.
Steps to Reproduce:
Observe the courier assignment process when multiple orders are involved.
Attempt to determine the factors that influence courier assignment.
Investigate whether there is a feature to allocate dedicated couriers to specific restaurants.
Expected Resolution:
You should clarify the logic for courier assignment when multiple orders are involved, ensuring transparency and efficiency in the process. Additionally, You need to implement a feature that allows administrators to allocate dedicated couriers to specific restaurants, improving the management of orders and deliveries. Addressing these issues will enhance order fulfillment and user satisfaction.
Contributor guide
Research direction
No files, tests, or entry points are identified. Start by tracing the existing courier assignment process for multiple orders and documenting which factors it uses, then define the administrator workflow for assigning dedicated couriers to restaurants; done means both behaviors are clearly specified and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100