Why your ToYou menu prices differ from the ones you set

Restaurant operators chasing a wrong price on ToYou are usually chasing a whole menu rather than a line in it. Deliverect, an integrator that carries ToYou, documents a single ToYou menu operation and no per item price update, and it states that “ToYou checks each published menu before setting it live on their platform”, a process that “can take up to three hours”. Correcting one price therefore means republishing an entire menu and waiting for it to clear review. ToYou itself publishes nothing on any of this.

ToYou is also carried by two other middleware vendors, and they do not apply the same rules to the number a customer sees. That makes the first useful question on this platform not what the price should be, but which route it travelled to get there.

Where is a ToYou price actually set?

In one of at least four places, and no ToYou document says which one wins. ToYou is documented as a channel by three separate integrators. Deliverect publishes a ToYou menu publishing article. UrbanPiper carries it as a channel under the code up-toyou, listed in Foodics documentation alongside up-mrsool, up-deliveroo, up-careem and others. The Saudi middleware FeedUs is described by Foodics as “a unified platform that connects Hungerstation, Jahez, Marsool, Lugmety, Shgardi, Lavender, Careem Now, Toyou, and several other online ordering platforms”. The fourth place is the ToYou merchant portal itself, which no vendor documents.

For a chain that is a governance problem before it is a technical one. A brand running several point of sale estates, or one that migrated between vendors, can have branches whose prices arrive by different routes, each with its own tax handling and its own idea of what a delivery charge is. The prices then disagree between branches for a reason nobody in the brand can see, because each system is faithfully reporting the number it sent.

Why does a ToYou price change go through a review?

Because ToYou treats every published menu as something to inspect, and a price is part of a menu. The only ToYou operation Deliverect names is a menu publish, and the review it describes is applied to each one: “ToYou checks each published menu before setting it live on their platform. This process can take up to three hours.” No integrator publishes a lighter path for a single price, a single item or a temporary offer.

The consequence is a rhythm most operators find uncomfortable. On platforms with an item level update, a wrong price is a two minute fix. On ToYou the same correction is a full republish that enters a queue with a published ceiling of three hours, which is long enough for a lunch service to trade on the wrong number and long enough that a second corrective push may be issued before the first has cleared. The discipline this rewards is batching changes and publishing outside trading hours, which is the opposite of the habit a chain builds on faster platforms.

There is a monitoring trap alongside it. Deliverect records that its own operation “will stay in the AWAIT status if ToYou haven’t approved the menu within 30 minutes”, and adds that “this does not affect the actual publication of your menu”. A price can therefore be live on ToYou while the integrator’s screen still reads as waiting, and a team that trusts the dashboard will republish a menu that was already correct.

What does the FeedUs route do to a ToYou price?

It applies its own tax and charge rules, and Foodics documents them. Describing the FeedUs integration, Foodics states that “FeedUs supports Tax Inclusive pricing only for now” and, separately, that “FeedUs will not send delivery charges to Foodics”. Both are properties of the middleware rather than of ToYou, and they apply to every platform FeedUs carries, ToYou included.

Tax inclusive only is the rule that quietly rewrites a price book. A brand that maintains prices net of VAT, which is normal for a group that also sells wholesale or trades across tax regimes, is sending a number that the chain downstream treats as already gross. Nothing errors, because both systems did what they were configured to do, and the customer simply sees a price below the one the brand intended. We describe the same trap in more detail, with a published percentage attached, on TheChefz menu price mismatch, where the integrator documents a default rate. For ToYou no rate is published at all.

The delivery charge rule cuts the other way. If the charge never reaches the point of sale, then the total a customer paid on ToYou cannot be rebuilt from the restaurant’s own records, and any reconciliation between the storefront and the till is missing a component by design. That is worth knowing before an operations team spends a week hunting the difference.

Foodics also documents that a FeedUs menu can be “customized based on the online ordering platform per (location, time, or day of the week)”. That is a legitimate reason for two branches of the same brand to show different ToYou prices, and it is the first thing to rule out before assuming a fault.

Can a ToYou price set in the merchant portal be overwritten?

Yes, and the warning is published, though not by ToYou. Deliverect’s instructions for adding a store state that selecting menus to publish means “Doing this overwrites the existing menu on your ordering channel”, with the advice to make sure the menu is complete first. Anything configured on the ToYou side, including a price somebody corrected there by hand, is replaced rather than merged.

This is how a fixed price un fixes itself. A branch manager reports a wrong price, someone with portal access corrects it directly at ToYou, and the correction survives until the next scheduled menu publish from the point of sale, which restores the original error without anyone touching it. The brand then has an intermittent fault that correlates with nothing visible, because the trigger is a routine publish rather than an edit. On a platform where every publish is also a review, the reappearance can be hours behind the push that caused it.

What does ToYou publish about prices?

Nothing an operator can rely on. There is no ToYou price parity position, so whether a delivery price may exceed the in store price is simply unstated, in contrast to Careem Food, Glovo, Bolt Food and Deliveroo, all of which publish one. There is no published propagation figure of ToYou’s own, no published item level out of stock wording and no merchant help centre in which such a statement could sit.

The disclosure gap has a structural explanation rather than a conspiratorial one. Platforms operating in the European Union publish partner terms and ranking parameters because Regulation 2019/1150, the Platform to Business rules, requires them to, which is why Wolt, Glovo, Bolt Food, Just Eat and Foody all have documents a restaurant can cite. We have found no equivalent Gulf requirement. Some Gulf platforms publish parity positions anyway, and ToYou is not one of them.

One practical warning follows. Statements about ToYou pricing do circulate online, and the ones we traced originate with commercial data vendors describing what they scraped rather than with ToYou describing its own rules. They should not be quoted to an account manager as platform policy, because ToYou has not published any.

How does a chain verify a ToYou price without a portal?

By reading the listing a customer reads, per city and per branch, and comparing it against the brand’s own price book. Every alternative check available elsewhere is missing here. There is no job identifier a chain can query, no published propagation window against which to call a change late, no parity clause to appeal to and no error report describing which items were altered in review.

A ToYou price that is wrong because a tax model reinterpreted it, or right until the next publish overwrites it, reconciles perfectly inside the restaurant’s own systems, since those systems hold exactly the number they sent, which is why the only place the discrepancy exists is the storefront Kitchain (kitchain.co) reads each day. The neighbouring question of a ToYou store that stopped selling altogether is covered on why a ToYou store shows as closed, and the platform itself, its markets and its ownership are on the Kitchain ToYou page.