--- title: "Overview and navigation" slug: "control-actions-and-notification-information" updated: 2026-11-03T14:47:38Z published: 2026-11-03T14:47:38Z canonical: "products.egretail.cloud/control-actions-and-notification-information" --- > ## Documentation Index > Fetch the complete documentation index at: https://products.egretail.cloud/llms.txt > Use this file to discover all available pages before exploring further. # Overview and navigation When the user has logged in and there are no ongoing transactions, the list is empty. When active registers start up (a sale is started) they are presented in the list. ### Controls and notifications definition In Monitor App there are controls and notifications. - **Controls** are requests where staff is required to intervene. The register shows a red flag, and the monitor gives an alert sound. - **Notifications** are messages where the user needs to perform a check in the app and with the customer to ensure all is well. They do not give an alert sound and do not block the register. An answer is not shown as handled until the register has confirmed it. The request then disappears on every screen that monitors the store. --- ### The top bar and the layouts The top bar has three parts: the **Menu** button on the left, the EG Retail logo with the title **Monitor App** in the center, and **Full screen** and the **Layout** menu on the right. On small screens Full screen and the layout menu show only their icons, so the logo and title keep their room. Controls are by default presented in a priority list. Registers with a control or notification are presented at the top, under **Action required**. Open active registers without controls or notifications are presented under **Active.** Using the **Layout** menu in the top right corner, the user can switch between: - **Store layout** – the fixed layout of the store, where each register has its own place as in the physical store ([see Store layout](/v1/docs/control-actions-and-notification-information#store-layout)). Only offered for stores that have a layout. - **Priority** – actions first, then active registers. - **By number** – all registers in register-number order. - **By area** – registers grouped by the areas defined for the store. Registers without an area are listed under **Ungrouped.** ![](https://cdn.document360.io/5c3fbf4a-b177-42ef-a5c9-ab5c60ca2ba9/Images/Documentation/image-FT0XHH2D.png) *The Layout menu with Store layout, Priority, By number and By area* --- ### Presented on a register tile Each register is shown as a ‘tile’. The ‘tile’ shows: - A colored bar at the top: **red** when a control is waiting, **orange** while a warning is pending, **grey** while a colleague is helping the customer or the sale is closed. - The register's name (or "Register {number}" when the register has no name), with an icon if a member is added to the sale. - A flag indicating that there is an action to do, and a timer showing how long the customer has waited (nothing is shown during the first 30 seconds). - The status: **Not active** (a register in the store layout that is not reporting), **Sale in progress**, **Awaiting control**, **Receiving assistance**, **Sale finished**, **Sale cancelled** or **Sale cancelled (inactivity)**. - The sales total and number of items for the sale (struck through when the sale is closed). - The last scanned item with quantity and amount. A register shows at most one request of each type. If the same type is raised again, the new request replaces the old one; the waiting time keeps counting from the first request. A sale can have several different requests at the same time. Most of them must be handled separately – approving one does not mean the other is checked and approved. ![](https://cdn.document360.io/5c3fbf4a-b177-42ef-a5c9-ab5c60ca2ba9/Images/Documentation/image-2NQGRRLG.png) *Register tile with pending age control: red bar, flag, Age control, sales total and number of items* --- ### Handling controls and notifications To handle a control or notification, press the register tile to open the register panel. Pending requests are listed as buttons under **Pending controls**, named after the control. Press the button to open the request, then complete an action on it. The request opens from the bottom of the screen. It shows the register name and control type as the header, an explanatory message, the member number if one is added, and – where relevant – the items related to the control, with quantity and price. When a request is raised while the register panel is open, it opens by itself unless another request is already open. Opening a request tells the register that a cashier is receiving assistance, and the tile turns grey for colleagues, so they know someone is already on the way. (A request that opened by itself does this only when you touch it.) The grey color is removed when the last pending request is answered or the sale ends. ![](https://cdn.document360.io/5c3fbf4a-b177-42ef-a5c9-ab5c60ca2ba9/Images/Documentation/image-M0VBRVD1.png) *Register panel with the receipt tabs and the pending Age control with its 25+ shortcut* If the app shows "Already handled elsewhere — refreshing…", a colleague has already answered the request. If it shows "No confirmation from the register yet — it may be offline.", the answer has not reached the register: check the register and try again. --- ### Store layout A store that has a layout opens in the **Store layout** view. The registers are shown in groups, each at its own row and column as the registers stand in the store. A gap in the layout is shown as an empty place. A register stays in its place, whether it has a request. - A group heading shows the name of the group, the number of registers, the number of waiting requests (flag) and an arrow. Select the heading to collapse or expand the group. When there is more than one group, the app remembers which groups are collapsed on this device and store. - A register in the layout that is not reporting is shown as a tile with the text **Not active**. Its register panel works as for other registers, with the tabs Current, Previous and History and the Alarm log. **Force control** is not offered because no sales are running. - A register that reports but is not placed in the layout is shown in a section called **Not in layout** after the groups. Its requests are never hidden. - A layout wider than the screen scrolls sideways. - While the layout is loading the app shows "Loading layout…"*.* - Choose **Priority**, **By number** or **By area** in the Layout menu to leave the fixed layout. ![](https://cdn.document360.io/5c3fbf4a-b177-42ef-a5c9-ab5c60ca2ba9/Images/Documentation/image-VKY1TZHF.png) *The store layout view: groups of registers in fixed places, with Not active tiles* --- #### Controls and notifications general handling The following buttons are common across controls: - **Close** - Closes the request. It does not cancel anything other than the opportunity to act at that moment. The request remains unhandled. - **Done** - Confirms that the user has handled the situation. The control or notification is removed. This is the default confirmation button on most controls. - **Approve** - Approves the control (used by Random control). - Remove notification - Removes the notification (used by Substance items and Blocked item). - **Alarm removed** - Confirms that the security tag has been removed (used by Alarm item). - **Full control** - Escalates to full control of the sale. Shown as an extra option on certain controls when a sale requiring it is ongoing.