ONA
Use case · Hospitality & multi-location

Configurations for shift-based locations.

Hospitality businesses use four recurring ONA configurations. Each configuration defines location setup, data model and access control.

The architecture is not limited to hospitality. Any multi-location business with shift work and mixed contract types maps onto the same model.

Configurations

Four configurations. Location, division, access rights and payroll run — the same architecture.

Each configuration describes location count, data model and access rights. Modules and payroll run stay identical.

Restaurant chain

3 – 15 locations → shared data model → location-based access control. Optional franchise separation via separate billing address.

  • 3 – 15 locations
  • Franchise-ready
  • Location roles

Single location with departments

1 location → divisions for kitchen, service, bar → own positions per division. Hour totals are consolidated across divisions.

  • 1 location
  • Divisions
  • Positions

Café · bar with POS

SumUp connected → daily revenue per location and day → staff cost ratio in the dashboard. Payroll run lives in the same system.

  • SumUp
  • Daily revenue
  • Staff cost ratio

Hotel · front- and back-of-house

Several departments → youth-protection and maternity rules in the data model → automatic check at write time.

  • Several departments
  • Youth protection
  • Maternity protection

The model is industry-agnostic. Retail configuration available on request.

Book a demo

One payroll run. Your setup. 30 minutes.

No generic demo. We configure ONA around your locations, contracts and POS connection — and run trial payroll in the system.

  • Locations and contract types as input
  • Trial payroll live in the system
  • Response within one business day
  • No contract commitment
Book a demoOpen platform

Reply within one business day.