POS And Marketplace Integrations

Capture POS sales, import external activity, map menus, sync stock, and review marketplace order inboxes.

POS and marketplace tools connect Zesty to sales outside the standard table-and-QR path: counter registers, imported sales, and third-party delivery platforms.

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.

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.

Marketplace integrations

Marketplace connects delivery aggregators to your kitchen and stock.

Typical capabilities

integration setup per provider and branch
menu mappings — external item ↔ Zesty item
order inbox — accept or reject incoming tickets
menu sync — push availability and items outward
stock sync — reduce overselling on platforms

Order inbox workflow

External order arrives
        ↓
Staff review in inbox
        ↓
Accept (maps to Zesty order) or reject with reason
        ↓
Same lifecycle as internal orders → KDS → handoff

Rejected orders should include a note kitchen or platform support can use.

Wrong mapping causes:

wrong item on KDS
incorrect stock deduction
bad revenue by item reports
customer complaints on substitutions

Mapping checklist

map every variant that differs in price or kitchen station
mark unavailable items on both sides after 86
re-map when you rename menu items
test one order per platform after major menu change

Sync discipline

Run menu sync and stock sync only when:

branch context is correct
you reviewed pending menu changes
kitchen knows a sync is happening (temporary item hides)

After sync, spot-check one item on the external app and in Zesty.

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
Marketplace order missing items	Mapping gap or sync lag
Stock wrong on Swiggy/Zomato	Stock sync off or threshold not updated