How to get Jahez to put your restaurant back online
Restaurant operators on Jahez lost a recovery route recently, and knowing that changes where the first hour of an incident goes. Deliverect, a certified integrator, states it without qualification: “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.” So the point of sale layer is out. What remains is the Jahez restaurant portal, the branch application, and a request to Jahez itself for the one axis a restaurant does not hold.
Jahez withdrew the integration route, so the reopen happens in Jahez tools
That single sentence from Deliverect’s Jahez troubleshooting article reorganises every runbook written before it. Source: help.deliverect.com. A brand whose standard procedure was to flip a store through its middleware will find the action either missing or ineffective, and will spend the incident debugging the wrong system.
The tools that remain are Jahez’s own. The restaurant portal at restaurant-portal.jahez.net carries a branches page whose columns include the branch name, the status, the integration identifier, the city, an open and close control and a separate visibility column, with the working hours for the day alongside. Jahez also ships two merchant applications, one for taking orders in the branch and one for owners.
There is a second reason the integration is worth keeping out of the recovery path. The portal warns, at the point where partner credentials are regenerated, that “Generating a new key will deactivate the previous one and may affect active integrations.” A team that reaches for a credentials reset while trying to revive a quiet branch can take the branch further offline than it started.
Which Jahez branch control ends which state?
Jahez keeps two independent axes and the portal labels them separately, which means a branch can be wrong on one and right on the other. The first axis is order acceptance, with the values “Open”, “Busy” and “Closed” and the control labelled “Open / Close”. The second is presence in the customer application, labelled “Visibility”, with the values “Visible”, “Hidden” and “Partially Visible”.
Only the first axis is fully in the restaurant’s hands. The portal carries “Set As Busy” and “Set Duration” for pausing a branch, describes the purpose in a string reading “To Stop Received Orders Of This Branch”, and confirms a change with “The status has been update successful”. For visibility the recovery is a request, and Deliverect states it in those terms: “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.””
The important consequence is diagnostic. A branch showing Open on the first axis and Hidden on the second will accept every reopen action anybody performs and will still not appear to a customer, and the person pressing will report, honestly, that the branch is open. Establishing which column is wrong has to come before any action at all.
Re-Set As Busy exists because a busy period expires on its own
The portal carries a control labelled “Re-Set As Busy”, and a control for setting something again only makes sense where the first setting ended by itself. Alongside it sits “Set Duration”, and a note shown to the operator when the state is chosen, reading “* You Restaurant Will Still Be Visible To Customers But As Busy For A While”.
Two facts sit in that note. A busy branch on Jahez is not removed from the application, it is marked, which is gentler than the equivalent state on several neighbouring platforms. And the state is described as lasting for a while rather than indefinitely, which matches the presence of a duration field.
What Jahez does not publish is the list of durations or the rule by which the branch returns. We looked, and that part is behind the login. So the honest instruction for an operator is to treat the busy state as timed but to verify the return by looking at the storefront rather than by trusting an expiry nobody has published. The visibility axis has one comparable preset, a value named for being invisible until the following day, which does carry its own ending.
What should you send Jahez when a branch will not come back?
The branch identifier as it appears in the portal, the two statuses separately, the time the branch stopped being orderable, and the hours that branch published for the day. Sending the two statuses separately is what makes the request actionable, because Jahez staff can change either and a request that says only that the branch is offline does not tell them which one to touch.
On channels, be precise about what is published and what is not. Foodics publishes integration contacts for Jahez, an address at Integration@jahez.net and a telephone number, +966558545755, in its official Jahez article. Source: help.foodics.com. Those are integration contacts. Jahez publishes no dedicated availability support address, no ticket type and no response time, and the route Deliverect names for opening and closing is simply Jahez directly, which in practice means the account manager the brand already has.
One thing not to ask for and one thing to expect. Do not ask for a compensation rule, because Jahez publishes none. And expect a lag on anything that has to propagate, since Deliverect records that on this platform “changes can take 10-45 minutes to take effect”, which means a branch that is still dark five minutes after a change was confirmed has not necessarily failed to change.
Why does a Jahez menu push fail while the branch is suspended?
Because Jahez blocks the catalogue while the store is not in a trading state, and Deliverect names the condition directly, listing among its Jahez failures the case where a menu publish fails “because the store is suspended or inactive”. An operator trying to fix a quiet branch by republishing the menu will get an error that describes the store state rather than the menu, and the error is telling the truth.
The order of work therefore has to be state first and catalogue second. That is the opposite of the habit on platforms where a menu republish is the standard first move, and it is worth writing into the procedure explicitly, because the temptation to push a menu at a silent branch is strong and here it wastes the hour.
Two further Jahez facts belong in the same note, because they bound how quickly anything propagates. Foodics records that “Jahez has an enabled auto sync everyday at 3 AM, If a manual sync is required please contact your Jahez Account Manager”, so a brand cannot force a synchronisation itself. And the portal contains a string reading “You are currently viewing restaurant ({{ restaurantId }}) as Jahez Employee.”, which confirms that Jahez staff can operate inside a restaurant’s own account, and therefore that a change nobody at the brand made is a real possibility rather than a suspicion.
What should a Gulf chain record before it contacts Jahez?
Both axes, per branch, with timestamps, because a Jahez request without them turns into a conversation about whether anything happened at all. The portal shows the current values and not the history, so a branch that was hidden on Tuesday and visible again on Wednesday leaves nothing to point at.
The reason to be disciplined about this on Jahez specifically is the length of its incidents. In Kuwait, where we measure it, Jahez shows one of the lowest downtime shares in the market at 0.28 percent of trading time, and one of the longest mean incidents at 10 hours 39 minutes. That shape means outages are rare and, when they happen, they run for most of a trading day. A platform with that shape is not improved by pressing the controls faster, it is improved by starting the request earlier, because almost the whole of a ten hour incident is time before anybody opened a ticket rather than time Jahez spent on it. The single change that shortens a Jahez outage most is therefore the hour at which the message is sent, and knowing when to send it is what Kitchain (kitchain.co) supplies by watching each Jahez branch page for the moment it stops being orderable.