Release Note 12.10.0 - 2.10.0
Control
Release Date | 10 August 2022 |
HO Version | 12.10.0 |
POS Version | 2.10.0 |
Web Database Compatibility Version | 1.17 |
Features & Enhancements | 05 |
Bug Fixes | 00 |
Navigation |
Features & Enhancements
Serial | Dev ID | Idea Tracker | Description |
|---|---|---|---|
1 | GIN-1626 | Local Procurement: Rate change allowed based on profile settingsModule: Procurement → Operations → Goods In/Out→ Receipts/Returns Scenario: There are cases where rate in GRC are different from rate in Purchase Invoice and in such cases Entity/Brand want to edit the GRC to ensure proper COGS calculation. As in Ginesys COGS is impacted from GRC item rate and not from Purchase Invoice. Currently, once the Local procurement documents are made and Authorized/Synced to POS sites, it can not be modified until it is reverted by the POS site. This process of reverting from the POS site/store and then editing it at HO is cumbersome. Hence, we have provided an option in user profile under Procurement - “Allow GRC/GRT edit after release.“ Based on this option user can edit the Local procurement document even after Authorization and edited document will re-sync to POS sites. | |
2 | GIN-1625 | Negative stock check from Store Stock pointModule: Procurement → Operations → Goods In/Out → Return Inventory → Operations → Conversion → Production Inventory → Operations → Conversion → Bundle Inventory → Operations → Conversion → Split Scenario: Currently in Ginesys negative stock check is done for the Store Location and not for the store stock point which lead to store stock mismatch at stock point level. Example to understand the current scenario Store Location: Item A | 10 pcs where Godown stock point: Item A | 7 Pcs & Showroom stock point: Item A | 3 Pcs Hence forth checking would be done at the store stockpoint level to ensure correctness of the stock. | |
3 | GIN-1627 | Applications migration to WebSome WinApps forms have been moved to web as part of our web journey. | |
License Manager ApplicationModule: Admin → Utilities → License Enhancement Summary: We have introduced three menus under this module :
| |||
Settlement Authorization ApplicationModule: POS Management → Operations → Process → POS Settlement Enhancement Summary: We have migrated the POS settlement menu from Ginesys Desktop (Winapps) to Web as a part of our cloud journey with improvised user experience. | |||
4 | GIN-1628 | Menu revampingEnhancement Summary:
| |
5 | GIN-1624 | Changes related to Zwing IntegrationProvision for managing MPOS site We have introduced a new menu in Ginesys ERP for Cloud MPOS Site from which user can create and manage MPOS sites. | |
Introduction of Connected app Ginesys ERP has come up with a new and unique offering of integration with Cloud/Mobile POS. All the configuration for setting up the connection between the two applications is available in front end. For more details, please get in touch with your account manager. | |||
Introduction of master to enable integration 1 ) Tender Master Path: Sales & Distribution → Retail → Retail Store Master (Zwing) → Tender We have introduced Tender only for the purpose of integration. For easy understanding it is like a MOP master for Ginesys POS site. Intended use of the Tender master Brands create multiple tenders that are used in the store such as Cash, Cheque, Promotion Voucher, Razor Pay, Credit Card etc. Purpose of creating multiple tender is to get tender wise accounting impact, so that settlement reconciliation could be done smoothly. Tagging of GL/SL is mandatory while creating the master. Further if the brand wants to maintain store/site wise ledger for tenders, it is also possible. For that GL/SL tagging is required in connected app for respective site/store. Path: Sales & Distribution → Retail → Retail Store Master (Zwing) → Income / Expense We have introduced Income/Expense only for the purpose of integration. For easy understanding it is like a Petty Cash head for Desktop POS site. Intended use of the Income/Expense Master This master will be used for managing petty cash transactions at store/site level. In petty cash transaction one leg is Cash as a tender and other is either Income/Expense head. Brand/Enterprise can define the GL/SL for each head in the connected app for respective store/site. | |||
Transactions allowed from MPOS site and its visibility in Ginesys ERP Below mentioned are the list of transactions that are allowed from MPOS site:
To know more about the assumptions made during deep integration, refer to the below table |
The following assumptions have been made while developing our integration with Zwing - Ginesys One Cloud POS
Area | Assumption | Reason | Workaround |
|---|---|---|---|
Item | VAT handling is not done | Time constraint | No workaround available - don't pitch in stores having liquor or don't go international with VAT. |
Item | Scan unit of 1 or 0.001 (NOT 0.01) is only supported, i.e., 1 for pcs and 0.001 for all others like kgs, ltrs, mtrs. | Architecture constraint | When any item with a different scan unit is sent, the technical handling will fail, the user will have to update the master, it will be resent to cloud POS and get created. |
Goods Receive | GRC revert not allowed | Time constraint | No workaround available. |
Goods Return | Return rate mandatorily will be as per last receive price at store | Time constraint | No workaround available. |
Goods Return Revert | Revert is not allowed for “Zwing store to Ginesys store” | Architecture constraint | No workaround available. |
GV | 100 % discount sale not available | Time constraint | Create discount with 99.99% discount, i.e., do 1% billing. |
GV | Institutional GV issue from head-office not available | Time constraint | Issue from any store location. |
POS Order | Sales order creation (at HO) against POS order is not available | Time constraint | No workaround available. |
POS Bill | Tax recalculation will only update HSN and tax rate | Integration constraint | For updating customer's GSTIN and trade type, then you need to modify the bill, the integration system will void and create a new bill (with same number). |
POS Bill | Customer master will be maintained in Cloud POS only | Functional constraint | Customer repo in such cases will be maintained in Cloud POS's retail management / manager / console. In future it will move to Ginesys One customer data platform. |
Goods Return / POS Bill | E-Invoice / EWB direct creation provision not available | Time constraint | Create manual using EMG / Govt. portal - however, EINV, EWB details won't be available in such cases in ERP. Development in progress - should be available soon. |
Local Procurement | Vendor name will not be visible | Integration constraint | Vendor name will be shown as "Undefined". |
Local Procurement | Price control / price book store wise has to be inputted directly in cloud POS system | Integration constraint | Use import option in cloud POS when to be updated in bulk. |
Local Procurement | Receive/Return price update in ERP, won't reflect in cloud POS | Time constraint | No workaround available. |
Local Conversion | Issue and Receive both should be available | Architecture constraint | "Integration failure handling Business case handling |
Petty Cash | Even after maintaining 2 cashpoints in cloud POS, it will show only in 1 ledger in ERP | Architecture constraint | No workaround available - see breakup if required at cloud POS's retail management / manager / console. |
Reporting | Pre-promo analysis and post-promo analysis won't be available with cost. | Architecture constraint | Check the pre-promo and post-promo analysis with stock in cloud POS and refer the cost (if required) in ERP. |
Migration from GPOS | Store should be closed and a new store should be opened. | Architecture constraint | "POS Returns ERP Sales Return (to set-off Invoices GST Credit Note purpose) Combined Sales / Stock report in ERP Combined Operational Analysis in Retail Management Note: Treat the working as a new POS software implementation." |