This feature consists of the following enhancements as part of our Drive-Thru initiatives:
Block Checkout
This feature enhances Activate X to follow a terminal configuration that allows order taking (but not tendering).
Lock Check and Multiple Users
This feature consists of enhancing Check Sync, adding additional configuration to:
- Allow multiple Activate X users to edit the same check (when using the same terminal role) while notifying each user and handling eventual collisions (with multiple updates to the same check) OR
- Prevent other users from editing the same check.
Check Queue
This feature consists of enhancing the Check Queue in ActivateX to support:
- Anyone who logged into the Drive-Thru terminal role on a POS can see newly created and removed orders (either completed or deleted/canceled) in the Check Queue (in the left sidebar in Activate X).
- Order changes (added, edited, or closed) are automatically visible on all Activate X terminals and the Check Queue and the Checks screen.
These features provide improved capabilities to Quick Service and Drive-Thru scenarios.
Terms
- Check Queue: A module within Activate X allows users to view, resequence, and remove upcoming checks as they are created and originated from Drive-Thru orders.
- Check Sync: Check Sync allows a user to open checks, create orders on one Activate device, and edit them on another device. It is also possible to add new items to the existing checks and modify a tab/check order remotely from other devices.
- UOP: Universal Order Payload is a 1st party member of the Appetize Environment. Like a Protobuff, it is a declared and versioned data declaration used by multiple services, platforms, and components. Its goal is to add, remove, and test services, platforms, and components easier by unifying under a single input model and separating the syncing of order data from the order itself.
- Collisions: Conflicts occur when there are concurrent updates to the same Order from multiple sources. If a client goes offline for an hour and comes back, any changes made on that client during that hour would be effectively concurrent with changes made by all other clients. In the synchronization process, conflicts are automatically resolved.
Instructions
Before You Begin
- Checks must be enabled at Terminal Role > Core UI > Check Management > Checks (select Yes).
- Check Queue must be enabled (for visibility/enablement of Block Checkout flag) at Terminal Role > Core UI > Check Management > Checks > Checks Queue (select Yes).
- Check Sync is installed, configured, and active.
Connect Setup
Block Checkout
This functionality requires the following dependencies to enable:
- A new flag in the Connect UI (Connect 11.3) that AX/IX terminals can control if Block Checkout is enabled.
- This new flag is available at Terminal Role > Core UI > Check Management > Checks > Check Queue > Block Checkout
- Yes (select to enable)
- No (default; select to disable)
Lock Check and Multiple Users
This functionality requires the following dependencies to enable:
- A new flag in the Connect UI (Connect 11.3) that AX/IX terminals can control if Lock Check is enabled. This new flag is available at Terminal Role > Core UI > Check Management > Checks > Lock Check
- Yes (select to enable)
- No (default; select to disable)
Check Queue
This functionality requires the following dependencies to enable:
- An existing flag in the Connect UI that AX/IX terminals can control if Check Queue is enabled. This flag is available at Terminal Roles > CoreUI > Checks > Check Queue
- Yes (select to enable)
- No (default; select to disable)
Activate
Block Checkout
ActivateX will retrieve the new flag from Connect as part of the Login data to define whether the Checkout button in AX is enabled or disabled for a terminal role.
AX will block the Checkout button if the flag is enabled (regardless of the Checks and Check Queue flags). When AX is configured with this new flag, the user can add/edit/remove items and orders; however, they cannot process any payment on this terminal.
Preconditions
- Terminal Role -> Core UI -> Checks -> Check Queue -> Block Checkout set to Yes
Steps for Usage
- Add items to the cart
- Click on submit
- Recall check from check queue
- Checkout should get disabled
Lock Check and Multiple Users
When Activate X is running with both the Check Queue enabled (Terminal Role > Core UI > Checks = Yes > Check Queue = Yes) and Lock Check enabled (Terminal Role > Core UI > Check Management > Checks > Lock Check = Yes), no other user can edit the order.
-
AX will indicate to the users that the order is locked.
When Activate X is running with Check Queue enabled (Terminal Role > Core UI > Checks = Yes > Check Queue = Yes) and Lock Check is disabled (Terminal Role > Core UI > Check Management > Checks > Lock Check = No), users with the same terminal role can update/complete orders in the Check Queue and the Checks screen (even when other users create the order).
-
AX will indicate to the users that the order is being edited from multiple terminals/users.
Activate X will handle collisions in order updates, as we have introduced with UOP, and resolve any major conflicts around order data updates.
When Activate X is running with the Check Queue disabled (Terminal Role > Core UI > Checks = Yes > Check Queue = No), users are not notified of others editing the check (or prevented from editing them).
- Lock Check flag will get disabled when Check Queue is disabled.
Preconditions
Multiple users operating simultaneously within a given vendor.
Steps for Usage
- User A creates Check Z on Terminal M
- User A updates Check Z on Terminal M
- User B, at the same time, tries to update Check Z from Terminal N
- User B sees the message, “Order Z is Locked,” preventing User B from editing Check Z on Terminal
Check Queue
Activate X will have the Check Sync routines reviewed so that order changes (added or closed) are automatically visible on the Check Queue and the Checks screen.
When Activate X is running with the Check Queue enabled (Terminal Role > Core UI > Checks = Yes > Check Queue = Yes), users that utilize the same terminal role can see newly created/updated/completed orders immediately in the Check Queue and the Checks screen.
- Activate X will allow users to re-sequence orders on the Check Queue.
Activate X will allow users to remove orders from the Check Queue.
- Order Tiles moved to Trash Bin will prompt the user to confirm the deletion/removal.
KDS Android will properly reflect the changes (voids & re-sorts) after each update.
- QSRA and KDS iOS do not support the resequencing of orders.
Preconditions
Terminal Role -> Core UI -> Checks -> Check Queue set to Yes
Steps for Usage
- The user creates Check on Terminal
- The user updates the checks sequence on the Check Queue
- Long press check (tile)
- Drag check (tile) to the desired position
- The user cancels the check on the Check Queue
- Long press check (tile)
- Drag check (tile) to the trash icon on the bottom of Check Queue
- The checks and sequences are updated on Check Queue, Checks Screen, and KDS Android.