Some of your branches are offline on Jahez and the rest are fine
Restaurant chains on Jahez are managing branches that carry two independent switches rather than one. The branch list in the Jahez restaurant portal shows an open and close column and a separate visibility column, and a branch can be open on the first while hidden on the second. Each branch also holds its own integration identifier, its own credentials and its own city, and each of those three can take a single location off the app while every other branch of the same brand keeps selling normally.
Why does the Jahez branches table carry two status columns and a city column?
Because those are three different things that can each hide a branch. The branch page in the Jahez restaurant portal lists columns for the branch name, the status, the integration identifier, the city, an open and close control, a visibility status and today’s working hours. The interface dictionary that ships openly with the portal names the values behind them. On the first axis, “Open”, “Busy” and “Closed”, with actions labelled “Set As Busy”, “Re-Set As Busy” and a field for “Set Duration”. On the second, “Visible”, “Hidden”, “Partially Visible” and a preset reading “Invisible until Tomorrow”. Source: restaurant-portal.jahez.net interface dictionary.
Being busy on Jahez does not remove the branch. The dictionary carries a note reading “* You Restaurant Will Still Be Visible To Customers But As Busy For A While”, so a busy branch is a labelled branch rather than an absent one. A branch on the second axis is a different matter, because that one disappears.
The city column is doing more work than it looks. Jahez ties offers and campaigns to countries and cities as well as to branches, so the column is not decoration, it is the field that decides which platform level rules a branch is subject to. Two branches of one brand in two cities are two different cases before anybody looks at their kitchens.
Which of your Jahez branches is on the new portal and which is still on the old one?
Both portals exist at once and Jahez names the older one inside the newer one. The current portal answers at restaurant-portal.jahez.net, and its own dictionary carries an entry labelled “OLD Portal” pointing at the previous system at portal.jahez.net, whose sign in page is headed “Restaurant Login”. Integrator instructions still route users through a button labelled “New Portal” inside the old one.
For a group that means the estate is not necessarily administered from one screen. A manager working in the older interface and a manager working in the newer one are not looking at the same view of the same branches, and only one of the two shows the visibility column described above. A brand debugging a dark branch over the phone should establish which portal each person is in before comparing what they can see.
Access itself is issued rather than claimed. Jahez states in its own security text that “Jahez representatives will never ask you to open external links outside of the official restaurant portal or app to update your information”, which is the platform naming its own surface. Anything that looks like a partner portal on another domain is not one.
Why can a Jahez branch go dark because somebody regenerated its integration keys?
Because credentials are held per branch and replacing them invalidates the previous set. The portal carries fields named “Integration Branch ID” and “Partner Credentials”, and it warns before a key is replaced with this message: “Generating a new key will deactivate the previous one and may affect active integrations.”
That is a per branch action with a per branch consequence. A technician working through an estate to refresh credentials, interrupted halfway, leaves half the branches connected and half not. Nothing about the second half looks wrong in the portal, and the failure appears later as orders that stop arriving at one set of locations.
The menu side has its own timing, and by the account of the integrator Foodics, “Jahez has an enabled auto sync everyday at 3 AM, If a manual sync is required please contact your Jahez Account Manager.” Source: help.foodics.com. A branch whose menu failed to sync overnight cannot simply be re pushed by its own manager, which means a fix applied to nine branches during the day may only reach the tenth the following morning.
Deliverect, another integrator, reports a harder boundary on availability itself, stating that “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.” Source: help.deliverect.com. A chain that automated its openings through middleware on other platforms cannot do the same here.
Jahez staff can work inside your portal as your account, one branch at a time.
The portal says so out loud. Its dictionary carries a banner string reading “You are currently viewing restaurant ({{ restaurantId }}) as Jahez Employee.”, and the branch page itself sits under a path named for a remote session.
For a brand investigating why one branch differs from its neighbours, that string closes off a whole line of blame. A change made in the portal was not necessarily made by anybody at the restaurant. It also means the recovery route for the visibility axis runs the same way, and by Deliverect’s account the instruction is to “Ask Jahez to set your store’s visibility status back to “Visible.”” for a store that does not appear on the app even when everything is set up correctly.
Two consequences follow for an estate. First, the branch that is hidden is not fixable by pressing anything in the branch, so it will stay hidden for as long as the request takes, while its neighbours trade. Second, any internal audit of who changed what has to allow for a party outside the company, which is unusual and worth writing into the brand’s own incident notes.
Why does a Jahez offer stop at a city boundary while the branches keep trading?
Because Jahez scopes offers by country and by city as well as by branch, and validates the dates at each level. The portal dictionary carries an explicit branch scope choice between “Specific Branches” and “All Branches”, alongside “Selected branches”, “Select Branches” and “Customize by Branch”. It also carries city and country level validation messages, including “The start date of the city offer cannot exceed the start date of the offer” and “The end date of the country offer cannot exceed the end date of the offer”, plus required field prompts asking the partner to select the country and the city the offer applies to.
There is a further step that most operators never see. The portal tracks the enrolment of restaurants into an offer as its own asynchronous process, with a status labelled “Adding restaurants to the offer status” and counters for “Total Partners” and “Active Partners”. Where those two counters disagree, some branches did not make it into the offer, and nothing in the branch itself reports that.
This is a different symptom from a dark branch and it is worth separating in the same investigation. A branch trading normally with no promotion is losing volume for a configuration reason, and a brand that only tracks availability will read the drop as demand.
What should a Saudi chain check when only part of its Jahez estate is dark?
Work the two axes first, because they are the only ones with a visible field. For each branch take the open and close value and the visibility value at the same moment. Where the first says open and the second says hidden or partially visible, the branch is not a kitchen problem and the route back runs through Jahez rather than through the portal control. Where both look normal, move to the branch’s integration identifier and credentials, then to its city.
The cost of getting that order wrong is unusually high on this platform. In our July 2026 Kuwait panel, Jahez listings lost 0.28 percent of stated trading hours, a low share, with a mean interruption of 10 hours 39 minutes, by far the longest of the platforms we measured in that market. Interruptions here are rare and enormous, which means an estate can look healthy on a monthly percentage while one branch has been dark for the better part of a trading day. Catching that requires a per branch record of when each listing could actually be ordered from, checked against the working hours that branch published, which is what Kitchain (kitchain.co) collects across a Jahez estate.