Why Foody says your restaurant does not deliver to an address you cover

Restaurant chains on Foody can lose a district without changing a setting, because Foody reserves the right to take it away. Its vendor terms let the platform “temporarily limit the coverage area of the Delivery Service for the Partner’s products” when order volume makes timely delivery impossible, and separately let it suspend order taking for a store “if it is found that there is no connectivity and orders cannot be received”. Both measures are temporary, both are Foody’s decision, and neither shows up in the store’s own configuration.

Can Foody shrink your delivery area without changing your settings?

Yes, and it says so in clause 2.3 of the “General Terms and Conditions for Business Users”, version 6.0, the contract signed with “Delivery Hero (Cyprus) Ltd” trading as Foody. The sentence is short and specific: the Company “reserves the right to temporarily limit the coverage area of the Delivery Service for the Partner’s products in the event of an increased number of orders that make it impossible to deliver new orders to Users in a timely manner, and for the necessary time until it is possible to effectively fulfill orders again”.

Read it as a demand valve rather than a punishment. The trigger is order volume, the lever is geography, and the release condition is Foody’s own judgement about when delivery is workable again. The consequence for a restaurant is that its furthest addresses go first, exactly at the hours that matter most, and that the shrink corrects itself before anyone gets round to investigating. That is why this failure is so often reported by customers and so rarely reproduced by the operator an hour later.

What else makes Foody stop taking orders for your store?

The same clause lists the reasons, and they are worth separating from a store closure. Foody may “temporarily suspend the receipt of orders from Users on its Platform for the Partner’s products, if, for example, the latter is unable to fulfil orders (such as due to a heavy workload of the Store that will cause a delay in the delivery of products to the User, if the Partner cancels orders due to the inability to fulfil them in the system, if it is found that there is no connectivity and orders cannot be received, etc.) and for the necessary time until the Partner is able to effectively fulfil orders again”.

Three distinct triggers sit in that sentence. Kitchen workload that would delay delivery, a pattern of the partner cancelling accepted orders, and a dead connection to the order device. Only the first is something a manager would describe as being busy. The second is a consequence of a decision taken order by order, and the third is a network fault that nobody in the restaurant experiences as an event at all. All three end the same way for the customer, with the store simply not offered.

Why does the Foody connectivity clause matter more than it reads?

Because the same contract sets the standard the connection has to meet, and points it at the restaurant. Annex III, the Technical Interconnection Agreement, requires the partner to ensure at its own expense that “the response time of his ordering system does not exceed 500ms”, that security protocols are in place, and that “the availability rate of the ordering system is at least 99.9% per year”. Foody keeps a manual fallback for itself, reserving “the right to forward orders by telephone in case of malfunction of the connection methods”, but the obligation to be reachable is the partner’s.

Left alone, a connectivity problem becomes a commercial one. Clause 5.4.6 lists “Failure to receive orders via the platform for at least two months, in a way that the Partner appears inactive – unavailable on the platform” among the grounds for suspension or deletion. A branch that quietly stopped receiving orders in one district is not on a two month clock yet, but the direction of travel is written into the agreement, and no notification obligation exists on Foody’s side for the temporary measures at all.

Does the Foody coverage rule apply to every partner?

No, and this is the most useful distinction on the page. The coverage limiting right and the order suspension right both sit inside clause 2.3, which is the Delivery Service clause, and Foody introduces them by saying “With regard to Partners who use the Delivery Service”. A partner delivering with its own riders under the Ordering Service alone is outside that clause, so the platform is not shrinking its map at peak.

The consequence is that two Cypriot restaurants reporting the same symptom may need entirely different investigations. For a store on Foody’s couriers, an address that disappears at 8pm and returns at 10pm is behaving exactly as the contract permits. For a store delivering itself, the same pattern has to be explained some other way, and the ranking clause is a better place to look than the logistics one. Knowing which service a branch is on is the first question, not a detail.

Why can a Foody address look uncovered when it is covered?

Because Foody may be showing a different branch of yours instead. The display clause states that “If multiple Partners belonging to the same chain of stores serve a User’s location, only the locally closest store may be displayed to the User”. A brand checking whether an address is served will find that it is. A customer at that address sees one storefront, and if the nearer branch is closed, out of range or paused, the further one is not automatically offered as a fallback.

Two smaller rules add to the same confusion. Clause 2.4 makes the set of store categories a customer sees depend both on the products a store sells and on which categories are available in that customer’s geographic area, so a category that exists in one Cypriot city need not exist for a customer in another. And subscribers to the “Foody pro” service are subject to restrictions “concerning the distance in kilometers and the setting of a minimum order value”, which means the same store can be reachable for one customer and not for another standing beside them.

What record actually moves a Foody coverage conversation?

A dated one, filed through the route the contract provides. Clause 10.2 gives partners a free Internal System for handling complaints, covering “conduct or measures of the Company related to the Services that affect the Partner and its activity”, filed through the portal, describing the issue “with reference to specific details”, and answered in writing “no later than 30 working days from its receipt”. Coverage shrinks and connectivity suspensions are precisely the measures that clause is written for.

The problem is evidentiary rather than procedural. Because both measures are temporary and self correcting, and because nothing obliges Foody to log them where the partner can see, an operator arriving at that process with a recollection of a bad Friday has nothing to file. An operator arriving with addresses, dates, hours and what the app showed at each has a complaint the system can answer.

How should a Cyprus chain take a coverage reading?

From the customer side, at the hours the district orders, and repeatedly. Cyprus makes this cheaper than it sounds, because demand concentrates in a handful of coastal cities separated by open country, so a small set of well chosen addresses covers most of a brand’s real exposure. Pick at least one point at the edge of where you believe you reach, and record not just whether the store appeared but the delivery time and fee it appeared with.

Two readings a week apart at the same addresses separate the three explanations that feel identical from inside the kitchen: a district that never had you, a district that drops only at peak, and a district that quietly stopped. Because a Foody coverage limit lifts on Foody’s schedule and leaves no trace on your side, the only usable evidence is what customers at fixed points were actually offered, which is what Kitchain (kitchain.co) Coverage records at kitchain.co. Our fuller profile of this platform and the Cyprus market is at https://kitchain.co/aggregators/foody/.