This site uses cookies to improve your user experience. If you continue to use our website, you consent to our Cookies Policy

Asset Management Tool for Restaurants

Managing all aspects of the restaurant business in one place

Time: November 2019 - Ongoing

Platform: Web

Industry: Hospitality

Type: Web development

Asset Management Tool for Restaurants [Case study]

About Project

1

The client had:

  • Previous versions of the platform
  • Ideas for new features

We were responsible for:

  • Building a new platform with a new design from scratch
  • Implementing new functionality
Idea

Our client is a US-based company with a huge partnership network for restaurants and industry-related businesses (manufacturers, vendors, suppliers, and more). They came to us with the task of creating a platform that would connect restaurants with all the necessary services and create one solid ecosystem.

Team

  • Project manager
  • Business analyst
  • UX/UI designer
  • DevOps engineer
  • Two frontend engineers
  • Two backend engineers

Technology stack

2

Frontend

React, TypeScript, Apollo GraphQL, React Router, AG Grid

Backend

TypeScript, Node.js, Strapi, MySQL, AWS

User roles in detail

3

The main part of the platform consists of four user roles and one admin role that are interconnected with each other and all the features are divided between them.

Restaurant

The business itself: restaurant, diner, cafe, or any other food provider registered on the platform.

Subroles:

  • Organization admin

  • Asset manager

  • Location manager

  • Project manager

  • Team member

These users can create organization profiles, add locations, set up the necessary equipment, create tickets for equipment malfunction, and create custom reports.

Manufacturer

The organization that produces and sells kitchen equipment.

Subroles:

  • Admin

  • Product manager

  • Program manager

  • Team member

  • Service manager

Manufacturers are responsible for creating a database of conditional models, assets, and builds for their equipment and managing the equipment itself depending on its status.

Supplier

Two types of organizations: a) an equipment spare parts supplier and b) a restaurant food supplier.

Subroles:

  • Admin

  • Pricebook manager

  • Document manager

  • Team member

Spare parts suppliers cover the requests from restaurants and vendors and provide new parts for broken equipment. Restaurant food suppliers can offer their own products to the restaurants or get a ticket about certain types of food a restaurant needs and organize delivery.

Asset Management Tool for Restaurants [Case study]Asset Management Tool for Restaurants [Case study]

Vendor

A service center that is able to maintain and fix the equipment.

Subroles:

  • Admin

  • Service manager

  • Technician

  • Back office admin

A vendor can accept tickets from restaurants and send their specialists to fix the equipment or check its status.

Platform admins

The platform staff responsible for user management.

Subroles:

  • System admin

  • Account manager

  • Help center


The platform staff can manage the user base, help new organizations set up their accounts, and answer other questions from all types of users.

Main challenge

4

Project requirements

Problem: Each user flow is a complex process with a lot of subroles that are interconnected between each other, so identifying the correct set of requirements was difficult.

Solution: A business analyst joined the team and took over the tasks related to requirements and documentation. As a result, the team has got a more accurate vision of what and when to build.

Results

5

The platform is up
and running!

300+ restaurants, manufacturers, vendors, and suppliers are registered.

The user role network works flawlessly.

Invoicing and improved analytics are to come.