Why your Jahez menu prices differ from the ones you set

Restaurant chains on Jahez have less direct authorship over a displayed price than on most platforms, and two mechanisms explain almost every mismatch. Discounts are usually built by Jahez and merely joined by the restaurant, so a shelf price can move without any price field being edited. Menu content arrives from the till on a fixed overnight schedule rather than on demand, so a price the operator did change is not the price customers are being shown until the following morning. A Jahez price is rarely something an operator set and watched take effect.

Who actually creates a discount on Jahez?

Usually the platform. Jahez records the answer in a field called Offer Owner Type, whose three values are Platform-managed, Partner Self-Service and System-managed, and in two of the three the restaurant does not author the offer at all. The full wording of each mode is on why your Jahez promotion is not showing to customers. The merchant app describes the same relationship from the operator’s side, offering the ability to “Enroll in delivery offers and promotional campaigns” (play.google.com).

Enrolling is not creating, and the difference decides where a price investigation starts. When a Jahez price looks wrong to head office, the first question is not what went wrong with an upload. The first question is which offer the branch is currently enrolled in, and whether anybody at brand level chose it. A branch manager who joined a campaign from the owner app has changed the shelf price of every item in it without touching a price field, and the portal will show the item priced exactly as head office set it.

Why does a Jahez menu price change wait until the small hours?

Because the menu sync runs on a schedule rather than on a click. Foodics, a Saudi point of sale vendor that operates a certified Jahez integration, documents the behaviour for its customers as “Jahez has an enabled auto sync everyday at 3 AM, If a manual sync is required please contact your Jahez Account Manager” (help.foodics.com). That is a third party describing the integration it maintains, so it should be read as such, but it is the clearest public statement of the timing.

The operational consequence is a full trading day of exposure. A price corrected in the POS at nine in the morning does not reach Jahez until the following night, and the shortcut past that wait is a request to an account manager rather than a button. For a chain running a promotion that starts at noon, or reacting to a supplier price change, the Jahez listing is structurally the last of its channels to catch up, and no state in the portal shows that a change is pending.

What does the mandatory restaurant contribution field mean for your Jahez margin?

Jahez builds funding into the offer form rather than into a separate commercial conversation. The portal carries a validation message reading “Please fill the field of restaurant contribution”, meaning the restaurant’s share of a discount is a required entry before an offer can be saved (Jahez restaurant portal interface dictionary). Offers also carry “Budget” and “Set Budget” fields, and coupons carry a separate “Discount Cap”.

This changes what a price mismatch means on Jahez. On a platform such as noon Food, a lower than expected price may be entirely platform funded and cost the restaurant nothing. On Jahez the contribution is captured per offer, so an unexpected discount on a branch is an unexpected cost with a number already attached to it. Jahez also lets a coupon be set to “Include Jahez offers” or “Exclude Jahez offers”, so whether a restaurant’s own code stacks on top of a platform offer is a setting, and the same basket can resolve differently depending on it.

One more scoping rule sits underneath all of that. Jahez offers carry a budget, and coupons carry their own “Discount Cap”, so an offer that is correctly scoped to a branch can still stop applying partway through a day once a ceiling is reached. From the storefront that is indistinguishable from an offer that never reached the branch at all, because both produce the full price with no marker on the item.

Why does a Jahez offer reach some branches and not others?

Jahez scopes an offer on three axes at once, and each one can leave a branch out. Branch scope is explicit, with “All Branches” set against “Specific Branches”, “Selected branches” and “Customize by Branch”. On top of that sit geography and separate dates, enforced by validation messages such as “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”, with required fields asking the operator to select the country and the city the offer applies to (Jahez restaurant portal interface dictionary).

There is also a documented in-between state that explains the most confusing cases. The portal tracks a status labelled “Adding restaurants to the offer status”, alongside counters for “Total Partners” and “Active Partners”. Enrolment into an offer is therefore an asynchronous process with its own progress. A gap between the total and the active count is precisely the situation where some branches show the promotional price and others show the full one, with nothing wrong at either end.

What silently fails to reach Jahez from your POS?

Two categories of content, according to the integrators that carry it. Foodics documents that the menu group feeding Jahez must be named exactly, warning that “If the name is incorrect, Jahez will not be able to read your menu”, and that scope is limited, since “Only menu group products will be synced with Jahez, Combos and Sub Groups will not be synced” (help.foodics.com). Combo pricing, which is where most bundled value sits, does not travel.

Deliverect, another certified integrator, documents a language limit in its own Jahez article, stating that “Jahez only supports English and Arabic. Any other languages won’t be sent through” (help.deliverect.com). Both are third party statements about an integration rather than Jahez’s own specification. Jahez’s own specification is public at integration-portal.jahez.net and says nothing on either point: it defines image_path only as “Product image URL”, with no format, no file size and no dimensions, and it names no language restriction anywhere, so an operator has no first party rule to check these against. That opacity is itself part of the problem, because a menu item that never arrived produces no error the restaurant can read.

How long can a wrong Jahez price stay live before anyone notices?

Kitchain (kitchain.co) measured Jahez in July 2026 at 0.28 percent of trading time offline, with an average incident of 10 hours 39 minutes. That combination is unusual and worth reading carefully. Jahez branches go offline rarely, and when they do the interruption lasts far longer than on any other platform measured, which suggests problems there are not resolved by the next passing check but by someone eventually noticing.

A wrong price has no equivalent of coming back online at all. A Jahez menu refreshes overnight, a manual sync requires an account manager, and most offers are created by the platform rather than by the brand. Between them, those three facts stretch the gap between a price being wrong and a price being noticed into reporting cycles rather than hours. Reading the live Jahez listing branch by branch each day and comparing it against the brand’s own price book, which is what Kitchain (kitchain.co) does, closes that gap without waiting for the next sync. Ownership, markets and the wider set of Jahez signals are covered on the Kitchain Jahez page.