SmartBarIQ
SmartBarIQ Β· Hotel Product Line

One Menu, Every Bar

How a hotel chain runs a centralized drinks catalog β€” and what each hotel, venue, and bartender controls on top of it.

Structure

The three-level hierarchy

Everything hangs off one chain account. Hotels group venues; venues serve guests. Only the chain owns menu content.

πŸ› CHAIN
Owns the catalog: bottles · wine · cocktails · mixers & garnish · rims · prices
🏨 Hotel
Groups venues · price overrides · manager grants
🍸 Restaurant Bar
Tango device · guests · orders
🍹 Lobby Bar
Tango device · guests · orders
πŸ– Pool Bar
Tango device · guests · orders

Venues own no menu content β€” every menu resolves up to the chain.

Chain level

What the chain controls β€” the central catalog

Managed once on the portal (hotel.smartbariq.com); every hotel and venue inherits it instantly.

Chain catalog

Liquor & Wine

  • Add bottles from the 58k-item catalog (search or barcode)
  • Wine is first-class: by the glass (175 ml) or by the bottle
  • Bottle pictures, tiers and retail data ride along automatically
Chain catalog

Cocktails

  • Full builder: spirits, mixers & garnish sections, step order, notes, rims
  • Copy-on-write: editing a master recipe forks a private chain version β€” the original disappears for this chain only
  • Chain-created cocktails stay private to the chain
Chain catalog

Mixers & Garnish

  • One stocked list ("we carry it") powers every recipe match
  • Rims (salt, sugar, tajΓ­n…) managed alongside garnish
  • Names auto-translated for guests and bartenders (5 languages)
Chain catalog

Prices

  • Chain sets the default price per drink, size and serving
  • Hotel-level overrides win where defined
  • Venue staff and bartenders never edit prices
Resolution

How a venue's live menu is computed

A guest at the Pool Bar and the bartender's Tango screen both see the same result of three filters applied in order.

1
Chain Β· permanent

Start from the chain catalog

Every bottle, wine and cocktail the chain manages β€” with garnish-stock gating: if a required garnish or rim isn't stocked, the cocktail never appears.

2
Venue Β· persistent

Subtract venue availability

Per-venue opt-outs set on the portal (Liquor & Wine / Mixers & Garnish / Cocktails tabs). "The Pool Bar doesn't serve fresh basil" β€” permanent until re-ticked, and every cocktail that needs it drops with it.

3
Bartender Β· resets daily

Subtract today's 86 board

Ran out mid-shift? The bartender marks it 86 on the Tango β€” the item and every dependent cocktail vanish from guest phones the same second. The board resets itself every morning.

=
Result

The venue's live menu

Served identically to guest phones (QR ordering, 5 languages) and the bartender's walk-up picker β€” with hotel price overrides applied, else chain prices.

Capabilities

Who can do what

Capability Chain admin Hotel manager Bartender (Tango)
Edit the catalog β€” bottles, cocktails, mixers βœ“ full with Items permission β€”
Set prices & hotel overrides βœ“ full with Prices permission β€”
Venue availability (what each bar serves) βœ“ all venues βœ“ their hotels' venues β€”
Rename venues Β· set 86 access code βœ“ with Availability permission β€”
Daily 86 board (out-of-stock today) β€” β€” βœ“ on the Tango
Walk-up orders Β· order queue Β· guided pouring β€” β€” βœ“ one screen
Dashboards Β· drill-down reports Β· pour control βœ“ whole chain βœ“ their hotels only β€”
Invite users Β· grant permissions & hotels βœ“ with Users permission β€”
Access model

Users & permissions

Portal access = a role, a set of permissions, and a set of hotels. All three are checked on every request, server-side.

Portal role

Chain Admin

  • Implicitly holds every permission across every hotel
  • Runs the catalog, invites managers, assigns their scope
Portal role

Hotel Manager

  • Sees only the hotels granted to them β€” dashboards, reports, venues
  • Acts only within granted permissions:
ItemsPricesAvailabilityUsers
Venue floor

Bartender

  • Works the Tango β€” no portal login at all
  • 86 board can require a per-venue access code set by the manager
πŸ‘€ Portal userInvited by email, temporary password
β†’
RoleChain Admin = everything, everywhere.
Hotel Manager = scoped ↓
β†’
PermissionsItems · Prices · Availability · Users
β†’
Hotel grantse.g. Grand Hotel only
β†’
Server-side checkEvery request: right permission + hotel within grants
Invitations are sent by email with a temporary password; each account is single-session (a new login signs out the old one). URL-guessing another chain's or hotel's data returns 403 β€” scoping is enforced in the API, not the UI.
Two dials, one menu

Availability vs. the 86 board

Manager Β· portal

Venue Availability

  • "We don't serve it here" β€” a policy decision
  • Set per venue on the portal, persists until changed
  • Item never appears on that venue's menu, board or picker
Bartender Β· Tango

Daily 86

  • "We ran out today" β€” an operational fact
  • Marked on the bar floor in two taps, resets every morning
  • Shows blocked cocktails greyed with the reason β€” and previews what an 86 would take off the menu before marking
Both feed the same resolution pipeline β€” guests and bartenders can never order what the venue can't pour.