Enhancement in Replenishment Source management
Module:
POS Management - Setup - Manage - Site
Sales& Distribution - Retail - Retail Store Masters (Zwing) - Cloud MPOS Site
Enhancement Summary:
- Replenishment Source tagging is separated from POS site master
- Current Working: When a user creates a POS/Managed site he need to mandatorily tag the replenishment sources in the site master for successful creation of the site.
- Proposed change: We have separated the Replenishment source tagging window from the POS site master and have introduced a new access control under both (POS site and Cloud MPOS Site) menu to manage the replenishment source tagging. User would still be able to view the replenishment sources from the existing site master tab, but will not be able to modify from here.
- Transition handling: All existing users who currently had right to add or modify the POS site, would be given the access right to manage the replenishment source. In case entity specifically wants to restrict the user, kindly mange it from role access after the update.
- User can select the Default HO/Owner site for POS Order fulfilment
- Current Working: Currently we do not have any option in the replenishment sites to mark it as a Default site for fulfilling POS Orders. System itself picks the site based on internal logic.
- Proposed Change: We have introduced a new checkbox in the replenishment site window “Default site for POS Order“. From where user can specifically mark the site as a default replenishment source for POS Order fulfilment.
- Transition handling: After the update system will continue to pick the owner/HO site as a replenishment source for POS Order fulfilment based on the internal logic. But once the checkbox is marked in the replenishment source, system will start considering this site as a replenishment source for POS Order fulfilment.
Note |
---|
title | Applicability in Zwing Stores |
---|
|
Note : Marking of Default site for POS order is required if the entity wants to push the POS Order from Zwing stores. We have made the necessary changes in internal API to cater the same. |