EDIT — Fashion E-commerce & Telegram Business OS

A real platform. A transparent launch state.

The HTTPS storefront is live. Verified stock and seller details are still pending, so enquiries remain closed. The trading bot awaits the owner’s credentials. No sales results are claimed.

Customer PWA. Separate staff workspace.

Server-rendered product pages and metadata, responsive AVIF/WebP images, local Ukrainian fonts and a network-first customer journey. The service worker caches only the public shell. Cart, enquiries, sessions, CRM and financial data stay out of the shared offline cache.

Staff roles are enforced by the API. Telegram signatures expire, sessions can be revoked, revisions protect edits and financial entries use a ledger. Public prelaunch pages stay noindex; the store is not presented as already indexed.

The interface in motion

Real browser recordings. Product interactions use labelled test data in an isolated environment; staff screens show a safe demo. No customer data or simulated business results.