Multi-Location Setup

Hiro CRM is designed for hospitality groups managing multiple restaurant locations across Spain. This guide explains how to set up and manage your multi-location infrastructure.

Understanding Locations

In Hiro CRM, a Location represents a physical restaurant or venue. Each location can have:

Unique settings and configurations
Its own reservation system
Separate staff and capacity
Integration credentials (Cover Manager, Revo TPV)
Custom branding (when grouped under brands)

Locations are the foundation of Hiro CRM’s multi-tenant architecture. All data like reservations, customers, and analytics can be filtered by location.

Creating Your First Location

Navigate to Settings

Go to Settings > Restaurantes in the main navigation.

Click 'Nuevo Restaurante'

Click the + Nuevo Restaurante button in the top-right corner.

Fill in Basic Information

Required fields:

Name: The restaurant name (e.g., “La Tasca Claudio Coello”)
City: Location city

Optional but recommended:

Marca: Associate with a brand if managing multiple concepts
Address: Full street address
Código Postal: Postal code
Phone and Email: Contact information

Configure Settings

Set operational parameters:

Capacidad Total: Total seating capacity
Zona Horaria: Timezone (default: Europe/Madrid)
Moneda: Currency (default: EUR)
CoverManager Slug: Your Cover Manager location identifier

Activate the Location

Check Restaurante activo to make the location operational.Click Crear to save.

Location Data Structure

Each location in Hiro stores the following information:

interface Location {
  id: string;
  brand_id?: string;           // Optional brand association
  name: string;                // Restaurant name
  slug: string;                // URL-friendly identifier
  address?: string;            // Street address
  city?: string;               // City
  postal_code?: string;        // Postal code
  country?: string;            // Country code (default: ES)
  phone?: string;              // Contact phone
  email?: string;              // Contact email
  timezone?: string;           // Timezone (default: Europe/Madrid)
  currency?: string;           // Currency (default: EUR)
  total_capacity?: number;     // Seating capacity
  covermanager_slug?: string;  // Cover Manager integration
  revo_tenant?: string;        // Revo TPV integration
  is_active?: boolean;         // Active status
}

See frontend/app/actions/locations.ts:11-35 for the complete type definition.

Managing Multiple Locations

Viewing All Locations

The Restaurantes settings page displays all your locations in a grid:

Active locations are marked with a green “Activo” badge
Each card shows the location name, city, and brand
Use the search bar to filter locations by name, city, or brand

Editing Locations

Click 'Editar' on a Location Card

Find the location you want to edit and click the Editar button.

Update Information

Modify any field in the form. All changes are tracked and timestamped.

Save Changes

Click Actualizar to save your changes.

Changing a location’s slug will affect URLs and API integrations. Only modify slugs if necessary.

Deactivating Locations

To temporarily disable a location without deleting it:

Edit the location
Uncheck Restaurante activo
Save changes

Inactive locations won’t appear in reservation systems or analytics but maintain their data.

Deleting Locations

Hiro uses soft deletes to protect your data:

Click the trash icon on a location card
Confirm the deletion

You cannot delete a location that has associated reservations. Deactivate it instead.

Location-Based Features

Location Filtering

Most views in Hiro support location filtering: Dashboard: Select a location from the dropdown to view location-specific stats

// Example: Dashboard location selector
<select value={selectedLocation} onChange={(e) => setSelectedLocation(e.target.value)}>
  <option value="all">Todos los locales</option>
  {locations.map((loc) => (
    <option key={loc.id} value={loc.id}>{loc.name}</option>
  ))}
</select>

See frontend/components/dashboard/CustomizableDashboard.tsx:439-447 Analytics: Filter reports by location for insights Reservations: View and manage reservations per location

Location-Specific Integrations

Each location can have unique integration credentials: Cover Manager:

Set covermanager_slug to sync reservations
Configured in Location Settings

Revo TPV:

Set revo_tenant for POS integration
Syncs orders and revenue data

See frontend/lib/inngest/functions.ts:15-91 for sync workflows.

Brands and Multi-Concept Management

What are Brands?

Brands allow you to group locations under different restaurant concepts:

La Tasca (tapas concept) - multiple locations
Manero Steakhouse (fine dining) - multiple locations
Claudio Coello (flagship location)

Each location can belong to one brand, or operate independently.

Creating Brands

Navigate to Settings > Marcas
Click + Nueva Marca
Configure brand identity:
- Name and slug
- Brand colors and logo
- Default settings for locations

Assigning Locations to Brands

When creating or editing a location:

Select a brand from the Marca dropdown
The location inherits brand styling and settings
Brand appears on location cards and reports

Multi-Location Workflows

Daily Operations Across Locations

View All Locations
Focus on One Location
Compare Locations

Dashboard View: See aggregated stats from all locations

// All locations stats
const stats = {
  totalReservations: 145,  // Sum across all locations
  totalPax: 380,           // Total diners
  vipCount: 12,            // VIPs across locations
  expectedRevenue: 15420   // Combined revenue
}

Filtered View: Select a specific location from the dropdown

// Single location stats
const stats = {
  totalReservations: 42,   // La Tasca Claudio Coello only
  totalPax: 98,
  vipCount: 3,
  expectedRevenue: 4200
}

Syncing Multi-Location Data

Hiro automatically syncs data from all active locations:

Automatic Sync

Background jobs sync each location’s data:

Cover Manager: Every 30 minutes
Revo TPV: Every 15 minutes
Loyalty calculations: Daily at 2 AM

Manual Sync

Use the Sincronizar button on the Dashboard to force a sync:

const handleSync = async () => {
  const result = await syncTodayAction(selectedLocation);
  if (result.success) {
    toast.success(`${result.count} reservas sincronizadas`);
  }
};

See frontend/components/dashboard/CustomizableDashboard.tsx:367-383

Monitor Sync Status

Check sync logs in Settings > Integraciones for each location.

Best Practices

Consistent Naming

Use clear, consistent location names:

✅ “La Tasca - Claudio Coello”
✅ “Manero Steakhouse - Recoletos”
❌ “Location 1”
❌ “Test Restaurant”

Keep Slugs Stable

Don’t change slugs after initial setup. They’re used in:

URLs and deep links
API integrations
External systems (Cover Manager, etc.)

Set Accurate Capacity

Configure realistic total_capacity for each location:

Affects reservation availability
Used in demand predictions
Impacts staff recommendations

Use Brands for Reporting

Group locations by brand to get:

Brand-level analytics
Cross-location insights
Consolidated reporting

Troubleshooting

Location not appearing in dropdown

Reservations not syncing for a location

Verify integration credentials:

Edit the location
Check covermanager_slug is correct
Verify API keys in Settings > Integraciones
Check sync logs for errors

Cannot delete a location

Locations with reservations cannot be deleted:

Check if the location has associated reservations
If yes, deactivate instead of deleting
Soft delete preserves historical data

See frontend/app/actions/locations.ts:336-344 for deletion logic.

Wrong timezone for a location

Each location can have its own timezone:

Edit the location
Set Zona Horaria (e.g., “Europe/Madrid”)
This affects reservation times and reporting

Next Steps

Now that you’ve set up your locations:

Configure User Roles

Set up role-based access for your team across locations

Set Up Automations

Configure automated workflows for each location

View Analytics

Track performance across all your locations

API Overview

Access location data programmatically

Get Started

Core Features

Integrations

Deployment

Guides

Multi-Location Setup

Understanding Locations

Creating Your First Location

Location Data Structure

Managing Multiple Locations

Viewing All Locations

Editing Locations

Deactivating Locations

Deleting Locations

Location-Based Features

Location Filtering

Location-Specific Integrations

Brands and Multi-Concept Management

What are Brands?

Creating Brands

Assigning Locations to Brands

Multi-Location Workflows

Daily Operations Across Locations

Syncing Multi-Location Data

Best Practices

Consistent Naming

Keep Slugs Stable

Set Accurate Capacity

Use Brands for Reporting

Troubleshooting

Next Steps

Configure User Roles

Set Up Automations

View Analytics

API Overview

Build docs developers (and LLMs) love

Get Started

Core Features

Integrations

Deployment

Guides

​Understanding Locations

​Creating Your First Location

​Location Data Structure

​Managing Multiple Locations

​Viewing All Locations

​Editing Locations

​Deactivating Locations

​Deleting Locations

​Location-Based Features

​Location Filtering

​Location-Specific Integrations

​Brands and Multi-Concept Management

​What are Brands?

​Creating Brands

​Assigning Locations to Brands

​Multi-Location Workflows

​Daily Operations Across Locations

​Syncing Multi-Location Data

​Best Practices

Consistent Naming

Keep Slugs Stable

Set Accurate Capacity

Use Brands for Reporting

​Troubleshooting

​Next Steps

Configure User Roles

Set Up Automations

View Analytics

API Overview

Build docs developers (and LLMs) love

Understanding Locations

Creating Your First Location

Location Data Structure

Managing Multiple Locations

Viewing All Locations

Editing Locations

Deactivating Locations

Deleting Locations

Location-Based Features

Location Filtering

Location-Specific Integrations

Brands and Multi-Concept Management

What are Brands?

Creating Brands

Assigning Locations to Brands

Multi-Location Workflows

Daily Operations Across Locations

Syncing Multi-Location Data

Best Practices

Troubleshooting

Next Steps