Receive Online Food Orders in Your POS
Online food orders from any platform that can send JSON land once as a ticket, with unmapped items named and refused.
Your captains no longer retype aggregator orders from a separate tablet in the middle of service. Give each channel its own secret, let it post the order, and it arrives as a ticket at that channel's price.
How it works on arrival
- The full payload is saved before any processing, so even a body that cannot be parsed is kept for later.
- The sender's reference number stops duplicates. Aggregators retry deliveries, and a retry still produces just one ticket.
- Each channel item ID is matched to one of your dishes. If an item has no match, the order is refused and the item is named, rather than being left off quietly.
- The dish is billed at the channel's own price, since aggregator menus are deliberately marked up.
What it does not do yet
F&B Point of Sale does not send your menu to an aggregator, and it does not accept orders for them. The aggregator builds that side through its own API after a restaurant connects. Today, anything able to post JSON can send orders in.
