Flow Lab's own demo project. Cedarline Bakehouse is fictional. An order bot like this for your business costs $500. How it was built and what it costs

order bot demo
Telegram bot · takes orders while you sleep

The bakery is closed, but the order is already taken.

A customer opens Telegram at 1:39 a.m., picks a cake, sees the exact price and the earliest available pickup time, and then leaves a phone number. The owner wakes up to a complete order. The demo on this page runs on the same code that connects to Telegram. Press the buttons and see for yourself.

The phone on this page is a Telegram-style window, not Telegram itself: the bot runs right in your browser. To work in Telegram, this code uses the Telegram Bot API.

Place an order

Tap the buttons or type. The bot understands Sep 25, 25.09, tomorrow, and plain numbers. If something isn't possible, it says so right away.

Cedarline Bakehouse
bot · online
The demo runs right in your browser, and nothing you enter is sent anywhere.

What the owner's phone shows

0
Nothing yet. Place an order in the chat, and it appears here instantly.

How orders are saved

OrderItemReady byPickup/DeliveryTotal
No orders yet.

The bot's code for Telegram saves the same record to an order file. Instead of a file, orders can go to the bakery's Google Sheet or CRM; switching only takes a change to one small part of the code.

One night, replayed

Press the button, and the bot will handle the pre-written orders of one fictional September night right here in your browser. Every number below comes from that replay, not typed in by hand.

The replay hasn't run yet.

How it is built

Same code in the demo and in Telegram

The bot moves through the conversation in clear steps: it knows what stage the order is at and, with each new message, picks the next step and reply. In Telegram it receives customer messages; on this page it receives your button clicks. There is no separate version for the demo: an automated check compares the code on this page with the bot's main code and flags any difference. The English and Russian versions run on the same code and differ only in phrases, menu and prices.

Working through the night

If the bot's reply doesn't reach Telegram, Telegram sends the message again, so the bot remembers each message number and handles it only once. If the connection drops or Telegram limits the request rate, the bot retries with growing pauses. Buttons from older messages are recognized and answered politely, and the order in progress stays unchanged. Each order is saved before the customer sees "booked".

No third-party libraries, key kept out of the code

The bot is written in plain Node.js with no third-party libraries, so there is nothing extra to audit or update. Its access key is stored separately from the code and never appears in the logs. Hosting runs on the shop's own account, so the shop keeps control of its data.

What monthly support covers

Menus, prices, and Telegram itself change over time. Monthly support keeps the bot working:

  • Menu, prices, lead times and delivery zones updated whenever the shop changes them.
  • Monitoring: Flow Lab watches the bot's replies and hears about any pause before customers do.
  • Flow Lab updates the bot for Telegram API changes.
  • Small additions based on what customers ask: new items, answers to new questions, new pickup times.
  • Monthly report: how many orders the bot took and how many customers reach each step of the order.
  • Order backups and export to the shop's bookkeeping software.