Written by: JJ Tan, Founder, Jelly | Last updated: 23 June 2026
Key Takeaways for UK Crunchtime–Toast Setups
- Crunchtime connects to Toast POS via API and shares sales, labour, and inventory data for UK multi-site operators.
- A six-step process covers confirming modules, preparing data, configuring the connector, testing, and going live.
- Common issues include mismatched job codes, revenue centres, and modifier sub-recipes. Fixes require careful remapping and UK checks such as VAT and PAYE alignment.
- Success metrics include zero manual sales entry, daily GP reports, and more accurate labour costs within the first 30 days.
- For real-time margins and automated invoice scanning on top of your Crunchtime–Toast data, book a demo with Jelly.
Six-step Crunchtime–Toast integration process for UK operators
The following six-step checklist covers the full deployment sequence for UK multi-site operators. Work through each step in order, because skipping ahead is the most common cause of failed syncs. The first two steps confirm that you have the right access and data before any technical configuration begins.
Step 1 — Confirm module access on both platforms
Log in to your Crunchtime admin portal and verify that Inventory, Labour, and the relevant POS Connector module are active on your licence. Without these modules enabled, the integration cannot function. Next, confirm in Toast that your plan includes API access and that your UK account has the integration flag enabled, because both are required for the connector to authenticate. After you have confirmed access on both platforms, raise a support ticket with each vendor before changing any configuration settings. This step ensures any account-level flags or permissions are set correctly before technical setup begins.
Step 2 — Prepare your Crunchtime–Toast mapping documents
Export the following from Toast before you start any technical setup: your full menu item list with PLU codes, your employee roster with job codes, and your location IDs for every site. In Crunchtime, pull your ingredient master list, recipe library, and cost centre codes. These documents give you a complete view of what exists in each system, so you can spot gaps and duplicates before you start linking fields. They form the foundation of every mapping decision you will make in steps 3 and 4.
Step 3 — Configure the POS Connector in Crunchtime
Inside Crunchtime, navigate to Administration → Integrations → POS Connector. Select Toast as the POS type, enter your Toast API credentials (Client ID and Client Secret, generated in Toast’s Developer Portal), and input each site’s Toast Location GUID. For UK multi-site operators, register each physical location as a separate entity in Crunchtime’s location hierarchy before you enter credentials. This structure keeps reporting clean by site and prevents data from merging into a single location.
Step 4 — Link menu items, job codes, and cost centres
This step takes the most time and has the greatest impact on accuracy. Link every Toast PLU to its corresponding Crunchtime recipe, because this link controls which ingredient costs are deducted when a dish sells. Next, connect every Toast job code to its Crunchtime labour category so that employee hours land in the correct cost buckets. Finally, align every Toast revenue centre with the right Crunchtime cost centre to ensure sales are attributed to the correct location or department. Errors in any of these links create silent mismatches, where sales post to the wrong recipe or labour lands in the wrong bucket, so a line-by-line review before going live is essential.
Step 5 — Run a parallel test period
Enable the integration in test mode for at least five trading days across all sites. During this period, manually reconcile Crunchtime’s imported sales figures against Toast’s end-of-day reports. Check that employee clock-in data from Toast’s timekeeping module, or from HotSchedules if you use it for scheduling, lands in Crunchtime’s labour actuals without duplication or gaps. Record every discrepancy in a shared log so your team and vendors can resolve issues before the live switch.
Step 6 — Go live and set a monitoring routine
Switch the integration to live mode during a low-volume trading period, such as a Tuesday or Wednesday morning for most UK operators. Assign one person per site to review the Crunchtime daily flash report against Toast’s sales summary every morning for the first two weeks. Set up email alerts in Crunchtime for any sync failures so issues surface within hours rather than days.
Once the integration is live, many operators realise they need real-time margin visibility and automated invoice processing on top of the operational data flow. These capabilities sit outside Crunchtime’s core feature set. Running a multi-site rollout? See how Jelly’s automated invoice scanning and live GP dashboards work alongside your Crunchtime–Toast integration from day one.
Crunchtime Toast integration cost for UK estates
Neither Crunchtime nor Toast publishes a fixed UK list price for the integration connector, so costs are negotiated as part of your enterprise contract with each vendor. Based on typical UK deployments, operators should budget across three categories:
- Crunchtime POS Connector module: Usually included in mid-tier and above Crunchtime licences.
- Toast API access: Standard Toast API access requires an active subscription to Toast Restaurant Management Suite (RMS) Essentials or higher. Lower-tier plans require an upgrade to enable it.
- Implementation and data-mapping services: Professional services or an implementation partner may be required for a full multi-site deployment, covering data mapping, testing, and go-live support.
Implementation timelines vary by operator, but several weeks should be allowed from contract signature to live operation. Larger estate rollouts typically require more time because of the volume of PLU and job-code mapping involved.
Common Crunchtime–Toast sync problems and fixes
| Problem | Likely Cause | Fix | UK-Specific Note |
|---|---|---|---|
| Employee records not syncing | Job codes in Toast do not match Crunchtime labour categories | Re-export Toast job codes and remap in Crunchtime’s Labour module | UK PAYE categories must align with Crunchtime cost centres; check with your payroll provider |
| HotSchedules shifts not appearing in Crunchtime actuals | HotSchedules is connected to Toast but not to Crunchtime’s labour feed | Enable the HotSchedules → Crunchtime direct connector, and do not rely on Toast as the intermediary | UK operators using Rota or Deputy instead of HotSchedules need a custom CSV export workaround |
| Sales figures mismatched between systems | Toast revenue centres not mapped to correct Crunchtime cost centres | Audit the cost-centre mapping table in Crunchtime’s POS Connector settings | VAT-inclusive vs. VAT-exclusive reporting differs; confirm Toast is sending net figures to Crunchtime |
| Inventory variance unexplained after sales import | Modifier-level sales (for example, add-ons and substitutions) not linked to sub-recipes | Build modifier sub-recipes in Crunchtime and map each Toast modifier PLU individually | UK allergen labelling requirements mean modifiers are often more granular than in US deployments |
How UK operators can measure integration success
A functioning Crunchtime–Toast integration should produce measurable operational improvements within the first 30 days. Track the following metrics to confirm the integration is delivering value and to spot issues early.
- Admin hours saved: Manual sales entry into Crunchtime should drop to zero. Benchmark your pre-integration hours and compare weekly.
- Margin reporting speed: Gross profit reports that previously required end-of-week manual compilation should be available daily. Aim for GP visibility within 24 hours of each trading day.
- Invoice discrepancy rate: Cross-reference Crunchtime’s theoretical food cost against actual purchase invoices. A well-mapped integration should reduce unexplained variance.
- Labour cost accuracy: Crunchtime’s scheduled vs actual labour report should align closely with Toast’s clock-in data.
If any of these metrics are not improving after 30 days, return to the data-mapping audit in Step 4. The root cause is almost always a PLU or job-code mismatch that was not caught during the test period.
Next step for real-time margins on top of Crunchtime–Toast
The Crunchtime–Toast integration gives you reliable operational data flow. It does not provide real-time gross-profit visibility at the dish level, automated invoice processing, or live supplier price alerts, which are the tools that turn raw data into margin decisions you can act on today.
Jelly fills that gap. Jelly integrates natively with Toast via a real-time API and pulls item-level sales data the moment a transaction completes. Alongside that real-time sales feed, Jelly automatically scans every line item of every supplier invoice, captured by photo or email, and updates dish costs instantly. By combining live sales data with up-to-the-minute ingredient costs, Jelly calculates dish-level GP in real time instead of waiting for end-of-week reconciliation. When an ingredient price changes, Jelly flags it immediately through its Price Alert feature and gives you the evidence to negotiate credits or switch suppliers before margin damage builds up.
These capabilities, including live sales data, automated invoice scanning, and instant price alerts, combine to produce measurable margin improvements. Operators using Jelly alongside their POS see an average 2-percentage-point gross margin improvement within three months. One operator moved from 65% to 72% GP within 12 weeks on approximately £500,000 in revenue. Populu lifted GP from 68% to 72% across 16 locations.
Jelly’s Flash Report gives you a daily, weekly, or monthly GP view calculated from your invoice costs and Toast sales data, with no accountant, no spreadsheet, and no delay. The Sales Mix report shows which dishes are most popular and most profitable at the same time, so menu engineering decisions are based on data rather than instinct.
Onboarding takes one week. Pricing is a flat £129 per site per month, with no per-user fees and no variable charges. Connecting Toast takes under five minutes inside Jelly’s integrations panel.
Ready to turn your Crunchtime–Toast data into live margin visibility? See the GP dashboard running on your own numbers in a 15-minute walkthrough.
Frequently Asked Questions
Who owns the Crunchtime Toast integration — Crunchtime, Toast, or a third party?
The integration is provided as a partnership between Crunchtime and Toast. For support, raise a ticket with the vendor responsible for the component that is not functioning.
How long does the full integration take to set up for a UK multi-site operator?
Implementation timelines vary. The majority of time is spent on data mapping in Step 4, where you align PLU codes, job codes, and cost centres across every location. Larger estates typically require more time because they have more items and roles to align.
Can the integration be rolled out to new sites after the initial deployment?
Yes. Adding a new site to an existing Crunchtime–Toast integration follows the same process as the original deployment but is faster because your mapping templates already exist. You register the new location in Crunchtime’s location hierarchy, enter the new site’s Toast Location GUID, apply your standard mapping templates, and run a five-day parallel test.
What should UK operators do after the integration is live to protect margins?
The integration provides data flow, and margin protection comes from acting on that data. The immediate priorities are to review Crunchtime’s theoretical vs actual food cost report weekly, investigate any significant variance, and use the labour actuals report to identify scheduling inefficiencies by site. These reviews are reactive and show what happened last week rather than what is happening today. For dish-level GP visibility and automated supplier price monitoring, which Crunchtime does not provide natively, connecting Jelly to your Toast account adds real-time invoice scanning, live dish costing, and Price Alert notifications at the flat monthly rate mentioned earlier. Most operators see meaningful margin improvement within the first three months. The demo mentioned in the Key Takeaways shows how these features work alongside your existing setup.