Company Hierarchy

Mando organizes business data in a three-level hierarchy: Company → Location → POS. Companies also form a parent-child tree, enabling multi-brand and franchise setups that share common features, such as products.

Hierarchy Overview

Root Company (parent_id = null, data.root = true)
├── Child Company A (parent_id → Root)
│   ├── Location 1
│   │   ├── POS 1  (postype: FlowPOS Windows)
│   │   └── POS 2  (postype: Android POS)
│   └── Location 2
│       └── POS 3
└── Child Company B (parent_id → Root)
    └── Location 3
        ├── POS 4
        └── POS 5

Example: Restaurant Chain

A restaurant chain “Burger Palace Oy” has restaurants in two cities, each operated as a separate company:

Level	Entity	Name	Notes
Root company	Company	Burger Palace Oy	data.root = true, owns shared product catalog
Child company	Company	Burger Palace Helsinki	parent_id → Burger Palace Oy
Child company	Company	Burger Palace Tampere	parent_id → Burger Palace Oy
Location	Location	Kamppi Restaurant	company_id → Helsinki company
Location	Location	Kallio Restaurant	company_id → Helsinki company
POS	POS	Kamppi Register 1	location_id → Kamppi, postype_id → FlowPOS config
POS	POS	Kamppi Self-Service	location_id → Kamppi, postype_id → Android config

The root company defines shared settings (accounting integrations, customer groups, product numbering). Child companies inherit products and can override location-specific settings.

Company Model

A company represents a business entity (legal entity with a business ID).

Field	Type	Description
id	guid	Unique identifier
name	string	Company name
ident	string	Business ID (Y-tunnus)
parent_id	id	Reference to parent company (null for root company)
active	boolean	Whether the company is active
state	string	Company state
data	company_data	Nested configuration (see below)

Company Types

The company_type enum defines the role: mando, mando_mini, root, reseller.

Key flags in data:

• data.root — marks a root company (top of the tree)
• data.reseller — marks a reseller that can create child companies
• data.type — the company type enum value

Each reseller company manages its own companies and has access to them. In API context this can be ignored.

Company Data (key sections)

The data field (type company_data) contains most of the company configuration:

• address — company address (line1, line2, postnumber, city, country)
• display_name — display name shown in UI, commonly a shop name
• contact, phone, admin_email — contact information
• additional_fields — custom field definitions for various entities (products, customers, locations, etc.)
• languages — available translation languages
• default_tags — default product tags
• product_numbering — product numbering template
• Accounting integrations — netvisor, procountor, fennoa (each with active flag, credentials, sync settings)
• E-commerce integrations — shopify, woocommerce, ecommerce
• franchising — franchise fee configuration
• timesheets — timesheet tracking configuration
• sales_channels — sales channel definitions (e.g. dine-in, takeaway, delivery)

Location Model

A location is a physical place of business (store, restaurant, warehouse) belonging to a company.

Field	Type	Description
id	guid	Unique identifier
company_id	guid	Owning company
parent_id	id	Optional parent location (for sub-locations)
name	string	Location name
active	boolean	Whether the location is active
data	location_data	Nested configuration (see below)

Location Data (key sections)

• address — street address
• position — GPS coordinates (lat, lng)
• email, phone — contact info
• opening_hours — per-day open/close times with optional time slots
• service_periods — named time periods (Breakfast, Lunch, Dinner) with schedules
• Location type flags — sales_location, stock_location, weeklyreport_location
• Calculation flags — calculate_stock, calculate_wastage, calculate_profit, calculate_labor_metrics, track_table_turnover
• tables / tableMaps — restaurant table/seating map configuration
• stock_locations — warehouse stock location mappings
• assortment — products not for sale or out of stock at this location
• weekly — weekly report parameters and data availability flags
• email_reports — automated email report settings
• wolt — Wolt delivery platform integration
• stock_settings — inventory management settings (auto-update, thresholds, cost method)

POS Model

A POS (point of sale) is a terminal/register at a location.

Field	Type	Description
id	guid	Unique identifier
company_id	guid	Owning company
location_id	id	Location where this POS is installed
name	string	POS name (e.g. “Register 1”)
active	boolean	Whether the POS is active
postype_id	id	Reference to POS type (configuration template)
data	pos_data	Nested configuration (see below)

POS Data (key sections)

• subscriptions — which tenders, pricings, discounts, and infocodes this POS uses
• receipt — receipt header/footer text and image
• eft — payment terminal identifier
• hostname — network hostname
• network_type — standalone, host, mobile, or selfservice
• network_host — reference to host POS (for networked setups)
• sales_channels — active sales channels for this POS
• automatic_open / automatic_close — auto open/close times

POS Type

Each POS references a postype — a configuration template that defines:

• Hardware settings (posagent) — payment terminal mode, printer configuration, customer display, scale
• Feature flags (flowpos) — table sales, kitchen printing, delivery, wastage tracking, order numbers, etc.
• Terminal platform — flowpos (Windows), android, castles, pos2 (POS 2026), etc.
• Receipt templates — which templates to use for customer receipts, kitchen slips, reports
• Peripheral devices — connected printers, scales, displays

Multiple POS devices can share the same postype, making it easy to configure a fleet of identical terminals.

Relationships Summary

Company (tree via parent_id)
  └── has many → Location (tree via parent_id)
       └── has many → POS
                        └── references → POS Type (configuration template)

• Company → Company: parent-child tree via parent_id. Root companies have parent_id = null.
• Company → Location: one-to-many via location.company_id.
• Location → Location: optional sub-hierarchy via location.parent_id.
• Location → POS: one-to-many via pos.location_id.
• POS → POS Type: many-to-one via pos.postype_id. The postype is a shared configuration template.
• POS → Company: also linked via pos.company_id (same company as the location).