If you're a Shift4 customer evaluating Eatsy — or vice versa — this article covers exactly what the integration does, what it doesn't do, and how to set it up correctly so you're not chasing phantom bugs three months in.
The five-second summary
Shift4 is your POS. Eatsy is your online ordering platform. They share menu data, order data, and customer data through a native integration. Online orders flow into your existing Shift4 KDS as if they came from your POS. Payments reconcile in your Shift4 reports. You manage one menu, both systems stay in sync.
That's the headline. The details matter.
What the integration actually does
Six concrete things:
1. Menu sync (1-click import)
You connect your Shift4 account once. Eatsy imports your full menu structure — categories, items, modifiers, modifier groups, prices, item images (if you have them in Shift4) — in roughly 90 seconds for menus under 200 items.
After the initial import, you have a choice:
- Shift4 as source of truth. Your Shift4 menu drives everything. Update prices in Shift4; Eatsy syncs within 5 minutes. Add a new item in Shift4; Eatsy picks it up.
- Eatsy as source of truth. You manage menus in Eatsy (because EatsyAI generates bilingual descriptions, which Shift4 doesn't). Eatsy pushes changes to Shift4. Shift4 stays in sync but isn't the master.
Most operators pick option B because EatsyAI's bilingual generation is the value add. But option A is supported for operators who want to keep their existing Shift4 menu workflow.
2. Order routing
Online orders from any Eatsy channel — Branded App, microsite, QR, iPad — route to your existing Shift4 KDS. Your kitchen team doesn't see a separate "Eatsy queue" and a "Shift4 queue." They see one queue: the one they're already using.
The routing respects your Shift4 station rules. If your Shift4 KDS routes hot items to one screen and cold items to another, online orders follow the same rules. Modifiers, special requests, allergen tags — all pass through cleanly.
3. Payment reconciliation
Every online payment processed by Eatsy through Shift4 (or NMI, if that's your gateway) flows into your Shift4 reporting. From Shift4's perspective, the order looks like an "online order" with a clear channel tag (which Eatsy channel it came from). Daily/weekly/monthly reports in Shift4 show your full revenue across in-restaurant + online without manual reconciliation.
This matters at month-end close, when you need a single source of truth for revenue, sales tax, and tip distribution.
4. Customer data sync
Customers who order direct via Eatsy (with a phone or email) get synced into Shift4's customer database. If you're running loyalty in Eatsy, the customer's loyalty status follows them — so if they walk into your restaurant and pay via Shift4 SkyTab at the counter, the cashier sees their tier.
This is the bidirectional sync most "integrations" promise but few deliver. Eatsy's customer database and Shift4's customer database stay reconciled in near-real-time.
5. Inventory and item availability
If Shift4 marks an item as "86'd" (out of stock), Eatsy updates within 60 seconds and pulls the item from your microsite, app, QR, and iPad menus. Customer trying to order the 86'd item sees "currently unavailable" and is prompted to pick something else.
Same in reverse: if you 86 an item from Eatsy's Menu management during a rush, Shift4 reflects it.
6. Tip and refund handling
Tips collected through Eatsy checkout flow into your Shift4 tip pool. If you process a refund in Eatsy, Shift4 records the refund. If you process a refund in Shift4 for an Eatsy order, Eatsy reconciles. No tip-distribution surprises at end of shift.
What the integration doesn't do (yet)
Honesty matters. Here's what's NOT in the integration today:
- Reservation sync. Shift4 has a reservation feature; Eatsy doesn't currently integrate with it. (Eatsy doesn't currently support reservations as a feature, period.)
- Loyalty program merge. If you're running a Shift4 loyalty program separately from Eatsy loyalty, the two are independent. Eatsy loyalty is more powerful (bilingual, WhatsApp triggers, etc.) so most operators move loyalty entirely to Eatsy and turn off Shift4's. We don't currently bidirectionally merge if you want to run both.
- Gift card sync. Shift4 gift cards work in your restaurant; they don't currently work in Eatsy online checkout. Online customers can't use Shift4-issued gift cards. (We're working on this.)
- Catering-specific Shift4 features. If you use Shift4's catering module, Eatsy's Catering module runs in parallel rather than syncing. Eatsy's catering is generally more flexible for the use cases we cover (Hispanic operator party catering), so most operators choose one.
If any of these are deal-breakers, raise them in your demo. We'll talk through workarounds or roadmap timing.
Setup: how to do it right the first time
The integration takes 30-60 minutes to set up properly. Here's the order:
Step 1: Connect your Shift4 account
In your Eatsy admin (admin.eatsyorders.com), go to Account → Settings → Integrations → Shift4. Click "Connect Shift4." You'll be redirected to Shift4's OAuth flow. Sign in with your Shift4 credentials. Approve the permissions Eatsy requests (read menu, write orders, read/write customers, read/write payments).
Once connected, Eatsy verifies the connection and lists your Shift4 locations.
Step 2: Map your Shift4 locations to Eatsy locations
If you have multiple locations, you map each Shift4 location to an Eatsy location. For new Eatsy customers, this happens during onboarding — your sales rep or onboarding manager handles it. For self-serve operators, the mapping is in Location management.
This is a one-time setup. After mapping, every online order knows which physical location it belongs to, which kitchen to route to, and which delivery zone applies.
Step 3: Choose source of truth
Account → Settings → Menu Source of Truth. Pick:
- Shift4 (Eatsy syncs from Shift4, you continue managing in Shift4)
- Eatsy (Eatsy is master, syncs to Shift4)
Default is Eatsy because of EatsyAI's bilingual menu generation. Most operators stick with the default.
Step 4: Run the menu import
Open Menu management → Import from Shift4. Click "Import."
Eatsy pulls your full menu structure. Items appear in your Eatsy admin in their Shift4 categories, with original Shift4 names. EatsyAI runs in the background to generate bilingual descriptions for items that don't have them.
Initial import takes 60-120 seconds for menus up to 200 items. Larger menus take longer.
Step 5: Review and clean up
This is the most important step and the one operators skip. Review every item that EatsyAI flagged with "low confidence" — usually because the original Shift4 entry was abbreviated, ambiguous, or had unusual modifier groupings.
For each flagged item:
- Confirm or edit the EN description
- Confirm or edit the ES description
- Confirm or set the allergen tags
- Confirm or adjust modifier groups
Total time: roughly 1-2 minutes per flagged item, typically 10-30 items flagged out of 100+.
Step 6: Configure routing rules
If your Shift4 KDS has multiple stations (kitchen, expo, bar), confirm Eatsy is routing online orders to the correct stations. Account → Settings → KDS Routing.
Default mapping: Eatsy items inherit their Shift4 station assignment. Override per item if needed (for example, if all online orders should go to a specific "online" station regardless of item type).
Step 7: Test end-to-end
Place a real order through your microsite (or QR or app). Confirm:
- Order appears on Shift4 KDS within 5 seconds
- Items show with correct modifiers
- Customer name and contact info show
- Order routing matches your station rules
- When kitchen marks order ready, Eatsy customer gets notified
- Payment shows in Shift4 reports
If any of these fail, review the integration health page (Account → Settings → Integrations → Shift4 → Health). It surfaces specific connection issues.
Step 8: Train your team
The integration means your kitchen sees one queue. Your team should know:
- How online orders look (vs. in-restaurant orders) — channel tag visible
- How to identify modifiers and special requests
- How to mark online orders ready (triggers customer notification)
- How to handle 86'd items (mark in Eatsy or Shift4 — it syncs)
Most operators do a 30-minute training session with kitchen + cashier teams.
Common integration issues and fixes
"My menu didn't fully import"
Usually one of two causes:
- Items were marked "inactive" in Shift4. Eatsy doesn't import inactive items. Activate them in Shift4, re-run import.
- Modifier groups had unusual structure. Eatsy's import handles standard Shift4 modifier groups well; non-standard ones may need manual mapping. Contact support — usually fixed in under 24 hours.
"Online orders aren't showing on my KDS"
Three things to check:
- Account → Settings → Integrations → Shift4 → Health. Connection should be green.
- Account → Settings → KDS Routing. Confirm the station is mapped.
- Shift4 KDS itself — are online orders filtered out of the view? Check Shift4 station settings.
"My menu in Eatsy and my menu in Shift4 are out of sync"
Sync runs every 5 minutes by default. If you don't want to wait, force a manual sync from Menu management → Sync Now.
If a specific item is consistently out of sync, contact support with the item ID. Usually a one-time data fix.
"Customer paid online but Shift4 reports show no payment"
Reconciliation runs at end of day (configurable). If you check mid-day and don't see online payments yet, that's expected. End-of-day report should show everything.
If end-of-day report still shows discrepancies, escalate. We're tight on this number — small discrepancies should never persist.
What this looks like at scale
A 5-location QSR running Shift4 + Eatsy:
- One Eatsy login switches between all 5 locations
- Each location's Shift4 KDS receives its own online orders, routed to the correct stations
- One Eatsy menu propagates to all 5 Shift4 locations (with optional per-location overrides)
- One owner Shift4 reporting account shows consolidated revenue across in-restaurant + online + delivery
The operational load doesn't grow proportionally with location count. Adding a 6th location adds 30 minutes of mapping setup, not a day of integration work.
Should you switch to Shift4 if you're not on it?
Common question. Honest answer:
If you're on Toast and considering switching to Shift4 just for the Eatsy integration: Probably not. Toast switching costs are real (hardware, retraining, payment migration). Eatsy works without Shift4 — you'd run Eatsy on your Toast operation with orders flowing into a separate Order Management dashboard (the kitchen-tablet product) or printing to a kitchen printer. You lose the tight POS integration but gain the rest.
If you're on a generic POS (Square, Clover, generic terminals) and considering Shift4: Maybe. Shift4 is generally a stronger restaurant POS than Square or Clover, especially for full-service or multi-location. The Eatsy integration is a bonus on top of that, not the only reason to switch.
If you're starting from scratch: Shift4 is a strong default for a restaurant POS, and the Eatsy integration is a multiplier on top of it.
The integration is a feature, not a forcing function. Don't let it dictate your POS strategy.
Payments work with Shift4 or NMI
Eatsy's payment layer supports both Shift4 and NMI as gateways. The Shift4 POS integration described here is independent of the payment gateway choice — most Shift4 POS customers also use Shift4 Payments, but you can route payments through NMI if your existing merchant relationship is there.
Frequently Asked Questions
Does the integration cost extra?
No. The Shift4 integration is included in both the Microsite plan ($89.99/mo) and the Branded App plan ($149.99/mo). You don't pay Eatsy extra for it; you don't pay Shift4 extra for it.
Do I need a specific Shift4 plan?
The integration works with Shift4 SkyTab (their flagship POS) and most Shift4 enterprise configurations. If you're on a legacy Shift4 product, talk to support — there may be a migration step required.
Can I disconnect the integration later?
Yes. From Account → Settings → Integrations → Shift4 → Disconnect. Your menu stays in Eatsy (we don't delete data on disconnect). Shift4 keeps its menu independently. From the disconnect point forward, the two stop syncing.
What happens if Shift4 has an outage?
Eatsy keeps accepting online orders (they queue locally). When Shift4 comes back online, queued orders flow through. Customer experience isn't affected.
Is there an API I can use instead of the native integration?
Yes — Eatsy has a public API (Phase 2; documentation in /resources/reference/api-overview). The native Shift4 integration covers 95% of use cases though, so the API is mostly for unusual edge cases or third-party integrations.