lmxR4 Release Version
This article describes improvements of the new version of the Loymax system.
Major changes in Version lmxR4 relate to optimizations, general system improvements, and bug fixes:
- list of optimizations in System version lmxR4
General changes
Stores renamed to Points of sale
Now the ARM section Partners > List of stores renamed to List of point of sale.
The Loymax System is used not only by Partners who own stores, but also, for example, pharmacies or other retail outlets. In points of sale (or a network of retail outlets) Partners' customers purchase goods and services using the Loyalty Program.
Points of sale may include:
- grocery stores,
- specialty stores,
- boutiques,
- pharmacies,
- supermarkets,
- hypermarkets,
- cafes, etc.
In all related sections of the System Stores also renamed to Points of sale. For example, the filter Stores, which is used when creating offers, since Version lmxR4 is called Points of sale.
Increased time period for which the LP Member will see the date of expiring bonuses in the Personal AccountExact bonus expiry date in the Personal Account of the LP Member is now displayed six weeks before the expiry date, and not one week as it was before. For example, if two bonus amounts with a validity period of 5 days and 1 month are credited to the LP Member on 04.05.2022, then the Personal Account will display the exact expiry dates of both amounts — 09.05.2022 and 04.06.2022, for the first and second bonus amounts, respectively. | ||||||
Opportunity for Customers without linked cards to manage their bonus accountMembers registered in the LP without linking a physical card and without issuing a virtual card now have an opportunity to make purchases, accumulate and withdraw bonuses and manage their bonus account. In order to realize such a case, when no cards are bound to a LP Member during registration, certain values should be set in the configuration settings. With some settings a bonus card can be bound/issued later, after registration. It should be remembered that in case when as a result of client's registration in the LP no physical card is linked and no virtual card is issued, the only way to identify the customer at the cash register will be the phone number. Product groups search is performed by incomplete name matchIf you set up the Dividing into sets in offers, as well as in the filters Product, Product availability in the receipt, Limitation on product (simple and with a counter), you can search for a group of goods if the name entered in the filter does not match the name of an existing group of goods. The filter works in the same way when searching in the Product groups and Personal Products sections of the MMP, as well as when searching for Favorite Products in Call Center. Use of any cash register identifier when referring to methods that support basic purchase-related transactionsWhen authorizing through an OAuth application, you can pass the X-Identifier and redirect fields in the request, which are used only when referring to methods of the Processing Public API . Interface improvements
Plugins removedThe following plugins were removed from the System:
| ||||||
CRM
New in the section Purchase Management
When viewing information about purchases registered in the System, it is no longer the number of the LP Member card that is displayed, but the one id, which was used in the purchase to identify the customer at the cash register. In the section Purchase Management using a filter by this identifier, you can find purchases in the System for further management.
The identifier used in the purchase is also displayed in the Purchase history of the customer in Contact Center and in the customer card in CRM.
Marketing
New in the Offers section
Specifying the logical name of the receipt item parameter that determines the product minimum price range
In the Setting the minimum price action, a new calculation method is available that allows you to specify the value of the receipt item parameter that determines the product MRC. Now there is no need to load the MRC in the catalog, because the action will work even when the cash register itself transmits the MRC value.
Possibility to quickly select the attribute value in the Points of Sale Filter
A substring is available for searching by the name of a specific attribute in the Points of sale filter (previously Stores).
Updated: Reading the QR code as a bonus card identifierNow filters from the group Card are triggered upon presentation of a QR code as bonus card identifier. Updated: Setting the minimum price of the product from the additional parameters of the receipt positionIn action Setting the minimum price a method for calculating The value of the check item parameter was added, with which you can set the logical name of the receipt position additional parameter from the cash request, which will be used as a restriction of the minimum price of the product. |
New in the Counters section
Updated: Creating counters for Coalition Loyalty ProgramsWhen creating countersit is now possible to select several Partners at once, to whom the counter will be available. Such counters can be used in offers that will be available to several Partners at once within the framework of coalition Loyalty Program. For example, such counters can be used when creating offers with a common product catalog. New in the Status Systems sectionThere are new fields in the window of editing additional status parameters that allow you to add a more detailed description of the status itself, as well as information about preferences available for the current status. For example, you can specify in a separate line the type of preference (discount or bonuses, fixed amount or percentage of purchase), and in another line specify a numeric value. These fields are necessary for displaying information in client services. You can also change these fields via API methods. |
Admin Panel
New in the Users section
Filtering by user statusTo simplify the search for users who are deleted or active, a filter by user status has been added. Now on the main page with users you can display:
|
New in the section Card issue
The logic of creating issuing cards and activating them has been optimized. Section The issue of booklets and the field of card activation were deletedPrior to version lmxR4 when creating card issue with the passwords from the booklet, it was necessary to attach a password to each issued card to activate it. Without this password, the client would not be able to activate the card. And when issuing a card without a password, it was necessary to select the option Without a password from the booklet in the Activation field. Now, when creating a card issue, the Activation field is missing. This field was an irrelevant functionality, because passwords were needed only when the card was activated for the first time, and if the card had a CVC code, the code itself also had to be used to activate the card, which was a duplicate functionality. Therefore, since version lmxR4, it is possible to generate only CVC codes when creating a card issue. Since there is no need to issue booklets with passwords for cards, the section Issue of booklets has also been removed from version lmxR4. |
Updated: New section Additional attributes for entities
The section Additional attributes for entities was added, with which you can create and edit additional attributes for: Each entity has its own list of additional attributes. Additional attributes are used when compiling analytical reports in the module Loymax BI. New filter Cash Register Type in the List of Cash Registers tabSince the System version lmxR4, a new filter Cash Register Type has been added to the Cash Register List tab in the Edit Partner section, which searches for cash register types provided in the System. Updated: New field in the Attribute Creating windowIn the Attribute Creation window, there is a new field Order Number, which specifies the order number of the attributes displayed in the Advanced Customer Search. |
Settings
Updated: New in the Configurations section
- Configuration parameters were added responsible for creating sessions for Marketing management platform (MMP) users. To configure these configurations, go to the System Setup> Configurations.
- Configuration responsible for mandatory transmission of the Customer identifier in the cash request for Direct Discount Calculation has been added. The configuration is set up in the System Setup> Configurations section.
- Configuration responsible for the maximum allowable number of target audiences involved in the calculation of the offer was added.
New in the section Regular tasks
Regular task to clean up calculations of Target Audiences
Data on all Target Audience calculations are stored in the database. To reduce the amount of stored information and increase the System performance this regular task leaves data on the last Target Audience calculation only and deletes data on all previous calculations. Configuration of the regular task is not required, as it is configured in the default MMP in the System Setup > Regular Tasks section.
Changes in API methods
New API methods
- There is a method that allows you to transfer created coupons to the state In the queue for issuance , and also allows you to get a list of coupon numbers that have changed states;
- In the group of methods for working with entity attributes the following methods have appeared:
- The method that archives the entity attribute;
- A method that restores an entity attribute from the archive;
- Method for updating the name of an entity attribute;
- There is a new group of methods for working with client attributes through the OAuth application;
- There is a new method that binds coupons to LP Members;
- There is a new method that returns information about the batch merging of clients, which ended with errors, in the form of a CSV file .
- Updated: In the group of methods for working with the Call Center, a new method that allows you to cancel the client registration that has begun. If the registration process has been started but has not yet been completed, the Call Center operator can cancel the registration through the customer's card using the button Cancellation of registration.
Changes to existing API methods
- In methods for working with clients the following changes have occurred:
- A new method has been introduced that returns a list of attribute values by the customer's card or phone number;
- There is a new method that returns the attribute value by the customer's card or phone number;
- There is a new method that checks the phone number verification code;
- The response models in methods that return information about client statuses;
- In methods for working with entity attributes the following changes have occurred:
- In the method for attribute creating, the list of transmitted parameters was expanded;
- In the method that returns all attribute values of the entity type, the list of transmitted parameters was expanded;
- In the method for updating the value of an entity attribute, a request model has appeared , in which the JSON model with the new attribute value is passed;
- In the method for uploading a file with a list of product codes contained in the product group one can now use both internal and external product group identifiers.