LifeChef
Ongoing development for personalised meal ordering, payments, delivery and a chef-facing application.
At LifeChef, I worked on an existing store where a change to a meal choice could affect the cart, account and delivery steps that followed.
- Field
- Meal delivery / USA
- Built with
- WordPress / WooCommerce
- Project year
- 2020–2022
The challenge
LifeChef was already selling prepared meals online when I joined the project. The store had to accommodate customers choosing dishes and putting together a menu, then carry that order through an account, a cart, payment and delivery. A change to the meal selection could not be treated as an isolated change to a product card.
The approach
I worked with OnePix on custom WooCommerce modules and support for LifeChef’s existing store. The scope covered the catalogue, menu, customer accounts, payments, delivery and a chef-facing application. The design changed more than three times, so the work continued across several versions of the product.
The meals behind the menu
These meal photos come from LifeChef’s public site in 2026. The project also includes original Figma design screens, labelled separately. My work took place in 2020–2022.
The project, in detail
The images show the interface and its context. Captions distinguish project archives from current-site views.
A meal is a sequence of choices
The customer-facing task starts with finding suitable dishes, then choosing what goes into an order. Behind that simple view, the selection has to remain intelligible in the basket and in the customer account. Custom WooCommerce work on LifeChef sat at these handoffs, where a meal choice becomes an order rather than just a picture in a catalogue.
Checkout and delivery remain part of the product
Payment and delivery were part of the same store environment. A change to ordering behaviour had to fit those existing steps so a customer's choices would remain clear all the way through the purchase.
The work, up close
The present-day plan cards make the customer's first decision visible: which meal programme to explore.
Dish cards bring food photography and nutrition details together while customers browse the menu.
The current site explains how a main and two sides form a meal. It illustrates the kind of choice the ordering system must carry forward.
New functions alongside maintenance
The engagement combined custom modules with ongoing support between 2020 and 2022. That meant working with the store's established ordering paths and keeping its everyday operation in mind as new requirements arrived.
The kitchen is part of the system
The engagement also included a chef-facing application. It is an important distinction from a conventional food catalogue. The product had an operational side as well as the customer’s menu and purchase journey. I keep those two sides in the same case without publishing internal kitchen screens.
A product that kept changing
The design went through more than three revisions. I supported development across those changes rather than describing one frozen version as the whole project. The images include design records and the current public store, with their source context kept clear.
The outcome
Custom WooCommerce module work and ongoing support within the existing store, 2020–2022.
Meal selection, accounts, cart behaviour, payment options and delivery rules.
Details of LifeChef
What did I work on for LifeChef?
I worked on custom WooCommerce modules and support for its existing meal-delivery store between 2020 and 2022. The scope included meal choices, accounts, checkout, payments, delivery rules and a chef-facing application. The design changed more than three times.
Are these images from that delivery?
No. They show LifeChef's public website in 2026 to explain the product context, not the interface from my earlier engagement.
