Restrictions and substitutions

Seat-level allergies and substitutions for fine dining service

Alinearo turns restriction notes into clear actions across FOH and kitchen.

Features

  • • KDS y pantalla cocina para fine dining.
  • • Aprobaciones antes de ejecutar pase.
  • • Pacing y coordinacion sala y cocina.
  • • Alergias y seat notes por comensal.
  • • Operacion offline LAN-first.
  • • Orquestacion de menu degustacion en Barcelona.

Restrictions visible where decisions happen

Guest restrictions persist through draft, approval and KDS with seat-level context.

  • Seat notes shared by floor and kitchen
  • Manual and suggested substitutions
  • Alerts when no valid substitute exists

Fewer pass errors

Guest-grouped changes reduce contradictions and keep counts accurate per course.

  • Grouped substitution lines by guests
  • Review before approval
  • Full edit traceability

Who it’s for

  • Restaurants handling high allergy/restriction variability.
  • Teams running seat-based service.

Not for

  • Operations without guest-level control.
  • Services that skip pre-execution validation.

Use cases

Request restrictions workflow demo

See how to reduce allergy-related service errors.

FAQ

How do seat-level allergies work?

They are captured by guest and resolved by seat once table mapping is done.

What if no valid substitute exists?

The ticket is flagged for review before kitchen approval.

Are restrictions visible in KDS?

Yes, KDS receives seat-level restriction and substitution context.