mO SharemO Share

Release Note 12.9.0 - 2.9.0

Control





Important Alert

Note: Please update all POS to version 2.9.0. to get the effect for all features.

Features & Enhancements

Serial

Dev ID

Idea Tracker

Description

Serial

Dev ID

Idea Tracker

Description

 1

6933



6933 Duplicate customers with the same mobile number can now be merged

Module:

Retail Management - Setup - POS Customer >Merge

Enhancement Summary:

Useful Customer Relationship Management can only be done when each customer can be identified uniquely by their mobile numbers. Ginesys makes it easier for its users to identify customers uniquely. After this update - 

  1. Single mobile number would be captured for each customer.

  2. Customer can change mobile number later.

  3. Transaction history is not lost for customer even if mobile number changes.

  4. Existing transactions with duplicate mobile numbers are properly merged.

Customer will now be created in the user's WebDB.

If the POS cannot connect the Web at the time of billing, POS bill will be generated with customer creation locally and customer will be tagged later .

If the POS can connect the Web at the time of billing, customer will be validated against the customer database present in the Web to avoid creation of duplicate customer if one is already existing. However, if there are no existing records in the WebDB against the given customer mobile number, new customer will be created.

In case of Customer mobile numbers with multiple customers already created against it, the duplicate customer ids would be merged with the one that has latest transaction.

Important - Issues that can crop up

  • Since customer is created locally, when internet is not available, as well as through Excel Import, so duplicate customers may still be available under one mobile number.

  • Since we are saving Customer Name (First name + Middle name + Last Name) in POS Bill, so it might happen that even after merging customer id there can still be different customer names in POS Bill and Customer master for the same mobile number.

  • During merge, customer record with the latest transaction details will be Marked in Bold and that is the final record which will be retained. 



Important

Customer with Loyalty Card will not be merged by above method.

How to do POS Customer merge?

  2

7255



7255 Ginesys POS Billing is now RFID enabled through third party integration

Module:

Retail Management - Setup - Configure - Plugin Manager

POS - Normal POS > Billing

POS - Collection Centre >Billing

Enhancement Summary:

Now Ginesys POS Billing is RFID enabled. A RFID chip is now attached with items and at the time of billing the items are scanned as single/ multiple barcodes through a RFID scanner and its details are obtained. 

The path of the plugin configuration in POS - GSL - POS - Plugin - < The folder will have the same name as the short code >.

In POS, after saving the Bill, the following message is shown- " Gate Notified Successfully " and Log is generating in the following Path:

C:\Program Files (x86)\GSL\GINESYS POS

Integrating EAS (Electronic Article Surveillance) systems with Ginesys POS

  3

6600



6600 Changes made for efficient bulk data sharing in EMR 

Module:

Ginesys Launchpad - System Utilities - Data Sync

Enhancement Summary:

Now EMR sync has been made more efficient for bulk data sharing. Changes have been made to import the data manually through a .csv file on the click of a button. 

How to manually process bulk data for EMR?

Bug Fixes



Serial

Dev ID

Issue Tracker

Description

Serial

Dev ID

Issue Tracker

Description

1

8037

 N.A.

8037 Webhook performance has been internally optimized

Reported Version:

12.8.0

Scenario:

Now Ginesys Webhook framework has been internally optimized to handle multiple events efficiently.

2

8038

N.A.

8038 The log has been restructured for better identification of errors in OMS

Reported Version:

12.8.0

Scenario:

The Ginesys log can better identify errors occurring in OMS.