Foaps Receiver was already being used to manage restaurant orders when I joined the project. My main focus was extending the product so that businesses with multiple outlets under the same location or account could use the same system without mixing up their operations.
I worked on the product as a UI/UX Designer, mainly around the multi-outlet experience and the changes needed to support it.
The original product was designed around a simpler setup, where a business could manage its orders from a single outlet.
As businesses grew, some started operating multiple outlets. They needed to manage them from the same system while still keeping orders, menus and operations separated between locations.
The challenge was to add this flexibility without making the existing product harder to use.
I worked on extending the existing product to support multiple outlets under one business.
The interface needed to make it clear which outlet the user was working with, while still allowing them to move between outlets when needed.
The goal was to keep the existing workflow familiar rather than forcing users to learn an entirely new product.
Receiver could now support businesses operating multiple outlets while keeping each outlet's operations separated.
Instead of creating separate accounts or systems for every location, businesses could manage their outlets from the same product — giving Foaps Receiver a stronger foundation for larger restaurant groups.
Since Receiver was already in use, I first looked at how the existing product worked and where the single-outlet assumption existed across the experience. This helped identify which parts needed to change and which parts were better left untouched.
I mapped how a business, its outlets, users and orders were connected. The important distinction was keeping business-level information separate from outlet-level operations. This became the foundation for the new experience.
One of the key parts was making outlet selection obvious without constantly getting in the way. Users needed to know where they were working at any point, while being able to switch outlets when required.
Rather than redesigning everything, I went through the existing flows and adapted the relevant screens for the new structure. This included areas where orders, menus, settings and other information were tied to a specific outlet.
I also worked through situations such as switching outlets, having different outlet configurations, and making sure the user always had enough context to understand which outlet they were managing.
The biggest constraint was not breaking what already worked. The multi-outlet experience had to feel like a natural extension of Receiver rather than a completely different product.
