conceptahg last reviewed 2026-05-21

AHG multi-venue ops model — 3 venues + cross-venue infrastructure

Context

Aspire Hospitality Group operates 3 distinct venues in Albany, WA. Each has its own brand, menu, staff, customers — but shares cross-venue infrastructure (payroll, accounting, accommodation channel management, POS). New agents and team members need a quick orientation to which entities are AT venue level vs AHG level.

Detail

The 3 venues (all Albany, WA — see aspire-venue-geography)

VenueTypeBrand presence
Chanya ThaiThai restaurantOwn brand, menu, kitchen
Venice AlbanyTakeaway / pizzeriaOwn brand, menu, takeaway-first
Six DegreesCoffee + dining + eventsOwn brand, multi-purpose venue

What's AT venue level

What's AT AHG level (cross-venue)

Tools per layer

LayerTools
Per-venue opsPowerEPOS (POS), Xero (one org per venue), venue-specific WordPress sites
AHG cross-venueTanda (payroll), Zinga CM (accommodation), STAAH (legacy, being phased out)
Aspire-wideAspire Hub (staff SSO), smart-dashboard (BI), MeetGeek (meetings), Slack

Key Xero orgs

OrgBrand
ADGAspire Digital Group holding
AHGAspire Hospitality Group holding
sixdegreeSix Degrees venue
chanyathaiChanya Thai venue
veniceVenice Albany venue

Note: org names like "chanyathai" and "sixdegree" are Aspire AU entities, NOT Thai entities — the names just reference the hospitality brand. See aspire-venue-geography for the AU default.

Customer flow patterns

Customer touchpointWhere it lives
Walk-in / dine-inPowerEPOS at the venue
Phone bookingCurrently manual; ZeeHost will eventually handle (see zeehost)
Online bookingZinga Booking (when LIVE)
Online reviewGA4 / Google Business per venue
Catering orderManual / venue-direct

Open questions

  1. When do we adopt Zinga PMS as the venue-level PMS for the accommodation-offering venues?
  2. Cross-venue customer recognition — what's the privacy model?
  3. AHG-level marketing automation — currently per-venue; could centralize via Postiz once integration ships.

Related

🔗 Relationships

graph LR multi_venue_ops_model["multi-venue-ops-model"]:::self multi_venue_ops_model --> aspire_venue_geography["aspire-venue-geography"] multi_venue_ops_model --> zeehost["zeehost"] multi_venue_ops_model --> aspire_brand_architecture["aspire-brand-architecture"] multi_venue_ops_model --> zinga_suite["zinga-suite"] classDef self fill:#715EE3,color:#fff,stroke:#291F50;