Why your Foody menu prices differ from the ones you set
Restaurant operators on Foody carry the cost of a wrong price, and Foody puts that in writing. Its technical interconnection annex says the prices that apply are “those that have been entered in the ordering system of the Company”, and that a partner who has not notified a change in time “will bear the sole weight of any cost differences arising due to an error, difference or discrepancy of these prices”. A partner can edit the price list in Foody’s portal instead of emailing it, but even then the new price counts only “after their submission has been systematically completed”.
Which price governs a Foody order, yours or the one in Foody’s system?
Foody’s. Annex III of the “General Terms and Conditions for Business Users”, version 6.0, is a Technical Interconnection Agreement, and clause 2.2 of it settles the question for both the customer and the invoice. It reads that “the selling prices / value of the Partner’s products, which will be ordered by users through the Company’s Website, will be those that have been entered in the ordering system of the Company and those that will be applied for the invoicing between the contracting parties”.
The next sentence assigns the loss. The partner “will bear the sole weight of any cost differences arising due to an error, difference or discrepancy of these prices, in case he has not timely informed the Company in writing for change of prices / price list”. Read those two sentences together and a Foody price mismatch stops being an IT question. Commission is calculated on Foody’s number, the customer pays Foody’s number, and the gap between that number and the kitchen’s costs the restaurant unless it can show it told Foody in time and in writing.
How does a Foody partner change a menu price at all?
Two routes, and only one of them leaves a record. Clause 2.6.1 says the partner “must inform the Company without delay via email or telephone of any changes he makes to the menu products or its prices”, and adds that “He can also enter such changes himself directly through the Company’s portal using the codes provided to him”. Telephone is an accepted channel for a change whose liability clause turns on having informed Foody “in writing”, which is a contradiction worth resolving inside your own team before you rely on a phone call.
Neither route takes effect on submission. Foody says only that “The changes will be finalized as soon as the Company proceeds with their systematic completion”, and Annex III repeats the same condition for portal edits. There is no stated turnaround, no queue position and no confirmation event named anywhere in the document. So between a price change and its appearance there is a window of unspecified length in which the storefront is legitimately showing the old number, and the contract makes that the partner’s exposure rather than Foody’s.
What does the Foody price parity clause actually require?
More than Foody’s consumer terms suggest, and this is a real difference between two Foody documents. Clause 2.13, headed “User Charges”, states plainly: “The Partner shall apply to Users the same, and in no case higher, charges than those offered for orders placed through the Partner’s own website, if any. The Partner is not prevented from making offers to its customers directly at its physical store.”
That is an unconditional obligation with one carve out. The comparison is your own website, and the exemption is your own dining room, so an in store price that undercuts the app is expressly allowed while a cheaper price on your own ordering site is not. Foody’s public terms of use, written for customers, describe the same idea far more softly, saying only that “In some cases, our Company may limit the ability of restaurants / cooperating stores to offer different prices on their own websites” (foody terms of use).
The same consumer page goes further in the other direction, telling customers that “The prices listed on the platform are determined by our business partners, the cooperating stores at their absolute discretion and for this reason may be subject to changes and variations”. Absolute discretion is not what the vendor terms grant. Both statements are current and both are Foody’s, so an operator quoting the customer facing page in a commercial conversation is quoting the document that does not bind them.
Which Foody price changes are not menu edits at all?
The ones bought from a sales representative. Under clause 2.11.4, a partner on the ordering service who joins “Foody Pro” offers subscribers “a discount, which will be applied to the total price list of their store and the percentage of which will be agreed upon with the company’s sales representative”, and is then “charged the amount corresponding to the discount percentage given to the User”. That is a store wide change to what a whole class of customers pays, agreed verbally with a salesperson, and it never appears as an edit to any individual item.
The loyalty and win back services work the same way on the money. Under the “Piniata” service the terms say “The Partner bears the amount of the discount offered to the User”, and for the regular user coupons that “The discount amount to the User is borne by the Partner”. None of these is a price error, and all of them make the price a customer sees differ from the number in the price book. An investigation that only compares item prices will keep finding nothing.
Does a POS bridge to Foody remove the price risk?
It moves it rather than removing it, and it adds obligations. Annex III makes the partner responsible for the ordering system itself, requiring at the partner’s own expense that “the response time of his ordering system does not exceed 500ms” and that “the availability rate of the ordering system is at least 99.9% per year”. That is an uptime commitment pointing at the restaurant, not at the platform, and it sits in the same annex as the clause that puts price discrepancies on the partner.
There is also a documented way for an integrator to erase a portal built menu wholesale. Deliverect’s own help article on adding stores warns that when you select menus to publish, “Doing this overwrites the existing menu on your ordering channel”, and tells operators to make sure the menu is complete on the integrator’s side first (help.deliverect.com). Where a chain has both a portal login and middleware, the first publish is the moment prices most often change without anyone deciding to change them.
How do you check a Foody price without a partner-side price report?
By reading the storefront, because that is the only surface where Foody’s number and your number can be compared. The contract gives no sync window to wait out, no error report to open and no confirmation that a submitted change has been “systematically completed”, and it names the portal three different ways across three clauses, as “the Company’s portal”, “the Vendor Portal” and “the online portal provided by the Company”. None of those is a price audit tool.
That leaves one workable method for a chain. Read every branch’s live Foody menu against the brand price book on a schedule, and treat the gap as a dated fact rather than an impression, because the liability clause turns on when you told Foody. Kitchain (kitchain.co) reads those live Foody menus item by item from the customer side and flags where a branch differs from the brand price, which on this platform is the only evidence either side can point at. Ownership, markets and the wider set of Foody signals are covered on the Kitchain Foody page.