Just Eat Toast Integration UK: Complete Setup Guide 2026

Just Eat Toast Integration UK: Complete Setup Guide 2026

Written by: JJ Tan, Founder, Jelly | Last updated: 23 June 2026

Key Takeaways for UK Toast Operators

  • UK multi-site Toast operators face daily friction because Just Eat orders sit on a separate platform and need manual re-entry into Toast.
  • A direct Just Eat–Toast integration exists but remains in limited release for UK operators in 2026, while middleware tools such as Deliverect or Otter provide a paid alternative.
  • Just Eat’s UK delivery commission must appear correctly in reporting, and recording net rather than gross order values prevents understated food-cost percentages.
  • Connecting Just Eat to Toast fixes order flow but does not automatically provide live gross-profit visibility, because real-time margin tracking needs Toast sales data plus supplier invoice costs.
  • Track live margins from Toast with a Jelly walkthrough and see gross-profit reporting across every site.

Why Toast and Just Eat Stay Siloed in the UK

Toast is the second-largest POS provider globally, holding 21.69% of the broader restaurant POS market through Q1 2026, and its UK footprint skews toward larger, multi-site operators. Just Eat remains one of the dominant food delivery aggregators in the UK market. When these two platforms run separately, order data stays siloed, delivery revenue does not automatically appear in Toast reporting, kitchen display systems do not receive Just Eat tickets, and finance teams must reconcile delivery income against food costs manually.

The operational impact is measurable. Each manual order entry introduces transcription risk, slows ticket times, and hides the true cost of a delivery sale once commission is deducted. For operators at £500k+ annual revenue expanding across sites, the cumulative effect on gross profit is significant and largely invisible without automated data flows.

To close this operational gap, UK operators have two main routes to connect Just Eat to Toast. They can use a direct integration through Toast’s partner programme or a middleware solution that sits between both systems. The next section explains the direct route and its current UK limitations.

Direct Toast–Just Eat Integration: Steps and UK Limits

Toast maintains a Directory of Channel and Integration Partners that manages delivery platform connections. The direct route for Just Eat connectivity usually follows these steps:

  1. Log in to Toast Web and open the Integrations section of your account dashboard.
  2. Search the Toast partner directory for Just Eat or its parent company, Just Eat Takeaway.
  3. Submit an eligibility request. As of 2026, direct access for UK operators remains in a limited-release programme, so timelines vary.
  4. After approval, configure order routing so incoming Just Eat orders reach the correct kitchen display or printer within Toast.
  5. Map Just Eat menu items to their corresponding Toast menu items to keep ticket generation and sales reporting accurate.
  6. Run a test order through the Just Eat platform and confirm it appears correctly in Toast before going live across all sites.

The main limitation of the direct route in 2026 is access. UK operators should contact Toast Support to confirm current eligibility criteria, because the programme has not opened universally to all UK accounts. Menu synchronisation also needs careful management, as some changes still require updates in the Just Eat merchant portal.

Using Middleware like Deliverect or Otter

Middleware aggregator platforms such as Deliverect, Otter, and Slerp act as a translation layer between Just Eat and Toast. They receive orders from Just Eat via the Just Eat API, reformat them to Toast’s order schema, and inject them into Toast as if they were native orders.

Middleware introduces extra cost for the group. Multi-site operators should request full pricing details, because per-site fees can add up quickly. Setup fees vary by provider and are sometimes waived on annual contracts.

The trade-off with middleware is an additional vendor relationship and a dependency on the middleware provider’s uptime. For operators who cannot access the direct Toast–Just Eat integration, middleware remains the practical path to automated order flow in 2026.

Handling UK Delivery Commissions and Menu Sync

Just Eat charges UK restaurant partners a commission on each order, with rates agreed contractually and varying by operator tier and market. This commission is deducted from the gross order value before settlement, so the revenue figure that appears in Toast, if orders are injected at face value, overstates actual net income.

Best practice for UK operators is to configure the integration, whether direct or middleware, to record the net settlement value rather than the gross order value, or to apply a commission adjustment at the reporting layer. Without this step, food cost percentages calculated against gross delivery revenue appear artificially low and hide the real margin impact of the delivery channel.

Menu synchronisation needs a clear workflow to prevent data conflicts between platforms. The most reliable approach keeps a single source of truth, typically the Toast menu, and uses the integration’s sync function or a manual update process to push changes to Just Eat. This one-way flow matters because price changes made directly on Just Eat that do not match Toast create reporting discrepancies and customer-facing errors when orders arrive.

Integration Costs for Just Eat and Toast

The cost of integrating Just Eat with Toast in the UK depends on the route chosen. The direct integration, when available, is usually included within Toast’s existing subscription or charged as a modest add-on through the partner programme, so operators should confirm current pricing with Toast Support because fees can change. Middleware solutions add a separate monthly cost, plus any one-time onboarding or setup fees charged by the middleware provider. Operators should calculate the full integration overhead, including per-site scaling, before committing.

Toast and Uber Eats Integration in the UK

Toast supports Uber Eats via a direct integration that does not require or appear in its Integration Marketplace partner directory. The connection follows a similar configuration process to Just Eat, where operators request access through Toast’s integrations dashboard, map Uber Eats menu items to Toast items, and configure order routing. UK availability and eligibility requirements mirror those for Just Eat, and limited-release access still applies in some cases. Middleware platforms that support Just Eat usually also support Uber Eats, which lets operators manage multiple delivery channels through a single middleware account.

Toast API Integration Guide for UK Restaurant Systems 2026

Operators with development resource can use Toast’s developer documentation for API references covering order ingestion, menu management, and reporting endpoints. Key considerations for UK implementations in 2026 include:

  • Authentication: Toast uses OAuth 2.0. UK operators must register their integration in the Toast developer portal and obtain client credentials scoped to their restaurant group.
  • Order injection: The Orders API accepts POST requests with line-item detail. VAT must be handled correctly at the line level, because UK tax requirements differ from the US defaults in Toast’s schema.
  • Menu sync: The Menus API allows programmatic updates to item names, prices, and availability. Automated sync scripts should run on a schedule that matches the menu update cadence.
  • Webhooks: Toast supports webhooks for real-time order events, which lets downstream systems receive order data without polling.
  • Rate limits: Current rate limit documentation should be reviewed before designing high-volume integrations, especially for multi-site groups where API calls aggregate across locations.

Custom API builds carry higher upfront development cost than middleware but give operators greater control over data mapping and commission handling logic.

Turning Toast Sales Data into Live Profitability

Connecting Just Eat to Toast resolves the order-flow problem but not the margin-visibility challenge outlined earlier. The operational gap sits between sales data and cost data.

Toast records what was sold and at what price, while supplier invoices record what ingredients cost. Without a system that reads both in real time, gross profit becomes a lagging figure calculated weekly or monthly by an accountant, which is too late to react to a supplier price increase or a menu item that has slipped below target margin.

The automated approach combines invoice scanning with POS sales data. Every supplier invoice is digitised at line-item level as soon as it arrives, ingredient costs update automatically, and dish-level gross profit margins recalculate in real time. When a cost moves, the operator sees it the same day, not at month end, and price alerts highlight which ingredients have increased and by how much so procurement teams can negotiate credits or switch suppliers before margin damage builds up.

Jelly automates this entire flow for UK restaurants, pubs, and boutique hotels running Toast. Jelly’s native Toast integration pulls item-level sales data in real time via API, maps each POS item to a costed dish recipe, and combines that with automated invoice scanning to produce live gross-profit margins across every menu item and every site. The Flash Report delivers a daily GP view, Price Alerts flag cost movements immediately, and the Sales Mix report shows which dishes drive profit and which erode it. Setup takes under five minutes, and operators consistently report GP improvements of two percentage points or more within the first three months.

Book a demo to see real-time margin tracking in action and understand how Jelly uses Toast data to protect delivery profitability.

Common Integration Errors and Fixes

  • Orders not appearing in Toast: Confirm that the integration is active in both the Toast dashboard and the Just Eat merchant portal, and check middleware uptime status if you use a third party.
  • Menu item mismatches: Unmapped items cause orders to fail or route incorrectly, so audit the item mapping table after every menu change on either platform.
  • Duplicate orders: Duplicates can appear if both a direct integration and a middleware connection are active at the same time, so disable one route before enabling the other.
  • Commission not reflected in reporting: Check whether the integration passes gross or net order values to Toast and adjust reporting logic or integration settings accordingly.
  • Admin access errors: Toast and Just Eat both require admin-level credentials to configure integrations, so confirm that the account used has the correct permissions before setup.

Decision Framework for UK Operators

The table below summarises the primary integration routes for UK operators in 2026. Cost figures are indicative, so confirm current pricing with each provider before committing.

Route Cost UK Limitations
Direct Toast–Just Eat integration Included in Toast subscription or low add-on fee (confirm with Toast Support) Limited-release access, so current status must be confirmed with Toast
Middleware (e.g. Deliverect, Otter) Additional monthly fees per site, plus potential setup fees Additional vendor dependency, fees scale with group size, uptime reliance on middleware provider

Frequently Asked Questions

Is Just Eat directly integrated with Toast POS in the UK?

A direct integration exists within Toast’s partner programme, but as of 2026 it remains in limited release for UK operators. Operators should contact Toast to confirm current access and process. Operators who cannot access the direct route usually use a middleware platform to bridge the two systems in the interim.

How long does it take to set up a Just Eat and Toast integration?

The technical configuration, once access is granted, usually takes a few hours and covers order routing, menu item mapping, and test order verification. The eligibility and approval process for the direct route can add days or weeks depending on Toast’s current queue. Middleware setups are generally faster to activate, with most providers offering same-week onboarding, although menu mapping still requires operator time proportional to the size of the menu.

Will integrating Just Eat with Toast automatically show my delivery margins?

No. The integration routes Just Eat orders into Toast and records sales data, but it does not calculate gross profit margins. To see live delivery margins, you need a system that combines Toast sales data with real-time ingredient costs from supplier invoices. Jelly does this automatically, pulling item-level sales from Toast via API, matching them to costed dish recipes updated by automated invoice scanning, and producing live GP margins per dish and per site, including the option to build a separate delivery menu that factors in commission overhead.

Can I manage multiple sites through a single Just Eat–Toast integration?

Yes, although each site usually needs its own integration configuration. In Toast, each location is a separate entity with its own menu and order routing settings. Middleware platforms generally support multi-site management from a single dashboard, which simplifies administration for group operators. Menu changes still need to be applied per location unless the middleware or Toast’s multi-location management tools support group-level updates.

What happens to my Just Eat data in Jelly once Toast is connected?

Once Toast is connected to Jelly, all item-level sales data, including orders originating from Just Eat that have been routed through Toast, flows into Jelly in real time. Jelly maps each sold item to its costed recipe, updates margins as ingredient prices change via invoice scanning, and surfaces the data in the Flash Report, Sales Mix, and Price Alert features. The delivery menu tool within Jelly also lets operators duplicate existing menu items and factor in delivery commission to maintain target GP on the delivery channel.

Conclusion: From Order Flow to Margin Control

Connecting Just Eat to Toast POS, whether through the direct partner programme or a middleware platform, removes manual order re-entry and brings delivery sales into a single operational record. That connection forms the first step. The second step, which decides whether the delivery channel is actually profitable, connects Toast sales data to real-time ingredient costs. Without that link, commission erosion and supplier price movements stay hidden until the monthly accounts arrive.

Operators who automate both flows, order routing and cost visibility, gain the control needed to protect margins at scale across multiple sites. Schedule a walkthrough of Jelly’s Toast integration and see how live gross-profit visibility supports better decisions on delivery pricing and menu mix.