Orders placed on foodpanda and talabat arrive in your POS beside the ones from your own website and your own counter — same list, same kitchen tickets, same stock, same reports. Nobody has to watch a tablet on a shelf, and nobody re-types an order that is already on a screen.
7 أيام مجاناً · بلا بطاقة ائتمان · كل الميزات مُفعّلة
The aggregator tablet on the shelf is where orders get missed during a rush. Foodpanda, Talabat, your website and your counter all ring the same bell in the POS top bar, and the counter answers them from wherever it already is.
And the platform is told. A marketplace cancels an order nobody answers, and enough cancellations take the shop off the app — so the answer goes back to Foodpanda or Talabat, not just into your own system.
The guest ordered in Arabic off the platform's menu; the ticket at the pass carries the dish exactly as your kitchen knows it, with the chosen size and every topping the guest picked.
Sales by Channel puts each marketplace beside your own website and your counter, so what a platform is worth after its cut is a number on a report rather than a feeling.
A platform retries an order it thinks failed. The same order code can only ever create one order here, so a retry during a rush does not put two of everything through the kitchen.
Yes — API access for your outlet, which you request from them. Once you have it, you paste the credentials into Settings → Integrations and the orders start arriving.
Yes. A restaurant on both runs both, and each order carries its platform on the ticket and in the reports.
Exactly like a counter sale. It is a real order in your POS, so its recipe ingredients come out of stock when it completes.
It stays on the bell until somebody answers it. The platform is only told once you accept or reject, so an order is never silently taken on.
