Home Features Pricing Integrations Blog Contact
Sign in Start free trial →
Real connections

Integrations built in,
not bolted on

Every integration listed here is live in the ZayPOS codebase — doing real work every day. No marketplace plugins, no third-party connectors. These are core.

💳 Payments 📧 Email (Brevo) 💬 SMS (Twilio) 🤖 AI (OpenAI) 🖨️ Hardware ⏱️ Schedulers
💳
Payment Processing
Clover OAuth · Smart routing across 4 providers
Clover
Card Payments · OAuth 2.0
🔐 OAuth 2.0 Connected
Clover is the primary card payment integration, connected via full OAuth 2.0. Staff authorise the connection once through the Clover login flow — no API keys to copy and paste. ZayPOS also syncs the Clover product catalogue bidirectionally, keeping your menu consistent across both systems.
  • OAuth 2.0 authorisation — staff connect via Clover login, no manual keys
  • Bidirectional product catalogue sync — Clover ↔ ZayPOS
  • Card payment requests sent directly to connected Clover terminal
  • Selectable as default payment merchant per location
  • Transaction confirmation and receipt data returned to ZayPOS
  • Refund processing routed back through original Clover transaction
Technical
OAuth 2.0 REST API Product sync Webhook callbacks
Smart Payment Routing
Multi-provider · Per-location config
✓ Live
ZayPOS doesn't lock you to one payment provider. The routing engine lets you configure which provider handles card transactions at each location, and switch instantly from Settings — no downtime, no re-integration.
  • Supported providers: Clover, SumUp, Dojo, Square
  • Default merchant configurable per location independently
  • Switch active merchant from Settings without any downtime
  • Split payments: route cash + card portions simultaneously
  • Refunds automatically routed back through original merchant
  • Per-merchant transaction volume tracked in payment analytics
Technical
Multi-merchant Per-location config Split payment routing Refund routing
📧
Email — Brevo
6 transactional email types · Event-triggered
Brevo
Transactional Email · formerly Sendinblue
✓ Live
All transactional emails in ZayPOS are sent via Brevo. Six distinct email types fire automatically based on events across the platform — from a completed sale to a missed food safety checklist. Recipients are configurable per organisation.
🧾
Digital Receipts
Sent to customers after payment when an email address is provided at checkout.
💰
Payroll Reports
Monthly payroll summaries auto-sent to all configured payroll email recipients.
📦
Low Stock Alerts
Triggered the moment any product drops below its configured par level.
📋
Missed Checklist Alerts
Emailed to managers when a food safety checklist passes its deadline uncompleted.
Review Requests
Post-order review invitations sent automatically to takeaway and delivery customers.
🔐
Account & Auth
Welcome emails, password resets, email verification, and trial expiry notices.
Technical
Brevo SMTP API Template engine Event-triggered Configurable recipients 6 email types
💬
SMS — Twilio
Opt-out compliance built in · PECR compliant
Twilio
SMS · With opt-out handling via webhook
✓ Live
Twilio powers all outbound SMS — safety reminders, customer review requests, and staff notifications. Opt-out is handled properly: when a recipient replies STOP, Twilio fires a webhook to ZayPOS which records the opt-out in the database and permanently suppresses that number from all future sends.
SMS use cases
  • Food safety checklist reminders to on-shift staff
  • Temperature probe reminders at configurable intervals
  • Missed checklist alerts to on-duty manager
  • Customer review requests after takeaway orders
  • Staff clock-in confirmation and shift reminders
Opt-out compliance
  • STOP keyword handled via Twilio inbound webhook
  • Opt-out recorded per number in the database immediately
  • Opted-out numbers suppressed from all future SMS sends
  • Opt-out status visible in the customer profile
  • Compliant with UK PECR messaging regulations
Technical
Twilio REST API Inbound webhook (STOP) PECR compliant Per-number opt-out DB Suppression list
🤖
AI — OpenAI
3 use cases · GPT-4o Vision + GPT-4o + GPT-3.5 Turbo
Invoice Processing
GPT-4o Vision
GPT-4o · Vision API
Staff photograph or upload a supplier invoice. GPT-4o Vision reads the image or PDF, extracts every line item — name, quantity, unit price, supplier — and updates stock levels automatically on confirmation.
  • Accepts JPEG, PNG photo or PDF upload
  • Extracts line items, quantities, unit prices
  • Maps to existing products in catalogue
  • Updates stock levels on staff confirmation
  • Full invoice audit trail retained
Model
gpt-4oVision APIJSON mode
Meal Deal Suggestions
GPT-4o · Sales data context
GPT-4o · Structured output
ZayPOS feeds your top-selling product combinations into GPT-4o, which analyses what sells together and suggests optimal meal deal bundles with recommended pricing — giving you data-driven promotions automatically.
  • Analyses real sales history from your business
  • Identifies best-performing product combinations
  • Suggests bundle name, contents, and pricing
  • One click to create the suggested deal
  • Re-runs automatically as sales data grows
Model
gpt-4oChat completionsStructured output
Upsell Recommendations
GPT-3.5 Turbo · Real-time at till
GPT-3.5 Turbo · Low latency
At the point of ordering, GPT-3.5 Turbo analyses the current cart contents and individual customer order history to suggest relevant add-ons — shown as prompts to staff before they complete the sale.
  • Cart-aware — analyses current order in real time
  • Uses individual customer purchase history
  • Suggestions shown as prompts on order screen
  • GPT-3.5 Turbo chosen for low latency at the till
  • Tracks add-on attach rate in analytics
Model
gpt-3.5-turboLow latencyChat completions
🖨️
Hardware — ESC/POS Receipt Printing
Network thermal printers · No drivers needed
ESC/POS Network Printing
Thermal receipt printers · TCP/IP socket connection
✓ Live
ZayPOS connects to any network thermal receipt printer that speaks ESC/POS — the industry standard protocol used by Epson, Star Micronics, and most modern receipt printers. No drivers, no software installation. Configure by IP address and port number, run a test print, and you're done.
  • Connects via TCP/IP — IP address and port
  • No printer drivers or software needed
  • Test print button in Settings → Printer
  • Prints order receipts and kitchen dockets
  • Works with Epson, Star Micronics, and generic ESC/POS
  • Configurable receipt header, footer, and logo
  • Digital receipt (email) available as alternative
  • Multiple printers configurable per location
Technical
ESC/POS protocol TCP/IP socket No drivers Epson / Star / Generic Per-location config

6 automated schedulers

ZayPOS runs six cron-based background jobs — keeping your business running automatically without anyone needing to trigger them manually.

Job Schedule Type What it does Sends via
💰 Monthly Payroll
0 9 1 * *
1st of month, 9am
Auto Calculates total hours, overtime, and gross wages for all staff from clock-in/out data. Generates the payroll summary and emails it to all configured payroll recipients. No manual action required. Brevo email
📦 Stock Check Reminder
0 8 * * 1
Every Monday, 8am
Auto Sends a scheduled reminder to the manager to perform a manual stock count. Frequency is configurable per organisation (weekly / fortnightly / monthly). Helps maintain accurate inventory records between AI invoice updates. Brevo email
🌡️ Temperature Probe Reminder
0 8,12,16 * * *
3× daily (configurable)
Auto Sends SMS reminders to on-shift staff to complete temperature checks — fridges, freezers, hot holding. Intervals are configurable per organisation. Checks opt-out status before every send. Never messages opted-out numbers. Twilio SMS
📋 Missed Checklist Alert
*/30 * * * *
Every 30 minutes
Auto Runs every 30 minutes to check whether any scheduled safety checklist (opening, cleaning, closing) has passed its deadline without completion. If overdue: SMS sent to on-shift staff and email alert sent to manager. Twilio SMS
+ Brevo email
⭐ Review Request
0 * * * *
Hourly · ~1hr post-order delay
Auto Hourly job that finds completed takeaway/delivery orders where the customer provided contact details, and the review request window has elapsed (~1hr). Checks opt-out status and whether a request was already sent for that order before sending. Prevents duplicates. Brevo email
+ Twilio SMS
🏥 System Health Check
0 6 * * *
Daily, 6am
Auto Daily automated health check — tests database connectivity, API responsiveness, authentication service, printer reachability, and storage capacity. Results logged internally. If any check fails, an alert is sent to the ZayPOS engineering team immediately. Internal
monitoring

How ZayPOS connects to the rest of your business

A till is only as useful as the tools around it. ZayPOS is designed so payments, accounts, delivery, rotas, food safety and hardware all talk to the same till data — instead of leaving you to re-key figures between half a dozen apps. Here is how each category works, and where the connections are already live.

Payments

Card payments are the most important connection a POS makes, so ZayPOS does not lock you to a single provider. Clover is integrated through full OAuth 2.0 — staff authorise once via the Clover login and the product catalogue syncs both ways — while the smart routing engine lets you choose Clover, SumUp, Dojo or Square per location and switch from Settings with no downtime. Refunds are routed back through the original merchant automatically, and every transaction reconciles against the matching sale, so your card takings and your till never drift apart at the end of the day.

Accounting

ZayPOS produces the numbers your accountant actually needs — daily takings, VAT summaries, wages and tips — in a format ready to flow into tools like Xero and QuickBooks. Instead of exporting a Z-report and typing totals into a spreadsheet, your sales and tax figures are captured as they happen, so month-end becomes a review rather than a rebuild. If you use an accountant or bookkeeper, they can work from clean, consistent ZayPOS data rather than a shoebox of receipts.

Delivery

For takeaways and restaurants running third-party delivery, ZayPOS is built to sit alongside platforms like Deliveroo, Uber Eats and Just Eat so orders and menus stay consistent with your in-house till. That keeps one menu, one set of prices and one stock count across counter, online and delivery — rather than a tablet farm where each platform tracks its own version of the truth. Completed delivery orders also feed the review-request automation, prompting happy customers to leave feedback after the food has arrived.

Rotas & payroll

Because staff clock in and out on ZayPOS, the same data drives both scheduling and pay. The monthly payroll job calculates total hours, overtime and gross wages from real clock-in records and emails the summary to your configured payroll recipients automatically — no manual timesheet tallying. AI-generated rotas use your sales patterns to suggest cover that matches demand, and tips and wages roll into the same reporting your accounts integration draws from.

EHO & food safety

Compliance is treated as a connected workflow, not a separate app. Temperature-probe reminders go out by SMS to on-shift staff, opening, cleaning and closing checklists are logged digitally, and a missed-checklist job runs every 30 minutes — escalating to managers by email if a safety task passes its deadline. With the allergen matrix kept Natasha's Law ready and a one-click EHO/SFBB report, the records an inspector asks for are already in one place rather than scattered across paper folders and standalone compliance tools.

Hardware

ZayPOS runs in the browser on tablets, phones and desktops you already own, so you are not buying proprietary terminals to get started. Receipt and kitchen printing use the standard ESC/POS protocol over a TCP/IP socket — no drivers — and work with Epson, Star Micronics and generic printers, with multiple printers configurable per location. Card terminals connect through your chosen payment provider, and a digital email receipt is always available as an alternative to paper.

Integrations FAQ

Common questions about connecting ZayPOS to the tools you already run.

How do ZayPOS integrations connect?

Most connections are built directly into the ZayPOS platform rather than added through a marketplace. Card payments use OAuth where the provider supports it — for example Clover, where staff authorise once through the Clover login with no API keys to copy. Other services connect through official APIs configured in Settings, so there is no separate connector software to install or maintain.

Is there an API I can build against?

Yes. ZayPOS exposes REST APIs and webhook callbacks used by its own payment, email, SMS and catalogue integrations, and these can be made available for your own tooling. If you have a developer or an existing system you want to connect, contact us at hello@zaypos.co.uk and we will share the relevant endpoints and authentication details.

Can you add an integration I need?

Often, yes. Because integrations are part of the core product, we add new payment providers, accounting tools, delivery platforms and hardware based on customer demand. Tell us which service you use and we will let you know whether it is already supported or can be added to the roadmap.

Do integrations cost extra?

The integrations themselves are included in your ZayPOS plan — there are no per-connection fees from us. You only pay any charges from the third-party service itself, such as a payment provider's transaction fees or your existing accounting or delivery platform subscription.