What is central product management?
It means products are defined from one shared central structure, and the branches work to that standard.
This approach keeps product data from scattering.
Does the price have to be the same in every branch?
It does not.
Different prices can be defined per branch while the central structure holds.
What matters is that the price difference is controlled and visible.
How should products a branch does not sell be handled?
Not every product has to be sold in every branch.
So the shared product card stays as it is, while the product's usage status is managed per branch.
What should be done when a new branch opens?
The new branch's:
- products,
- menu,
- prices,
- users,
- payment types
should be defined before it opens.
The aim is not for the new branch to build a different structure from scratch, but to carry the existing standard to the new location.
Can a user change a price?
That depends on the business's permission policy.
Critical actions such as changing a price should be limited through the permission system.
In summary
In multi-branch restaurant management, the point of centralising is not to remove branch flexibility altogether.
It is to hold a shared product and data standard while managing the branch differences you do need, under control.
Kerzz