Building QRelia through a live deployment at Le Pommier Hotel
This project began as a request for a QR ordering system — but quickly revealed a deeper problem:
hospitality operations break down under pressure. Orders get miscommunicated, modifiers are misunderstood,
and staff rely on fragmented tools that don’t reflect real-time reality.
Instead of building a thin “digital menu”, I engineered a real-time operational platform where guest actions,
kitchen workflow and management control exist as one connected system. That foundation evolved into what is now
QRelia — a scalable hospitality platform.
- End-to-end system designed & built solo
- Real-time operational architecture (SignalR)
- Multi-tenant SaaS foundation
- Complex menu & modifier handling
- IoT-ready event-driven system
Live Operations Snapshot
System Shape
From one venue problem to a broader hospitality product
The initial requirement sounded simple: allow guests to order via QR code.
In practice, the real challenge was operational — ensuring orders are clear, correctly structured,
immediately visible to staff, and manageable under real service conditions.
Rather than building a surface-level solution, I designed a system where guest interaction feeds directly into
internal operations in real time. The result is not just ordering — it is a coordinated operational flow,
designed to scale beyond a single venue.
Designed for real hospitality environments, not a single use case
This system was not built for one static scenario. It was designed to operate across multiple service environments
within the venue, each with different expectations, pacing and operational constraints.
At Le Pommier, the platform supports:
Room Service
Guests can order directly from their rooms with full menu access, structured modifiers and clear delivery context, while staff receive clean, actionable orders without additional interpretation.
Poolside Ordering
A more dynamic environment where location awareness and speed matter. QR routing ensures orders are tied to the correct area, allowing staff to respond efficiently without confusion.
Al Fresco Dining
Outdoor dining introduces variability in service flow. The system maintains clarity across tables, modifiers and timing, while preserving a premium guest-facing experience.
Importantly, this system is not designed to replace human interaction — it enhances it.
By removing friction from ordering and reducing the need for guests to actively seek attention,
staff are able to focus on delivering the service itself rather than chasing requests.
The result is a shift from “in-your-face” service to hospitality on demand —
where the human touch arrives faster, more precisely, and at the moment it’s actually needed.
This is especially valuable in more private environments such as rooms, poolside areas or outdoor dining spaces.
The key idea is consistency: the same underlying system adapts to different environments without fragmenting the experience. This is where QRelia moves beyond “QR ordering” and becomes a unified operational layer across the venue.
Hospitality looks simple on the surface. It rarely is underneath.
Real hospitality operations contain edge cases everywhere: modifiers, timing, different menus by period, location-aware ordering, staff visibility, item availability, category ordering, wine-specific pricing rules, and the need to avoid adding more friction to already busy teams. Most generic QR systems flatten this complexity. I took the opposite route and built around it.
- Guests needed a smooth ordering flow that still respected real menu structure.
- Staff needed instant clarity, not another confusing dashboard.
- Management needed control over menus, areas, QR placement and operational changes.
- The product needed to be strong enough to become a reusable SaaS platform, not just a one-off build.
Build the venue solution like the first tenant of a larger product
Model the real workflow
I treated guest ordering, kitchen visibility and admin control as one continuous system rather than isolated pages.
Centralise logic in shared services
Core business logic, models, SignalR hub, EF Core access and tenant-aware services live in a shared library.
Design for scale from day one
Tenant propagation, grouped real-time broadcasting and modular apps created the base for the wider QRelia platform.
OPush beyond software alone
The project also informed an IoT layer where physical devices respond to live operational events in the venue.
What the platform actually does
This was not a brochure-site level build. It included meaningful operational logic, multiple applications, structured data flows, real-time communication and careful UX handling around menu complexity.
Guest Ordering Experience
Mobile-first customer journey with polished visuals, category-based menu browsing, basket creation, modifier selection, order confirmation and live order status updates.
Advanced Modifier Logic
Support for modifier groups, single or multi-select rules, min/max selections, color-coded options and clearer representation of order intent rather than raw item lists.
Wine-Specific Pricing Model
A dedicated inheritance-based model for wines supporting size-dependent pricing such as glass, 175ml, 250ml and bottle within the same broader menu architecture.
Kitchen / Receiver Interface
Separate receiver application for kitchen and staff devices, designed for clarity and supported by audio notification when new orders arrive.
Admin Control Layer
Manage locations, areas, menus, categories, items, modifier groups, staff accounts, QR generation, dashboard metrics and availability windows from a dedicated admin portal.
Real-Time SignalR Workflow
New orders and order status changes propagate live across the platform, removing lag between guest action and staff awareness while also powering external connected devices.
QR Routing by Area & Location
QR codes direct guests into the correct context, passing through ordering parameters so the platform knows where the order originated.
Multi-Tenant Foundation
Tenant-aware middleware, grouped broadcasts and data isolation mean the same product architecture can serve multiple venues under the QRelia platform.
IoT-Ready Direction
The same event stream can drive ambient operational hardware such as connected bar devices with LEDs and OLEDs, bridging digital workflow and physical space.
A modular system built for delivery now and scale later
I designed the product as four connected applications sharing a common domain and database layer. That allowed fast iteration for the live venue while keeping the architecture organised and reusable.
Why this mattered
Hospitality software can become messy very quickly when features are added in reaction to operations. I deliberately centralised the domain and service logic so each application stays focused on its role while the rules remain consistent across the whole platform.
- Shared domain logic reduces drift between customer, admin and receiver apps.
- SignalR hub becomes the operational spine of the system.
- Tenant-aware grouping keeps the SaaS path viable.
- Future integrations and external device listeners remain possible without rethinking the whole product.
Solving for real use, not just visual polish
Good hospitality UX is not just about making things look elegant. It is about reducing decision friction for guests and operational friction for staff at the same time. That shaped many implementation decisions, from how modifiers are presented to how menu categories are ordered and how order states appear live.
- Premium UI language with gradients, blur, spacing and visual hierarchy.
- Ordering flow designed around clarity, not feature dumping.
- Improved representation of complex item configurations.
- Admin controls focused on actual day-to-day venue needs.
- Room for future platform-level experience upgrades under QRelia.
Real-time isn’t a gimmick here. It changes the workflow.
When a guest places an order, the system doesn’t simply save it and hope someone notices. It triggers a real-time chain across the venue. Receiver devices update, staff get immediate awareness, statuses can flow back to the guest journey, and the same event stream can also drive connected ambient hardware.
- New order broadcasts reduce manual checking.
- Status updates help keep the guest informed.
- Operational signals can be consumed by multiple interfaces at once.
- This same pattern becomes a major differentiator for QRelia as a platform.
This project also shaped a wider idea: ambient operational computing
One of the most exciting outcomes of this work is that it informed a hardware direction as well. Because the operational state already exists as real-time events, it can be translated into physical signals inside a venue. That opens the door to an entirely different class of hospitality experience.
Connected Venue Devices
I prototyped a Raspberry Pi-based device that listens to live order events and communicates them through LEDs and OLED displays. In practice, that means the venue environment itself can become an operational interface: not only screens, but light, motion and ambient cues.
Why it matters for QRelia
Most hospitality systems stop at software screens. QRelia is moving toward a model where software, operations and physical environment can work together. That is where the platform becomes more than ordering. It becomes infrastructure for how a venue behaves in real time.
The long-term vision is not just better QR ordering. It is a hospitality platform where guest experience, staff operations, real-time data and connected physical systems converge into one coherent product ecosystem.
Direction shaped directly through the Le Pommier build and expanded through QRelia.What this case study says about my work
This project reflects how I work at my best: I do not just implement pages or features in isolation. I connect product thinking, technical architecture, operational understanding and interface quality into one system.
I build full systems, not fragments
From guest flow to admin tooling to receiver interface to live event architecture, the whole delivery is connected.
I can turn a client project into product infrastructure
The Le Pommier delivery was not trapped as a one-off. It became the foundation for QRelia.
I think beyond obvious software boundaries
The IoT direction emerged naturally because the system was built around real-time operational events.
I care about UX and underlying complexity equally
Premium visuals matter, but only when they sit on top of solid workflow and durable implementation.
I work well with real-world operational detail
Hospitality brings edge cases, exceptions and timing constraints. I am comfortable building inside that reality.
I design with scale in mind
Tenant-aware architecture, modular apps and shared business logic gave this project a future beyond one venue.
QRelia started as a venue solution. It is becoming a hospitality platform.
The Le Pommier case study captures a transition point in my work: from delivering bespoke software to shaping a product with broader strategic potential. It shows how a real client engagement became the proving ground for a much larger idea — a modern hospitality ecosystem built on real-time operations, strong interface design, scalable architecture and a willingness to rethink how digital systems interact with physical space.