POS Sales And Imports
Capture POS sales, import external activity, and reconcile both against the operational shift.
POS tools connect Zesty to sales outside the standard table-and-QR path: counter registers and imported sales.
Everything still lands in Orders and Payments for reporting—POS uses a hidden order type so service queues stay clean.
POS workspace (counter sales)
What POS is for
- walk-in customer pays immediately
- takeaway counter without table session
- quick sales that should not appear on KDS or service Billing queue
What happens under the hood
Each completed POS sale creates:
- one hidden POS order (not in service Orders/KDS/Tables queues)
- one successful payment for reporting and settlement
The POS receipt is the staff-facing record. Reports read the same spine as table service—without double counting.
Sales workflow modes
| Mode | POS role |
|---|---|
| POS only | Primary sales path; service modules hidden |
| Orders only | POS optional or off |
| Combined | POS + table service; reports split by capture mode |
Detail: Sales workflow modes
Shift requirement
Open an operational shift before POS sales—same as other protected actions.
Customer capture
Optional name and phone on POS help customer history and loyalty. Do not block the line for optional fields during rush.
Refund and void
| Action | Behavior |
|---|---|
| Refund | Money back; original receipt preserved; correction receipt issued |
| Void | Sale cancelled; choose keep ingredients consumed (default) or restore mapped ingredients |
Train staff: void is not "delete silently"—audit trail remains.
Unpaid counter orders
The register no longer requires payment at the moment of sale. A counter order can be created unpaid and settled, printed, edited, or cancelled later, and POS history lists deferred and directly-paid sales together. See POS register.
Unpaid counter orders
The register no longer requires payment at the moment of sale. A counter order can be created unpaid and settled, printed, edited, or cancelled later, and POS history lists deferred and directly-paid sales together. See POS register.
POS on mobile
The same register on phone and tablet, with the same canonical reporting. See Mobile app workflows.
Combined mode reporting warning
Reports read Orders and Payments once. Use capture mode to split POS vs service. Do not add POS receipt totals to order totals manually—that double counts.
Imports and connectors
Depending on your setup, Zesty may support:
- internal register (native POS)
- Petpooja import
- Posist import
- Square sync
- custom webhook or other configured providers
Before production
- confirm provider credentials and branch mapping
- run a test import in a quiet window
- verify one sale appears correctly in reports and Shift Desk
- document who owns re-sync when provider is down
Provider outages can leave external menus or sales delayed—have a manual fallback policy.
Operational shift and Shift Desk
POS totals flow into the same shift boundary as service orders. Managers reconcile both in Shift Desk in Combined mode.
Common problems
| Problem | Likely cause |
|---|---|
| POS sale on KDS | Wrong workflow or wrong entry path—use POS module |
| Double revenue in reports | Manual addition of POS + orders totals |