Restaurant management systemLive

Vanilla

A restaurant runs its back office from one system: inventory, shopping lists and vendors, banquet packages and orders, end-of-day sales, assets and breakages, and daily tasks and workflows across departments.

Client
Vanilla, a restaurant
Used by
Managers and staff across every department
Runs on
Web platform and staff mobile app
What we did
Design, build and launch
A Vanilla shopping list waiting for manager approval, with each item’s supplier and cost, using sample data

The challenge

A busy restaurant runs on many small decisions: what to buy, who approved it, what sold today and what needs fixing.

When those decisions live in notebooks and chat messages, it is hard to trace where stock and money went. Vanilla wanted its whole back office in one system, with a phone app so staff could play their part from the floor.

How a request moves through the restaurant

Every request follows the approval steps the restaurant sets for itself.

  1. Set up

    Managers set up departments, staff, roles and permissions.

  2. Design the steps

    They build approval workflows, with the roles and actions for each stage.

  3. Raise a list

    Staff create a department shopping list from the mobile app.

  4. Approve

    The list moves stage by stage through review, and the people at each stage are told straight away.

  5. Close the day

    End-of-day sales and reports are recorded, so managers see how each day went.

What we built

A web system for managers and a mobile app for staff, sharing the same records.

For managers

Run the back office from one system

  1. Departments, employees, roles and permissions
  2. Inventory with reorder levels, expiry dates and bulk upload
  3. Vendors, assets, locations and breakage records
  4. Banquet packages and customer banquet orders
  5. Approval workflows with stages and actions
  6. VAT and service charge settings, and reports

For staff

Get the day’s work done from a phone

  1. Department shopping lists
  2. End-of-day sales and reports
  3. Service requests for repairs
  4. Checklists and tasks with a calendar
  5. Customer banquet orders
  6. Notifications and fingerprint or face sign-in

Decisions that shaped it

  1. Purchases follow approval steps

    Each shopping list moves through review stages, such as the kitchen, managers and accounts, and the right people are told when it reaches them.

  2. The restaurant designs its own workflows

    Stages, roles and actions are set up in the system rather than written into the code, so the process can change without rebuilding the software.

  3. Every day closes with a record

    End-of-day sales and reports are recorded each day, so managers can see how each one went.

The outcome

Vanilla is live. Managers run inventory, purchase approvals, banquet orders and staff records from the web system, and staff raise lists, report the day’s sales and log repairs from their phones.

Tell us what you are planning and how many people will use it.

Start an enquiry