Toast Configurations in the Bbot App Store
This article will go over all of the technical aspects of the various settings available in Bbot's Toast configurations. These configurations are located in the Bbot App Store in your Owner Panel.
Inject orders into Toast?
This setting turns on/off Bbot's order injections into Toast.
Bbot orders will sometimes fail due to a variety of reasons:
- In Toast: The designated Bbot Dining Option configuration has been changed
- In Toast: Certain menu configurations have changed, leading to a price check error
- In Toast Terminal: Auto-Firing configurations are set incorrectly - there should only be a single always-on terminal that has no Non-Printing Prep Stations set for the device.
Set Bbot order status to "done' when marked done in Toast
This setting will essentially allow the orders in Toast to communicate its 'Fulfilled/Ready' status to a Bbot order, within 7 days of the guest placing the order.
- This updates the order-item status in Bbot to the last, second to last (for Driver Delivery), or third to last (for Runners with Bbot Command Centers) stage in the order flow once an order item is 'Fulfilled/Ready' in Toast via the Kitchen Display Screen.
*Note: Bbot order items are injected in the 'Sent' status. 'Ready' is the next stage after 'Sent' in Toast. - This does not apply for Pickup w/ no feedback to guest or Catering Fulfillment Methods
- This will also trigger any Guest Notification Sets that are configured to a Bbot order status
*Note: If you would like to enable Bbot's Guest Notification Sets to send texts to your guests, please make sure that the text settings in your Toast are disabled to prevent double texting. - If a 'Fulfilled/Ready' item is later marked unfulfilled in Toast, it will remain marked as ‘Ready’ in Bbot.
- For Toast-integrated customers who do not wish to have texts sent from Bbot when orders' statuses are updated, they can disable the setting from the Toast Integration modal in the Bbot App Store. Alternatively, they can disable all Guest Notification Sets within Bbot.
Set Bbot order status to "done" when ALL items are marked done in Toast
When this setting is enabled, orders and items within Bbot will not have their order status mapped back from Toast until all items in the Toast order have been marked as ‘Ready’ or ‘Voided’. When items are voided, their statuses will also be mapped back to Bbot and will send a text out, up to 7 days after the order has been placed.
This will also allow individual item fulfillment to be utilized on Toast KDS, and will prevent multiple texts (via Guest Notification Sets) from going out to the guests when individually fulfilling items on an order.
Examples:
‘Set Bbot order status to "done" when ALL items are marked done in Toast’ = DISABLED
- I have multiple Prep Stations and an Expeditor
- A guest places a dine-in order for a pizza and a special dessert.
- The pizza gets routed to Hot Prep Station and the special dessert gets routed to Cold Prep Station.
- When the pizza is marked Ready at Hot Prep Station, the item’s status will update in Bbot, triggering a text.
- When the special dessert is marked ready 5 minutes later at Cold Prep Station, the status for that item will be mapped back to Bbot as Ready for Pickup and another text will be sent from Bbot.
- I only use one Expeditor to fulfill orders.
- At the soonest point an order is marked ready, a text will be sent.
- A guest orders a pizza and special dessert.
- I mark the whole order (with all the items) complete.
- Bbot sends a single text.
Note: If you mark one item complete from an order, and then mark another item or group of items Ready within 6 minutes of the first one, only the first order text will be sent to guests. This is current Bbot SMS behavior for all Bbot orders, not just ones injected into Toast.
'Set Bbot order status to "done" when ALL items are marked done in Toast’ = ENABLED
- I have multiple Prep Stations and an Expeditor.
- A guest places an order for a pizza and a special dessert.
- The pizza gets routed to Hot Prep Station and the special dessert is routed to Cold Prep Station.
- I mark the pizza as complete.
- Two minutes later, the Cold Prep Station voids the special dessert because it ran out.
- In the next poll (within 30 seconds), the order items will be marked as appropriate in Bbot.
- Based on the Guest Notification Sets I have set up in Bbot, Bbot will send guests an order complete (with the fulfilled item) and a refund text.
- I have food and drink orders routed to two separate Bbot Fulfillment/Prep Stations and then injected into Toast as two separate orders.
- Guest orders a pizza, a burger, and a mocktail.
- When they checkout, the order is split to route the food order to the Kitchen Prep Station and the drink order to the Drinks Prep Station.
- These two orders are now injected into Toast.
- I mark the pizza as Fulfilled/Ready on Kitchen KDS.
- 10 minutes later, I mark the burger as Fulfilled/Ready on Kitchen KDS.
- The guest receives a text from Bbot.
- I mark the mocktail as Fulfilled/Ready on Drinks KDS.
- The guest receives another text from Bbot.
- Note that in this scenario, due to how Bbot separates food and drink orders, there must be both a kitchen KDS and a drink KDS in order to send the text notification to guests. If you do not have a drink/bar station KDS, your guests will not receive notifications for their drink orders.
Toast-to-Bbot Status Mapping
READY
Takeout/Counter Service- notified (Ready for Pickup)
server_delivery - humandelivered (On Its Way)
runner_with_cc - wait_for_runner (Ready for Runner)
driver_delivery - wait_for_driver (Ready for Driver)
runner_nofeedback - Dine In
Show full delivery info below items on Toast KDS screen?
When this setting is enabled, Bbot will add the guest details such as phone, room number, address, etc. as a 'Special Request/Instructions' onto the order so that it is visible on the Toast KDS.
Automatically mark orders Accepted by Staff in Bbot, once they're injected into Toast?
When enabled, this setting will mark orders Bbot orders as 'Accepted by Staff', once the order has been successfully injected into Toast.
Toast Ticket Format
This setting refers to how your Toast printers will print Bbot orders, after they have been injected into Toast.
- Guest name & location code
- Guest name & phone number
Bbot Order Revenue Center
This setting refers to which Toast Revenue Center that all Bbot orders should be mapped/assigned to. It is recommended that you set up a dedicated Bbot revenue center, or at the very least, assign it to the "Online Ordering" Revenue Center that already exists in Toast. This will make accounting more convenient and cohesive.
Bbot Order Employee
This setting refers to which Toast employee/user receives the injected Bbot orders. This is significant, because any tips, revenue, and other reporting aspects will be tied to this specific employee/user. It is recommended that you set up a "dummy" employee/user in Toast that is dedicated to being assigned to Bbot orders.
Tab Name Template String
This setting allows you to enter variables into the text field to have guest information populate at the top of the Toast printed ticket and on the order in the Toast KDS.
- $ORDER_NUMBER - This will display the order number at the top of the ticket.
- $LOCATION - This displays the location code's long name that the order was placed through.
- $PATRON_NAME - This will display the guest's name as it was entered in the Guest Checkout Information field on the Bbot checkout page.
- $ROOM - This will display the room number that the guest entered on the checkout page if the Room Number field is enabled in the Guest Checkout Information Information settings.
- $PATRON_PHONE - This will display the guest's phone number that was entered in the Phone Number field on the checkout page.
- $PATRON_EMAIL - This will display the guest's email address that was entered in the Email Address field on the checkout page.
For any questions about the Toast integration or for help with configuring any of the settings above, please contact our support team at bb-support@doordash.com.