Skip to content
Software

Te Lisi

Business software for catering orders, calendars, payments and returnable dish tracking.

Mockup Gallery

The phone mockup here shows the responsive web interface. The project also includes a mobile application.

3 Images

Project Overview

Business software for catering orders, calendars, payments and returnable dish tracking.

Orders, dates, payment records and returned dishes belong to the same catering workflow. The application presents those operational tasks together, focusing on the work that continues before and after an event.

Built with Next.js, React Native, React, Expo. The portfolio previews show the project's interface and visual structure.

Case study · Catering operations

Te Lisi: business software for catering operations

A catering application covering orders, calendars, payments and returnable dish tracking, with a web interface and a mobile application.

Development scope
Business application development for the catering workflow, with web and mobile interfaces.
Concrete deliverables
  • Order management and calendar views
  • Payment records and returnable dish tracking
  • Web interface and a separate mobile application
Visible result
Orders, event dates, payment information and dish returns are represented in one catering application. The phone preview shows the responsive web interface.

An order continues after the event

Catering staff need more than an order list. They need the event date, payment information and a record of dishes that must return afterwards. Te Lisi brings orders, calendars, payments and returnable dish tracking into one business application. These connected records give the project its operational focus.

Browser access and a separate mobile application

The project includes a web interface built with Next.js and React and a mobile application using React Native and Expo. When comparing the two delivery options, start with where staff work and which tasks they need to complete away from a desk.

Keep the order understandable at every handoff

An event date, a payment entry and a dish return can concern the same order but be handled by different people. For a new application, name the person responsible at each stage and the information they leave for the next colleague. That is a more useful starting point than commissioning separate screens in isolation.

Review exceptions, not only the ideal order

For your own catering system, walk through an order whose date changes, a payment recorded later and dishes returned in two batches. Identify who updates each record and what the next staff member must see. Agree those review scenarios alongside reports, data migration and any external connections before accepting a development scope.

Discuss a similar project

Describe your workflow and what your business needs to do differently. We can discuss requirements, integrations and the scope of a first release.

Pricing is negotiable for each project. We agree the quote after discussing your requirements and the scope of work.

Te Lisi: business software for catering operations

info@grevision-ks.com
We use these details to respond to your enquiry. Read our privacy notice.

What we agree before work starts

Your proposal sets out the work, responsibilities and commercial terms. Pricing is negotiable for each project.

Read how we work
  • Code and handover

    Define repository access, deliverables, usage rights and third-party licences in the agreement.

  • Data and confidentiality

    Agree access, confidentiality and hosting responsibilities before sharing production information.

  • Milestones and payments

    Set the project scope, review points, acceptance criteria and payment arrangements together.

  • Launch and support

    Agree launch responsibilities, handover and any support period and response expectations.