All work

UX/UI Design · Baemingo · UX/UI design of a menu builder

Letting restaurants build the ordering menu their customers see

I designed the layout builder in the Baemingo back office: the tool where a restaurant decides how its menu looks to customers in the ordering app and self-service. Staff create categories, add products and style each category card, and see the result in a phone preview as they work. Every change saves automatically.

My role
UX/UI designer, alongside my role as Product Development Lead
Year
2021–2022
Industry
Restaurant tech, B2B SaaS
Company
Baemingo
Users
Restaurant owners and staff
Platform
Web app, with a preview of the ordering app
Tools
Figma

The short version

The challenge

Restaurants had their products in the system, but needed a way to turn them into a menu that works for their customers in each sales channel, without help from Baemingo.

What I did

I designed the flow and the UI of the layout builder, from creating a layout to categories, products, styling and sort order, and tested it with users.

What it was built for

A menu that restaurant staff can build and change on their own, and see exactly as their customers will see it.

What I did as UX designer

Flows and structure

How a layout is created, named and connected to a sales channel and a menu, and how it is found and edited again later.

UI design for the back office

Finished screens for every step: the layout list, the builder, the category and product panels and the detail view.

Live preview

Two phone previews in the builder, so staff see the menu the way their customers will see it while they build it.

Interaction details

Autosave, drag and drop for sort order, a step that opens only when it can be used, and guidance on the page.

Usability test

Testing showed the order users expected: first create the products, then the layout, the menu.

Next steps

Ideas for the product backlog: visibility by service type or time, colour palettes, subcategories and app branding.

01

The challenge

In Baemingo, products are created once, in the product catalogue (PIM). But a list of products is not a menu. A restaurant needs to decide how the products are grouped and shown to the people ordering: in the ordering app, in a self-service kiosk or at the till.

A layout is that decision: how staff or customers experience the menu when they place an order. In a usability test, users described the order they expected to work in:

  1. Create the productsName, price, image, description and ingredients, in the product catalogue.
  2. Create a layoutWhich is the menu: the categories and products the customer sees, and how they look.

So the layout builder had to start from products that already exist, and make building a menu feel like arranging it, not like filling in forms.

02

Version 1 and the user test

Building menus was one of the biggest pain points for new restaurants. I designed a first version of the menu builder, tested it with users, and improved it from what we learned.

Version 1: create a menu layout

The first version of the Menu layout page: a layout name, a sales channel and a Create layout button, with an empty list of existing layouts
The first version: name the layout, pick a sales channel and create it.

Version 1: build the menu in a phone preview

The first version of the builder: two phone previews with the Lunch category and Ohana Bowl, and a panel to edit the category and select products
Categories and products in a phone preview, with one panel to style the category and pick its products.

What we tested

  1. Is it easy to understand what to do, and how?Create the first layout: enter a name, and create it.
  2. Is it easy to understand the menu layout as a concept?That a layout is how the menu looks to the people ordering, separate from the products themselves.

What we learned

  1. Products first, then the menuUsers wanted to first create their products, and then create the layout: the menu.
  2. Drag and drop workedThe format, with categories and products sorted by drag and drop, held up as the menu grew.
  3. Help with coloursUsers asked for recommended colour palettes instead of typing hex codes.

The rest of this case shows version 2, improved from what we learned.

03

Create a layout

A new layout needs three things: a name, a sales channel and a menu. The sales channel list only shows the channels the company has activated, and choosing the till (POS) leads to the POS layout. Existing layouts are listed next to the form, so they are easy to find and change later. Click a screen to enlarge it.

Name the layout and pick sales channel and menu

The Layout page with a form: layout name, sale channel Mobile app / Online ordering, and the menu dropdown open with Online menu, Bas menu and POS menu
A layout is connected to one sales channel and one of the menus the restaurant has already created.

Find and edit existing layouts

The Layout page with an empty form and a list of existing layouts with Baemingo online layout
Once created, the layout appears under Existing layouts. A click opens it in the builder.
04

Build the menu

The builder shows the menu in two phone previews: the start of the menu with its categories, and the category that is open with its products. Panels for adding and editing open on the right, so the preview always stays in view.

Start with the first category

The builder with two empty phone previews, Create layout category active and Add product greyed out, and a layout summary with a three-step guide on the right
Until the first category exists, Add product is greyed out. The right side shows a summary of the layout and how to get started.

Style the category card

The Create layout category panel with name Lunch, text colour #FFFFFF, background colour #474762, an image upload and a toggle Use image as background
Name, text colour and background colour, with defaults filled in. An image can be used as background instead.

Add products to the category

The Lunch category with Ohana Bowl in the preview, and a panel listing products by group, Bowls, Dryck, Pizza and more, with Add, Add all and Remove
Products are picked from the catalogue, grouped as they are there. The product shows up in the preview as soon as it is added.

Change the order

The builder with the categories Lunch and Dessert in the menu preview and Ice cream in the Dessert category, and All layout changes saved! at the top
Categories and products are sorted by drag and drop. All layout changes saved! confirms that nothing needs to be saved by hand.

Edit a product from the layout

The detail view of Ohana Bowl as it looks in the ordering app, with the article panel on the right: name, category, VAT, cost, price, description and image
A click on a product opens it as the customer will see it, with the product panel next to it. Changes other than price are saved on the product in the catalogue.
05

Key design decisions

Show what the customer will see

The builder is two phone previews: the menu with its categories, and the category that is open. What staff build is what customers get in the app, so they never have to guess.

One step at a time

Add product stays greyed out until the first category exists. The order of the work is shown by the interface, not explained in a manual.

Guidance where the work happens

While no panel is open, the right side shows a summary of the layout and a short guide in three steps. It disappears when there is work to do.

Products are reused, not copied

Products come from the product catalogue (PIM) and are added per category, so the same bowl can sit under both Lunch and Bowls without being created twice.

Simple styling with safe defaults

Each category card has a name, a text colour and a background colour with defaults filled in, or an image as background with one toggle.

Nothing gets lost

Changes save automatically, and “All layout changes saved!” confirms it. Sort order is changed by drag and drop, and a product can be edited from the layout itself.

06

Next steps

Ideas I noted for the product backlog, beyond this design:

  1. Visibility settingsShow a category or product only for a certain service type or time of day, such as lunch.
  2. Colour palettesChoose from a palette or a recommended colour combination instead of typing a hex code.
  3. SubcategoriesNot supported in this design, and an open question for the next round.
  4. App brandingA place to set up the start page and general branding, such as logo and default colours.