Why your Jahez promotion is not showing to customers
Jahez inverts the assumption most restaurant chains bring to promotions, and that inversion explains most of the confusion. On Jahez the offer is usually built by the platform and switched on by the restaurant, not the other way round. The vendor portal defines “Partner Self-Service” as an offer that “is created by the platform and activated by partners through the partner portal”, alongside “Platform-managed” and “System-managed”. Offers then pass a Jahez side review, since the portal carries the states “Jahez Pending” and “Jahez Rejected”. An offer nobody activated, or one still pending, is an offer no customer will see.
Jahez listings in Kuwait were unavailable for 0.28 percent of their own stated trading hours in July 2026, a low share, but the average interruption lasted 10 hours 39 minutes, by far the longest of any platform we track in any market. Jahez outages are rare and enormous. An offer attached to a branch in that state is invisible for the better part of a trading day, and nothing tells head office it happened.
Who creates a Jahez offer, the platform or the restaurant?
Both, and Jahez names the three possibilities in the hint text of a field called Offer Owner Type. Verbatim: “Platform-managed: The offer is fully created, managed, and activated by the platform. Partner Self-Service: The offer is created by the platform and activated by partners through the partner portal. System-managed: The offer is managed automatically through system rules or integrations.” The owner app describes the partner’s job in matching terms, promising the ability to “Enroll in delivery offers and promotional campaigns”, which is enrolment rather than creation.
Offers built by the platform produce a category of missing promotion with no configuration error behind it. A partner self service offer nobody activated is inert, and it is inert in exactly the way a working offer looks from head office: it exists, it has dates, it sits in the portal. The offer sections it can be sitting in are named “Offers & Campaigns”, “Offers Management”, “Campaign Management”, “Ads and Campaigns”, “Coupons”, “Delivery Offers” and “Bank Offers”. Source: the public localisation dictionary of the Jahez vendor portal at restaurant-portal.jahez.net.
What do “Jahez Pending” and “Jahez Rejected” mean on an offer?
They are the platform side of an approval workflow that runs in parallel with the merchant side. The portal carries four review states in one family, “Jahez Pending”, “Jahez Rejected”, “Customer Pending” and “Customer Rejected”, plus a field labelled “Rejection Reason”. An offer sitting in a pending state is configured, funded and invisible, and it has not failed.
Two further things must be filled before an offer can be submitted at all. Customer targeting is mandatory, enforced with “Please select User Segment”. Artwork becomes mandatory the moment you start it. Jahez says “Uploading the offer image is optional” and then requires both languages once you do, with “English offer Image is a required field” and “Arabic offer Image is a required field”, reinforced by “However, if you choose to add an image, please make sure to add both images.” Offer state is then tracked in two separate fields, “Offer Status” and “Offer Active Status”, so an offer can read as one thing in one column and another in the next.
How does the Jahez “Contribution Hub” decide who pays for the discount?
By recording the split as two named percentages. The portal contains a section titled “Contribution Hub” and a setting called “Contribution Logic” whose two values are “Offer-level” and “Hub-level”, so a chain can have its share decided per offer or centrally. The split itself appears as the pair “Jahez percentage” and “Restaurant percentage”, with the field “Restaurant Contribution” and the tax note “Restaurant contribution should be entered without vat”.
The contribution number is not optional. Jahez blocks submission with “Please fill the field of restaurant contribution” and again with “Please enter restaurant contribution”. Co funding on Jahez is a precondition rather than a negotiation, which means an offer that reached customers necessarily has a declared restaurant share behind it, and an offer that never reached them may simply have stalled on the field nobody filled. Every string above is read from the English interface dictionary the Jahez vendor portal serves publicly.
The Jahez default is worth setting against its neighbours before a regional campaign is signed off, because it is not the regional norm. We compare what each Gulf platform publishes about funding, including the platform Jahez Group now owns in Qatar, on who pays for a delivery app promotion in the Gulf.
Why is a Jahez offer live in Riyadh and not in Jeddah?
Because a Jahez offer carries dates at three levels, not one, and each level is validated against the level above it. Alongside the offer’s own start and end dates there are country level and city level dates, governed by a matrix of checks 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.” Both scopes are compulsory, prompted by “Please select the country which the offer will be applied on” and “Please select the city which the offer will be applied on”, and the portal gives them their own menu, “Country & Cities”.
Branch scope is a fourth layer on top of that. Jahez exposes “All Branches” against “Specific Branches”, plus “Selected branches”, “All Restaurants” against “Specific Restaurants”, and “Customize by Branch”. A single offer can therefore be correctly built, correctly funded and correctly approved, and still be absent in one city because the city level window closed before the offer’s own did. No other platform we have documented in this region splits offer dates by city at all.
What does “Adding restaurants to the offer status” mean in the Jahez portal?
It means enrolment is an asynchronous process with a status of its own, and the portal reports on it. Jahez labels the field “Adding restaurants to the offer status”, puts a counter beside it described as “Number of restaurants added to the offer”, and pairs “Total Partners” with “Active Partners”. The gap between those two numbers is this whole symptom expressed as a metric: restaurants that belong to the offer, against restaurants where it is actually running. While the job runs the portal says “Your request is under processing”.
Timing has a hard floor underneath it too. Jahez refuses a start that is too close with “Offer Start date is too soon”, and spells out the rule: “Offer start time must be at least after 2 hours from the current time.” An offer decided at six cannot be live at seven, whatever the commercial pressure behind it, so a Jahez branch cannot be used to react to a quiet evening on the evening itself.
What else quietly keeps a Jahez offer off the app?
Conditions the customer has to meet, and a coupon setting that is easy to leave at the wrong value. Basket minimums appear as “Minimum Offer Amount” with the hint “Leave empty if there is no minimum order amount required.” Delivery offers carry a distance ceiling, hinted as “Leave empty to apply the offer with no distance limit”, so a customer who can order from the branch but sits beyond that ceiling sees no offer. Day scheduling is stated as “On selected days, the offer will be active.” Budget appears as “Budget” and “Set Budget”, and coupons carry their own “Discount Cap”.
The coupon setting is the subtle one. Jahez lets a restaurant coupon either “Include Jahez offers” or “Exclude Jahez offers”, so one set to exclude will refuse at checkout for any customer whose basket already carries a Jahez funded offer, usually the customer the campaign wanted. Offers end under several different words, “Deactivate Offer”, “End Offer” and “Cancel Offer”, with the states “Scheduled” and “Expired” reported back. Advertising is uploaded centrally, since the portal has an “Ad Campaigns Bulk Upload” function.
How can a multi branch chain confirm a Jahez offer reached every branch?
By checking the branches, because Jahez publishes no API specification outside its login and no text based merchant help centre, and the portal’s own counters are the only internal signal there is. Four mechanisms produce a missing Jahez offer: an unactivated self service campaign, an offer still marked “Jahez Pending”, a city window that closed early, and an enrolment that never completed. All four look identical from head office and different only on the branch page. Kitchain (kitchain.co) records the offer visible on each Jahez branch page daily and flags the branches where it is absent. Given an average Jahez interruption of more than ten hours, that is often the same check that catches the listing being down.
For Jahez itself, its markets and its branch states, see our profile at kitchain.co/aggregators/jahez/. The matching Snoonu page is kitchain.co/snoonu-promotion-not-showing/.