Skip to main content

How-to Guide - Configuring Voids


Introduction

This guide provides a foundational understanding of the options and capabilities available when configuring void functionality in the Enactor Retail System. Void functionality encompasses the full end-to-end setup required to enable void operations at the POS -- from defining the void types operators can perform, through to exposing those functions in the Sale menu and granting the appropriate user role privileges.

Void operations allow operators to cancel or remove items, transactions, or tenders from consideration. Common scenarios include a faulty item, a customer leaving the store, or an operator error.

Enactor supports four types of void operation at the POS:

  • Item Void - Allows an operator to mark a selected basket item as void, removing it from the active transaction.
  • Transaction Void - Allows an operator to void an entire active transaction before it is completed.
  • Post Transaction Void - Allows an operator to void a transaction that has already been completed, with optional time and value limits.
  • Item Tender Void - Allows an operator to void a tender (such as cash or card) that has been applied to a transaction.

The purpose of this guide is to demonstrate the steps required to configure void functionality in the Enactor Estate Manager: setting up the void types available at the POS, configuring the Sale menu to expose void functions to operators, setting up user role privileges, and broadcasting the configuration to the POS.


Overview

The following steps are required to enable void functionality at the POS:

  1. Item Voids - Configure item void operations to allow operators to remove individual items from an active transaction.
  2. Transaction Voids - Configure transaction void operations to allow operators to cancel an entire active transaction.
  3. Post Transaction Voids - Configure post transaction void operations, with optional time, value, and item count limits.
  4. Item Tender Voids - Configure tender void operations to allow operators to reverse an applied tender.
  5. Menus - Configure the Sale menu to expose void functions to POS operators.
  6. User Roles - Assign privileges for void operations to the appropriate user roles.
  7. Broadcasting - Deliver the configuration to the POS.

Prerequisites

Before starting, you should have the following resources in place:

  • Enactor Estate Manager
  • Enactor POS (configured within the appropriate region, connected to the Estate Manager)
  • Standard Configuration, including base configuration and regionally appropriate data

You should be familiar with the following:

  • Estate Manager configuration
  • Data broadcasting

Configuration Steps

Reasons are created based on a pre-defined Reason Type and associated with a Region in which they are applicable. Each Reason Type is known to a specific function of the POS application that is required to capture reasons of that type.

Item Void Reason

There are instances when a customer requires an item to be removed from the basket before proceeding with the transaction. The Item Void Reason allows marking a selected basket item as void.

Navigate to Reason Maintenance using Search or the path:

Configuration > Organisation > Reasons

The Reason Maintenance list is displayed, showing all configured reasons across all reason types. Use the Region and Reason Type filters to narrow the list.

Reason Maintenance list showing existing reasons including Item Discount and Transaction Discount types across multiple regions. Create a new Reason button is highlighted at the bottom.

The Reason Maintenance list shows all configured reasons. Click Create a new Reason to begin adding a new void reason.

To create a new Item Void Reason, click Create a new Reason and complete the following fields:

  • Select the appropriate Region from the Region drop-down.
  • Select Item Void from the Reason Type drop-down.
  • Enter a unique Reason ID for the new Item Void Reason. The ID can be alphanumeric and contain a maximum of 20 characters.

Reason Maintenance create screen with Region set to 'All Regions', Reason Type set to 'Item Void', and Reason ID entered as 'IV-AR1'.

Set Region, Reason Type to Item Void, and enter a unique Reason ID. Click Create to proceed to the reason detail screen.

Click Create. The Reason detail screen is displayed with the following tabs: General, Transaction Types, and Witness.

Reason - General Tab

The General tab contains the basic identifying information for the Item Void Reason.

Reason Maintenance General tab for Item Void Reason IV-AR1. Description is set to 'Item Faulty' with locale English (UK). All checkboxes are unchecked and optional fields are empty.

The General tab defines the reason identity and behaviour. Enter a meaningful Description and select a Locale. Use Function Authorisation Code to require manager authorisation before this reason can be selected.
ConfigurationDescription
DescriptionA user-friendly description for the reason. Can be alphanumeric, maximum 50 characters. Select the display locale from the dropdown.
Function Authorisation CodeSelect an authorisation code from the dropdown if this reason requires manager approval when selected. Codes are defined in Role Maintenance.
Capture Reference NumberIf checked, the operator is prompted to enter a reference number when using this reason.
Capture Customer Name and AddressIf checked, the operator is prompted to capture the customer name and address when using this reason.
Parent Reason IDIf a parent reason hierarchy is required, select the parent reason from the dropdown. The list shows all reasons of the same Reason Type.
Reason Start DateOptional. The date from which this reason becomes active.
Reason End DateOptional. The date after which this reason is no longer active.

Reason - Transaction Types Tab

The Transaction Types tab allows restricting this reason to specific transaction types. If no transaction types are selected, the reason is valid for all transaction types.

Reason Maintenance Transaction Types tab for IV-AR1 showing all transaction types unchecked, meaning the reason applies to all transaction types.

The Transaction Types tab restricts this reason to specific transaction types. If no types are selected, the reason applies to all transactions. Tick the applicable types to limit the reason's availability - for example, tick Restaurant Sale Transaction for a reason that applies only to restaurant transactions.

Reason - Witness Tab

The Witness tab is available for reasons that require the operator to obtain a witness when using this reason. If Capture Witness is checked, the operator is prompted for a witness whenever this reason is selected.

Reason Maintenance Witness tab for IV-AR1 with Capture Witness checked, Witness User and Skip Function Authorisation Codes set to default, and Capture Witness Rate set to 100%.

Tick Capture Witness to require a witness for this reason. Set the Capture Witness Rate as a percentage to define how often a witness is required relative to the number of times this reason is used - for example, 100% requires a witness every time.
ConfigurationDescription
Capture WitnessIf checked, the operator is prompted to obtain a witness when this reason is selected. Additional fields become visible when checked.
Witness User Function Authorisation CodeSelect from the dropdown to require the witness to have a specific authorisation code (e.g. Manager Authorised).
Witness Skip Function Authorisation CodeSelect from the dropdown to allow the witness requirement to be skipped if the operator has a specific authorisation code.
Capture Witness RateA percentage value defining how often the witness prompt appears. Enter 100 to require a witness every time this reason is used.

Click Save to complete the Item Void Reason.

note

Multiple reasons can be created for the Item Void reason type as required. All configured Item Void reasons are presented to the operator when performing an Item Void at the POS.

This completes the Item Void Reason configuration.


Transaction Void Reason

The Transaction Void Reason allows voiding an entire active transaction. This is used when a complete transaction needs to be cancelled - for example, when a customer changes their mind before tender is applied.

To create a new Transaction Void Reason, click Create a new Reason on the Reason Maintenance page and complete the following:

  • Select the appropriate Region from the Region drop-down.
  • Select Transaction Void from the Reason Type drop-down.
  • Enter a unique Reason ID. The ID can be alphanumeric, maximum 20 characters.

Reason Maintenance create screen with Region set to 'All Regions', Reason Type set to 'Transaction Void', and Reason ID entered as 'TV-AR1'.

Set Reason Type to Transaction Void and enter a unique Reason ID. Click Create to proceed.

Click Create. The Reason detail screen is displayed with the General and Witness tabs.

Reason - General Tab

Reason Maintenance General tab for Transaction Void Reason TV-AR1. Description is set to 'Customer Left Store' with locale English (UK).

Set the Description for the Transaction Void reason. The General tab fields are the same as for Item Void - refer to the field reference table in the Item Void Reason section above.

Set the appropriate values on the General tab. Field definitions are the same as described in the Item Void Reason - General Tab section above.

Reason - Witness Tab

The Witness tab is available for reasons that require a witness. Set the appropriate values as described in the Item Void Reason - Witness Tab section above.

Click Save to complete the Transaction Void Reason.

note

Multiple reasons can be created for the Transaction Void reason type as required. All configured Transaction Void reasons are presented to the operator when performing a Transaction Void at the POS.

This completes the Transaction Void Reason configuration.


Post Transaction Void Reason

The Post Transaction Void Reason allows voiding a transaction that has already been completed. This is used when a customer or manager needs to reverse a transaction after it has been tendered - for example, if the wrong items were sold or the transaction needs to be reversed for another reason.

To create a new Post Transaction Void Reason, click Create a new Reason and complete the following:

  • Select the appropriate Region from the Region drop-down.
  • Select Post Transaction Void from the Reason Type drop-down.
  • Enter a unique Reason ID. The ID can be alphanumeric, maximum 20 characters.

Reason Maintenance create screen with Region set to 'All Regions', Reason Type set to 'Post Transaction Void', and Reason ID entered as 'PTV-AR-1'.

Set Reason Type to Post Transaction Void and enter a unique Reason ID. Click Create to proceed.

Click Create. The Reason detail screen is displayed with the General, Post Void, and Witness tabs.

Reason - General Tab

Reason Maintenance General tab for Post Transaction Void Reason PTV-AR-1. Description is set to 'Post Void' with locale English (UK).

Set the Description for the Post Transaction Void reason. Field definitions are the same as described in the Item Void Reason - General Tab section above.

Set the appropriate values on the General tab. Field definitions are the same as described in the Item Void Reason - General Tab section above.

Reason - Witness Tab

The Witness tab is available for reasons that require a witness. Set the appropriate values as described in the Item Void Reason - Witness Tab section above.

Reason - Post Void Tab

The Post Void tab is specific to Post Transaction Void reasons and controls the limits and conditions under which a completed transaction may be reversed.

Reason Maintenance Post Void tab for PTV-AR-1 showing all numeric limits set to 0 (unlimited) and all checkboxes unchecked.

The Post Void tab controls the conditions under which a post void may be performed. Set limits to restrict when this reason can be used - for example, set Reversal Time Limit to 24 to prevent voiding transactions older than 24 hours. Leave all fields at 0 for no restrictions.
ConfigurationDescription
Reversal Time Limit (hours)The maximum number of hours after a transaction was completed within which a post void is permitted. Enter 0 for no time limit.
Reversal Days Limit (days)The maximum number of days after a transaction was completed within which a post void is permitted. Enter 0 for no day limit.
Allow Manual ReversalIf checked, the operator can perform a manual reversal of the transaction through the POS.
Transaction Value LimitThe maximum transaction value that may be post-voided using this reason. Enter 0.00 for no value limit.
Item Count LimitThe maximum number of items in a transaction that may be post-voided using this reason. Enter 0 for no item count limit.
Limit To Last Day EndIf checked, only transactions from the current trading day (since the last Day End) can be post-voided using this reason.

Click Save to complete the Post Transaction Void Reason.

note

Multiple reasons can be created for the Post Transaction Void reason type as required. All configured Post Transaction Void reasons are presented to the operator when performing a Post Transaction Void at the POS.

This completes the Post Transaction Void Reason configuration.


Item Tender Void Reason

The Item Tender Void Reason allows voiding a tender that has been applied to a transaction. This is used when a customer needs to change the payment method - for example, switching from cash to card after a cash tender has already been entered.

To create a new Item Tender Void Reason, click Create a new Reason and complete the following:

  • Select the appropriate Region from the Region drop-down.
  • Select Item Tender Void from the Reason Type drop-down.
  • Enter a unique Reason ID. The ID can be alphanumeric, maximum 20 characters.

Reason Maintenance create screen with Region set to 'All Regions', Reason Type set to 'Item Tender Void', and Reason ID entered as 'ITV-03'.

Set Reason Type to Item Tender Void and enter a unique Reason ID. Click Create to proceed.

Click Create. The Reason detail screen is displayed with the General, Transaction Types, and Witness tabs.

Reason - General Tab

Reason Maintenance General tab for Item Tender Void Reason ITV-03. Description is set to 'Invalid Discount' with locale English (UK).

Set the Description for the Item Tender Void reason. Field definitions are the same as described in the Item Void Reason - General Tab section above.

Set the appropriate values on the General tab. Field definitions are the same as described in the Item Void Reason - General Tab section above.

Reason - Transaction Types Tab

The Transaction Types tab restricts this reason to specific transaction types. Set the appropriate values as described in the Item Void Reason - Transaction Types Tab section above.

Reason - Witness Tab

The Witness tab is available for reasons that require a witness. Set the appropriate values as described in the Item Void Reason - Witness Tab section above.

Click Save to complete the Item Tender Void Reason.

note

Multiple reasons can be created for the Item Tender Void reason type as required. All configured Item Tender Void reasons are presented to the operator when performing an Item Tender Void at the POS.

This completes the Item Tender Void Reason configuration.


To enable the void functions at the POS, the appropriate menu events must be configured in Menu Maintenance.

Navigate to Menu Maintenance using Search or the path:

Configuration > System > Menus

The Sale Menu contains most of the functions required for a standard retail POS. Void functions are typically found under the Voids folder within the Sale Menu.

Menu Maintenance showing the SALE menu tree with eight top-level items including Voids at position 3. Action links for adding menu items are highlighted at the bottom.

The SALE menu tree shows all available POS functions. Void events are configured under the Voids folder. Use the action links at the bottom to add a new event item to the appropriate folder.

The following events can be added to the menu for each void reason type:

Reason TypeEvent NameEvent ID
Item VoidItem VoidItemVoid
Transaction VoidTransaction VoidTransactionVoid
Post Transaction VoidPost VoidPostVoid
note

Configuring Menus in detail is described in a separate how-to guide. Refer to the POS Menus guide for full menu configuration instructions.

This completes the Menus configuration.


User Roles

To allow operators to perform void operations, the appropriate privileges must be assigned to their user roles.

Navigate to User Role Maintenance using Search or the path:

Configuration > HR > User Roles

Select the role you wish to edit and navigate to the Authorised Functions tab. Set the Application Package to Enactor POS and the Process to the relevant void process to view and configure the void privileges.

User Role Maintenance Authorised Functions tab for SALES_ASSISTANT. Enactor POS Void Item process is selected showing four function IDs, with AuthorisesVoidItem and VoidItemAllowed checked.

The Authorised Functions tab controls which POS functions this role can perform. Filter by Application Package and Process to find the void privileges. Tick the required Function IDs to grant access to each void operation.

The following privileges can be configured for void operations:

Application PackageProcessFunction ID
Enactor POSVoid Itemenactor.pos.AuthorisesVoidItem
Enactor POSVoid Itemenactor.pos.VoidItemAllowed
Enactor POSVoid Transactionenactor.pos.AuthorisesVoidTransaction
Enactor POSVoid Transactionenactor.pos.VoidTransactionAllowed
Enactor POSPost Transaction Voidenactor.pos.AuthorisesPostTransactionVoid
Enactor POSPost Transaction Voidenactor.pos.PostTransactionVoidAllowed
Enactor POSVoid Tender Itemenactor.pos.AuthorisesVoidTenderItem
Enactor POSVoid Tender Itemenactor.pos.VoidTenderItemAllowed
note

Configuring User Roles in detail is described in a separate how-to guide. Refer to the User Roles guide for full privilege configuration instructions.

This completes the User Roles configuration.


Broadcasting

To deliver the configuration changes to the POS, broadcast the following:

  • Reason
  • Menu
  • Roles
info

All three entities must be broadcast to the POS before the void reason configuration will take effect. Restart the POS application after the broadcast has been received to apply the changes.

This completes the Broadcasting configuration.


POS Functionality

Item Void Reason Functionality

With items added to the basket, the operator selects the item to be voided. The item-specific function buttons are displayed at the bottom of the screen.

Enactor POS sales screen showing a basket with two items totalling £948.00. Main menu buttons including Voids are visible at the bottom.

Screen 1: The operator has added items to the basket. To void an item, select the item in the basket to highlight it.

Enactor POS with Samsung TV item selected (highlighted in cyan). Item-specific function buttons are shown including Item Void highlighted with a red box.

Screen 2: After selecting an item, the item-specific function buttons appear. Click Item Void to proceed to reason selection.

The configured Item Void reasons are displayed. The operator selects the applicable reason and clicks OK to apply the Item Void to the selected item.

Enactor POS Item Void reason selection screen showing four configured reasons: Customer Left Store (selected), Item Faulty, Operator Error, and Customer Left Store - Witness Capture.

The configured Item Void reasons are listed. Select the applicable reason and click OK to apply the void to the selected item.

Transaction Void Reason Functionality

With items in the basket, the operator selects the Voids function from the main menu to display the Transaction Void option.

Enactor POS Voids submenu showing three void options: Item Void, Transaction Void (highlighted with red box), and Scan Item Void. The basket contains two items.

After selecting Voids from the main menu, the void type options are displayed. Click Transaction Void to proceed to Transaction Void reason selection.

After selecting Transaction Void, the configured Transaction Void reasons are displayed. The operator selects the applicable reason and clicks OK to void the entire transaction.


Post Transaction Void Reason Functionality

The operator accesses the Post Transaction Void function from the management functions area of the POS when the basket is empty.

Enactor POS with empty basket showing the Post Void button highlighted with a red box in the function buttons at the bottom.

Screen 1: Navigate to the management functions with an empty basket. Click Post Void to begin the post transaction void process.

Enactor POS Post Void entry screen prompting to scan a transaction ID or use search options. Search button is highlighted with a red box.

Screen 2: Scan the transaction barcode to locate it directly, or click Search to enter transaction details manually.

Enactor POS Post Void search form with Original branch number pre-filled as 1. Other search fields are empty. Search button is highlighted with a red box.

Screen 3: Enter the original transaction details and click Search to display matching transactions.

Enactor POS Post Void search results listing transactions by Branch, Term, Trans, Date, Time, and Total. Transaction 17 (£299.00) is highlighted in blue. Select button is highlighted with a red box.

Screen 4: The search results display matching transactions. Select the relevant transaction from the list and click Select to proceed to void reason selection.

Item Tender Void Reason Functionality

When a tender has been applied to a transaction, the operator can select the tender line and use the Void Tender function to remove it.

Enactor POS tender screen with a Cash tender of £200.00 applied (highlighted in cyan) and Void Tender button highlighted with a red box. Balance due is £99.00.

Screen 1: Select the tender line to be voided in the basket (the Cash line is highlighted). Click Void Tender to proceed to reason selection.

Enactor POS Item Tender Void reason selection screen showing two configured reasons: Invalid Tender (selected) and Other. OK button is highlighted with a red box.

Screen 2: The configured Item Tender Void reasons are listed. Select the applicable reason and click OK to void the tender.

After the tender void is confirmed, the tender line is removed from the transaction and the balance is recalculated.

Enactor POS tender screen after Item Tender Void. The Cash tender line is struck through and highlighted with a red box indicating it has been voided. Balance is restored to £299.00.

After the tender void is applied, the voided tender line is shown struck through. The balance is restored to the full transaction amount and the operator can select a new tender.