Why Jahez says your restaurant does not deliver to an address you cover

Jahez does model distance in kilometres, and restaurant operators can see the evidence in the portal’s own labels, but none of those labels is a delivery area you control. Jahez configures “Global Delivery Tiers” with a “Tier Name”, a “Start [km]” and an “End [km]”, grouped by city, and it caps offers with a “Maximum Distance (km)” field whose hint reads “Leave empty to apply the offer with no distance limit.” Distance decides what a customer pays and which promotion they see. It is not something a branch declares.

Jahez pairs one of the lowest downtime shares we measure anywhere with by far the longest interruptions in its market. In July 2026 its Kuwait listings were unavailable for 0.28 percent of their stated trading hours, on interruptions averaging 10 hours 39 minutes. Jahez fails rarely and then stays failed for most of a trading day, which sets the cost of noticing late higher on this platform than on any of its neighbours.

What does a Jahez branch actually tell Jahez about geography?

One point and nothing else. The Jahez integration documentation publishes the whole Branch object, and it has four fields: branch_id, a name in Arabic and English, an address described as “Description of the branch location”, and coordination, described as “coordinate of the branch, double value of latitude and longitude”. There is no delivery zone, no radius, no list of districts and no maximum distance in it. Visibility is handled separately by POST /branches/visibility with a single boolean, documented as “if set to true branch will be visible in customer app”.

So the entire integration contract between a restaurant chain and Jahez, on the subject of where its food can go, is a latitude, a longitude and a yes or no. Everything a customer experiences as coverage is computed by Jahez from that pair of numbers. A branch whose coordinate is wrong is not slightly wrong, it is wrong in every downstream calculation at once, and there is no second field anywhere to contradict it.

What are “Global Delivery Tiers” on Jahez?

They are Jahez’s own distance bands, and the portal names every part of them. A tier has a “Tier Name” with a “Start [km]” and an “End [km]”. Tiers are organised by city, with a grouping screen explaining that “Cities that have commen properites are grouped toghter”, the typos being Jahez’s own, and a global set that applies “For Tiers that are not defined in cities”. Adding one is “Add Global Tier”, and success is confirmed with “Global Tier Have Been Added Successfully”.

Read that structure carefully, because it tells you how coverage on Jahez is actually shaped. A customer is not inside or outside a polygon drawn around your branch. They are a certain number of kilometres away, that number lands them in a tier, and the tier is a property of the city rather than of your restaurant. A district can therefore change behaviour for every branch in the city at once, because the tier definition moved, and nothing in your own account will have changed.

Where else does distance decide what a Jahez customer sees?

In promotions and in placement, which is why coverage on Jahez often looks like a marketing problem. A restaurant offer carries a “Maximum Distance (km)” alongside a “Minimum Offer Amount” and a “Contribution” field, and the hint under it reads “Leave empty to apply the offer with no distance limit.” A merchandised “Top List” placement has a “Max Distance Number” with its own validation message, “Please enter the distance”. Both of those are distance gates that sit on top of ordinary availability.

The practical result is a state that no dashboard names. A customer four kilometres away can order from you at full price with no promotion visible and no placement, while a customer one kilometre away sees you promoted and discounted. Neither customer is out of coverage. From the outer ring the brand simply looks more expensive and less prominent than it does from the centre, and the orders drift accordingly. This is not a Jahez fault, it is a Jahez design, and it is only visible if you look at the app from both addresses.

Does the branch or Jahez run the delivery on this order?

Check, because the answer changes who owns the problem. A Jahez branch carries a “Delivery Services” setting, and the portal’s own options include “Own Delivery” and “Use Other Delivery Service”. A branch on Jahez logistics inherits Jahez’s tiers and Jahez’s rider supply. A branch on its own delivery is answering a different question, because the area it can serve is then a fact about the restaurant’s own drivers and not about the platform at all.

Chains that grew by acquisition or opened branches in waves frequently have both configurations live in the same city without anyone realising, and it explains apparent coverage differences between branches that look identical on paper. It is worth reading this setting branch by branch before escalating anything, because a coverage complaint about a branch running its own delivery will be sent straight back to you, and correctly.

What happens on Jahez when a branch is under pressure?

Jahez caps throughput at the branch rather than by narrowing the map, which is the important thing for a coverage question. A branch marked busy stays on the customer’s screen with a busy marker, and Jahez says so next to the control itself. Visibility is a separate switch with more than two positions, running “Visible”, “Partially Visible” and a preset called “Invisible until Tomorrow”, and the two axes are set out on why your Jahez branch is open but customers still cannot see it. A branch also carries a “Max Orders” limit and an auto accept configuration, so pressure is absorbed by refusing volume rather than by shrinking the area.

“Partially Visible” is the state worth knowing about, because it is the only label in this whole subject area that admits, on the platform’s own screen, that a restaurant can be neither fully present nor fully absent. Jahez does not publish what determines it. We looked and did not find a definition, and we are not going to supply one. What it tells an operator is that a binary reading of your own listing, present or missing, is not enough to describe your state on this platform.

What can a Jahez operator actually prove about coverage?

Only what a customer was offered, at an address, on a date. Every distance rule on this page belongs to Jahez rather than to the restaurant, the tiers are defined per city rather than per branch, and Jahez publishes no partner facing statement of how any of them is set. There is nothing in the account to audit, so an internal review of a coverage complaint has no document to review.

The portal is not even a closed record of the restaurant’s own decisions, since Jahez staff work inside the same screens on a restaurant’s behalf. A setting nobody at the brand remembers changing may genuinely not have been changed by anybody at the brand, and the branch list shows the value rather than its history. The reading that settles arguments is therefore the one taken from outside. A Jahez interruption averages more than ten hours, so nearly all of the cost on this platform sits in the interval between something going wrong and someone noticing. Closing that interval from the customer side is what Kitchain (kitchain.co) Coverage and Kitchain Alert are for at kitchain.co. Our fuller profile of the platform is at https://kitchain.co/aggregators/jahez/.