Some of your branches are offline on The Chefz and the rest are fine

Restaurant chains on The Chefz are managing an estate that the platform never assembled for them. By the account of the integrator Foodics, branch working hours have to be configured inside the Chefz account rather than in the restaurant’s own systems, and the first synchronisation of menu and branch settings is arranged by contacting The Chefz directly. Availability itself sits on a phone in each branch. There is no published partner portal documentation, no developer documentation and nothing that would let a head office read every branch at once.

Where do The Chefz branch working hours actually live?

Inside The Chefz, not inside the restaurant’s point of sale. Foodics states it in one line in its integration article: “Branch working hours have to be configured inside your Chefz account.” Source: help.foodics.com.

That single sentence decides where a whole class of problems can be fixed. A brand that manages trading hours centrally in its till system, and pushes them to every other channel, cannot push them here. The hours that decide whether a Chefz branch appears at eleven in the morning are held on the platform side and edited there, branch by branch.

For an estate the consequence is predictable. Whichever branches were set up carefully at onboarding keep correct hours. Whichever were set up in a hurry, or set up before a trading change, keep the hours they were given, and nobody in the restaurant’s own tooling will ever see the discrepancy because the record does not exist there.

The failure this produces is the quietest kind. The branch is not closed and nothing is broken. It is outside hours it never agreed to, every day, at the same time.

Why does adding a branch on The Chefz require a conversation?

Because the platform performs the first synchronisation itself. Foodics instructs the partner: “After the successful authorization flow, please inform The Chefz team to configure the integration at their side. The Chefz will activate your account at their side and will sync the data.” It repeats the point for branches specifically: “You should Contact The Chefz to Sync your Menu and Branches settings for the first time”, adding that “any Menu updates after the initial sync will be automatically synced.”

Read the split carefully, because it is the source of most estate level confusion. Menu updates flow automatically once a connection exists. Branch settings do not flow at all until somebody at the platform performs the first sync for that branch.

So a group that opens a new location and pushes its menu will see the menu succeed and the branch remain absent, which reads internally as an integration failure rather than as a missing request. Deliverect, describing its own connection to the same platform, gives the activation window for The Chefz as “Within one week after being requested.” Source: help.deliverect.com. That is an integrator’s account of its own activation timeline rather than a statement by The Chefz, and it is the only published number of that kind we found.

Only the owner account can switch The Chefz integration on.

Foodics is explicit about the credential required: “Log in to your Foodics console at console.foodics.com/login using the owner email. If you logged in with a non-owner user, you will not be able to activate the integration.”

For a single restaurant that is a minor inconvenience. For a group it is a bottleneck with a name. Every activation, every reconnection and every repair that touches the integration waits for one specific login, and if that login belongs to someone who is travelling, or to a former director, the branches that need it stay as they are.

It also produces a very particular kind of split estate. Branches connected during a period when the owner was available are integrated. Branches opened during a period when they were not are running on whatever manual arrangement was made instead, which is usually the merchant application alone. Two branches of one brand can therefore be operating on two entirely different arrangements without anybody having decided that.

Nothing published names a central view that would show which is which. We found no partner portal documentation and no status interface, and the merchant surfaces themselves sit behind sign in pages at portal.thechefz.co and restaurant-hub.thechefz.co.

What happens when one branch leaves a preparation time blank?

The platform substitutes its own value, and the substitution is per item rather than per brand. Foodics states it directly: “Make sure to fill all menu items preparation times inside Foodics, if left blank The Chefz will default to 30 minutes.”

That is not an availability control, and it is worth including here because it is the same shape of problem. A field left empty at one branch does not fail. It silently becomes something else, and the branch then quotes a preparation time nobody chose while its neighbours quote the real one.

The integration carries a second requirement of the same kind, this time with no fallback at all. Foodics tells the partner to create a charge and copy the name exactly, warning that the name “must be exactly the same otherwise the integration will not work”. A single character difference at one branch breaks that branch’s connection and leaves every other branch working, which is exactly the pattern this page is about, produced by a naming convention.

Configuration faults of this shape share one property that makes them expensive. They are invisible until somebody compares two branches side by side, and nothing in the tooling invites that comparison.

Why does the distance between regions decide how long a Chefz branch stays dark?

Because availability is exercised on a device in the branch and there is no remote route to it. The platform’s own description of its merchant application says so in its framing: the app “puts control in the hands of restaurant staff”, covering “managing incoming orders, reviewing order history, or temporarily pausing service”, and letting partners “switch to Busy Mode when needed during rush hours or special circumstances”. Source: play.google.com.

What the listing does not say is what Busy Mode does, and no published Chefz material defines it. On Deliveroo busy mode keeps a site selling with longer preparation times. On Glovo the equivalent closes the store for half an hour. On HungerStation the phrase means temporary closure outright. An operator here cannot know from the published material whether a branch in Busy Mode is still taking orders, which means a brand cannot even write a correct instruction for its own staff.

Now add geography. The Chefz partner registration form asks a new partner to choose among Central, Eastern Province, Western Province and Southern Province before choosing a city, with the Central list including Al Kharj, Alras, Buraidah, Dawadmi, Hail, Riyadh, Tabuk, Unaizah and Wadi Al Dawasir, and the Western list including Al Madinah, Jeddah, Makkah, Taif and Yanbu. Source: thechefz.co partner registration.

A brand spread across those regions has the availability of each branch sitting on a handset in that city, and the further a branch is from whoever notices, the longer any paused state survives.

What can a Saudi chain compare across The Chefz branches?

Only the storefronts, and the comparison has to be deliberate because nothing prompts it. There is no status endpoint to poll, no published closure vocabulary, no reason codes and no central branch list that a brand can export. What exists is the consumer listing for each branch, which is where the answer to every question above eventually shows up.

Two habits close most of the gap. First, agree who at each branch is allowed to pause service or use Busy Mode, and treat that state as something handed over at the end of a shift in the same way a till float is handed over, because nothing in the published material promises either state ends on its own. Second, check the branches nobody visits most often rather than least often, since distance from head office is the best available predictor of how long a paused branch stays paused.

Turning that into evidence means recording, per branch, whether a customer could actually order at a given hour, which is what Kitchain (kitchain.co) collects on The Chefz listings because there is no portal or API to read instead. Kitchain publishes no downtime figures for The Chefz, so no number on this page describes it.

Related

• Why your Chefz store shows as closed when the restaurant is open
• The Chefz on the Kitchain platform index
• Delivery monitoring for restaurant groups and franchises