AirMenu

A pricing decision is made once, in a spreadsheet or a back office system, and applies to eleven venues. The agent resolves each venue with Get Enterprise and its divisions with Get Division IDs, then calls Get Menu for the division at the relevant weekly time so it is comparing against what guests are actually being shown rather than against last month's export. It builds the new tree, matching every node to the live menu on plu rather than on title, because a title is a display string and a plu is what the till charges against. The diff it produces is in money and item names, not in JSON: eleven venues, thirty four items repriced, four items whose plu does not appear in the live tree at all. Those four are the interesting ones, because a plu that has no match is either a genuinely new item or a rename that would strand a node. A person sees that list before Save Menu runs, and the flow writes only the tree that was released.

A concierge app, a kiosk or a partner channel produces an order for a venue. The agent calls Send Order against the enterprise division with the item plus and counts, an optional booking time, and the customer's username, and receives back the order number, the order ID and a tracking URL it can hand straight to the guest. From there the order moves through the venue's own workflow: Activate Order Flag sets Accept, Deny, Ready or Picked with the operator's email recorded against each transition, Get Active Flags reads the current state back with its timestamps, and Notify POS pushes an alert to a specific terminal with an optional file URL for the terminal to fetch. Because there is no trigger to lean on, the flow keeps a scheduled poll running alongside this: Get Order IDs across the last interval, then Get Orders for anything new, so an order placed directly in the venue is picked up on the same cycle as one the agent created. Exceptions, a Deny or an order that sits unflagged past its booking time, go to the duty manager in Slack rather than into a report nobody opens.

Marketing wants a voucher campaign live on Friday. Create Promotion takes locale keyed title and description objects, a validity window and an offer window as Unix millisecond timestamps, and an Offered Item Branch listing the menu node IDs the promotion grants. That last field is where campaigns quietly break, because it points at nodes in a menu tree that a separate flow may have rewritten since the campaign was drafted. So the agent reads Get Menu first and confirms every offered node ID still resolves, calls Update Stock to set the lots for the offered items with their consumable or reusable type and quantity so the kitchen has what the voucher promises, and only then creates the promotion. Redeem Code turns a guest's code into vouchers at redemption time and returns the voucher IDs, which the flow logs to Airtable alongside the campaign so redemption can be reconciled against stock afterwards. If an offered node has gone missing, the campaign stops and a person is asked which item replaces it.