gray-mueller / gray-mueller/food-delivery-platform-for-restaurants-using-python

Zone not found error while placing order in Enatega Multivendor App

Open
#1,982 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Issue: "Zone Not Found" Error while placing order from Enatega Multivendor App.
Description:
When I attempt to place orders for delivery from Enatega Multivendor App, I encounter an error message stating, "Zone Not Found." This error occurs specifically while placing order, preventing me from proceeding with order. The error message does not provide sufficient information to help me to understand the cause of issue.

Impact:
Order disruption: The "Zone Not Found" error disrupts the order placement process, preventing customers from completing their food orders. This results in frustration and inconvenience for customers, potentially leading to abandoned orders and a loss of revenue for the restaurant.

Steps to Reproduce:
Visit the Enatega Multivendor mobile application.
Browse the menu and select the desired items for delivery.
Proceed to the checkout page and enter the necessary customer information.
When I click on "Place Order" button the error found.
Encounter the error message indicating "Zone Not Found," preventing from placing order and further progress.
Expected Resolution:
Identify and resolve the underlying cause of the "Zone Not Found" error in the restaurant's ordering system. The resolution should allow customers to place order smoothly without encountering any issues, ensuring a seamless and satisfactory order placement experience.

Activity

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the failure in the Enatega Multivendor mobile app, following the menu, checkout, and Place Order flow described in the issue. Trace where the “Zone Not Found” message appears and determine what zone data or condition prevents order placement. Done means delivery orders can proceed without this error and the failure provides useful diagnostic information if it remains.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.