How To Guide - Configuring POS Behavior (Menus)
This guide covers the basic configuration of POS Menus in Enactor. Retail applications that present user interfaces use Menus as the principal means to navigate and access application functionality. Menu configuration provides the first level of retailer control over what application functionality individual users and groups of users may access, and how they navigate to the functions they require.
This guide focuses on the POS Sale Menu and Tender Menu - the menus most likely to require customisation for a retailer. Please refer to the full solution documentation and other How-to Guides for information on other menus.
Configuration
Menus are associated with a Locale, User Role, and Menu Group. These relationships must be understood and the related configuration elements defined before creating menu configurations.
From the POS user perspective, some POS Menu options select other menus or invoke software functions. These are the POS Menus for which the action behind the menu option is an Event - a Function or Process defined within the constraint of the Menu Set.
In the standard NextGen UI, the menu is represented as two rows of four buttons at the bottom of the screen, or a single column of eight buttons on the right side depending on the theme resolution. The Sale Menu is displayed while in the basket view. Once the transaction has been tendered, the menu switches to the Tender Menu.
Accessing Menus
Navigate to the Menus option using the path:
Main Menu > Configuration > Menus > Menus
Menus Maintenance List
The Menus option opens the Menus Maintenance list page. The list displays currently configured menus and enables the user to Add, View, Edit, Copy, or Delete menus.
This completes the Menus Maintenance list overview.
Creating a New Menu
In the Menus Maintenance list page, select Create a new Menu. An initial form is presented to capture a Menu Set, Role, Menu Group, Locale, and Menu ID - all of which serve to uniquely identify a menu. Enter values and select Create.
This completes the new Menu creation.
Menu Creation Options
The Create New Menu option initiates the creation of a new menu from scratch. However, menus may also be created by copying existing menus, including the supplied example menus. To copy an existing menu, click the copy icon associated with it in the Menus Maintenance list. The initial form to capture the mandatory identifying elements is common to both methods.
It is recommended to start by copying an existing menu and making modifications rather than starting from scratch, as this provides a ready-built menu structure that can be customised as required.
This completes the Menu Creation Options overview.
Specifying MenuSet
The Menu Set is specific to each application and is associated in the Estate Manager database with all the Events of the application, which are available to be referenced by options in menus. The MenuSets available appear in the dropdown list for the property. There are two fundamental Enactor Retail Application Menu Sets: Web Maintenance and POS.
This completes the MenuSet specification.
Specifying Locale
Locale is configured using Configuration > Organisation > Locales. Equivalent menus for different Locales may be created by copying the first-created menu and applying the different Locale values. These copied menus may remain equivalent in all respects other than Locale if the menu option labels are specified based on a Message Resource, since the Message Resource will be dynamically selected based on the Locale of the user. Alternatively, Locale-specific labels may be explicitly specified as text in the menu configuration.
This completes the Locale specification.
Specifying Menu ID
For supplied Enactor Retail Applications, the set of Menu IDs applicable to the software associated with the Menu Set is available as a dropdown list for selection. Absent any customisation using the Enactor Toolset, the Menu ID need only ever be selected from the dropdown list, since these are the only menus that the software will ever request and load.
This completes the Menu ID specification.
Editing the Menu
Once created, or when selected for Edit, an individual menu is presented in the Edit window of the Menu Maintenance page in an expandable tree structure. Sub-menu nodes have an expand/collapse icon by which the user may navigate and view the menu as presented in the configuration maintenance interface. The Menu Edit page captures identifying properties of the menu and allows manipulation of its structure and content.
This completes the Menu Editing overview.
Menu Construction
Menu Options shown in the Edit window that have an expand/collapse icon are Sub-Menu nodes (i.e., Folders) to which new Options may be added. When such options - including the root configuration menu itself - are selected (shown highlighted in Bold), the Add option is available to add new options to them. This is the basic method of Menu Construction.
Using the Copy method as described above is the ideal starting point for menu construction, as it provides a ready-built menu structure that can be customised by applying the various options described in the following sections. Menus are internally hierarchical in the sense that Folder options may be added to the main root menu, which appear in the user interface as sub-menus and to which further options may be added, including other Folder options.
This completes the Menu Construction overview.
Adding Menu Elements
New menu options may be added using the Add option. When selected, the user is presented with a pop-up menu of the types of menu items that may be added. Only two of the Add options should ever be required for the creation of POS menus: Add a new Button and Add a new Button Folder.
In all cases, when one of these options is selected, the Menu Maintenance function opens in the General tab of the Menu Element Maintenance page to capture details of the new element.
This completes the Menu Elements overview.
POS Menus
This guide covers the POS Sale Menu and Tender Menu. While there are other menus in the POS Menu Set, these are most likely to require some level of customisation to suit the retailer.
Sale Menu
In the Menus Maintenance view, use the filters to locate an existing Sale Menu. In the example below, filters have been applied for POS as the Menu Set, Sales Assistant as the Role, and Standard POS as the Menu Group.
Locate the Sale Menu and click the copy icon to create a duplicate.
Select the desired Role, Menu Group, Locale, and assign a Menu ID. Click Create to create the new menu, which is now ready to be edited.
The Sale Menu contains most of the functions required by a retailer. Most customisation work involves restructuring the hierarchy of the menu, removing unnecessary items, or adding new items.
The numbers in the menu tree represent the button position for each item. In the example below, the main Sale Menu has seven buttons defined, so the eighth button will not appear. To change the order in which functions appear, select the button that needs to be moved and use the Move Up or Move Down buttons until the correct order is achieved. This can be done at any level of the hierarchy.
Removing an item is done by selecting the item and clicking Remove. Note that the Remove action can be applied to individual functions as well as folders - removing a folder removes the folder and all its contents.
Buttons and Folders can be added by selecting the containing folder first, then clicking Add and selecting either Add a new Button Folder or Add a new Button.
If Add a new Button Folder is selected, a form appears to collect the folder name and button position.
As the button style is already defined within the UI, the only information needed is the Folder Label (the text that will appear on the button) and the button Position.
When Add a new Button is selected, a similar form is presented. This form additionally requires the Event that is to be fired by the button to be selected. For example, to add a button that triggers a No Sale, select the No Sale event. Enter the desired button text as the Button Label and specify the Position at the bottom of the form.
All events that can be launched from POS appear in the Event dropdown.
In addition to changing the order of appearance, the structure of the hierarchy can also be adjusted. Using the Change Folder option, it is possible to move a function or folder to a different location or level of the hierarchy. For example, to move the Loyalty Folder from the second level of the Sales Folder up to the first level, click on the Loyalty Folder and select Change Folder.
A dropdown appears to select the desired target folder from the menu hierarchy. In this example, select the Sales Folder.
After saving the change, the Loyalty Folder now appears at the top level of the Sales Folder. When a folder or button is moved, it retains its previous position ID. Use the Move Up and Move Down functions to select the desired position within the new folder.
Once the Sale Menu is completely revised, it can be saved. If additional variations of the menu are required for different Roles, Locales, or Menu Groups, this process can be repeated using the newly created menu as the source for the working copy.
This completes the Sale Menu configuration.
Tender Menu
In the Menus Maintenance view, use the filters to locate an existing Tender Menu. Apply the same filters as before: POS as the Menu Set, Sales Assistant as the Role, and Standard POS as the Menu Group.
Locate the Tender Menu and click the copy icon to create a duplicate.
Select the desired Role, Menu Group, Locale, and assign a Menu ID. Click Create to create the new menu, which is now ready to be edited.
The process to reorder, add, and remove items from the Tender Menu is the same as described above for the Sale Menu. What is different about the Tender Menu is that each tender represented on the menu must be linked to a tender that has already been configured. It is therefore recommended to complete tender configuration prior to modifying the Tender Menu.
Additionally, the Event triggered must be properly selected. In the example above, Cash is the first button in the menu. By editing the button, the General tab shows the Event is set to Cash Tender, the Button Label is Cash, and the Position is 1.
The Data tab is where this button is linked to the correct Cash Tender. In the Tender Maintenance view, the Cash Tender has a Tender ID of CASH-UK.
On the Data tab, enactor.mfc.TenderID must have the correct Tender ID specified in the Value field. In this example, the correct value is CASH_UK. If the value is incorrect, it must be changed to match the desired Tender ID.
If a new Menu Button is being added, there will be no pre-existing entry on the Data tab. In this scenario:
- Enter
enactor.mfc.TenderIdin the Name field. - Enter the appropriate Tender ID in the Value field.
- Press the +Add button before leaving the page.
All options on the Tender Menu must be linked to the appropriate Tender ID.
This completes the Tender Menu configuration.
This completes the POS Behavior (Menus) configuration. If additional variations of a menu are required for different Roles, Locales, or Menu Groups, the copy and edit process described in this guide can be repeated using the newly created menu as the starting point.
About This Document
| Document ID | HowToGuide-ConfiguringPOSBehaviorMenus |
| Product(s) | Enactor Estate Manager |
| Audience | Configuration Engineers |
| Author | Mark Harrison |
| Published | 27 Feb 2026 |
Document History
| Version | Author | Reason |
|---|---|---|
| 1.0 | Enactor Ltd | Initial version |
| 2.0 | Mark Harrison | Reformatted to Enactor documentation standard; figure blocks and AI metadata added (27 Feb 2026) |
© 2020 Enactor Ltd