Restaurant365 Toast POS Integration: UK GP & Live Margins

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

Key Takeaways for UK Toast + Restaurant365 Users

• The native Restaurant365 and Toast POS integration transfers sales, labour and payment data but does not calculate live dish-level gross profit when ingredient costs change.
• UK operators face daily margin pressure because supplier price increases do not automatically update recipe costs or GP percentages in Restaurant365.
• Menu mapping, recipe linking and schedule sync issues create ongoing admin overhead and reconciliation problems for multi-site operators.
• Jelly adds real-time dish costing, automated invoice scanning and price alerts that update GP the moment supplier invoices arrive.
• Operators can see live margins alongside their existing Toast and Restaurant365 setup in a working demo.

How Restaurant365 Integrates with Toast

Restaurant365 connects directly to Toast. Toast’s Restaurant365 integration page confirms a live data connection between the two platforms. The integration transfers sales, labour and payment data into Restaurant365’s accounting and operations modules.

The data flow covers what accountants need for period-end reporting. It does not cover what a head chef or operations manager needs at 11 am on a Tuesday. They need a live gross profit percentage per dish that already reflects that morning’s supplier delivery and its updated ingredient costs. Recipe-level costing inside Restaurant365 depends on item costing, which is automatically calculated from transactions or can be manually maintained.

When a supplier raises the price of a key ingredient mid-week, that change does not automatically flow through to dish-level GP. The figures only update after the item costing is refreshed and the next sync cycle completes. For multi-site UK operators running on thin margins, that lag creates a structural blind spot.

Step-by-Step: Syncing Toast POS with Restaurant365

The seven steps below reflect the standard setup sequence. Confirm current permissions and field mappings with your Toast account manager and Restaurant365 implementation contact before you begin, because configuration options change over time.

1. Confirm admin access on both platforms. You need owner-level credentials in Toast and an admin role in Restaurant365. Without both, the OAuth handshake fails at step four.
2. Audit your Toast menu structure. Every menu item, modifier group and combo must follow a consistent naming convention before mapping. Inconsistent names create duplicate GL accounts in Restaurant365 and corrupt your sales mix reports.
3. Map Toast revenue centres to Restaurant365 locations. Each Toast location ID must correspond to a single Restaurant365 location entity. Multi-site operators should complete this mapping in a spreadsheet before changing anything in either system.
4. Connect the integration via the Restaurant365 integration hub. Navigate to Settings, then Integrations, then POS, then Toast. Enter your Toast API credentials and authorise the connection. Restaurant365 pulls a test transaction to confirm the link.
5. Map menu items to Restaurant365 GL accounts. Food, beverage and modifier categories each need a corresponding GL code. Errors here cause revenue to post to the wrong account and distort your P&L from day one.
6. Choose your sync frequency: daily batch or near-real-time. Daily batch, typically a 3 am close, is simpler to maintain and works for period-end reporting. Near-real-time sync reduces lag for labour and sales dashboards but increases API call volume and requires monitoring. For dish-level GP visibility, neither option is sufficient on its own because ingredient cost changes are not part of this sync.
7. Run a parallel period before going live. Operate both your old process and the new integration for one full trading week. Compare sales totals, labour figures and modifier revenue line by line before you decommission manual exports.

Restaurant365 Toast POS Integration Costs for UK Operators

Restaurant365 uses a subscription model with tiers based on the modules you activate, such as accounting, operations and payroll. Toast charges separately for POS hardware, software and any add-on modules. The integration sits inside Restaurant365’s platform at no extra software fee.

For UK multi-site operators, the less visible costs come from time and administration. Initial menu mapping across three or more sites can take a finance manager or operations lead several days. Ongoing maintenance adds recurring overhead. Teams must update cost cards when supplier prices change, reconcile modifier mismatches and troubleshoot failed sync cycles. These tasks rarely appear in a vendor’s cost estimate. UK operators also need to confirm data-residency arrangements with both vendors, because default storage locations may not align with UK GDPR requirements post-2021.

Common Toast Integration Support Issues

Most friction points reported by operators connecting POS systems to back-office platforms fall into two categories. The first involves menu-item-to-recipe linking. The second involves schedule sync failures.

Menu-item-to-recipe linking: Restaurant365 requires each Toast menu item to be manually linked to a recipe or cost card inside Restaurant365. If a menu item sells before its recipe is linked, the sale posts with no cost attached. That gap produces a falsely inflated GP figure. The problem is common after menu changes or seasonal updates, when new items go live on Toast before the back-office team has built the corresponding recipe.

Schedule sync issues: Labour punch data from Toast can fail to sync when employee IDs do not match between the two systems. This typically appears after staff onboarding or payroll system changes. The fix requires reconciling employee records in both platforms and then re-running the sync.

For both issue types, Restaurant365’s customer support centre and Toast’s support portal provide documented resolution paths. Resolution times vary by case.

Readiness Checklist Before You Connect Toast and Restaurant365

Strong preparation reduces integration headaches. Confirm the following points before you begin the connection.

• You hold admin credentials for both your Toast account and Restaurant365 instance.
• Your Toast menu items use consistent, unambiguous naming across all locations.
• Every menu item has a corresponding recipe or cost card built, or scheduled, in Restaurant365.
• Your employee records are synchronised between Toast and your payroll or HR system.
• You have confirmed data-residency and UK GDPR compliance with both vendors.
• You have allocated internal resource, such as a finance manager or operations lead, for the parallel-run period.

If two or more of these remain unresolved, fix them before you connect the integration. Setup on incomplete data creates reconciliation problems that grow over time.

How Jelly Sits Between Toast and Restaurant365

The diagram below shows how data moves across the three systems when Jelly sits alongside the native Toast and Restaurant365 connection.

 Supplier invoices → [Jelly: automated line-item scan] → live ingredient costs ↓ Toast POS (item-level sales, real-time API) → [Jelly: dish-to-ingredient mapping] → live dish GP % ↓ Restaurant365 (daily/batch sales + labour sync) → period-end P&L and payroll ↓ Jelly → [one-click push] → Xero (digitised invoices, 90% bookkeeping time reduction) 

Jelly does not replace Restaurant365 or Toast. It fills the gap between them. The moment a supplier delivers an invoice with a new price, Jelly scans it, updates the ingredient cost and recalculates every dish GP that uses that ingredient. Restaurant365 continues to handle accounting and labour. Toast continues to handle transactions. Jelly makes the margin visible in real time.

See the Jelly + Toast architecture running live with your menu data.

Frequently Asked Questions

Does adding Jelly require replacing Restaurant365 or Toast?

No. Jelly connects to Toast through a real-time API and sits alongside Restaurant365 rather than replacing either system. Restaurant365 continues to handle your accounting, labour and period-end reporting. Toast continues to process transactions. Jelly adds the layer that neither system provides natively, which is live dish-level gross profit updated every time a supplier invoice arrives. Operators typically run all three systems simultaneously, with Jelly also pushing digitised invoices into Xero for bookkeeping.

How long does it take to see value from Jelly after connecting Toast?

Connecting Toast to Jelly takes under five minutes. Open Jelly, click Integrations, sign in to Toast, grant permissions and select which categories to sync. Jelly then surfaces item-level sales data from that point forward. Invoice scanning begins generating price alerts and updated dish costs within 24 hours of the first invoices being submitted. Operators typically see meaningful GP data within the first week. Jelly’s customer data shows an average GP improvement of two percentage points within the first three months.

Who owns the Jelly integration day-to-day, the chef or the finance team?

Both teams can use it independently. The head chef uses the Kitchen section to build and cost recipes, review price alerts and monitor dish-level margins. The finance manager or operations director uses the Flash Report and Insights Dashboard for a top-down view of GP, spending by supplier and invoice reconciliation. Because Jelly is automated, neither role depends on the other to keep data current. Management can view the same figures the kitchen team sees, which removes the friction that arises when chefs and finance teams work from different data sources.

What happens to dish costing when a supplier raises prices mid-week?

When a supplier delivers an invoice with a new price, Jelly scans every line item automatically. The updated ingredient cost flows immediately into every recipe that uses that ingredient, and the dish GP percentage recalculates in real time. A red margin indicator appears on any dish whose GP has dropped below target. The Price Alert feature simultaneously flags the specific ingredient, the percentage change and the supplier responsible. The head chef then has the data needed to negotiate a credit note or switch supplier before the week’s trading is complete. This behaviour closes the core gap in the native Toast and Restaurant365 integration, where ingredient cost changes are not part of the sync.

Conclusion: Filling the Live GP Gap for UK Operators

The native Restaurant365 and Toast POS integration gives a solid foundation for restaurant accounting and labour reporting. It moves the data that accountants and payroll teams need. It does not move the data that operations managers and head chefs need to protect margins in real time. Dish-level GP, live ingredient costs and supplier price alerts sit outside the scope of what either platform delivers natively.

Jelly fills that gap at £129 per month per location, with no variable user fees, UK data residency, a quick Toast connection and automated invoice scanning that starts generating value within 24 hours. The two-point GP improvement typically achieved within three months comes without replacing any system already in place.

See how Jelly delivers live margins alongside your Toast and Restaurant365 setup.