mO SharemO Share

Release Note 11.149.0 - 1.149.0


Control

Release Date

26 October, 2019

HO Version11.149.0
POS Version1.149.0
Web Database Compatibility Version1.16
Features & Enhancements03
Bug Fixes02
Navigation


Features & Enhancements

Serial

Dev ID

Idea Tracker

Description
128102GIN-I-2191

28102 Cash acceptance limit introduced in POS

Feature Video:

Module:

Retail Management - Setup - Master Policy / Site Policy
POS - Administration - Master Policy
POS - Normal POS / Collection Center
POS - Back Office - Transactions - Deposit

Enhancement Summary:

Government had introduced a restriction on accepting cash of 2 Lacs or more from the customers as follows:

  • in aggregate from a person in a day, or
  • in respect of a single transaction, or
  • in respect of transactions relating to one event or occasion from a person

Till date, this was managed by all via standard operating procedures (SOP) but now Ginesys has introduced this feature in the system which shall restrict the cashier from receiving cash "of and above" as specified in the new system policy setting (Restrict cash transactions of and above <specify value>).

For example, if the policy value is 2,00,000.00, then the cashier won't be allowed to:

  • Receive tender of 2,00,000.00 and above in a single bill, i.e., max cash tender in a single bill should be 1,99,999.99.
  • Receive tender of 2,00,000.00 and above in aggregate from a single customer in a business day.

In such cases, the cashier should ask the customer to pay balance by other mode of payments like Credit Card, Digital Payments, Vouchers, etc.

Note:

If cash restriction limit is set to Blank/Null, then no cash receive limit validation will be applicable.

231912GIN-I-2633

31912 POS Settlement at HO will now be restricted if all local procurement bills have not been done till that day

Module:

Ginesys Launchpad - POS Settlement
Procurement - Invoicing - Purchase Invoice

Enhancement Summary:

A new validation has been applied that the system won't allow settlement to be processed at Head-office until the purchase invoice process of the goods procured locally has been prepared. This is to ensure that the bills are timely prepared as there is no provision to make modification to the goods receive once the settlement is completed at HO.

Process flow:

  • Store does local procurement goods receive transaction.
  • Store does store settlement.
  • The settlement processing at HO will show error as Purchase Invoice is pending.
  • HO/Store prepares the Purchase Invoice as required.
  • The system processes the settlement automatically.

Important Notes

Validation applicable only for Non-consignment Purchase
The aforementioned validation is applicable only for goods procured locally in non-consignment mode. For consignment mode purchase, this validation remains not applicable.

Modification of Goods receive in error state
To modify any goods receive while preparing purchase invoice, user will first have to prepare goods receive, then wait for the settlement to move to "Pending Approval / Unposted" state. Once that state is achieved, user can revert settlement and do necessary modifications to Goods receive post untagging from purchase invoice.

331898GIN-I-2461

31898 Customer name and mobile number can now be seen during POS Bill Modification

Module:

POS - Back Office - POS Control - Bill Modification

Enhancement Summary:

In the POS bill modification list view, now the cashier can now see & filter the bills based on the customer name/mobile number so that they don't have to open transactions to understand which bills belongs to a particular customer.


Bug Fixes

Serial

Dev IDDescription
130605

30605 Extinct Items were showing in search item list in store

Module:

POS - Normal POS
POS - Take Order - Select Item

Reported Version:

1.148.0

Scenario:

  • Send an Item to a store.
  • Make that Item extinct.
  • Sync to the store.
  • Check that still that Item is available in the various search list at store end.

This has been fixed.
Note: Scanning of such items is not restricted similar to the behaviour we have in head-office.

228452

28452 EasemyRetail (EMR) bill submit discrepancies removed

Module:

HO - Data Synchronization - EMR Bill Submit

Reported Version:

11.148.0

Scenario:

There were some minor differences between the data submitted from store and the same data being submitted from head office to EasemyRetail (EMR). This has been fixed.