Logic Flaws in Enatega Multivendor Restaurant App

Open

#1,356 opened on Apr 4, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 45/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: javascript, react-native
Domain: mobile

Research direction

Reproduce the order flow across the restaurant and rider apps using the listed steps, then trace the status transition triggered when the restaurant marks an order as delivered. Compare the displayed status with the expected handoff-to-rider behavior, including an order with an assigned rider already en route. Done means the restaurant action no longer marks the rider's delivery as completed prematurely on either iOS or Android.

Written by the indexing model from the issue text.

Description

Describe the bug
incorrect Delivery Status Update: When a restaurant marks an order as delivered, it incorrectly signifies that the food has been delivered to the customer instead of the rider. Similarly when the rider for instance accepts the order and the rider is on his way and if the restaurant mark the order as delivered the riders which is on its way and the delivery is not yet done will be considered as done in the rider app. This results in confusion and inaccurate tracking of the delivery process.
To Reproduce
Steps to reproduce the behavior:

Place an order from customer app.
Mark the order as delivered from restaurant app after accepting it.
Observe the incorrect status update in restaurant app and rider app if the rider has been assigned to that order.
Expected behavior
When the restaurant marks an order as delivered, it should indicate that the food has been handed over to the rider for delivery to the customer.

Screenshots
https://github.com/ninjas-code-official/food-delivery-multivendor/assets/153413752/77013d08-2860-4968-9964-6fbf313a97ab

**Smartphone **

Device: IOS & Android.

Dominant language: JavaScript
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.