xolus.
← Back
Sushi XO · 2025 – active

An online ordering site connected directly to the POS system, with a loyalty program the POS couldn't deliver

Sushi XO started with a single restaurant, a phone, and orders on paper. Today they operate at five locations, and the site handles hundreds of orders a day — connected directly to the POS in the kitchen, with SMS login and a loyalty program the POS couldn't support.

View live ↗

The story

From one location to five during our collaboration — and a loyalty program the POS couldn't support.

Worth noting

  • · From 1 to 5 locations during our collaboration
  • · Hundreds of orders a day through the web app
  • · The phone is no longer the bottleneck

The problem

Ordering by phone doesn't scale. As order volume grows, the phone becomes the bottleneck: staff lose time on entry, errors happen during rushes, there's no way to recognize a regular customer and reward returns. The client wanted a web app for delivery and pickup, a loyalty program that actually brings guests back, and an integration with the existing POS — without replacing it. Hard constraint: the POS they use doesn't support loyalty, and there was no good alternative. The system had to extend the POS, not take it over.

What we built

We built a two-part solution. On the customer side — a modern web app for ordering, designed from scratch in Figma so it carries the Sushi XO brand rather than the template every restaurant has: menu, cart, delivery or in-person pickup, SMS login without passwords. On the business side — a middle layer that fills what the POS lacks: a unified customer registry across all five locations, discount-based loyalty mechanics, automatic SMS notifications about order status, and a direct integration that drops online orders straight into the POS as a kitchen ticket. The phone is no longer the bottleneck; the kitchen sees one queue regardless of where the order came from.

Modules & surfaces

  • Web app for orderingMenu, cart, delivery or pickup choice, ordering, history. Mobile-first — the vast majority of orders come from a phone.
  • SMS login and authenticationSign-in by phone number, no passwords. Faster for the user, a unified identity for the loyalty system.
  • Loyalty programTracks customer activity and automatically applies discounts to qualifying orders. What the POS doesn't support on its side — added on our side, without touching the kitchen flow.
  • POS integrationAn online order drops straight into the POS as a kitchen ticket. Same queue, same flow, no manual rewriting.
  • Unified customer registryOne record per customer across all five locations — history, favorites, loyalty.
  • SMS notificationsOrder confirmations, statuses, loyalty events — all via SMS.

How we approached it

We started with a conversation with the client about what the POS actually does, where it stops, and what happens to an order after the customer hangs up the phone. We first built the middle layer, the customer registry, and loyalty before we even worked on the customer-facing design. For the customer we designed a standalone branded product, not yet another SaaS template. The most important phase was testing the integration with the actual POS: loyalty plus ordering had to land cleanly in the flow the kitchen already knows. After production went up we kept iterating as the chain grew.

Outcome

Sushi XO grew from one location to five during our collaboration. The site handles hundreds of orders a day. The loyalty program actively brings repeat guests — and that's without a single change in the POS. It's currently in version 2, with version 3 in the works. We do all of their software projects.

In use

Related case studies

Next case study

An operational system for multi-country e-commerce — orders, warehouses, packages, couriers, and data ingest from multiple formats →