Why your TheChefz promotion is not showing to customers

Restaurant operators will not find a discount anywhere inside the one integration TheChefz has documented publicly. Foodics, which runs a certified connection to the platform, publishes what that connection carries: menu items, branches, working hours, preparation times, a tax model and a single delivery charge whose name has to match character for character. There is no offer, no coupon and no campaign object in it. A promotion on TheChefz therefore cannot arrive from your point of sale, and nobody publishes where it does come from.

That absence is unusually clean evidence. The published data model for this platform has a place for a charge and no place for a discount, which tells an operator where to stop looking and who to ask instead.

What does TheChefz publish about restaurant promotions?

Nothing, in either of the two places a restaurant would look. TheChefz runs two merchant hosts, portal.thechefz.co and restaurant-hub.thechefz.co, and both are server rendered applications behind a login and a challenge, so neither exposes any interface text to read. There is no partner help centre, no developer portal and no published partner terms in which a campaign could be defined.

The single mention of promotions anywhere in the platform’s own material is a content feature rather than a discount engine. Its merchant analytics app names a stories tool for showcasing a restaurant’s menu, promotions and brand personality, which we cover in why a restaurant is not showing in TheChefz search. That is a publishing surface a restaurant controls. It is not a mechanism for putting a price down.

The silence has a cause worth naming rather than resenting. Platforms operating in the European Union publish partner terms and ranking parameters because Regulation 2019/1150, the Platform to Business rules, obliges them to, which is why an operator on Wolt, Glovo, Bolt Food, Just Eat or Foody can quote a clause when a campaign misbehaves. We have found no equivalent Saudi requirement on an intermediation platform, and TheChefz, Jahez, HungerStation and ToYou publish nothing about how an offer is funded, approved or scheduled. Asking to see the rules is asking for a document that, as far as we can establish, nobody was required to write.

Why can a Chefz discount not come from your point of sale?

Because the documented integration has no field for one. Foodics, describing the connection it operates with TheChefz, sets out what crosses it, and every object named is structural: menu items with their prices, branches, working hours, preparation times and charges. The charge is singular and named, and the guidance is that a charge called “The chefz delivery charge” must be created and its name copied exactly, or the integration misbehaves. A data model that is that strict about one charge name and silent about discounts is not a model with a discount in it.

The tax rules point the same way. Foodics documents that the integration “works with Tax-inclusive pricing only” and that “The Chefz will set a default 15% tax on all menu items and charges”. Read the last four words. Items and charges are the two things the platform applies its own tax logic to, and offers are not mentioned, because as far as this connection is concerned they do not exist.

For a chain the consequence is a change of address for the whole conversation. A promotion that is missing on TheChefz is not a sync failure, not a mapping error and not something an integration engineer can investigate. It lives on the platform side, in an account whose tooling nobody outside TheChefz has described, which means the only people who can confirm what is configured are the people at TheChefz.

Who at your company can actually change anything on TheChefz?

Fewer people than any marketing team expects, and the published requirements are specific. Foodics states that activation requires logging in “using the owner email” and warns that “If you logged in with a non-owner user, you will not be able to activate the integration”. The same guidance sends the partner outward for the rest of it, telling them to “inform The Chefz team to configure the integration at their side”, after which “The Chefz will activate your account at their side”, and to contact TheChefz to sync menus and branch settings for the first time.

Three parties therefore appear in one short procedure: an owner account at the point of sale vendor, a team at the integrator and a team at TheChefz. None of those three is the person running a campaign. So on this platform the distance between the person who decided the offer and the systems that would carry it is at its widest, and every step in between is a message to somebody rather than a control on a screen.

That is the practical explanation for the commonest failure here, which is not a broken campaign but an unactioned one. Where a promotion is a request rather than a configuration, it can be actioned late, actioned for some branches, or actioned with different dates, and none of those produces an error anywhere, because no system was asked to do anything.

How long does a change to a Chefz connection take?

A week, for the part that is documented. Deliverect’s activation table gives The Chefz as “Within one week after being requested”, the slowest band in its Middle East list alongside ToYou, against “Within 48 hours” for Keeta and Ninja. That figure describes activating an integration channel and nothing else. It is not a campaign turnaround, and it should never be quoted to an account manager as one.

The point of citing it is the tempo it implies. On a platform where connecting a channel is measured in a week and the first menu sync has to be requested by a human, an expectation that an offer can be launched on Thursday for Friday is out of step with everything else that is documented about how this company works. Chains that plan Chefz campaigns on the same lead times they use for Talabat or Deliveroo will keep missing their own start dates.

No campaign clock is published at all. There is no stated approval time for an offer, no stated propagation time and no status an operator can read, so a promotion that has not appeared cannot be classified as late, because nothing defines what late would be.

Where does a Chefz promotion actually become checkable?

On the consumer storefront, one city at a time and mostly in Arabic. TheChefz publishes restaurant pages addressed by city and by a numeric restaurant identifier, under Arabic language paths, which means a brand with branches across the Central, Eastern, Western and Southern regions is looking at a set of separate pages rather than one national listing. A campaign confirmed in Riyadh is not evidence about Jeddah.

That structure decides what a useful check looks like. It has to be per branch, it has to record the city page it was taken from, and it has to be repeated, because a campaign arranged by message rather than configured in a tool can start late and stop late without anybody being told. A single screenshot on the launch date proves nothing about the days that follow, which are where the money is.

How should a Saudi chain evidence a Chefz campaign?

By building the record the platform does not provide. TheChefz publishes no campaign object, no funding split, no approval step and no offer history, and the integration that carries everything else has no discount in it. Between those two facts there is no artefact anywhere, inside the brand or inside its vendors, that shows what a Chefz customer was offered on a given day.

Because a Chefz promotion exists only as an arrangement between people until it appears on a storefront, the dated record of what each branch page actually displayed is the whole audit trail a brand can hold, and it is what Kitchain (kitchain.co) captures on TheChefz listings day by day. The neighbouring questions are covered on why a Chefz store shows as closed and TheChefz menu price mismatch, and the platform itself is on the Kitchain TheChefz page.