Why is my ToYou store showing as closed when the restaurant is open?

Restaurant operators looking for a ToYou switch that closed their store will not find one documented anywhere, and the more likely explanation is a menu that has not cleared review. Deliverect, an integrator carrying ToYou as a channel, states that “ToYou checks each published menu before setting it live on their platform” and that “This process can take up to three hours”. The same vendor lists “Your menu is not yet published” among the reasons a store reads as closed to customers. On ToYou those two facts meet more often than operators expect.

Nothing on this page comes from ToYou. The platform publishes no merchant help centre and no partner documentation, so every quotation below belongs to an integrator describing what it sees from its own side of the connection. Our published July 2026 downtime measurements cover Careem Food, Deliveroo, Talabat, Keeta, noon Food, Snoonu, Jahez and HungerStation, and ToYou is not among them, so no figure here describes ToYou.

What does ToYou publish for restaurants about a closed store?

Nothing readable, and the shape of the silence is worth describing precisely because operators keep looking. The merchant portal at merchants.toyou.io refuses a plain request outright and, opened in a browser, presents an onboarding application behind a challenge rather than a documentation site. Its own address structure describes a funnel rather than a back office, moving a new partner from a login through a profile step to a success page. The routes that would normally expose an interface dictionary answer 403, and we did not press further.

There is one public contact, and it reaches the right team. Deliverect’s ToYou article instructs a partner to “Send an email to integration@toyou.io” with a menu push identifier attached. That is the only ToYou address in this whole subject area that is published anywhere, and it belongs to an integration desk rather than to restaurant support.

The platforms that do publish this material largely publish it under legal compulsion. Wolt, Glovo, Bolt Food, Just Eat and Foody all set out ranking and partner terms in writing for their business users, and Foody says plainly that it reports on its partner complaint system under European Regulation 2019/1150, the Platform to Business rules. We have found no equivalent Gulf requirement. ToYou, Careem, Talabat, HungerStation and Jahez publish little toward restaurants, and ToYou least of all. Reading ToYou’s silence as evasive misses the point. It is what a regime with no publication requirement tends to produce.

Why can a ToYou menu publish leave your store looking closed?

Because ToYou reviews every menu before it goes live, and a store without a live menu is not a store a customer can order from. The review is described by Deliverect in one sentence, “ToYou checks each published menu before setting it live on their platform”, with a stated ceiling: “This process can take up to three hours.” That is pre publication moderation applied to each menu, not a spot check on new partners.

Deliverect separately publishes the list of conditions that make any of its channels show a store as closed, and the six headings include “Your menu is not yet published” alongside incorrect opening hours, incorrect menu scheduling and special hours. Putting the two documents together is our reading rather than a claim by Deliverect, and it produces the single most testable hypothesis on this platform: a ToYou store that stopped selling shortly after somebody republished the menu is probably waiting on review, and the window to expect has a published ceiling of three hours.

That timing matters most at the start of the day. A brand that pushes a corrected menu at nine in the morning has been told to allow until noon, which on a Saudi lunch service is the whole trading peak. The safe habit on ToYou is to publish the night before, not to publish and then watch.

What is the AWAIT status on a ToYou menu, and is it a failure?

It is a status invented by the integrator, not by ToYou, and Deliverect is explicit that it does not mean the menu failed. Its wording is that the status “will stay in the AWAIT status if ToYou haven’t approved the menu within 30 minutes. However, this does not affect the actual publication of your menu.” Read that carefully, because it sets a trap for anyone monitoring the wrong screen. AWAIT after thirty minutes is normal, and the menu may well be live.

The vocabulary belongs to Deliverect throughout. The operation type is named “MENU PUBLISH”, the record carries an “Action ID”, and the escalation route is an email to ToYou quoting that identifier. Nothing in that chain is a ToYou interface string, and an operator quoting AWAIT to a ToYou account manager is quoting a word from another company’s product. What the chain does reveal is a limit: since the only way to hurry a review is to email a human with a job identifier, there is no published way to query a ToYou menu’s review status programmatically.

Two numbers therefore live in this one workflow, and they measure different things. Thirty minutes is when an integrator’s record stops updating. Three hours is the ceiling ToYou is said to hold to for the review itself. Treating the first as a deadline for the second is the commonest way a team escalates a menu that was never late.

If ToYou closes your store, does your integrator find out?

Assume not, because nothing published says otherwise. Deliverect states the rule for its channels in general terms: “Some channels inform Deliverect when a store closure is triggered from their platform.” Some, not all, and ToYou is not named among those that do. The same passage sets expectations about the record even where it exists, noting that a “Busy Mode Sync is just Deliverect syncing through the state of your channel and not Deliverect triggering the changes”.

That is a mirror, not a control, and on ToYou there is not even a documented mirror. Deliverect publishes exactly one ToYou article, and it covers publishing a menu. ToYou is also carried by UrbanPiper, which lists it as a channel under the code up-toyou, and by FeedUs, and neither publishes a ToYou availability article either. Three integrators, zero published descriptions of how a ToYou store is switched off or brought back. An operator who believes their middleware dashboard would show a ToYou closure is believing something no vendor has claimed.

How long does it take to get a ToYou store trading again?

Longer than any comparable platform in the region, if reconnection is what is needed. Deliverect’s activation table gives ToYou as “Within one week after being requested”, against “Within 48 hours” for both Keeta and Ninja, and named weekday windows for Careem, HungerStation, Jahez and noon. ToYou and The Chefz are the two slowest entries in that table. The same article adds a precondition that catches new partners: “You must already have a menu created in Deliverect to activate an integration with a delivery channel.”

Read that figure narrowly. It is the time to activate an integration channel at Deliverect, not the time ToYou takes to onboard a restaurant or to reopen a store it closed, and the two should never be quoted as one. What it does establish is that no part of the ToYou connection is self service, which means every recovery path on this platform runs through a person and a queue.

There is a related hazard when a store is reconnected rather than reopened. Deliverect warns that publishing menus to a store “overwrites the existing menu on your ordering channel”, so a reconnection performed to fix an availability problem can silently replace whatever was configured on the ToYou side.

How should a Saudi chain watch a ToYou store it cannot query?

From the customer app, at the hours that matter, because nothing else exists. On ToYou there is no availability endpoint, no published status vocabulary, no dashboard a chain can read and no vendor claiming to mirror a platform side closure. The one state change with a published duration, the menu review, is invisible from inside the brand’s own systems, which show the menu as sent rather than as approved.

Because a ToYou store awaiting menu review and a ToYou store closed by the platform look identical from head office and neither announces itself, the only test that separates them is whether a customer in that city can order right now, which is the daily record Kitchain (kitchain.co) keeps on ToYou listings. Ownership, markets and the wider set of ToYou signals are covered on the Kitchain ToYou page.