Step 01: Select items and click price change button
In the initial step, the user is directed to choose specific items, presumably from a transactional list. Following this selection, the instruction advises the user to click on the “Price Change” button. The implication is that by taking this action, the user expresses an intention to modify the prices associated with the items they have selected. The “Price Change” button likely serves as the trigger or interface element to initiate the process of adjusting the prices for the chosen items within the transaction.
Step 02: Click “override” button in the popup screen
Once the user triggers the price adjustment, a popup screen emerges, and the user is instructed to click the “Override” button. The term “override” implies that the user is requesting authorization to make changes that might exceed their typical permissions. In this context, the user seeks approval to proceed with price adjustments that deviate from the established standard pricing, indicating a need for special authorization or permissions beyond their usual scope.
Step 03: Click administrator and change the price and enter okay
The user is guided to click on the “Administrator” option in the next step, signifying the requirement for elevated permissions to override prices. This action suggests a transition to an administrator mode, granting the user the necessary authority for altering the prices of the selected items. After making the required adjustments, the final step involves entering or confirming the changes by clicking on an “Okay” button or a similar confirmation option. This sequence of actions ensures that the user, now operating with higher-level permissions, successfully completes the process of modifying prices with the appropriate confirmation.
Introduction Video
