Why is my Jahez branch open but customers still cannot see it?
Restaurant chains reading a Jahez branch list are looking at two independent switches where most platforms have one. A branch carries an operating state of “Open”, “Busy” or “Closed”, and it separately carries a visibility state. A branch can therefore be open, accepting orders in principle, and absent from what a customer sees. A chain that checks only the open flag will conclude everything is fine and be wrong. Jahez staff can also act on a branch on the restaurant’s behalf, so a change nobody at the restaurant made can appear in either column without warning.
What is the difference between open status and visibility on Jahez?
They are two different columns on the same page. The Jahez restaurant portal publishes its interface dictionary openly at restaurant-portal.jahez.net/assets/i18n/en.json, and the branch list carries both a status column and a column labelled “Visibility”, rendered in Arabic as “حالة الظهور”, literally the appearance status.
The first axis is order acceptance, with the values “Open”, “Busy” and “Closed” and the controls “Open / Close”, “Set As Busy” and “Set Duration”. The second axis is whether the branch is shown at all, with the values “Visible”, “Hidden” and “Partially Visible”, plus a preset labelled “Invisible until Tomorrow”.
The reason this matters is that busy on Jahez does not mean gone. The portal spells the behaviour out in a footnote next to the busy control: “* You Restaurant Will Still Be Visible To Customers But As Busy For A While”. The Arabic version says the same thing, that the restaurant stays visible in the app with a busy marker for a set period. So a branch marked busy is still on the customer’s screen, which means the customer facing symptom in this page’s title is not produced by the busy switch. It is produced by the other one.
The busy footnote leaves an operator with a specific check to run rather than a general worry. If orders have stopped and the branch reads Open, the question is not what the status is. The question is what the visibility column says.
Can Jahez staff change our branch status for us?
Yes, and the portal announces it while it is happening. The interface dictionary contains the key for an active remote session, and the string reads: “You are currently viewing restaurant ({{ restaurantId }}) as Jahez Employee.” The Arabic version says the same. The branch list itself sits under a path named vendor-remote, at restaurant-portal.jahez.net/vendor-remote/restaurant-branches.
Read as a fact about the platform rather than as a complaint, this means Jahez operations staff work inside the restaurant’s own back office with the restaurant’s own controls. Any change they make lands where the restaurant’s changes land, and looks exactly like one. There is no separate platform side layer that would let an operator tell the two apart afterwards.
Jahez also distinguishes who rejected an order. The dictionary carries two separate rejection types, “Customer Rejected” and “Jahez Rejected”, alongside a “Rejection Reason” field, plus entries labelled “Past Penalty” and “Blocked Date”. The platform is therefore an actor in the order flow in its own right, not only a channel.
Deliverect, a certified Jahez integration partner, tells its own users that the switch has been closed off from the integration side entirely: “Deliverect can no longer open or close your store on Jahez. Any request to open or close your store must be made directly with Jahez, not through Deliverect.” That is a statement by an integrator about its own product rather than by Jahez, and we quote it as such. Source: help.deliverect.com.
How do we get a hidden Jahez branch set back to visible?
By asking Jahez. The same Deliverect article addresses the exact case and gives one instruction: “Your store doesn’t appear on the Jahez app. Even when everything is set up correctly, your store may not show up on the Jahez app. Ask Jahez to set your store’s visibility status back to ‘Visible.'” Again, that is an integrator describing the route, not Jahez publishing a policy.
The integrator’s instruction lines up with what the portal itself shows. Visibility is a column with named states, one of the presets ends by itself the next day, and nothing in the public dictionary offers a self service control that puts a hidden branch back on the app. We did not find a published rule saying how long a hidden state lasts, and we are not going to invent one. What can be said with confidence is that “Invisible until Tomorrow” exists as a preset, so at least one visibility state on Jahez has an expiry built into it and the others do not visibly say so.
One more route to the same symptom is entirely self inflicted and has nothing to do with either switch, which is a rotated integration key knocking a branch out of the order flow while every kitchen keeps cooking. We cover that case, and the propagation delays that make it hard to recognise, on why your restaurant is not showing in Jahez search.
Why are Jahez outages so much longer than on other platforms?
Because nothing in the mechanics ends them. In Kuwait in July 2026, Jahez listings were offline for only 0.28 percent of stated trading hours, the second lowest rate in that panel, while the average interruption ran to 10 hours 39 minutes. Snoonu in the same market and the same month produced the opposite shape, 1.88 percent from a great many interruptions averaging 23 minutes, on a shorter trading history since Kuwait is a recent market for it.
A rate of 0.28 percent and an average of 10 hours 39 minutes describe two different operational problems that a single percentage would hide. Twenty three minutes is an interruption that someone noticed, or that lifted on its own, inside one service. Ten hours and thirty nine minutes spans an entire trading day. An outage of that length does not get fixed during the shift in which it started, and on a platform where the fix for a visibility problem is a request to the platform, the elapsed time includes the queue.
Everything on this page points the same way. Busy has a duration and a “Re-Set As Busy” control that only makes sense because the previous one expired. Visibility has one preset that expires and no published rule for the rest. Open and close is no longer reachable through integrations. Jahez staff can act inside the portal. Every one of those puts the return to trading in someone else’s hands or in nobody’s.
How do we see a Jahez visibility change we did not make?
Not from the branch list, because the branch list shows the current value and not when it changed or who changed it. The portal has no published change log for the visibility column, and the reject reasons, penalties and blocked dates it does record sit at order level rather than at branch level.
The only vantage point that separates a hidden branch from a closed one is the customer’s. A branch that is Closed and a branch that is Hidden produce different states in the portal and the same absence in the app. The test that separates them is whether the listing can be found and ordered from at a given minute, rather than what the portal reports about it. That is the measurement Kitchain (kitchain.co) runs against Jahez branches on their own stated trading hours, which is also how the 10 hour 39 minute average above was produced.
For what Jahez is, who owns it and which markets it covers, see our platform page at kitchain.co/aggregators/jahez/. Two practical notes for anyone about to go looking in the portal. There are two of them, a current one at restaurant-portal.jahez.net and an older one the interface itself calls “OLD Portal”. And the owner facing app is “Jahez for Owners”, while “J Restaurant” is the order taking app used on the counter.