Feature Requests

Flow Control & Blocks
It would be highly beneficial if flow control within Toast Tables could be managed at the service-area level rather than applied globally to an entire shift. For restaurants like ours, this added level of control would allow us to better manage pacing and guest experience across distinct areas without needing to manually create blocks each day. Additionally, having the ability to manage and apply reservation blocks from the desktop platform—rather than solely through the app—would significantly improve efficiency. The option to create and apply blocks in bulk would streamline operations and reduce the time required for daily setup. Another key enhancement would be more advanced and flexible control over seating times. For high-demand holidays such as Mother’s Day, each table often follows a very specific seating schedule. For example, one table designated for 3–4 guests may be booked at 10:30 AM, 12:00 PM, 1:30 PM, and 3:00 PM, while another table for 5–6 guests may follow a different cadence such as 10:15 AM, 12:15 PM, and 2:15 PM. Currently, to accommodate this level of detail, we must create shifts in 15-minute increments and manually adjust multiple variables within each slot—including maximum party size for online reservations, specific table assignments, and flow control cover limits. This process is time-consuming and operationally cumbersome. A more efficient solution would allow operators to define table-specific seating schedules and constraints within a single interface, reducing the need for manual workarounds and significantly improving both usability and precision in managing reservations.
0
·
Host App
Improve Customer Data Linking Between Checks, Rewards, and Integrations
Currently, customer data is very disconnected in how it links to checks, which creates significant challenges for reporting accuracy and syncing with third-party integrations (such as Klaviyo). At present, the following actions do not attach customer information to a check: Adding a rewards account to a check Having a customer “check in” via the guest display Allowing Toast to match a customer using credit card matching The only consistent way customer information is attached to a check is through the customer info prompt on takeout orders. When a rewards account is added, the customer details are effectively stored behind a hyperlink rather than being directly associated with the check in a usable way. This makes the data difficult to access, creates discrepancies in reporting, and prevents reliable syncing with third-party systems. Additionally, customer information and rewards data appear to function as separate entities rather than a unified customer profile, which further complicates workflows. There is also a significant duplication of effort in daily operations. For example: If a customer’s rewards account is entered for a takeout order, the system still prompts again for customer information instead of recognizing that the check is already tied to that customer. If a customer enters their information on the guest display, staff must still look up or re-enter the customer again to apply or redeem points. This results in unnecessary searching, repeated lookups, and a slower checkout experience. Suggested Improvement: Create a unified customer profile where adding a rewards account, guest check-in, or card match automatically attaches full customer information to the check and is recognized across all workflows (ordering, rewards redemption, reporting, and integrations). Ideally, this would be a “one-and-done” process that eliminates duplicate prompts and ensures consistent data for integrations. Improving this would reduce friction for staff, improve data integrity, and enable more reliable syncing with marketing and reporting tools.
0
·
Backend
Load More