PASTRY
STUDIO
B2B portal / Food production
Tech stack
- React / Next.jsApp Router, SSR and API routes for server logic.
- SupabasePostgreSQL + Auth + Row Level Security for a multi-tenant architecture.
- Tailwind CSSUtility-first, mobile-first styling.
- 1C IntegrationREST API for sending orders to 1C and receiving statuses back.
- Telegram Bot APIAutomated notifications about order statuses (sent to 1C, errors).
- VercelHosting with Edge Functions and auto-deploys from GitHub.



The challenge
Partner coffee shops sent their orders over WhatsApp, and collecting them from chats was a mess. Everything after that was manual: orders were re-entered into 1C, and a staff member put together the summary for the kitchen. The goal was a portal where outlets place orders themselves before the cut-off, orders go straight into 1C, and the kitchen summary is generated automatically.
Result
Outlets place orders from their phones before 21:00, every order goes straight into 1C, the accounting system, and the kitchen’s consolidated sheet builds itself. 70+ outlets order through the portal every day, and nobody re-types orders by hand anymore.
What I built
- Mobile ordering PWA: order intake closes at 21:00, after that the system won’t accept an order.
- Two-way integration with 1C accounting: orders flow into the database automatically and statuses flow back to the portal.
- Roles and access: a barista sees their own coffee shop, a manager sees their chain of outlets, the office and admins have separate accounts.
- Order adjustments: an admin can change an order only by giving a reason, which is stored in the history, so the client sees what changed and why.
- Telegram notifications: managers learn about new orders and important changes instantly.
- Analytics: sales filtered by period and outlet, CSV exports for accounting.
- Demo mode: a separate environment for showing the portal to clients without touching the production database.


