SABRAMAN

SABRAMAN DANYA YUDIN КАРТОН SABRAMAN DANYA YUDIN КАРТОН SABRAMAN DANYA YUDIN КАРТОН SABRAMAN DANYA YUDIN КАРТОН SABRAMAN DANYA YUDIN КАРТОН SABRAMAN DANYA YUDIN КАРТОН
Loyalty + POS
Case Study

Smoky Market Loyalty Miniapp

A loyalty platform combining Telegram mini app experiences with web POS operations for staff.

Problem and context

Loyalty actions happened across disconnected channels, making discount handling and transaction traceability inconsistent.

The product had to support seller speed at checkout while preserving admin-level control over discount policy and shifts.

Architecture and implementation

The system split responsibilities between customer-facing Telegram interactions and staff-facing POS workflows with shared transaction state.

Shift lifecycle, customer lookup, and discount validation were modeled as explicit state transitions to reduce ambiguity.

Feature deep dive

Store operators can process QR/manual customer lookup, apply policy-safe discounts, and close shifts with exportable reporting.

Admin views focus on transaction analytics and role governance instead of decorative dashboards.

Outcome and impact

The loyalty process became operationally explicit: staff actions, discount decisions, and shift accountability are recorded in one system.

This reduced ad-hoc handling and improved handoff quality between store staff and management.

Constraints and tradeoffs

Balancing speed for checkout staff with policy enforcement requires careful UX prioritization and strict domain validation.

Monorepo coupling improves consistency but demands discipline in release coordination.

Tooling and integrations

The monorepo setup keeps mini app and POS codebases aligned while sharing domain contracts.

Convex-backed data workflows support real-time operations where stale status can break checkout routines.

FAQ

Is this just a customer mini app?

No. It includes a full web POS layer for sellers and admins.

How are discounts controlled?

Through role-aware validation and explicit policy checks in transaction flow.

What is exported to Telegram?

Operational reports and transaction summaries needed by management workflows.