A guest choosing a salon wants to see where it is before anything else. The header's Menu location blocks put your locations inside the mega menu under the item you choose, usually Locations, with a photo, a short area label, the address and the phone number.

Adding locations
Open the Header section and choose Add block → Menu location. Up to twelve.
- Show under menu item is the position of the top-level menu item that should hold the location, counting from 1 at the left. The item must have children (a dropdown), because that is where the blocks render. The demo's Locations item is second, so every block uses 2.
- Image is a photo of the location. Optional; a block with no image renders as a text row.
- Location name, Area (a short label such as Flagship or the neighborhood), Address, Phone number and Link to the location's page.
Menu location block
Up to 12 per section- Show under menu itemSlider: 1 to 8 · 11 is the first item in the main menu. Only applies to items that have a dropdown.
- ImageImageUpload a photo of this location. Optional.
- Location nameText · Downtown
- AreaTextA short label such as Flagship or the neighborhood name.
- AddressText
- Phone numberText
- LinkLink
Images or rows
Show images for location entries, in the header's Locations group, switches between photo cards and plain text rows for every location at once. Turn it off for a group with many locations, where a dozen photos in a menu is too much; the rows list name, area, address and phone and still link to the page.
A location with no image always shows as a row, whatever this is set to.
On phones
The drawer lists the same locations under the Locations item, as rows with the name, area and a tap-to-call phone link, after the item's regular sub-links.
Keeping locations in step
Locations live in a few places in Atrium: the header blocks here, the location finder on the locations page, the locations grid on the home page, and the booking picker in the overlay group. They are separate blocks, so a new location is added to each. Use the same name everywhere, especially the spelling that appears in your team metafields, so filters and analytics group correctly.

