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

Version 1.6.3

October 13, 2021

Release Overview

This release includes the following information:

• New Features
• Fixes

New Features

REF 359488: Tender: Support Payment and Refund on Account – Charge Account Tender
Emerald was enhanced to support payments and refunds on account during checkout at the POS. Customers registered with a loyalty ID and a 'Charge Account' associated to the retailer can purchase items at the POS and charge them to their account. The POS is not requested to execute any real time authorization against the customer 'charge account'. The POS will automatically approve any Payment/Refund if the shopper is registered as a loyalty customer with a 'Charge Account'. Retailers who support this feature maintain a separate system to handle payment and balancing of the customer's charge account. These systems get the customer payment total amount/debts from the Emerald Canonical TDM and charge the customer accordingly. Emerald supports the new feature by using the existing Stored Value tender type, which can already be set up with a dependency on a loyalty member and loyalty account as a requirement. The Stored Value tender type was updated with an option to enable the tender to be set up without the need for EPS authorization, indicating that the payment is not authorized via an EPS provider. Payment, Refund, and Tender Exchange flows are all supported.

REF 483318: Receipt Add the Ability to Print the Loyalty Card Number
Currently, Emerald supports the ability to print a masked customer's loyalty ID (2 last digits) by the logic described below:

• Print a masked alternate ID when the customers are introduced by their alternate ID (e.g. phone number).
• Print a masked Loyalty Card Number when the customers are introduced by their Loyalty Card.
• Print a masked CAN number when the customers are introduced by their name. This is implemented by configuration in the Receipt Templates using the parameter called Masked Loyalty ID. Emerald was updated to print the customer's full loyalty card number on the receipt regardless of the way the loyalty customer is introduced. This is available by configuration of a new parameter called LoyaltyCardNumber. It can be printed in the Header, Footer, or Loyalty section of the receipt. Both the MaskedLoyaltyId and LoyaltyCardNumber can be printed on the receipt. Once the LoyaltyCardNumber parameter is configured and added to the receipt, after a sale or return transaction that includes a loyalty card, the customer's loyalty card number is printed on the receipt in the relevant area, i.e., Header, Footer, Loyalty section.

Note: The option to mask the number on the receipt can be achieved by using a new capability that was added as a general capability to manipulate any string parameter printed on the receipt.

REF 483318: Receipt Manipulate String Parameters
Emerald was updated with the ability to manipulate printable string parameters before they are printed on the receipt. The option can be applied to any string parameter. For example, print the last 11 characters of the customer's Loyalty Card Number starting from position 4. For Loyalty card Number 560400000000079, the string that is printed on the receipt is: 00000000079

REF 506910: L&P Search Loyalty Customer by a Fixed Prefix and a Customer Number
Today, a customer can be identified as a loyalty customer by a loyalty card number given to them when registered on the loyalty system or by an alternate ID the customer selects when they registered on the loyalty system. When searching for a customer at the POS, the option to search by Loyalty card ID, customer first and last name, Alternate ID, or phone number and Alternate ID is supported. There are retailers who do not maintain their loyalty members at their HQ level, and the customers have a unique member number valid in a specific store only. This means that the same specific loyalty number may be associated to two different customers. Emerald was updated with the ability to handle such retailers' loyalty members enabling the cashier to search for the loyalty member by a number provided by the customer. The feature is supported on search by Alternate ID at the POS.

REF 503072: L&P Emerald to Integrate with the ULP V2 instead of ULP V1
Emerald POS upgraded the ULP integration from ULP version 1 to ULP version 2. The Emerald POS functionality is now working with the ULP version 2 where the Promotion Engine (PE) is either the AMS/UE or LPRO/LPE. All functionality is working as expected.

REF 507097: L&P Drive Cost Plus Discounts, by Sending Cost Price from the Catalog to the PE
There are retailers who support Cost Plus discounts for their loyalty members, such as industrial customers (restaurants) who buy their products from the retailer's stores. A Cost Price is a 'Price' paid to the supplier and the Plus is calculated according to the loyalty member's level/tier. Emerald can now drive Cost Plus Discounts by sending the Cost Price from the Catalog to the PE. For example: The Item Cost price is $5.00 and the Item price is $10.00.

• A High Level Customer can buy the item by cost + 10%, i.e., $5.50.
• A Medium Level Customer can buy the item by cost + 20%, i.e., $6.00.
• Non Loyalty Customers can buy the item by the Item's full price $10.00.

Giving a cost-plus price to a customer is based on triggering a promotion that will reduce the regular item price to the cost-plus price.

REF 504737: Support GS1 Barcode with Amount/Weight
Till now, Emerald only supported GS1 barcodes for products/items and coupons. For coupons, Emerald just identified the barcode is a coupon and sent it as such to the Promotion Engine for further analysis. For products, Emerald just used the GTIN (01) AI for finding the item in the Catalog. In addition, Emerald supported amount embedded barcodes for 'Variable price' ('prepacked' /'on the spot prepared') items, such as cheese that is weighed in front of the customer at the dairy. Emerald was updated to support selling, returning, and voiding 'Variable price' items introduced by GS1 barcodes. The following GS1 barcodes are now supported:

Regular Price Barcodes:

GS1 Amount Embedded barcode – this barcode will have the same functionality as the Emerald Amount embedded barcode, just with the following GS1 AIs

• (01) GTIN
• (392x) amount

GS1 Amount and Weight Embedded barcode – this barcode introduces a new functionality where the weight of the item will be taken from the barcode. Barcode will include the following GS1 AIs:

• (01) GTIN
• (392n) amount
• (320n) weight

Markdown Price Barcodes These barcodes are used to sell reduced price 'variable price' items and automatically execute a price override. Used by retailers to increase sales, e.g., for items that may go to waste at the end of the day such as sandwiches.)

GS1 Override Amount Embedded barcode - this barcode will have the same functionality as the Emerald Override Amount embedded barcode, just with the following GS1 AIs

• (01) GTIN embeds the original amount of the item in addition to the item code.
• (392x) new amount

GS1 Override Amount and Weight Embedded barcode - this barcode introduces a new functionality where the weight of the item is taken from the barcode. The barcode will include the following GS1 AIs: (01) GTIN embeds the original amount of the item in addition to the item code. (392n) new amount (320n) weight

Note: The GS1 is a common industry standard used to create product barcodes. For More information on GS1 barcode formats look at: https://www.gs1us.org/industries/emerging-topics/gs1-digital-link AI is the Application Identifier, GTIN is Global Trade Item Number which is usually the item UPC.

REF 488287: Sale Transaction A/B Transaction Toggle
Emerald POS touchpoints are now supported as part of a solution in which the POS can toggle between two transactions concurrently using a dual output belt lane. This enables the cashier to process two customer's transactions at the same time on a single POS, making the checkout process much faster. The POS comprises a single terminal, payment reader (PIN pad), scanner, scale, printer, and customer display. There is one lane, also referred to as a belt that splits into two lanes (takeaway belts).

Once the cashier starts a transaction on the POS, they can start another transaction using the toggle between Lane A and Lane B. i.e., move from one to the other. The Active lane is the lane on which the cashier is working. All the POS peripherals, i.e., the scanner, etc., including the PIN pad are available for the Active transaction. The Inactive lane is the one on which there is a live transaction waiting to be completed/paid once the customer finishes bagging their items. For example, the cashier can scan Customer 1's items and sends them down Lane A. The customer then goes to the end of the lane and starts bagging their groceries. At the same time, the cashier starts scanning Customer 2's items and starts sending the items down Lane B. Customer 1 then completes bagging and would like to pay, so the cashier pauses the current active transaction on lane B, which becomes In Active, and toggles to the Inactive transaction on lane A, which now becomes the Active transaction and the cashier can complete payment. The cashier can toggle between the transactions until both are completed. The cashier decides which lane to send the items down, i.e., A or B by physically placing a barrier on one lane to drive the items to the free lane. The POS is agnostic to which physical lane is A or B. All existing functionality is supported on the POS in both Lanes A/B, i.e., scanning the customer's loyalty cards, items, coupons, etc. The new toggling option is controlled by configuration of a new Touchpoint Group defined in the CCM called Toggle. This solution is only supported when POS is integrated with Aurus EPS.

REF 509901|512771: WIC EBT: Remove/Add Items from/to WIC EBT after a Card is Introduced and Prior to Payment Completion
Currently, once a customer's eWIC/sWIC card is introduced on the PIN pad the utilization process is completed determining the WIC item amount covered by the customer's eWIC/sWIC card. At this stage the customer cannot make changes to the WIC EBT basket unless the cashier/customer first cancels the WIC card. Emerald was enhanced to support a new option in which the customer can request to make changes to the items in the WIC basket that they are purchasing with their eWIC/sWIC card after the card was introduced to the transaction, and before approval of payment. The customer can request to remove an item from being paid for with their WIC EBT card and pay for the item with a different payment mean, the system automatically covers a different item (if available) to maximize the WIC card balance, or the customer can request to add an item to the basket that may be able to be covered by the WIC EBT card, for example, select to pay for a more expensive item with the WIC EBT card. Every change triggers the Utilization process to rerun always automatically maximizing the WIC EBT card balance. Any changes to the WIC EBT basket are supported without having to re swipe/dip the customer's eWIC/sWIC card on the PIN pad again. The new feature is controlled by configuration of the WIC settings per retailer.

REF 513229: Fuel/Tax – Support Fuel Tax for Canada (Inclusive and Exclusive in the Same Transaction – Phase 1
Today, Emerald already supports Canadian Taxes and complies with the Canadian regulations. In this development, phase 1 to support Canadian tax regulations for Fuel Sales taxation was tested for Prepays. Currently, Fuel item prices are tax included, whereas dry items are tax excluded. To support the Canadian Tax regulations for Fuel Sales, Emerald was updated to support tax inclusive and tax exclusive items in the same transaction. The transaction calculation will support a mix of both methods. The individual tax rates can be printed on the receipt and captured in the Tlog. The functionality is available for Prepays.

REF 486965: Fuel-Handle Over Dispensing in Fuel Prepay
Emerald was updated to handle scenarios in which a fuel transaction is over dispensed. For example: If the customer purchases a prepay for $25.00 and on fueling the vehicle, for some reason, e.g., a hardware issue, controller or pump issue, the pump fails to stop at the requested amount and over fuels a small amount of fuel. In such a scenario, the transaction is fully dispensed, and the customer drives off, however, the transaction cannot be closed by Emerald without handling the over dispensed amount. To support this feature, a cash tender type called 'Over Dispensing' will be configured that is manually reconciled and used to record the over dispensed fuel amounts. Each time the Fuel Forecourt Client or the POS tries to close over dispensed fuel transactions, the Fuel Forecourt Client / POS adds a tender line with the over dispensed amount in the transaction. At the end of the transaction, two lines are recorded, the original tender paid and the over dispensing tender. The Over Dispensing tender amount is equal to the over dispensing cost, the final balance due is 0.00, and the transaction can be finalized by the forecourt or POS. If the retailer does not configure an Over Dispensing Tender and the fuel system over dispenses, the over dispensed gap is not covered, and the transaction cannot be finalized.

REF 479297: Sale: Display the Price per UOM to the Customer and Cashier when Selling/Weighted/ Quantity/ Volume Items – Phase 1
Emerald was updated to display the price per UOM next to the item on the item line in the Ticket Zone on the POS and Customer Display. In this phase the development for the sale of items sold by unit, weight, with a linked tare was completed. Bottle Deposit and Returns will be handled in phase 2. The Price/UOM is the net price of a unit. This enables the cashier and the customer to view the cost of a single unit of the item sold. The display is controlled by configuration of a new parameter called: 'Display Price Per UOM On Ticket Zone'. For example: DisplayPricePerUOMOnTicketZone is set to true: 'Each' items sold by quantity are displayed as follows: Banana ---------2-----------------------------6.00 3.00/Units Weight items are displayed as follows: Tomatoes ---------0.500 Kg-----------------3.50 $6.99/Kg

DisplayPricePerUOMOnTicketZone is set to False: 'Each' items sold by quantity are displayed as follows as is today: Banana ---------2--------------------------6.00 Weight items are displayed as follows as today: Tomatoes -------0.500 Kg----------------3.50

The new display option applies to:

• Each Items sold by quantity. The UOM is unit, which is configured on the PLU.
• Weight Items
• Linked Items – the Tare Item shows the price/UOM for the main item

Note: For linked tare items, the solution assumes that the price of the box is 0 and does not affect the Price Per Unit for the Customer Display. On the FuelPOS: the quantity of weighed items is displayed only on the Customer Display, therefore, the Price Per Unit is only displayed on the Customer Display.

• Promotions – for simple promotions, the price/UOM is displayed in the line and matches the discount price/UOM.
• MSU – the price per UOM is the price for X items, for example $10/3 Units.
• Price Override – the price per UOM is the new price.
• Amount Embedded Barcodes – supported if the UOM is weight. The price per UOM is taken from the catalog, the weight is calculated.
• GS1 amount and weight embedded barcodes – the price per unit is calculated by the amount and weight.
• Items sold by weight/quantity embedded barcodes are supported.
• Items sold by Price embedded barcodes are supported.

The solution supports scenarios where the item description is too long and does not fit the assigned area as with existing functionality, for example, Harry Potter Special E... In addition, other existing features, such as multiple icon display and the display of simple promotions (displayed in line or on a separate line, which is configurable) is supported with the price per UOM display, see the examples in the details.

REF 466012: Remove Product Remote DAO
The ProductRemotableDao is an interface that interacts in scenarios in which a product/price is not found in the Store Catalog. It is not required by Emerald and was removed. Emerald works directly with the Store Database catalog without using this interface. All the items and details of the items come from the cloud catalog to the local POS database. For example, Item lookup is performed on the local server and there is no need for a remote lookup. When an item is not found in the Store Catalog, the 'Item Not Found' message is prompted with no change.

REF 511312: Security Violation - Remove Security Data from the Logs
To prevent security violations, all Emerald Passwords/PIN codes are masked in all the log files.

REF 511735: Support Cashier Authorization for PAP
Currently, Pay At Kiosk (PAK) transactions are authorized by the Cashier via the Pump and the 'Arm' function, which is a process to enable a fueling point for operation before dispensing can begin. Only pumps that can be viewed can be armed. Emerald was enhanced to enable this option for Pay At Pump (PAP) flows. The pump will not allow fueling to begin until the cashier visually checks the forecourt and arms the pump from the FuelPOS. In addition, when the Pump is requesting authorization, i.e., the Pump icon flashes, an audible alarm will beep. To support this feature, the Fuel Control Center (FCC) application must be configured to support Auto Authorization for PAP transactions.

Notes: This feature is dependent on Fuel PumpSrv development (Jira Reference # RFUEL-4340). The request for pump authorization occurs after the payment card is approved, regardless if the nozzle is lifted.

REF 466012: Sale Price Query/Price Check Enhancement
The Emerald Price Query/Price Check feature was enhanced with new functionality. The option to perform the Price Query/Price Check from the 'hello login' screen without having to log in to the POS was added. The ability to print the Price Query/Price /Check details on demand via a new 'Print' button that was added to the existing Price Query/Price Check screen was added. In addition, if the item's catalog price includes a loyalty price and/or discount price in addition to the item's regular price, the POS display these prices as well.

REF 512719: NTEP Certification - Update Certification Number on the POS
Emerald was issued with a new Certificate of Conformance for both Grocery and Fuel clients. The new certification includes certification for both the scale and fuel controller and a new certification number. The new Emerald POS Certificate number is 17-090A1. 'A1' was added to the previous certification number. The same number is displayed on every POS terminal. It only changes when another number is received. The USA Certification Compliance Details is a strip of information displayed on every screen in all modes. This strip includes the following details:

• Manufacturer = NCR
• Model = Emerald
• Version number – the version number of the currently installed program
• CC# - the Certificate of conformance number.

REF 497378: Capture TouchPoint Group in Emerald Tlog
Till now, the Emerald Tlog was capturing the TouchPoint group in an inconsistent way across different types of transactions, using the element. The WorkstationLocation information generally included the ID and Type. As a result, the TMD Parser was getting incorrect data, causing incorrect data on platform applications such as NCR Analytics. Emerald Tlog was enhanced to also capture the Touchpoint Group ID for all transaction types in the element. This change is applicable to all TLog types.

REF 434033: Integration: Publish Events for any LP (Loss Prevention/CCTV) Product
Emerald was updated with the ability for the POS to publish events that can be caught by a Loss Prevention system/CCTV (closed circuit televisions) product. To support a Loss Prevention system, the retailer must install and be integrated with such a system, for example, a system with a video analytics solution available for POS terminals to detect shoplifting and employee theft in the store. To support such a solution, Emerald would require a camera is installed above the lane, a Digital Video Analyzer to analyze video streams and a validation center to validate and filter noise out of the computer vision technology. A Validation Center requires a subscription with the retailer. (It is the Retailer's responsibility and is outside of Emerald Scope). Once integrated, Emerald can then export all the POS events that can then be analyzed later on. This development was done to enable Emerald to export all the POS events per touchpoint associated to a specific Touchpoint Group into a dedicated RabbitMQ queue, which is created for the integrated Loss Prevention system in Json format. The Loss Prevention system is then able to pull the messages from the queue and process them. The export feed can be turned on or off on each POS by configuration of the Business Unit and Touchpoint Group.

REF 509901: EPS Aurus Integration
Emerald completed an infrastructure to integrate with an EPS system that is not supported out of the box by Emerald. Emerald will be able to work with any retailer using a different EPS system via the new API. The first Emerald implementation is with the Aurus EPS. The API will support payments, refunds, Online Item activation, reloading and balance inquiries.

Resolved Issues

The following defects were fixed in this version:

• Fixed TFS509981: Tests in Retalix.IntegrationTests.Operability failed.
• Fixed TFS511067: Deleted specific snapshot by version number.
• Fixed TFS511101: Start Use Case did not function properly.
• Fixed TFS511247: Log files were deleted on install.
• Fixed TFS511520: POS registration failed on the store server.
• Fixed TFS511932: Fuel – The Customer Approval message was prompted after a customer card was scanned in Tender mode in a Fillup transaction, and then removed and the POS moved again to Tender Mode.
• Fixed TFS512598: Set and update new port for StoreDmsService.
• Fixed TFS512616: BRM – BRMs with the same description were updated incorrectly.
• Fixed TFS512645: Fuel - Emerald called the PE for promotions with the wrong price precision (in case of zero digits after the point).
• Fixed TFS512747: Fuel - PAP with Car Wash -Promotions were written incorrectly to the Tlog.
• Fixed TFS513118: Fuel - Promotion discounts on dry items were not displayed in Receipt before Fueling.
• Fixed TFS513225: Fuel - Fuel promotions were not sent with an adjustment on recall after a prepay was resuspended.
• Fixed TFS513246: In some cases Fuel items were displayed in one line with the promotion and some in a separate line.
• Fixed TFS513589: ColdStart Catalog Tool failed on Store tier level.
• Fixed TFS513649: There was no Customer Indication when a PapToPak fuel transaction was recalled on the POS.
• Fixed TFS513652: Fillup - Unfuel multiple fuel finalize.
• Fixed TFS514292: Fuel Transactions were displayed in the TDM twice with the SAME transaction numbers.
• Fixed TFS514390: Prepay transactions with dry items which contained a promotion were returned with an error from the ULP-UE.
• Fixed TFS514715: Fuel POS - Stored Value Tender Type – The Search Customer button had to be clicked twice to search for the customer.
• Fixed TFS514719: Fuel POS - Stored Value Tender Type – The Search Customer button to search for the customer was not displayed.
• Fixed TFS515567: User Update install stage failed on Store tier level due to "IdmAddUser" Rti send failure.
• Fixed TFS516093: The POS stuck after a fuel price update.
• Fixed TFS516292: Cash Office – An error occurred after saving at the end of the process.
• Fixed TFS516326: The $ sign was dropped on the Electronic Journal - POS client, printed text.
• Fixed TFS516659: Promotion configurations as 'Item, Reward, net price in Single Line' did not work when working with the UE. It worked in the LPE.
• Fixed TFS516913: Government Program Tests failed with a "Processing WIC prescription or utilization has failed" error.
• Fixed TFS517172: Print Receipt - Items with price after discount - Default Configuration - Prices were changed while moving to ULP-UE-V2.
• Fixed TFS517318: The Open Drawer Activity was missing in the RabbitMQ messages.
• Fixed TFS517565: BusinessException - Toggle Configuration was not found for the relevant Business Unit.
• Fixed TFS517583: Object reference was not set as instance error - Refund visa operation.
• Fixed TFS517749: Prepay line was not aligned with other selling lines on the FuelPOS and Customer Display.
• Fixed TFS517798: There was a mismatch in the column order of the Cat_Price table.
• Fixed TFS517960: WIC EBT - Payments with eWIC and SmartWIC could not be completed.
• Fixed TFS517963: The POS did not redirect to Tender mode when the Close button in the 'Cannot pay with tender' popup was clicked.
• Fixed TFS517974: The Price Query screen was not displayed correctly, and the POS stuck on the POS Query screen for Tare items.
• Fixed TFS518051: A Transaction (saved in Mainlane POS) that was recalled from Toggle POS when the POS crashed could not be recovered.
• Fixed TFS518174: Training mode logout.
• Fixed TFS518385: Test for DiscountDataParser was missing.
• Fixed TFS518428: Localized Resources Versions Mismatch – FuelPOS – RIG button and messages of closing transaction by POS were displayed as Missing.
• Fixed TFS518604: In Fuel stations - DMs server - Data was not downloaded to the store.
• Fixed TFS518616: An unhandled exception occurred when trying to add a transaction Pap2Pak to a transaction which already had the same customer and regular PAK.
• Fixed TFS518871: When trying to pay with an HSA card the payment was only for FSA Eligible Items.
• Fixed TFS519050: Fuel Prices were not downloaded to the Pump in the POS station.