yeksax
← Back to home

QuickTag

Kitchens and multi-location teams

Know what expires. Act before it does.

QuickTag helps kitchens manage food expiry dates across multiple locations. It calculates dates from product and storage rules, prints traceable labels, and brings production and expiry status into one dashboard. Email and WhatsApp alerts help teams act before food goes to waste.

Stack

language

TypeScript 01 language TypeScript Routines, work orders and labels, typed down to the unit of measure. typescriptlang.org

front-end

Next.js 02 framework Next.js The store app and the routes the printer talks to. nextjs.org React 03 interface React Built for the floor: few taps, big targets. react.dev TanStack Query 04 client cache TanStack Query The production queue, refreshed while the store floor works. tanstack.com Tailwind CSS 05 styling Tailwind CSS The interface, tuned for a shared screen in the aisle. tailwindcss.com shadcn/ui 06 design system shadcn/ui The component base under the CRUD screens. ui.shadcn.com

back-end

Auth.js 07 auth Auth.js Sessions per store group, with roles that define who can print. authjs.dev Zod 08 validation Zod Validates the label layout before it becomes ZPL. zod.dev

data

Drizzle 09 ORM Drizzle Schema and migrations for the multi-tenant model. orm.drizzle.team Neon 10 database Neon Serverless Postgres, since the load is spiky by nature. neon.com

infra

Vercel 11 hosting Vercel Where it runs, close to the stores. vercel.com

integrations

Resend 12 email Resend Invites and operational notices for the store. resend.com
01 routine

Production routine

Each kitchen defines its products, storage conditions, and shelf-life rules. Expiry dates are calculated from production.

  • Routine per store group
  • Items with unit and location
02 run

Work order

Staff select the product and quantity to generate standardized labels with a unique tracking code.

  • The run generates the labels
  • Transfer between stores
03 print in store

Print queue

The layout is rendered to the printer's own language, so nothing depends on a driver behaving.

  • Layout rendered to ZPL
  • Code on every label