Ability to Migrate (Copy) Pricing & Availability Between Restaurants
- Yildirim, Semih
This capability enables admin users within the Digital Operations Portal to migrate (copy) pricing & availability from one base restaurant into another restaurant.
The Process
1. Select the Base Restaurant
Once a restaurant is selected, users will be prompted with the bottom action bar. In this bar, they will have the option to migrate (copy) the restaurant data:
The option Migrate(Copy) Restaurant Data will be available only when the user has 1 restaurant selected.
2. Choose the Restaurant to Receive the Data & Confirm
After selecting the base restaurant (Restaurant_A), users then need to choose the restaurant that will receive the pricing & availability data (Restaurant_B).
Afterwards, users need to confirm the action:
Important Notes
When pricing & availability is copied from Restaurant_A into Restaurant_B, it will override all the pricing & availability data for Restaurant_B.
If Restaurant_B includes pricing & availability for PLUs that don’t exist in Restaurant_A, those PLUs will keep their existing pricing & availability configurations.
If certain menu items are having late night pricing values in restaurant_A, then the pricing will also be configured for those menu items for restaurant_B after the migrate (copy) action. However, the store would need to have the lateNight prcing enabled, and the timeslots correctly configured in Sanity. The migrate (copy) action only covers the P&A, and not the restaurant configurations in Sanity. How late night pricing is used and configured are explained in detail in the following guide:
If certain menu items are having pricing & availability values in additional channels (e.g. UberEats), then the P&A will be configured for Restaurant_B for those chanels too after the migrate (copy) action. There won’t be a need for additional channel extension configuration. How Channel Extension is configured is explained in detail in the following guide:
The capability doesn’t involve migrating the content aspects of the menu.
The solution might require a pre-requisite of the PLUs to be correctly set for the restaurant in Sanity, under Restaurant POS Data depending on the configurations in the market (e.g. https://prod-plk-es-whitelabel-cms.rbi.tools/desk/orderLevelContent;restaurants;restaurant;restaurant_237917;restaurantPosData_13311%2Ctype%3DrestaurantPosData%2CparentRefPath%3DrestaurantPosData)
A separate user permission will be later required to be able to perform this activity, to be configured in the User Management capability of the portal.