...

1. How is this integration working now? What is the trigger point?

   1. The Customer scans a QR Code containing an ID of the Order

   2. The BookingAll solution gets information from the getOrders endpoint

2. Is BookingAll an RBI or Partner tool?

   1. It’s a partner tool

3. Is there a dependency on BookingAll? (new endpoint?)

   1. They will need to adjust the order-to-kitchen workflow to read the new LoyaltyId data from the getOrders endpoint and automatically send the Order to the kitchen.

   2. BookingAll to confirm the development timeline

   3. Need to organize integrated tests and UAT with BookingAll

4. Does this impact other countries? Is BookingAll used by all of Iberia?

5. Should this be sent to any other partner platform? (autoking?)

   1. By adding the information to the Partners API any other platform that might make use of it can already benefit from this solution.

6. Is there documentation on BookinAll integration?

7. Do we have data on how many Mobile Ordering orders are picked up in the drive?

   1. No, the data is not specific enough at the time.

8. This situation occurs in which markets/brands of Iberia?

9. The manual approve is only necessary for Drive Thru service mode? If yes, why the other service modes works automatically?

10. The process to approve the order in the POS oblige the restaurant employee to re-type the full order?

11. Why it is necessary the LoyaltyID to automated the process?

12. If the order was already injected in the POS, why BookingAll need to call the getOrder endpoint? Which information the POS needs at this point?

📈 Success Metrics

...