Toast POS and Shopify Integration: A Complete Guide

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

Key takeaways for Toast and Shopify operators

• Toast offers a native integration with Shopify Retail, but connecting Toast POS to Shopify e-commerce still requires a third-party connector or a custom API build.
• Third-party tools like Itembase provide the most practical route for most UK operators, while custom API builds suit complex or multi-site requirements.
• Integrations often create fragmented customer data and loyalty programme issues that need separate workarounds such as Zapier or unified CRM layers.
• Connecting Toast and Shopify solves inventory routing but does not deliver live margin visibility on individual dishes and retail products.
• Jelly layers directly onto Toast to deliver real-time gross profit reporting from day one, book a demo to see how it works.

How Toast POS integrates with Shopify

Toast offers a native integration with Shopify for Toast Retail that supports item linking and inventory quantity syncing. Toast’s own retail module handles in-venue product sales, but it operates as a separate data environment from Shopify’s e-commerce layer. Connecting the two environments requires either a third-party integration platform or a custom API build. Two routes are in active use among UK operators in 2026.

Route 1: Third-party connector (for example, Itembase)

1. Create accounts on both Toast and Shopify with admin-level credentials on each platform.
2. Sign up for a connector service such as Itembase and authenticate both platforms within the connector dashboard.
3. Map your Toast product catalogue to the corresponding Shopify SKUs. Automated mapping tools within the connector handle most of this step.
4. Configure sync direction and decide whether inventory counts flow from Toast to Shopify, Shopify to Toast, or in both directions.
5. Set sync frequency using real-time webhooks or scheduled batch intervals, then run a test transaction to confirm stock levels update correctly on both sides.
6. Enable order routing rules so that Shopify online orders that require fulfilment from a physical location trigger the correct Toast location record.

Route 2: Custom API build

1. Obtain API credentials from the Toast Developer Portal and the Shopify Admin API.
2. Scope the data objects to sync, including menu items, modifiers, inventory quantities, and order records.
3. Build or commission middleware that listens to Toast webhooks and writes changes to Shopify via REST or GraphQL calls, and vice versa.
4. Implement error handling and retry logic for failed webhook deliveries, because missing this step often causes silent stock discrepancies.
5. Deploy to a hosted environment, configure monitoring alerts, and run end-to-end testing across all product categories before going live.

Troubleshooting the most frequent failure points

• Admin access gaps: The integration stalls when the authenticating user lacks full admin rights on either platform. Confirm permissions before starting.
• SKU mismatch: Toast and Shopify use different product identifier formats. Any discrepancy between the two catalogues breaks automated mapping and requires manual correction.
• Modifier complexity: Toast modifiers such as size or add-ons do not map cleanly to Shopify variants. Custom API builds must handle this explicitly, and connector tools vary in how well they manage it.
• Webhook timeouts: High-volume periods can cause Toast webhooks to time out before Shopify acknowledges receipt, which results in inventory counts drifting out of sync.
• Multi-location routing: Operators with more than one Toast location must configure location-specific rules. A blanket sync aggregates stock incorrectly.

Toast POS Shopify integration cost comparison

The table below compares the three integration routes on pricing, SKU handling, and customer-data capability using 2026 figures. Use this comparison to match each route to your catalogue size, data needs, and budget. All costs are indicative, so confirm current pricing directly with each provider before committing.

Route	Setup cost	Ongoing monthly cost	SKU limit	Customer data handling
Itembase connector	Varies depending on catalogue size and onboarding support	Varies depending on order volume and sync frequency	Handles large catalogues, pricing tiers may apply at higher thresholds	Order-level customer data can be passed, loyalty programme sync may require additional configuration
Custom API build	£3,000–£15,000+ depending on complexity and developer rates	Varies for hosting, maintenance, and monitoring	No hard SKU limit, performance depends on infrastructure provisioned	Can provide full control over data mapping, including customer profiles and loyalty fields, if built to spec

The data above confirms the recommendation from the key takeaways. Custom API builds are justified only where catalogue complexity, multi-site scale, or bespoke loyalty requirements make a connector insufficient.

Explore a Jelly walkthrough to see how it layers onto your existing Toast setup and delivers live margin data from day one.

What Reddit reveals about Toast POS Shopify integration

Threads across r/shopify and r/restaurantowners highlight two recurring pain points that vendor documentation consistently underplays, customer data fragmentation and loyalty programme incompatibility.

The core complaint is that a Toast–Shopify integration creates two separate customer records for the same guest, one in Toast’s guest profile system and one in Shopify’s customer database, with no automatic reconciliation. Operators running loyalty schemes find that points earned in-venue via Toast do not carry over to Shopify purchases, and the reverse also holds true, which frustrates repeat customers and undermines retention programmes.

Workarounds for contact syncing and loyalty

1. Email as the unifying key: Standardise on email address as the primary customer identifier in both Toast and Shopify. Train front-of-house staff to collect email at point of sale consistently. This approach allows manual or scripted deduplication runs to merge records periodically.
2. Zapier or Make.com middleware: Use a lightweight automation tool to watch for new Toast guest records and create or update matching Shopify customer profiles in near real time. This approach avoids a full custom API build and costs significantly less.
3. Third-party loyalty platform: Introduce a loyalty tool such as LoyaltyLion or Smile.io that integrates independently with both Toast and Shopify, treating each as a sales channel rather than the source of loyalty truth.
4. Unified CRM layer: For multi-site operators, a CRM such as HubSpot or Klaviyo can ingest customer data from both platforms via API and serve as the single customer record, with loyalty logic managed centrally.

How to layer profitability reporting on Toast and Shopify data

The workarounds above address customer data fragmentation, but they do not answer the core financial question every operator faces once the integration is live. Operators still need to know whether the products and dishes being sold are actually profitable, and by how much. Getting Toast and Shopify talking to each other solves an inventory and order-routing problem, not a margin problem. Jelly answers the margin question by pulling item-level sales data directly from Toast in real time and mapping it against live ingredient costs from scanned supplier invoices.

Steps to connect Jelly after the Toast and Shopify integration is live

1. Open Jelly and navigate to the Integrations section, then click the Toast integration tile.
2. Sign in to Toast with admin credentials and grant Jelly the required read permissions for item-level sales data.
3. Select which Toast categories, such as food, beverages, and retail, to sync into Jelly. Categories not selected are excluded, which keeps the data environment clean.
4. Map each Toast menu item to the corresponding Jelly dish or product. Only items sold since the integration connected appear in the mapping queue, which removes legacy menu clutter.
5. Upload supplier invoices to Jelly via email forwarding or photo capture. Jelly scans every line item, including quantity, SKU, price, and tax, automatically.
6. Within 24 hours of the first invoices processing, Jelly’s Flash Report delivers a gross profit view that combines Toast sales data with live ingredient costs. Price Alert notifications flag any supplier price movement the moment a new invoice is scanned.

Onboarding typically takes under one week. Jelly charges a flat £129 per location per month with no per-user fees. Operators consistently see gross margin improvements of around two percentage points within three months, with one customer moving from 65% to 72% GP on approximately £500,000 in revenue within 12 weeks.

See live Toast margin data in a demo and watch how quickly Jelly surfaces the numbers you need.

Measuring success after go-live

Three metrics define whether a Toast–Shopify integration with Jelly layered on top is delivering value.

Reduced admin hours: The integration removes manual stock reconciliation between in-venue and online sales. Jelly removes the additional burden of manual invoice entry and spreadsheet-based dish costing. Combined, operators can recover significant admin time each month.

Accurate margin visibility: Success means knowing the gross profit margin on every dish and retail product in real time, not at month-end when the accountant files a report. Jelly’s live dish costing updates automatically each time a new supplier invoice is scanned, so margin data is never more than one delivery cycle out of date.

Faster supplier negotiations: Jelly’s Price Alert feature flags every ingredient price movement, up or down, with the supplier name, SKU, and percentage change. Operators use this data to challenge unjustified increases, request credit notes, and switch suppliers with evidence rather than instinct. Amber restaurant in East London saves £3,000–£4,000 per month through this process alone.

Frequently asked questions about Toast and Shopify

Who owns the sales and customer data generated through a Toast–Shopify integration?

Both Toast and Shopify treat the merchant as the data owner for transaction and customer records generated on their respective platforms. When a third-party connector or custom API moves data between the two systems, the merchant retains ownership of that data under the terms of their agreements with each platform. UK operators should review their data processing agreements with any connector tool to confirm GDPR compliance, particularly around customer personal data transferred between systems.

How long does a Toast–Shopify integration typically take to go live?

A connector-based integration using a tool like Itembase can be live within a few business days, assuming admin credentials are available and the product catalogue is clean. Custom API builds typically require several weeks depending on scope and developer availability. Adding Jelly on top of an existing Toast integration takes under five minutes to connect and under one week to reach full operational value once invoices begin flowing.

Can a Toast–Shopify integration scale across multiple sites?

Multi-site setups can scale effectively when location mapping is configured correctly in both Toast and the connector or API layer. Each Toast location must be linked to the correct Shopify fulfilment location or warehouse record. Connector tools handle this at the configuration stage, and custom builds must implement it in the routing logic. Jelly supports multi-site rollouts natively, and each location runs as a separate Jelly instance at the same flat monthly rate, with the same five-minute POS connection process applied per site.

What happens when the product catalogue grows beyond 2,000 SKUs?

Some connector tools apply higher pricing tiers or impose rate limits at higher SKU volumes. Operators approaching higher volumes should audit their catalogue for inactive or seasonal items before the integration goes live, and confirm with their chosen connector provider what the pricing and performance implications are at their projected scale. Custom API builds have no hard SKU limit but require infrastructure scaled to the catalogue size.

Conclusion, and where Jelly fits

A Toast POS Shopify integration is a viable solution for UK restaurants, pubs, and boutique hotels that need to synchronise in-venue and online retail inventory. The connector route via tools like Itembase is the practical starting point for most operators, while custom API builds suit those with complex catalogues or bespoke loyalty requirements. The integration solves a data-routing problem and still leaves the margin problem unsolved.

Jelly fills that gap. By pulling item-level sales data directly from Toast and combining it with live ingredient costs from scanned invoices, Jelly delivers the gross profit visibility that no POS-to-e-commerce sync can provide on its own. Flat pricing at £129 per location, onboarding in under a week, and a consistent two-percentage-point GP improvement within three months make Jelly the logical next step after the integration is live.

Find out how Jelly turns Toast sales into live margin intelligence, book your demo now.