JS / Jantore Suleimenov

Internal operations automation

A hospitality venue

An internal ordering system for a venue

A staff-facing tool that turns supplier ordering from scattered messages and spreadsheets into one structured, repeatable flow.

Process Automation

staffordersuppliersrecord

Problem

A hospitality venue ran its supplier ordering by hand: requests scattered across chats and spreadsheets, no consistent record of what was ordered from whom, and no structure a new hire could follow. It worked right up until the people who held it in their heads were unavailable.

Build

A staff-facing internal tool that turns ordering into a guided flow: items grouped by supplier, a running order built like a cart, and a checkout step that captures each order as a clean, repeatable record instead of a one-off message. It is built to be run by anyone on shift, not only the person who used to own the process.

How it works

The win is making an informal process legible. Ordering used to live in someone's memory; now it follows a fixed structure that anyone on shift can run, with every order captured the same way each time. The system encodes the workflow itself, so the knowledge no longer walks out the door when a person does.

Outcome

  • /Supplier ordering moved from scattered messages into one structured flow.
  • /Anyone on shift can run the process, not only the person who built it in their head.
  • /Each order is captured as a clean, repeatable record.

At a glance

  • Staff-facing internal ordering tool
  • Items grouped by supplier
  • Cart-style ordering with a structured checkout
  • Built to be run by any team member

Role

Sole builder of the internal ordering tool, end to end.

Stack

  • Next.js
  • TypeScript
  • Tailwind
  • PostgreSQL

Screens

01 / 02

ordering
Internal supplier ordering, grouped by supplier
checkout
Structured order checkout