Foodics + WhatsApp Integration
Foodics is the GCC restaurant POS. Push order-created and order-ready events into Ominiflow so Kuwait diners get WhatsApp updates instead of a missed SMS.
Foodics is the POS Kuwait and GCC restaurant groups already run — not Clover, not Petpooja. Ominiflow subscribes to Foodics order webhooks (created, accepted, ready, completed) and sends the matching approved Utility template to the diner’s +965 number when consent exists. Pickup-ready and table-waitlist messages are the volume use cases; Marketing win-back is a separate opt-in list.
Keep Foodics as the operational source of truth. Ominiflow does not replace Foodics menus or KDS. It is the WhatsApp layer: bilingual templates, shared inbox for “where is my order?”, and optional MyFatoorah/Tap links for prepay or leftover balance.
Multi-branch groups in Salmiya, Kuwait City, and Ahmadi can route Foodics location IDs to inbox teams so Hawally tickets do not land on the Mall of Arabia shift.
How It Works
-
1
Authorize Foodics APICreate an Ominiflow app token in Foodics (read orders, customers, locations). Sandbox first.
-
2
Map locations to inbox teamsEach Foodics branch → Ominiflow team. Prevents cross-branch reply mix-ups.
-
3
Enable order templatesConfirm, accepted, ready, completed — Arabic and English pairs. Utility only; do not mark pickup-ready as Marketing.
-
4
Capture WhatsApp opt-inCheckout checkbox or QR at table. No purchased lists. Test with one branch before group rollout.