Voco operates alongside your current hardware and software setup. We route phone orders directly to your screens or receipt printers with zero friction.
Compare how Voco interacts with different Point of Sale and hardware systems.
| Capabilities | Square POS | Clover POS | Star CloudPRNT |
|---|---|---|---|
| Order Answering Routing | ✔ Direct Sync | — Fallback Channel | ✔ Thermal Receipt Print |
| Kitchen Display (KDS) | ✔ Supported (Active) | — (Printer only) | — (Printer only) |
| Customer CRM Write | ✔ Yes | — No | — No |
| Connection Type | OAuth 2.0 | Fallback Alerts | Polling Webhook |
| OCR Menu Support | ✔ Yes | ✔ Yes | ✔ Yes |
How we interface with key restaurant infrastructure.
How does the Square sync work? Voco integrates natively using the Square Orders API. It connects via OAuth and automatically handles token refreshes. Orders are created with scheduled pickup times set to 15 minutes in the future, transmitting customer names, phone numbers, item totals, and details directly to the Square Kitchen Display System (KDS).
What is the hardware printing fallback? For kitchen lines operating without direct POS integrations, Voco supports Star CloudPRNT. Star thermal printers poll our `/cloudprnt/poll` API over LAN/WAN. Voco queues formatted plain-text receipts (ESC/POS byte arrays) which the printers automatically fetch and print.
Are there backup notifications? Yes. Regardless of the POS pathway, Voco's `notifyKitchen()` fan-out routing runs parallel on every single order. Notifications are sent via email (Resend), real-time dashboard alerts (Supabase Realtime), and optional text or WhatsApp messages (Twilio) to prevent missed tickets.
Voco features a decoupled POS architecture. Square is fully integrated for orders, customers, and locations in production. Clover and other legacy systems connect via CloudPRNT fallback triggers.