Multi-Location Menu Management: Maintain Consistent Item IDs Across Locations
Multi-location merchants using Clover Enterprise currently receive unique Clover Item IDs at each location, even when menus are centrally managed through Multi-Location tools. Testing confirmed that uploading and managing menus through Multi-Location still generates different Clover Item IDs per location.
This creates challenges for third-party integrations that rely on Clover Item IDs for product mapping. As a result, merchants operating multiple locations are forced to maintain separate menus and mappings for each store, despite managing inventory and menu updates centrally through Clover Enterprise.
Requesting an enhancement that allows items to maintain a shared/master Item ID across all locations within a multi-location enterprise environment, or an option to preserve Item IDs when propagating menus across locations.
Business impact: Multi-location restaurant chains cannot maintain a single centralized menu within third-party ordering platforms and must manage duplicate menus for every location.
Keshmi
shared this idea
Thank you for submitting your Idea to UserVoice.