Supported POS Integrations
Eatsy is online ordering software, not a POS: we sit alongside your point-of-sale system and route online orders into your existing kitchen workflow. This page lists exactly which POS systems we integrate with today, and at what depth.
Integration tiers
We classify every POS integration into one of four tiers, based on what’s actually wired up in production:
- Native: automatic menu sync (items, prices, modifiers, and availability), one way from the POS, with no manual re-import.
- Order routing only: online orders push to the POS as tickets, but the menu lives in Eatsy (one-way).
- Manual export: daily CSV exports of orders and sales for accounting reconciliation.
- Not supported: operate Eatsy alongside the POS as parallel systems (still works, just less tight).
Supported POS systems
| POS System | Integration tier | Menu sync | Order routing | Payment recon | Notes |
|---|---|---|---|---|---|
| Shift4 / SkyTab | Native | 1-click import + ongoing sync | No | No | Flagship menu integration. 90-second menu import. |
| Toast | Order routing only | Manual import (one-time) | Toast Hub | Manual CSV | Migration from Toast supported; full native integration on the roadmap. |
| Square for Restaurants | Order routing only | Manual import | Square Dashboard | Manual CSV | Common for sub-3-location operators. |
| Clover | Manual export | Manual import | Eatsy dashboard only | Manual CSV | Order routing planned for Q3 2026. |
| Lightspeed Restaurant | Manual export | Manual import | No | Manual CSV | Available on request. |
| Aloha NCR | Not supported | – | – | – | Run Eatsy as a parallel system. |
| Restaurant365 | Not supported | – | – | – | Run Eatsy as a parallel system. |
| Other / custom POS | Manual export | Manual import | No | CSV | We can usually accommodate via CSV import on request. |
What “native” actually means
For Shift4 specifically:
- Menu sync: when you update an item in Shift4 (a price change, 86’ing an item, a new modifier), the change reflects in Eatsy in under 60 seconds. No manual re-importing.
- It’s one-way: Shift4 leads. Edit there and Eatsy updates; there’s no way to edit the menu in Eatsy and have it reflect in Shift4.
- It doesn’t send orders to Shift4 or your KDS: Online Ordering and Branded App orders are handled directly in Eatsy. Your kitchen doesn’t see a Shift4 ticket for an online order.
- It doesn’t sync customers or loyalty: Eatsy’s customer database and loyalty program are its own, independent of Shift4’s.
If you’re on Shift4 today, your migration to Eatsy is the lowest-friction path we offer. Most operators are live in 5–7 days.
Payment processing
For online orders processed through Eatsy (Online Ordering, Branded App, QR ordering), payments are handled by Shift4 or NMI, depending on your account configuration. Both are PCI-DSS compliant and settle directly to your merchant bank account: there is no intermediate Eatsy-controlled wallet.
If your POS already processes card payments in-restaurant, those flows stay untouched. Eatsy only processes the online ordering channels.
Roadmap (subject to change)
- Q3 2026: Native Toast integration (full menu sync + payment reconciliation)
- Q4 2026: Native Square for Restaurants integration
- Q1 2027: Native Clover integration
- 2027+: Lightspeed, Aloha NCR, and Restaurant365 (driven by customer demand)
If your POS isn’t listed and you’re evaluating Eatsy, bring it up on your demo. We can almost always make it work via CSV export at minimum, and customer demand drives our integration roadmap.