The issue on site
A single central portal shows the same message everywhere: a summer campaign for Bodrum also appears in Erzurum, a mall-only discount spreads across the chain. Building a separate portal per branch quickly becomes unmanageable.
Check these first
- 01
Group locations by region, brand, concept or city.
- 02
Decide which content is mandatory from HQ and which is branch-specific.
- 03
List campaigns needing a schedule (start/end date, hours).
- 04
Note each location's language needs (multiple languages for tourist areas).
HotSpot / LogIQ approach
In HotSpot, portal designs, welcome pages, ads, announcements and surveys are published by targeting a location or location group. HQ locks the brand template; branches customise only permitted fields. Publications are scheduled by date and time and expire automatically. Unlimited language support shows each publication in the guest's language at every location.
Guest and team outcomes
The right message, in the right branch, at the right time. Brand consistency holds while branch teams manage local announcements within their permissions.
Frequently asked question
Which branch's screen does a recognised guest see?
The publication of the location they are connecting at. Identity is organisation-wide; content is location-specific.
Can I publish one campaign to 200 branches at once?
Yes. Target the location group to publish, and remove it, in one action.
This content supports technical assessment, not legal advice. Verify scope against product, version and institutional policies.