Download CV
← all 25 systems

platform · 2025 · client unnamed

Hotel PMS with Gym and Restaurant

One guest folio across three businesses on one site, so a hotel guest using the gym and the restaurant is a single account.

21

Domain models

3

Subsystems

hotel, gym, restaurant

541

Technical README

lines, with diagrams

The problem

A hotel also operating a gym and a restaurant had three systems and therefore triple data entry, with no unified view of a guest who used all three. Cross-subsidiary charging is the specific thing that breaks: a guest signs for lunch and the charge needs to reach their room folio.

The approach

Twenty-one interlinked models across the three subsystems sharing one guest identity, so hotel stays, gym membership and restaurant billing all resolve to the same person and the same folio. An admin frontend served directly from the API, plus a technical README with diagrams, because a system this interlinked is unmaintainable without one.

Architecture

Shared guest identity across three subsystems, with charges from any of them able to post to a single folio.

One decision

Each with what it cost

A decision without a stated tradeoff is a preference.

01

One guest identity across all three businesses

Why

The cross-subsidiary charge is the reason the client wanted one system. Separate identities per subsystem means matching people by name, which fails on the first duplicate.

What it costs

The guest model has to satisfy three different sets of requirements, making it the most constrained entity in the schema.

Outcome

One guest record follows the customer across all three businesses, and management sees consolidated revenue instead of three partial pictures.