Does Foody tell you when your restaurant goes offline?
Restaurant operators on Foody get more explanation than almost anywhere else in this category, and it is written onto a screen rather than sent. The availability plugin loaded by the Foody partner portal ships closure reasons the platform displays to the merchant, and one of them promises a human will follow up: “Your device is consistently disconnected. An account manager will contact you shortly”. Foody’s general terms go further still and set an actual notice period for suspension. Both of those depend on somebody either reading a screen or watching an inbox.
Which Foody closure message promises that a human will be in touch?
The disconnection one, and it is the only string in this whole set of platforms that commits to contact. It reads in full: “Your device is consistently disconnected. An account manager will contact you shortly”. Source: availability dictionary loaded by partner-app.foody.com.cy.
The reasons around it are equally direct about who acted. “Check-in required” and “Check-in failed” cover an opening that was never acknowledged. “You have been declining orders” is displayed where rejections have accumulated. “Couriers are waiting too long. Ensure that orders are prepared on time for courier arrival” closes a store for a delivery problem measured at the door.
Naming the cause on the merchant’s own screen is a real design choice and it deserves credit. It also has one condition attached. A string is displayed to a session, so the value of all four depends entirely on the portal being open in front of somebody when the closure lands.
How much notice do the Foody general terms require before a suspension?
Five days in the ordinary case, immediately in the serious ones, and the clause says so in a single sentence: “The Company reserves the right to suspend or temporarily cease the provision of part or all of its Services to the Partner with five (5) days’ prior written notice if a serious reason exists, or even immediately (by notifying the Partner of its relevant decision) in cases such as the occurrence of malicious software, data breach, illegal or inappropriate content, unsolicited electronic messages, inappropriate products or services of the Partner, counterfeiting, alteration, fraud, etc.” Source: Foody General Terms and Conditions for Business Users.
Read the parenthesis in the second half. Even where Foody acts immediately, the document still describes notifying the partner of the decision. Very few platform contracts in this space bind themselves to that.
Permanent termination carries its own periods, with thirty days of prior written and reasoned notice in the ordinary case, and immediate termination upon prior written notice where there is a legal obligation or a proven repeated breach. So the contract distinguishes between three speeds and attaches a notice to each of them.
Where does Foody send a written notice, and who reads that address?
To the address the partner declared, which is a question worth answering before it is needed. The terms describe electronic invoicing going to “the email address provided by the Partner for this purpose in the Special Terms”, and payment related changes going to a named mailbox at the company.
For a single restaurant that is usually the owner. For a chain it is very often a finance address set up during onboarding years earlier, monitored monthly, and unknown to the operations team who would actually act on a suspension notice.
That is the practical failure mode of a good contractual commitment. Foody undertakes to write. Whether the letter arrives in front of a person who can do anything about it on a Friday evening is a question about the brand’s own address book rather than about the platform. Auditing which mailbox each national entity declared is a ten minute job that decides how much the five day clause is worth.
Does Foody say anything before it suspends order intake for a connectivity fault?
The clause that authorises it does not say so. Foody reserves the right “to temporarily suspend the receipt of orders from Users on its Platform for the Partner’s products, if, for example, the latter is unable to fulfill orders”, listing among the examples a heavy workload causing delivery delays, cancellations for inability to deliver, and the case where “it is found that there is no connectivity and orders cannot be received”, holding the suspension “for the necessary time until the Partner is able to effectively fulfill orders again”.
No notice period appears in that clause, and none is implied by the five day rule above, which is written for suspension of the Services rather than for a temporary hold on order intake. These are two different powers in two different parts of the document, and only one of them carries a clock.
The portal is where the difference is visible, and it distinguishes the cases in its own vocabulary. A merchant initiated closure reads “You are closed. Reopen if you’re ready to accept orders.” A closure the merchant cannot lift shows “Temporarily closed” with either “{reason}. You will automatically reopen in {time}.” or the blunter “You can’t reopen at the moment.”
Can a long Foody outage become the reason for a longer one?
Yes, and it is written into the list of grounds for suspension. Among the reasons the terms name is “Failure to receive orders via the platform for at least two months, in a way that the Partner appears inactive – unavailable on the platform.”
That closes a loop most platforms leave open. On Foody, a listing that has been dark long enough becomes a listing that can be suspended for having been dark, which turns an unnoticed availability problem into a contractual one.
Two months is long enough that the branches at risk are usually the ones nobody is looking at, a site that was opened and quietly abandoned, a location whose device was never replaced, a franchise that changed hands. Those are exactly the listings a portal session in head office does not cover, because nobody opens the portal for a branch they have stopped thinking about.
Why does the screen carrying the reason depend on the thing that failed?
Because on Foody the portal session is part of the connection rather than a window onto it. Foody says as much when it recommends installing the portal properly, warning that a session left behind other tabs can end in closures the platform applies on its own. The mechanism and the exact wording are set out on why a Foody store shows as closed while the restaurant is open.
So the sequence closes on itself. The session drops, the store closes automatically, and the reason for the closure is rendered into the session that is no longer there. The one message that promises an account manager will call is displayed on the surface most likely to be absent at the moment it is written.
There is a second dependency in the same place. Changing a status is a permission, and the portal has a message for anyone without it: “Looks like you don’t have the order management permission to change your status. Please contact your manager if you need access.” For notification purposes the effect is doubled, because the person the portal is talking to may not be a person who can answer it.
The check that survives both is the customer’s view. A declined run of orders, a dropped session and a permission nobody holds all end in the same place, which is a customer who cannot order at an hour the store said it would be trading. Measured from there, all three become one interval with a beginning and an end. Kitchain (kitchain.co) reads Foody listings that way, from the public storefront and with no portal login involved, so the record survives a change of franchisee or of agency.