Access Hospitality - Ideas Portal

Help us shape the future of our products by submitting your own ideas and reviewing ideas submitted by other users. If you see an idea you like, feel free to vote it up and add any comments that you feel would be beneficial.
This is a collaborative community, so please join in, contribute your innovative ideas and help our product teams to shape their roadmaps and future product development.

Our teams will review the ideas which have received the most votes on a regular basis, meaning that not all ideas will receive updates. When an idea has received enough votes, the status will be updated to 'Under Review' and then a decision made.

Create idea Subscribe
Status Idea Received
Product Access Collins
Created by Guest
Created on Aug 14, 2025

RELATED IDEAS

Organisation Settings

To be able to push and pull settings to multiple sites based on site tags/brands. In a business with multiple brand/district set ups currently we have to use test sites to set up individual settings and then copy to the relevant sites that require this.

It is not possible to replace existing settings or delete menus/items across multiple sites at once. You have to update sites each time individually or delete everything then copy over fresh for example if you wish to change to multiple sites cut off times or turn times for say a dinner booking type, you have to do this one by one or delete the whole booking type, re-apply all settings and then add all individual sites tables and site specific settings one by one. This is very labour intensive and means we can not update brand set ups or refresh them at various times of the year.

  • Attach files
  • Guest
    Mar 26, 2026

    To add to the above - we would find it really useful to apply deposit rules to multiple sites (on specific booking types) for key dates such as mothers day. I am finding it more and more challenging to manage a large multi sites brand (with sub brands) when it comes to updating settings centrally. We tend to update quarterly/seasonally so it is quite frequent and as mentioned above labour intensive for a small central team. Is there any update on if the above is being considered?

    Reply