Learn what's new in the 1.8.1 version of Emerald POS software for retail customers.

Version 1.8.1

May 30, 2023

Release Overview

This release includes the following information:

• New Features
• Fixes
• Known Issues

New Features

REF 558884: Catalog: Ability to Retrieve Dynamic Fields from Catalog and Apply to PE and Tlog based on Configuration

Emerald 1.0 was enhanced with the ability to retrieve dynamic fields that are not required for any calculation or function by Emerald, but need to be taken from the catalog and based on the ‘action’ passed on to other components, such as the Tlog, Universal Loyalty and Promotion (ULP) service, etc. For example, a ‘Cost’ field that may be used in a product margin report can be sent to the Tlog and used by the NCR Analytics reporting system, or a Promotion attribute relevant to the ULP used to trigger additional validations or calculations, etc.

• New RTIs were added to configure the mapping of the dynamic attribute fields from the catalog:

  • CatalogDynamicAttributeMappingMaintenanceRequest – used to configure the mapping of the dynamic attributes
  • CatalogDynamicAttributeMappingLookupRequest – used to retrieve the mapping of the dynamic attributes

  Based on the configuration, the POS performs the required action, i.e., passes the dynamic attribute to the Tlog, ULP, etc.

• New database tables were added to capture the dynamic fields from Cold Start and the Snapshot.

• The Tlog was updated with a new element called DynamicAttributes to capture the dynamic attributes received.

NOTE: In the future, the TDM Parser will parse all dynamic attributes (without setup).

REF 552686: Catalog - Ability to set Priority for Promo/Ad non-card price sent to ULP

NOTE: This feature is only relevant to the Unified Loyalty Promotion (ULP) service.

Emerald 1.0 was enhanced with the ability to determine the priority on price adjustments when sending Non Member promotion price adjustments with the price types Promotion Non Card and/or Ad Price Non Card to the ULP service. This enables the retailer to control price adjustments coming from Emerald in conjunction with promotions set up in the Promotion system.

The PricesPrioritiesConfigurationMaintenance Request RTI was updated with a new parameter called NonCardPriority with the option to define a priority. The value is a numeric value. The default is 1.

Once the non-card prices (Ad Price Non Card / Promotion Non Card) are sent to the ULP as an adjustment during the sales transaction, the pre-configured priority is included in the adjustment message and the system will apply the priority.

REF 561442: Catalog – Modify Poll Time to Reduce Calls

Emerald 1.0 supports a Catalog refresh mechanism, which is activated according to a Poll timer. The Poll timer is used by the CCM/StoreServer to check if there are new prices in the catalog ready to be downloaded to the store.

The Poll timer is controlled via a system parameter in the DataTransportationConfigurationMaintenance Request RTI called DownloadDelay. The value of the Catalog Poll timer was updated from 1 to 3 minutes (180 secs) to initiate polling less frequently after a clean install/upgrade.

This is only relevant to the Store Server and CCM.

NOTE: Following an installation/upgrade, the retailer must define the Poll timer (DownLoadDelay) parameter with the new definition for the store.

REF 548866: Donation – Enable Donation Items Based on Store Variety (Catalog)

Currently, Emerald 1.0 supports a donation feature, where the customer can select to donate (by selecting a donation item) directly via the PIN pad, or the cashier can add the donation item via the POS by selling the relevant item.

One or more items can be configured in the catalog for each charity organization. The BSP/Catalog interface supports a flag (item type) to identify Donation items. Once the item is downloaded to Emerald, Emerald is able to detect an item as a donation.

Emerald was updated to only display the charity options on the PIN pad based on the store variety to make sure only relevant donations are offered.

For example:

The Donation item ‘Red Cross’ may only be available in Store A, whereas the Donation Item Greenpeace may be available in Store A and Store B. On performing a donation in Store A, both the Red Cross and Greenpeace options are available.

To support the feature, the following configuration must be performed:

ProductMaintenance Request RTI (CCM and Store) - the ‘InVariety’ flag must be set to true for the specific items in the relevant store. TouchPointConfigurationMaintenanceRequest for the relevant Stores must be set with DonationsActivated set to true.

REF 460648: Age Restrictions, Receipt - Ability to Add Age Approval Message to the Receipt

Emerald 1.0 was updated with the ability to print age verification approvals on the receipt and the method by which the age restricted items were approved. This makes it clear during an external audit that the retailer checked the age of the customer before selling an age-restricted item. The Tlog already captures these details.

The message can be configured per item or per transaction and includes the entry method (keyed or scanned). If the Date Of Birth was entered, it can be masked.

In case of various age verifications policies in one transaction, all messages will be displayed.

For example, if the cashier sells two age restricted items related to two different age restriction policies and approves one by entering the customer’s date of birth, and the other by scanning the customer’s driver’s license, the receipt prints each one and its entry method

The CCM/Receipts Templates module was updated with a new Receipt Line Definition called Age Approval. The following printable data is available to define the template:

• PolicyID
• EntryMethod
• InputValue
• OperatorName

The new Age Approval template was added under the Items section in the Default Receipt.

REF 549148: Age Restrictions – Ability to Correct DOB for Age Restriction by Triggering the BRM On Demand

Emerald 1.0 was enhanced with an option to be able to correct a Date Of Birth (DOB) entered during an Age Restriction verification flow.

Currently, if the cashier enters a customer’s DOB incorrectly, there is no way to correct it and if the age entered is below the age restriction limit, the item is not added to the transactionthe transaction needs to be voided and started over.

With this development based on new configuration, the cashier will be able to perform an additional Age Verification flow to reverify the customer’s age.

To support this feature, the CCM was updated:

• A new ‘Age Verification’ POS function button was added to the CCM/Commands Menu to trigger an Age Verification flow in Sales Mode enabling the cashier to reenter the customer’s DOB.

  The Age Verification POS function can only be selected once in a transaction in Sales Mode.

  NOTE: To use this Age Verification command in Sales mode, you must configure the Age Restriction Policy with the new option, and to prevent the user from selecting the command twice, a BRM must be configured, both options described below.

• The CCM/Age Restrictions/New Age Restricted Policy screen was updated with the new option called Reverify Age Allowed to support the new Age Verification flow.

  If the cashier selects the Age Verification in Sales Mode, the system verifies that the Reverify Age Allowed parameter is set to Yes and that a DOB was previously entered. The POS prompts the Age Restriction flow for the cashier to reenter the customer’s DOB. The DOB entered takes effect immediately and any additional restricted items added to the transaction are then automatically verified according to the DOB entered.

• The CCM/Business Rules (BRM) Actions were updated with a new option called Reverify Age. This action is available for the existing BRM Type: Age Verification.

  • When the new Age Verification function is selected at the POS, if the Age Verification POS function was already selected in the transaction, the BRM is triggered to prohibit the Age Restriction flow from prompting again. The POS prompts a Prohibit message.

The Tlog captures the information from the new age entered via the new ‘Age Verification’ POS function as with existing functionality. In a scenario in which the first time the Age Verification was rejected, and the second Age Verification was approved, both are captured with the information of the item and the policy in two separate lines.

REF 561123: Business Rules - Refactor Delayed Coupon BRM to Improve Performance

Emerald 1.0 was enhanced to improve performance when resolving all Delayed Coupon Business Rules (BRMs) at the POS that require Manager Approval only.

Delayed Coupon BRMs triggered at the POS are displayed in the Intervention List prompted after the cashier finishes scanning the customer’s items before payment.

In the Intervention List, the cashier can select the Approve All button to resolve all the BRMS at the same time. Previously, on selecting Approve All, each coupon was sent separately to the Universal Loyalty and Promotions (ULP) to validate the coupon causing performance issues.

A new service called CouponAddBulk was added. The service sends all the coupons in a bulk request to the ULP reducing the time to resolve all the Delayed Coupon BRMs.

The Request bulk contains the coupons triggered from the same BRM.

If one of the coupons is rejected by the PE/ULP, the system prompts a message and will revert the request. In this instance, the cashier is required to approve the coupons one by one.

REF 497735: Business Rules - Propose to Add Items on Total (Support CA Carry Out Bags)

Emerald 1.0 was enhanced with the ability to charge a fee on carry bags to comply with government regulations which impose a bag fee on each carry bag used.

Carry bag items are created in the store catalog and linked to a PLU sub group.

The feature is implemented via a Business Rule, which is triggered when moving from Sale to Tender mode and is linked to the PLU Sub Group containing the carry bag items.

To support this feature the Total Transaction BRM Type is configured with a new Action type called Select Items, and when selected can be linked to the relevant PLU Sub Group.

When the BRM is triggered, the POS prompts a new screen called Carry Bags.

POS UI

The Carry Bags screen displays up to 4 different items (retrieved from the PLU Sub Group linked to the BRM. The first item on the list is in focus, i.e., highlighted with a green border. If the PLU has an image it is displayed. The screen includes the following options:

• Keypad - to enter the number of carry bags the customer uses. The OK key is used to move the focus (green border) from one item to the next.
• Scroll buttons – only displayed if the PLU Sub Group contains more than 4 items.
• Approve – to approve the number of bags used and add the bags to the transaction. If the cashier entered a quantity of bags and then after approving, updated the quantity to zero, the line is displayed as a void line.
• Skip button – to go to tender mode, i.e., no bags are added to the transaction and the POS goes back to Tender mode.

CCM The Business Rules (BRM) Total Transaction BRM Type was updated with a new Action type called Select Items. On selecting this Action type, you can link the relevant PLU Sub Group.

In the BRM Customer Order Condition, the following fields were renamed:

• Max transaction amount was renamed Transaction amount over
• Max transaction quantity was renamed Transaction items quantity over

For example, on moving to Tender mode, the BRM is triggered. The Carry Bag screen displays the first 4 carry bag items from the relevant PLU Sub Group. If the first item (in focus by default) is the correct bag type, the cashier can enter the number of bags used and select Approve to add the bag and the fee to the transaction.

Carry bag items are added to the transaction, printed on the receipt and captured in the Tlog.

REF 469005: Sale - Ability to Display Linked Items Combined or Separately

In general, there are different options to display linked items (Bottle Deposit Items and Warranty items) on the POS EJ, Customer Display, and Receipt. For example, an item can be displayed on one line, i.e., the main item and linked item price are combined and displayed in a single line, or as two separate lines, i.e., the main item is displayed on one line and the linked item under it on another line.

Emerald 1.0 currently supports different implementations and configurations for different display options.

Emerald 1.0 was enhanced to support additional options, and in this development, focus is on how Deposit/Warranty items are displayed on the POS EJ and Customer Display in Sales and Returns, and how Deposit Items are displayed in Price Queries.

A new RTI called LinkedItemsDisplayConfigurationMaintenanceRequest was added to determine how linked items for both Deposit and Warranty items are displayed on the POS EJ, POS Customer Display, and on the POS in an Item/Price Query flow with the following parameters:

• PosElectronicJournal – to define how the item is displayed on the POS EJ and Action Window
• PosCustomerDisplay – to define how the item is displayed on the customer display
• PosItemQuery – to define how the item is displayed when performing a Price Query (this only applies to Deposit items)

The available values are:

• Split – indicates that the main item and linked item are displayed on separate lines.
• Inclusive – indicates that the main item and the linked item are combined into one line

REF 555724: Tax - Item-Fee Tax with Fixed Value Which is Raised by Non-EBT item Should not be Exempted When EBT Food Stamp Tender is Used

Emerald 1.0 was enhanced to prevent exempting fixed rate taxes and fees collected for non-EBT items when paying with EBT Food Stamps in the transaction.

For example:

A fixed tax rate for Item fees may be set up and linked to a non-EBT item group. On adding an EBT eligible item and non-EBT eligible item to the transaction, the fixed tax rate for the non-EBT item is added to the transaction. On moving to tender mode if the customer pays with an EBT Food Stamp tender to pay for the EBT eligible item, which is exempt from tax, the fixed tax rate for non-EBT item remains in the transaction.

REF 425503: Usability - Enhance the PLU Menu to Control Information on the PLU Button (PLU Number and/or Price)

Emerald 1.0 was enhanced with the ability to display the item price and/or item code or both on the PLU buttons in the PLU Menu displayed on the POS.

Based on the option selected, the PLU button is displayed as follows:

• Price - the item image, description, and price are displayed on the PLU button.
• Code - the item image, description and code are displayed on the PLU button.
• Price and Code - the item image, description, price, and code are displayed on the PLU button. The CCM/PLU Menu Assignments module was updated with the following options:
• View – drop-down list for filtering. On filtering by Price, Code, or Price and Code, on selecting Retrieve, the PLU menus with the selected View option are defined.
• View – a new field in the grid. This enables the user to select the view by which they want the PLU Menu to display the PLU buttons.

A new View Picker was added. On selecting the View browse button from the grid, the following options are displayed: ItemPrice, ItemCode, and PriceAndCode. The selected option is applied to all the PLU Buttons in the PLU Menu in the assigned Location, Touchpoint Type and Touchpoint Group.

The same Menu that is linked to one touchpoint can be used for a different touchpoint but with a different View option selected.

The existing MenuDisplayTermsMaintenance Request RTI was updated with a new PluMenuItemDisplayOption parameter that can be configured with the following options: ItemPrice, ItemCode, or PriceAndCode.

This feature is also supported on the FuelPOS.

REF 554387: WIC EBT - Enhance LEB (Least Expensive Brand) Categories Management

Least Expensive Brand (LEB) policies is one of the ‘Item Selection Practices’ used by WIC agencies to control the costs of WIC food items.

Currently, Emerald 1.0 CCM supports a WIC LEB Categories module to retrieve the categories and sub-categories and indicate which Category/Sub-Category are the least expensive brand items from within all the items that are imported in the APL and a WIC LEB Inclusions module to include items in the selected category/sub category as LEB items. The user was required to manually select the LEB items that the retailer wanted to include.

With this development, on retrieving a list of Categories/Sub Categories in the WIC LEB Category /WIC LEB Category Inclusions – Select the LEB Categories screen, on marking a checkbox for a Category/Sub Category row, the system now automatically includes the items in the Sub Category as LEB items. Previously, each item in a category or sub-category in the APL file imported from the WIC Agency had to be manually marked as either LEB or non-LEB.

In the CCM/BRM module for WicNonLEBSaleApproval BRM types, the Scope field was updated with the existing Transaction option to allow configuring the BRM to trigger only once in a transaction. The rule is triggered when the first non-LEB item is added to the transaction. Once the BRM is approved, the rule is not triggered again in the transaction.

The Tlog captures the flag when an item belonging to a LEB category is purchased using a WIC tender as with existing functionality.

REF 497161: EPS, WIC EBT – Remove the Cashier Ability to Edit the Amount of a WIC EBT

Currently, in a transaction with WIC items, when an eWIC/sWIC card is added to the transaction, on checking out, the POS prompts the total WIC amount that will be paid for with the eWIC/sWIC tender. Till now, if the WIC balance was equal to the balance due, the POS processed the amount without cashier confirmation, but if it was less than the ticket balance, the cashier was able to approve or change the amount, causing an error since WIC transaction amounts cannot be adjusted.

Emerald 1.0 was enhanced to block the option of editing the eWIC or sWIC tender total amount displayed on the POS. This was added as a hardcoded feature and is not configurable, regardless of the EPS provider. The prohibit message is no longer prompted.

REF 564154: Receipt: Enhance the Display of Promotions on Department Grouped Receipt

Emerald 1.0 currently supports printing promotions on the receipt by the sales order, i.e., the order by which the items are scanned, or ‘By item hierarchy’, which is configured in the Receipt settings / Items / Item Grouping option. Till now, when Item Grouping was defined with ‘By Item Hierarchy’, the promotions were not printed under the relevant item under its hierarchy/department.

This feature was enhanced to align the printed data when grouped by hierarchy/department in the same way the data is printed when set to ‘Following Sale order’, i.e., the promotions are displayed under the item, but with this enhancement also under the hierarchy/department.

The discounts are printed below the items under the relevant hierarchy/department:

• Simple/Complex promotions
• Simple promotions are displayed inline, and the promotion discount is reduced from the item price.
• Complex promotions are displayed on a separate line and the promotion discount is not reduced from the item price.
• Items – promotions at the item level
• Items – promotions at the order level
• Items with linked items
• Items with linked items and multiple promotions

When the transaction includes multiple promotions with different levels (item/order level) and various types of items, such as linked items, etc., the POS will print a Grouped receipt. The promotions are displayed beneath the item.

REF 563131: Returns, EBT - Restrict the Return of EBT Tender on TBR and Return All

Currently, during a Return transaction (Transaction Based Return/Return All) the POS does not validate between the recommended tender and tender swiped at the POS.

Emerald 1.0 was enhanced to validate between the recommended tender and swiped tender at the POS, and in addition, to validate if there were restricted items in the original transaction.

The following changes were made:

• During a TBR the PIN pad is now blocked from being able to pre-swipe a card and is only open for ‘pre-swipe’ once the cashier selects the ‘Confirm’ button in the ‘recommended tender’ popup.
• The POS can now distinguish between the Tender Ids of the tender swiped on the PIN pad and the tender used in the original transaction, i.e., verify if the Recommended Tender Id is the same as the one swiped on the PIN pad.
• A new parameter called IsRestrictedinRefund was added to the Tender RTI to validate if the items being returned were paid for with a restricted tender, e.g., EBT, and make sure that the items paid for with the restricted tender are only refunded to the restricted tender, which is defined in the recommended tenders. The parameter is configurable via the Tender RTI only.
• False – indicates that the system allows returning all items to the recommended tender (up to the original amount paid) (Default).
• True – indicates that the system checks the restricted items that were paid for by the original tender and compares it to the recommended tender and allows refunding the amount of those restricted items only to the recommended tender.

A new message was added to prompt when the selected card for refund does not meet the configuration requirements. For example, on returning items in a TBR, if the Return Policy rejects the card entered for a refund, the system prompts ‘Card prohibited, please swipe {0} card’.

In a partial payment the system validates each payment separately according to the configuration (i.e., the system enforces the refund for the amount paid with the original the tender and not for each item). Therefore, if part of the transaction was originally paid for with a government tender, i.e., EBT or tender with restricted item, the system is able to force the refund on those items to the original tender. In addition, the system also validates the total transaction amount to prevent a scenario in which a refund to a restricted tender does not exceed the total amount paid with that tender, e.g., EBT.

The changes in this feature do not apply when the cashier selects the ‘Switch Tender’ function (existing functionality). If the cashier selected to switch tenders, the PIN pad is reopened for card entry.

REF 563004: TBR Fuel POS UOM Fix

Emerald 1.0 updated the Transaction Based Return (TBR), Return Transaction, Return All, and Return Item functionality on the Fuel POS to only display UOM (EA). In case of items sold by any other UOM, such KG, LTR, GL, etc., the UOM is not displayed, the line is displayed empty.

This change was done because item lines for items sold by other UOMs were not showing the full data, therefore, it is better to display the line empty.

REF 522412: Fuel – Support Split Payments in Prepay Transactions – Phase 1

Till now, Fuel Prepay transactions could only be paid for with a single tender, e.g., Cash or an EFT card. Emerald was enhanced to allow Fuel Prepays to be paid for with a combination of tenders and to enable closing the transaction by a defined tender closing priority.

Currently, this feature is supported when paying with Cash, EFT (2-phase (preauthorization/complete)), Personal Checks, and Stored Value tenders.

This feature is supported by both the Connected Payments (CP) and Epsilon providers.

A new parameter was added to the FuelConfigurationMaintenanceRequest RTI called ‘AllowPartialPaymentOnPrepaid’.

• If set to false, only one tender can be used in a Fuel Prepay (existing functionality) - default
• If set to true, more than one tender can be used in a Fuel Prepay.

In the CCM/Tenders module in the Fuel Definitions section (UI and RTI), a new field called ‘Prepay Closing Priority’ was added. This field indicates the order in which the POS closes / accepts tenders in an unbalanced prepay.

If configured for the defined tender, on closing an unbalanced prepay, the POS accepts the tender and will balance it based on the priority from the highest PrepayClosingPriority value to the lowest. The default is 0. When there are multiple tenders in the transaction with the same ‘PrepayClosingPriority’ value, the POS utilizes them in a FIFO order, i.e., the first tender that was used is the first to be utilized (or consumed).

No changes were made when performing a RIG (Rest in gas) or Fillup, split tender is not supported, only one tender is allowed to complete the transaction.

In scenarios in which the Prepay is fully utilized, EFT card tenders are closed by the EPS provider automatically (using preauthorization complete). The amount captured is the preauthorized amount for each tender. All manually reconciled tenders are used to fulfill the remaining balance.

In scenarios in which the Prepay is not fully utilized, if the tender is an EFT card that is auto reconciled, the utilized amount is captured with the EPS using the preauthorization complete process. If the tender is defined as manually reconciled, e.g., cash, the customer must return to the store to collect their change. To support this option, the ‘change’ options must be configured per tender.

The existing validation that validates the tenders used in a prepay was unblocked for Fuel Prepays.

REF 509926: Fuel – Add ‘X’ Quantity to the FuelPOS Keypad

The Emerald FuelPOS now supports the ability to sell items (non-fuel items) by quantity as on the regular grocery POS client. For Fuel items, the ‘X’ key is not enabled.

The Keypad is invoked via the Keypad function. On selecting a number on the keypad, the ‘X’ key is enabled. On selecting the ‘X’ key, the quantity is recorded. The cashier can then scan or key-in the item code to add the quantity of items to the transaction.

REF 472368: Fuel – Print Final Prepay Receipt at the Pump

The Emerald FuelPOS was updated with the ability to send transaction data to the Fuel EFS system to print the final prepay receipt at the Pump for balanced Prepays only, i.e., the full requested amount is fueled, saving the customer from having to go back to the store just for their receipt.

NOTE: This enhancement is only implemented with the EFS controller.

To support this feature, once the Prepay is authorized, the transaction details are sent to the EFS system in the existing ‘AuthorizeAndLimit2’ message under the Fuel Transaction data in an element with the following data:

• Merchandise Total - total amount of all the good (all non-tax and non-fuel items). If there were any promotions applied on the merchandise, the Total Amount is the amount after reducing the promotions.

• Merchandise Tax Total – the total of all non-inclusive taxes (Fuel items are always tax inclusive)

• Transaction Barcode (Suspended Receipt Barcode) – this is the transaction code captured when the prepay is suspended. It is the same code that the customer gets in the suspend receipt.

  This barcode can be used for an ‘Enhanced Reprint’ function to reprint the full receipt. The Full receipt contains the final barcode of the transaction, which can be used when searching for a transaction in a Transaction Based Returns/Return All.

The EFS system is responsible for printing the receipt and the receipt design.

If the Prepay is unbalanced, the EFS sends a message to the pump to prompt the customer to return to the store.

REF 558890: Upgrade Automation Fuel Labs with the Latest RFS Version Hosted by the Fuel Team

The Fuel server integrated with Emerald 1.0 was upgraded to version 10.33.3968.

REF 464385: L&P - Enhance the Loyalty Customer - Improve Customer Search and Add

Emerald 1.0 was enhanced to allow searching for Loyalty customers directly from the Unified Loyalty Promotions/Promotion Engine (ULP/PE) without having to first search for the customer in the CDM. This is based on configuration.

In the CCM/Customer Capture Policy module, a new field called ‘ULP Search’ was added in the Alternate ID tab.

• When set to Yes, on scanning a Loyalty card or entering the customer’s Alternate Id at the POS, a request is sent directly to the ULP/PE to search for the customer. Once the ULP/PE validates the Loyalty card, the customer is added to the transaction.
• When set to No, the system first sends a request to the CDM to search for the Loyalty member. If the customer is not found, a request is then sent to the ULP/PE. (Existing functionality).

REF 373148: L&P - Support Cashier Intervention Coupons

NOTES:

• This feature is dependent on the integration with the ULP/PE and will only work if the ULP/PE has completed the development on their side.
• Not supported on the FuelPOS.

Emerald was enhanced with an option to support a specific supplier coupon type (‘gThankU’ coupons that are neither really manufacturer or store coupons).

On scanning such a coupon, the POS sends the coupon data as is to the Universal Loyalty and Promotions (ULP) / Promotion Engine (PE). The ULP/PE returns a response with a new ‘Cashier Intervention’ request with a sub type called APPROVE_AND_ITEM, and the Coupon Value.

Once the POS identifies this response, the POS prompts a new screen triggered by a Business Rule. The screen displays the coupon value.

The cashier can approve the coupon value or manually enter the coupon amount before it is approved. The coupon does not require validation against a specific item, it is validated at the order level. Emerald currently supports the data pattern required for such coupons to be accepted.

To support this feature, the following changes were made:

• POS UI - a new screen called ‘Cashier Required Data’ was added.
  • The screen includes a field called ‘Coupon’s Value’. The field is automatically populated with the coupon’s default value, i.e., the coupon threshold.
  • New validations were added to validate the Coupon Value based on the cashier’s action.
    • If the cashier approves the coupon (up to the coupon threshold), it is added to the transaction.
    • If the cashier changes the coupon value to an amount greater than the coupon threshold, the value is rejected and not added to the transaction.
    • The cashier can change the coupon value to an amount less than the suggested coupon amount, but not less than the total basket amount.
    • If the cashier voids an item that is already attached to the coupon, the POS prompts the cashier to void the coupon first and then the item.
• New messages were added, which are prompted if the new validations fail. See the Text Resources section for details.
• CCM Office/Business Rules/Unused Coupon Business Rule Type:
  • Conditions Tab – the Rule Applies to field was updated with a new reason code called CASHIER_INTERVENTION.
  • Action Type – a new action type called Coupon-Cashier Intervention was added. When the BRM is triggered with this action, a Coupon Require Data screen is displayed.
  • Reason Codes Module - The Unused Coupon Reason Code Group was updated with a new Cashier Intervention Reason Code.

REF 554259: L&P - Loyalty Points Reversal on TBR and Return-All

Emerald 1.0 was enhanced with the ability to return the points earned or redeemed by a Loyalty customer when returning items in Transaction Based Return (TBR) and Return All transactions.

On returning an item, the system identifies the Loyalty Member added in the original sales transaction and adds the Loyalty Member to the return transaction. The returned points are then added or deducted from the Loyalty Member’s account.

NOTE: Currently, AMS does not yet support returning the points redeemed in a sales transaction back to the loyalty account in a return transaction.

The returned points are printed on the receipt and captured in the Tlog.

In the CCM Return Policy module/Details tab, a new field called ‘Apply original Loyalty’ was added for TBR and Return All transactions.

• If set to Yes – specifies that when a TBR or Return All transaction is performed and the original sales transaction contains the Loyalty Member, the Loyalty Member is automatically added to the return transaction.
• If set to No – specifies that the Loyalty Member added to the original sales transaction is not added to the return transaction. (Default value)

In the Receipt Templates module, a new ItemLevelPoints Line Definition was added to the Items SectionName to print the earned and redeemed points on the receipt. The line definition was added to the Default LayoutLine Template.

The Tlog was updated to capture the points earned and points returned.

REF 554386: Customer Display - Support a 2/4 Line Customer Display Device – Phase 2

The Emerald POS was enhanced to support a 2 or 4 line Customer Display.

A 20 character based, 2 (or 4) line Customer Display is supported.

The following table shows the text displayed on the Customer Display in each POS Mode.

REF 542547: FLSCO – GoToPOS Block Moving to Tender Mode on POS when Using GoToPOS using the Config File

The ability to block the option of moving to tender mode while in POS mode after moving from the Fast Lane SCO mode using the GoToPOS function was added by configuration.

If the FLSCO attendant approaches the SCO lane and performs a GoToPOS to handle an intervention or issue on the SCO, after solving the problem if they select OK to move to Tender mode, the POS prompts an error to prohibit moving to tender mode.

This enables the retailer to prevent the attendant who may have moved to POS mode to handle issues on a FLSCO lane, e.g., manual weight, BRM override coupons, etc., from moving to Tender mode and completing the transaction with cash, which can cause discrepancies.

Vouchers that can be scanned in sales mode will be added to the transaction, however, in this scenario, the system is also blocked from automatically moving to Tender mode.

The configuration is performed via the SCOStateNavigationRules.xml, which was added to the installation package.

REF 558108: Hardening & Improvement and Reconnection to Fuel Components

Emerald was enhanced with the ability to configure the time the system waits after a communication timeout between the TcpCom Client and Fuel server. Once the specified time has elapsed, a reconnect call is sent until the Fuel server and TCP connection is successfully restored.

A new parameter called TcpComReconnectWaitTime was added to the DeviceConfigurationAdd RTI. The parameter specifies the number of milliseconds to wait after a communication timeout after which the device sends a reconnect call.

REF 556962: Item Scan Duration - Automation

A range of technical infrastructure changes were made to improve the ‘item scan duration’ and general performance during sales.

Large basket scan performance issues were addressed with a result of improvements in item scanning efficiency, ticketing time efficiency, and overall processing times that were previously slower.

REF 558884: Adjustments for Order Services V3

Emerald 1.0 made adjustments in the integration with the BSP Order Service following changes from V2 to V3, which broke backward compatibility.

Following these adjustments, all testing passed successfully.

Resolved Issues

The following defects were fixed in this version:

• TFS552170 Suggested Amount was not rounded when payment with a tip was allowed.
• TFS554015 When the cashier was logged off from the lane and the POS had no active user, the transaction could be continued in Sale Mode. (Phantom user issue).
• TFS554460 The Description field was empty in the ItemHierarchyLookup response.
• TFS555522 The POS displayed an unhandled exception error when attempting to suspend a transaction that contained a Team Member Loyalty Card that generated a Member Discount.
• TFS555595 The POS froze when using voucher X.
• TFS556906 Print Receipt - Items with price after discount - Default Configuration – The $ sign was missing from the receipt.
• TFS557045 Swiping a card on the Choose/Find transaction screen in a TBR flow caused the PosClient to switch to Sale Mode.
• TFS557047 Private Charge received an error.
• TFS557176 Stored Value Tender Type – The POS did not prompt for a Loyalty entry when the tender was defined with ‘Open Amount with suggested options’.
• TFS557347 Tender Exchange - Age Restriction - When one tender Payment and one Tender Refund was configured, a ‘General error occurred. Please contact your System Administrator was prompted’.
• TFS557373 The Receipt was not printed as expected TBR flows.
• TFS557383 Additional logs for ColdStart were required - Import flow.
• TFS557657 Price Override – The Original Price in the Price Override screen after transaction recall for Warranty Items was incorrect.
• TFS558142 ExemptFixedRateWhenPayingWithGovermentTenderFixedFee_Step10to16() – The POS stuck after an exception error was prompted.
• TFS558466 Upgrade after CCM upgrade V1.2.340 ->V1.7.202 - Data Export service failed to run.
• TFS558630 The PosClient stuck in the Amount screen in a Tender Exchange flow.
• TFS558991 During a TBR Refund, the scanned UPC barcode from the sale returned an ‘Item Not Found (Able to Return when selected from Ticket Zone)’.
• TFS559101 The ‘Small box’ button did not respond for Tare Weight.
• TFS559386 The WicGetCategoryLEBInclusions business service response was missing the first item in each none-zero page.
• TFS559481 Tender CashCheque (tender 5) created the wrong in Basic RTI and did not allow partial payment - ‘Closing Tender without Message’ exception was prompted.
• TFS559523 Prepay by Volume – When Loyalty was removed from the transaction, a ‘Limit LTR of Promotions in case of only 1 Promotion that trigger according to Loyalty customer’ message was displayed.
• TFS559703 After not allowing a lottery ticket cashout during an Age Verification, there was no way to exit the Tender Exchange screen.
• TFS559896 The Weight was not shown in decimal format in the receipts.
• TFS560052 There was a text error in Balance inquiry.
• TFS560153 The recharge Gift Card process used the ExternalId of the previous scanned tender.
• TFS560300 Print Receipt - Items with price after discount - Default Configuration – The $ sign was missing from the Receipt
• TFS560345 The Product Lookup response was not as expected.
• TFS560387 Loyalty and non-loyalty discounts were not printed on the receipts.
• TFS560403 PLU Groups - Retrieving Item lookup threw an unhandled exception.
• TFS560418 When a check was declined by the host, Emerald promoted the wrong message instead of the declined message.
• TFS560792 When a customer was replaced (using remove customer) in the middle of a Prepay transaction – 'Customer Approval' promotions was not re-prompted.
• TFS560886 The CCM client did not work - opened with an exception.
• TFS560914 Price Override (Extended and Pre Price override) was not working for GS1 Barcode with linked item (Deposit or Warranty) when the Link Group policy was not configured.
• TFS561185 Go To POS was randomly not working after idle time.
• TFS561414 A 'General error occurred' error message was prompted when using Manual EFT and a Reset occurred.
• TFS561573 A general error occurred when a Promotion item with a quantity was voided by code.
• TFS561746 Online Item exception occurred.
• TFS561788 CCM – The ‘Save’ button did not respond.
• TFS561829 The POSClient application crashed when the ‘Close’ button was pressed before all the MFR coupons limits were approved in the Intervention List screen.
• TFS561848 Gift Receipt flows could not be performed using the customer details on the POS.
• TFS561853 DMS failed after a ProductMaintenance Request.
• TFS562044 Display price per UOM - Default Configuration Standard POS - The price and Weight were not displayed in the EJ line.
• TFS562267 The Product lookup response was not as expected.
• TFS562397 The last transaction log could not be retrieved.
• TFS562398 The Sequence contained more than one element.
• TFS562399 When exchanging a currency from GBP to USD, the currency conversion failed.
• TFS562636 Assert failed.
• TFS562776 Item scan performance fix.
• TFS562801 The ‘Confirm’ dialog showed a ‘General error’ if the ‘Cancel’ button was clicked after the ‘Confirm’ button.
• TFS563099 Selecting Approve Manager on Intervention List disabled all the buttons.
• TFS563106 MTX ‘Card Conversion’ not as expected.
• TFS563188 ‘Error code = 114’ from the MICR caused the cashier to be unable to directly interact with the POS requiring a POS bounce.
• TFS563279 Tare quantity percentage was not reflected in the Tlogs.
• TFS563293 Driver License could not be scanned or entered manually in a Tender Exchange with a large check.
• TFS563316 Deposit linked item quantity was not reduced after void by code.
• TFS563319 The Tax symbol was not displayed on the POS EJ for warranty items
• TFS563425 POS Server Version was unavailable for some touchpoints.
• TFS563537 The Line Display Simulator was not working as expected.
• TFS563682 In a PAK, the Manual Fuel screen opened for a few seconds when working with Epsilon.
• TFS563880 The PLU Menu was displayed when the user launched the POS for the first time and disappeared if the same POS was launched again.
• TFS564037 Age Verification for Tenders – Could not select the tender amount when an age verification was cancelled even though it was approved.
• TFS564126 The ‘How Many Bags You Bring’ Carry Bags screen did not respond after clicking OK or approval.
• TFS564136 When paying with a voucher, unexpected text (expiration date) was printed in the receipt.
• TFS564240 Dollar Sign placement on the Coupon Intervention screen was incorrect.
• TFS564281 Tender Exchange from Coin/GC redemption (Voucher ) to Gift Card.
• TFS564288 A ‘Promotion Engine Not Available’ error was prompted and then a promotion engine error occurred
• TFS564309 DMS download did not work in the lab.
• TFS564405 Token Tender caused the screen to go ‘blank’ in the Tender Amount screen.
• TFS564532 The SCO Msg index was outside the bounds of the array when scanning a coupon.
• TFS564535 1.7.1 to 1.7.3 Emerald upgrade issues.
• TFS564589 All labs failed on Pos build in method R1Connection – The RTI response sent an error.
• TFS564668 New Bug - EBT Food Stamp card could be used to purchase alcohol (non-EBT item).
• TFS564812 Fail to print in lab – Get Print error.
• TFS564839 The Multiply button was disabled.
• TFS564873 Fuel POS - Return 1 item from 5 - Wrong text was displayed in the EJ ‘Filled Cookies 1 / 5 112.50’.
• TFS564935 Selecting the 'Logout' button on the sidecar during receipt printing caused the POS to get stuck.
• TFS565284 Unfuel Prepay – A 'General Error' occurred at the Fuel POS.
• TFS565377 If a Tender was restricted for Paid Out with any EFT Tender, a ‘Payment Declined by Provider’ error message was prompted on the POS.
• TFS565481 The Item Search screen showed the 'Sale' starburst icon on the screen, even though nothing was on sale.
• TFS565663 The Loyalty icon uploaded for levels in the CCM office was not correctly displayed on the POS.
• TFS565919 Multi version CCM V1.7.300 -> Store server V1.5.102 – Coldstart Failure
• TFS566076 Fuel Prepay - When moving to tender with a credit card, the following was prompted ‘Must Be Paid with Cash, Debit’
• TFS566104 Tender Exchange with Bottle Return Slip generated a ‘General Return Error’.
• TFS566191 The POS was locked with an EftRecoveryFailed error on the screen.
• TFS566200 After upgrade to 1.7.202, loyalty customers could not be removed after from the transaction.
• TFS566240 EBT FS covered non-FS items.
• TFS566245 The ReceiptConfigurationParameter class contained lazy loaded properties which prevented the usage of the cached class instance out of the scope of the original session in some specific scenarios.
• TFS566259 The ‘Dummy’ Cashier name in Receipt CP block had to be replaced with ‘Unknown’.
• TFS566268 The Tlog did not record cancelled age restricted items.
• TFS566269 The POS stuck with a ‘General Error’ when ‘Trigger as Delayed was set to YES for SCO.
• TFS566347 FUEL POS - Pressing the Amount Due button when a transaction is tendered, triggered Emerald to prompt the cashier to shut down and restart the lane.
• TFS566494 An incorrect popup message was prompted when performing a Balance Inquiry using a debit card.
• TFS566608 The ‘BarcodeMappingManagement’ business service responded with the ‘An error occurred while updating the entries. See the inner exception for details’ error if the existing map was updated.
• TFS566682 Fuel - Prepay with Fill Up - Visa card configured as Open Amount in Immediate Tendering Option - When moving to Tender mode and scanning a credit card – an edit text box to enter the amount was opened.
• TFS566784 Unable to complete age verification when a Driver License was scanned a second time.
• TFS566843 Printable Data - Missing Information.
• TFS567011 The Household name was missing on the receipt.
• TFS567212 The Age Verification screen was prompted even after approval.
• TFS567308 Emerald displayed incorrect discount breakup on the UI, when the transaction contained multiple multi-quantity items and the customer was added to transaction at the end (i.e., after the items).
• TFS567377 There was an issue with the installation of last trunk version on station with an old SQL.
• TFS567409 The Velocity report had the wrong font and alignment.(manager approval - more info).
• TFS567450 PrePay Split Payment - Stored value with mixed tenders - Balance, unbalance, unfuel – Transactions were not closed.
• TFS567516 Unbalance PrePay Split Payment with EFT 1 Phase -a message was prompted when trying to close a transaction at the POS.
• TFS567522 Server unit testing failed.
• TFS567523 Unable to complete/void a transaction in a Toggle POS.
• TFS567524 ‘Insufficient privileges’ was displayed without giving any credentials in the Approval Message prompt.
• TFS567614 Automatically resumed prepay transactions interfered with starting a new prepay transaction on the Fuel POS
• TFS567677 Order level promotions were duplicated on the receipt.
• TFS567684 Transactions with Linked Deposit items could not be closed with cash, and an exception was prompted.
• TFS567700 Return Items when the transaction total is negative were displayed as ‘Sale’ instead of ‘Refund’ on the P400 PIN pad.
• TFS567745 Testing failed with 'Business Service "SetDateDiffService" Not Found' in the labs.
• TFS567805 When an eWic item with NTE was sold more than once in a ticket, the values of WICNTEAmount and the WICNTELostAmount in the Tlog were incorrect.
• TFS567806 The ‘Paper near end’ warning message was suppressed until the paper ran out.
• TFS567852 Unbalance PrePay Split Payment with EFT ss Phase - After Unbalance Prepay - Press Pay button - 'Can't finish transaction when 'PreAuthorization' was done without 'Complete' was prompted.
• TFS567860 PrePay Split Payment with Epsilon - Partial payment with EFT - When moving Tender Mode to Sale Mode and then back to Tender Mode - the amount in Pay button was incorrect.
• TFS567870 PrePay Split Payment with EFT 1 phase –Extra data was printed.
• TFS567968 Biometrics – The POS stuck with processing a screen when a BRM was approved by a fingerprint.
• TFS567979 An unhandled exception occurred when a customer was added at the POS
• TFS567980 Critical issue due to changed BRM RTI.
• TFS567981 An unhandled exception message was prompted after scanning a coupon in the FLSCO.
• TFS568039 When an eWic item with NTE was sold twice and there was a discount on one of the items, the value of TransactionTotalWICNTELostAmountin in the Tlog was incorrect.
• TFS568068 TBR failed when the price override failed
• TFS568084 Toggle – An unhandled exception occurred while trying to complete the transaction.
• TFS568085 PendingForRetryLookup - Transaction ID was incorrect. Seemed to be the ProccessId.
• TFS568086 PendingForRetryLookup – The Touchpoint was not the Original TP (currently it is touchpoint 200 which closed the transaction)
• TFS568087 PendingForRetryLookup – The Worker ID value was the Original Worker and not the Forecourt Worker
• TFS568100 Split with Unbalanced – The wrong message was displayed when trying to void Payment.
• TFS568124 Store&Forward - When finalizing prepay failed in a Promotion, the FailureStep was incorrect.
• TFS568155 Catalog data updates on the Store Server resulted in a stuck token as a result of attempting to apply to Hierarchy Nodes with a Null code value in the registers.
• TFS568195 TBR - Search for transaction by a Credit card did not retrieve the transaction.
• TFS568344 TBR/Return All transactions were not completed without point reversal.
• TFS568354 UnBalance PrePay Split payment with mixed Tenders - Visa and Stored Value – When working on MTX, the transaction stuck on the POS.
• TFS568380 The Price Override screen was not displayed after selecting the OK button in a error message prompted in the Extended Price Override screen in a TBR.
• TFS568448 Check cashing in Tender Exchange prompted a ‘General Error occurred’ message if the None button was pressed during identity verification.
• TFS568569 An error occurred while trying to modify the Coupon Limit BRM.
• TFS568629 Force cashier log off with an active transaction caused the POS to get stuck on the “Welcome Shopping Cart On Next Log In’ screen.
• TFS568660 A ‘General Error Occurred’ message was prompted when the POS performed a Top up.
• TFS568663 The POS prompted 'Failed mapping customer order to Basket' message and Return items could not be added to a sale transaction or vice versa.
• TFS568846 Pap2Pak and Manual Fuel – The POS stuck on the Manual Fuel Form and could not continue. After rebooting the POS, the form was empty.
• TFS568880 The AlternativeItemID was missing when performing ItemLookUp.
• TFS568883 Product/Department BRM was not working in return transactions.
• TFS568974 The Product Lookup response included an unexpected Priceid.
• TFS569071 Server unit testcases failed.
• TFS569220 ‘Error code = 114’ from the MICR caused the cashier to be unable to directly interact with POS requiring a POS bounce.

Known Issues

The following defects remain open in this version:

• TFS564817 Fuel Prepay with Volume - The OK button remains disabled after selecting the Nozzle and entering an amount greater than zero.
• TFS566778 Enhanced Reprint - Reprint All - The final receipt for suspended transaction barcodes is not printed.
• TFS568338 Sometimes communication with the Emerald Server fails when configuring Receipt Settings.
• TFS568567 Additional Age Verification is not working as expected.
• TFS568789 Fuel POS - POS Testing -The Tender menu does not allow navigating to the Tenders, and payment cannot be continued.