Project 01 · Case study

Multi-site restaurant platform

Mobile ordering, partner SSO, operations, event commerce, and invoicing for a restaurant chain.

Full-stack product engineer · mobile, access, and operational systems

The mobile app sat inside the product system of a multi-site restaurant chain. Ordering had to connect to multi-company access, operational tooling, event commerce, and invoicing—without turning those concerns into isolated products.

One service, several people depending on it

Employees used a mobile product to order. Partner organisations needed access through their own identity systems. Restaurant teams worked through operational paths. Event customers entered through a different commercial flow that continued into management and invoicing.

The challenge was not to make every path identical. It was to give each audience a clear journey while keeping their work connected to one service and administration layer.

Mobile experience, identity, and connected operational work

I built the mobile experience and the backoffice authentication layer. I implemented SAML SSO for partner organisations so their people could use existing identity systems instead of a parallel account flow.

I also worked on POS integration and the supporting services around it, daily and weekly menu-management workflows, and event ordering, management, and invoicing as a contributor.

  1. A clear customer entry point

    The mobile experience had to remain usable even though an order connected to systems and teams beyond the screen.

  2. Partner access inside the product path

    SAML SSO made organisational access a deliberate product capability rather than a separate administrative workaround.

  3. Menu and POS work as product work

    Daily and weekly menus, POS integration, and supporting services were part of the operating rhythm behind the ordering experience.

Keep commercial flows connected

Event ordering was not just another checkout screen. It needed to remain connected to management and invoicing without becoming a separate tool beside everyday restaurant service.

That same principle applied to partner access and menu work: cross-system complexity belonged at the right boundary, while each audience retained a coherent path through the product.

The parts of the product I worked on

Scope is deliberately grouped by my ownership boundary. It is not a claim about the whole system.

01

Direct work

  • Mobile product work.
  • The backoffice authentication layer.
02

Built

  • SAML SSO for partner organisations.
03

Worked on

  • POS integration and supporting services.
  • Daily and weekly menu-management workflows.
04

Contributed to

  • Event ordering, event management, and invoicing workflows.