From one hotel to a distributed hospitality system.

The first system is not built around a SaaS abstraction. It is built around the physical place where hospitality service happens.

The retained Le Pommier history begins with Admin and Receiver, then quickly adds Areas, Menus, MenuItems, Orders, Locations, URLs and QR entry points. That shape matters: a QR code is not merely a shortcut to a webpage. It maps a real room, table or service area into software context.

By the end of January the three surfaces that survive every later rewrite already exist: guest-facing ordering, an operational Receiver and an administrative control plane.

Persisting an order correctly is not enough if staff do not see it at the right moment. SignalR enters the codebase on 5 February and shortly afterwards live updates reach Admin as well.

Modifiers stop being a string and become groups, options, min/max selection semantics, descriptions and active state. Availability stops being a boolean and becomes time-aware, then gains multiple windows. Wine needs distinct rules. Cancelled orders change totals. Bestsellers need date ranges. Audit data gains provenance.

The useful part is that the abstractions are earned. There is no speculative service architecture invented before the problem. The schema changes because production requires the concept.

QRelia SaaS does not begin after the standalone system ends. It begins while the live venue product is still changing. One codebase has to keep serving real guests; the other has to remove the assumption that there is only one venue.

That turns correctness into a boundary problem. Registration, onboarding, tenant resolution, venue identity, devices and a QRelia super-admin appear while the standalone application continues to gain operational features.

Stripe, subscription lifecycle, two-factor authentication, device ordering, tenant operations, platform audit and QReliaAdmin move the boundary outward. The 28 April EF re-baseline becomes a platform consolidation point rather than the birth of the domain.

By June, branding is venue-controlled, QR Print Studio is a production tool and physical devices can be provisioned and owned as tenant objects. Ordering remains the centre of gravity, but no longer defines the system.

The first device repository begins eleven days after SaaS. Early OLED status, LED experiments and animation code evolve into a system that consumes the same operational events as Receiver.

The hardware reveals a different class of correctness problem: a stale webpage is wrong on one screen; a stale ambient light is wrong to everyone who can see the room.

The dedicated ambient-device history shifts the problem from “can the LEDs work?” to “can this become an appliance?”. It cannot assume SSH, valid Wi-Fi, a reachable cloud or a clean previous shutdown.

Performance also becomes a scheduling problem. LEDs, display refresh, heartbeat, SignalR and animation all compete for a small Raspberry Pi. Visual smoothness has to be cooperative with operational work.

When production moves into SaaS, the old QR codes are already on tables and in rooms. That means the physical artefact is part of the compatibility contract.

Legacy routes carrying AreaId and LocationId are translated into the new QRelia context so printed codes continue to resolve correctly. The best cutover is the one the guest never notices.

Replacing a 128×64 OLED with a 480×320 SPI LCD changes the physics. The production history becomes a performance investigation across SPI frequency, framebuffer strategies, damage refresh, boot presentation and renderer isolation.

The screen can be smooth and still be operationally wrong. If Wi-Fi is down, the footer cannot imply cloud readiness. If the unit is resetting, normal live-service status is misleading. If startup is complete, “runtime starting” is false state.

Urgency becomes part of the interface contract too: stale orders outrank Pending; Pending outranks lower-urgency state; multiple active orders scroll rather than disappear; a new SignalR event invalidates the visible selection immediately.