Channels
Zomato, Swiggy and other channels
Receive aggregator orders at the till.
POS receives orders from delivery channels in your kitchen. Zomato and Swiggy do not offer a self-serve public order API: direct integration is granted to approved partners, or you can use an aggregator middleware (for example UrbanPiper). POS therefore provides the receiving side and a no-code mapping for the vendor's format.
#How an order arrives
The channel (or your gateway) sends the order to your outlet's webhook address. The order is created as Pending (or Accepted with auto-accept), recorded as prepaid, and rings on every terminal within seconds. Redeliveries are safe — the same order is never created twice. Items are matched to your menu by the channel's item id set on each dish (Menu → edit dish), or by the dish SKU; unmatched lines still print, marked "unmapped".
Turn each channel on per outlet under Settings → Channels.
#Custom payload mapping (no code)
Settings → Channels → Custom payload mapping… lets you describe where each field lives in the vendor's data, paste a sample, Test it to see the normalised order, then Save. Remove reverts to the built-in format.
#Telling the channel what happened
Set a status callback URL per channel (https only). POS then notifies it as the order is accepted, being prepared, ready, dispatched, completed or rejected, and when a dish is sold out or back in stock. Failed callbacks are retried.
Note You need real partner access and a sample payload from the vendor before orders will flow from Zomato or Swiggy specifically.