How to get Foody to put your restaurant back online
Restaurant chains on Foody get something almost no other delivery platform provides, which is a straight answer on screen about whether a reopen is theirs to make. The partner portal shows one of two subtitles under a closure. Where the closure has an end attached it reads “{reason}. You will automatically reopen in {time}.” Where it does not, it reads “You can’t reopen at the moment.” Reading that line before pressing anything is the single most valuable habit on this platform, because it separates a thirty second recovery from a case that has to be argued.
Read the Foody banner first, because it says whether a reopen is permitted
The portal loads an availability dictionary that names every state a store can be in, and the states are not interchangeable. A merchant initiated closure carries reassuring wording and an invitation: “You are closed. Reopen if you’re ready to accept orders.” A platform applied closure carries the heading “Temporarily closed” and one of the two subtitles above. Source: the availability dictionary loaded by the Foody partner portal.
A third message covers the case that traps most operators, because it looks like a fault and is a configuration state: the heading “Restaurant cannot be opened” with the subtitle “You are outside of your opening hours.” The portal then supplies its own instruction, “To reopen, please update your schedule in Opening times.” No number of presses on the status control will do anything until the schedule allows trading.
So the first action in a Foody incident is not a button. It is reading the banner, writing down the exact words, and choosing between three completely different routes: press reopen, edit the schedule, or start a conversation with Foody.
Which Foody control returns a store, and where does each one sit?
The portal names them individually rather than hiding them behind one toggle. “Reopen now” ends a closure the merchant owns. “Stay open” declines a prompt to close. “Close now” and “Close for the day” go the other way, and a successful change confirms with “Status updated”. A busy state is created with “Set to busy (30 mins)” and shows the banner “Closed until {time}”, so it ends on its own without anybody returning to it.
Two of those deserve emphasis for a chain. The busy state is a closure with a timer rather than a longer preparation window, which means choosing it during a rush costs half an hour of trading and then repairs itself. Close for the day has no such timer and is the option that most often gets chosen by accident at seven in the evening.
The schedule is a separate surface with its own vocabulary. The opening times dictionary keeps a list of planned closure reasons including “Temporary Closure”, “Vacation”, “Renovation”, “Maintenance”, “Staff Sickness”, “Public Holidays” and “Special Occasion”. Source: the opening times dictionary. A closure entered there ends when its dates end, and pressing reopen in the availability screen will not shorten it.
What do Foody’s General Terms say about how a suspension ends?
They give an ending condition rather than a duration, and the condition is operational. On stores using the delivery service, Foody reserves the right “to temporarily suspend the receipt of orders from Users on its Platform for the Partner’s products” where the partner is unable to fulfil orders, giving as examples a heavy workload causing delays, cancellations due to inability to fulfil, and a case where “it is found that there is no connectivity and orders cannot be received”. The suspension runs “for the necessary time until the Partner is able to effectively fulfill orders again”. Source: Foody General Terms and Conditions for Business Users, version 6.0, valid from 1 June 2026.
Compliance suspensions end the same way, by demonstration rather than by expiry. For breaches involving illegal content and for abuse of the complaint system the terms state that “The suspension of services lasts until confirmation of the Partner’s compliance”, and warn that a repeat gives the company the right to terminate the collaboration immediately.
Two timing facts sit alongside that. For a serious reason, Foody may suspend or temporarily cease part or all of its services “with five (5) days’ prior written notice”, or immediately in cases such as malicious software, a data breach, illegal or inappropriate content, counterfeiting or fraud. And a store that receives no orders through the platform “for at least two months, in a way that the Partner appears inactive – unavailable on the platform” is itself listed as a ground for suspension, which is the rare case of an outage that eventually causes a worse outage.
Who does a Foody partner contact when the reopen button is refused?
Foody publishes its partner communication channels in the same terms, naming an email address at info@foody.com.cy and a telephone number, 77772250. That is the general channel for partner communication rather than a dedicated availability line, and Foody publishes no response time for a suspension, no ticket category and no evidence list, so treat it as the documented address and not as a service level.
There is a second route the portal itself points at, and it is worth knowing which closures trigger it. The reason string “Your device is consistently disconnected. An account manager will contact you shortly” tells the merchant that Foody has already assigned the case, which means the useful action is to fix the connection and be reachable rather than to open a parallel conversation.
A different message blocks some people from acting regardless of the closure type: “Looks like you don’t have the order management permission to change your status. Please contact your manager if you need access”. That one is internal to the brand, not to Foody, and it is worth auditing before an incident, because a store whose only permitted account belongs to somebody off shift has a recovery time set by that person’s phone.
The Foody closures that end by repair rather than by request
Several of the published reasons name a condition the restaurant can correct, and correcting it is faster than asking. “You have been declining orders” is shown for order failures and excessive rejections, so the fix is to stop the rejections rather than to argue about the closure. “Couriers are waiting too long. Ensure that orders are prepared on time for courier arrival” names the remedy inside the reason itself. “Check-in required” and “Check-in failed” describe a scheduled opening that was never acknowledged, which is a routine to change rather than a state to appeal.
Then there is the closure the portal causes by losing its own connection, which Foody addresses by recommending that the portal be installed as an application rather than kept in a browser tab. That one is repaired by following the recommendation, not by opening a ticket, and a group that does it once per machine removes a whole category of closure from its estate permanently.
Sorting the reasons this way is the whole discipline, because only a minority of them require Foody to do anything at all. Everything named above ends when the condition behind it ends, which means the fastest route back is almost never the support address.
What should a Foody chain hold so a reopen never becomes a ticket?
Four things, none of which can be assembled during an incident. A named account per branch that holds the order management permission. The partner portal installed as an application on the machine that stays logged in. A schedule that matches the kitchen, so that “You are outside of your opening hours.” never appears during trading. And a habit of recording the exact banner text at the moment a store goes quiet, because that string is the only diagnosis Foody gives and it disappears the moment the state changes.
What none of those provides is notice. A busy state, a closed day, a platform closure for declining orders and a dropped portal session all produce the same result for a customer and very different things inside the portal, and nothing is sent to head office when any of them begins. What separates them is the interval during which the store could not actually be ordered from, measured against the hours that store published. Kitchain (kitchain.co) builds exactly that on Foody listings, and it does so without needing an account on a platform where account access is itself part of the problem.