SABRAMAN

SABRAMAN DANYA YUDIN КАРТОН SABRAMAN DANYA YUDIN КАРТОН SABRAMAN DANYA YUDIN КАРТОН SABRAMAN DANYA YUDIN КАРТОН SABRAMAN DANYA YUDIN КАРТОН SABRAMAN DANYA YUDIN КАРТОН
Retail Operations Mini App
Case Study

Flower Mini App

A Telegram Mini App for flower write-off tracking across retail locations, with role-based access, fast daily flows, and built-in reporting.

Problem and context

Flower retail teams needed a lightweight way to record write-offs per location without falling back to chats, spreadsheets, and manual recounting.

The goal was not a demo shell, but an operational product that staff could use daily while owners still had clean reporting visibility.

Architecture and implementation

The app uses server-side Telegram init-data verification in Convex, token-hashed sessions, and explicit role boundaries for owner, admin, and staff users.

Write-off events are stored as append-only records, while daily totals are pre-aggregated to keep owner-level reports fast.

Feature set

The Today screen supports search, one-tap `+1` write-offs, optimistic UI, haptic feedback, and undo for the last action within a 60-second window.

Point invite links, date-based history, day/period reports, and CSV export turn the product into a real operating surface rather than a starter MVP.

Tooling and integrations

Next.js 16, Convex, and Telegram Mini App tooling form the main stack, with shadcn/ui and Tailwind v4 used for the interface layer.

Automated checks cover init-data validation, permissions, invite limits, undo logic, and CSV reporting paths.

Outcome and readiness

The project is still evolving, but it has already crossed the line from scaffold to usable operations product.

Core daily flows, access control, and reporting are already shaped around real point-level usage instead of placeholder functionality.

Constraints and tradeoffs

Telegram-first ergonomics keep the workflow fast on phones, but they also constrain information density and navigation depth.

Auditability and export requirements add data-model discipline, but that tradeoff makes the product safer for day-to-day retail use.

External links

Private / In development

FAQ

What does the app handle today?

Daily flower write-offs, date-based history, point invite access, role-aware permissions, owner reports, and CSV export.

How is access controlled?

Through Telegram-authenticated sessions in Convex plus explicit owner, admin, and staff role boundaries tied to store locations.

Why is this no longer just a scaffold?

Because the app already contains production-shaped daily flows, reporting, exports, invite mechanics, and tested permission logic.