EN
Demo Early Access

Development log

How we build Storegram

From the first line of code to ordering from the table: what we built, what we optimised and why it matters for your venue.

27 June 2025first day of work
530+changes to the core code
4 languagesEN, LT, LV, RU

October — November 2026

Beyond Telegram

The latest. Storegram stopped asking guests for an app and moved onto big screens.

10 November 2026
Optimisation

A faster storefront, more reliable notifications

The storefront got faster: menu photos load as you scroll, and the server does no unnecessary work on each page. On mobile internet it is especially noticeable.

Order notifications are sent in the background: the guest gets confirmation right away, and if Telegram is slow to respond, the message is sent again.

And the schedule now takes the switch to summer and winter time into account by itself.

Our new team member says hello 🤖

5 November 2026

A storefront for desktop and new themes

On a big screen the menu no longer looks like a stretched phone: three columns, the cart on the right, a cover with opening hours, address and directions to the venue.

And a day earlier, two new themes: “Monochrome” and “Bronze”.

27 October 2026

Order from the table, even without Telegram

A guest scans the QR code on the table and orders, and the kitchen sees the table number right away.

And since 27 October Telegram is no longer required: the menu opens in an ordinary browser, with ordering and payment right there.

The feature stays off until the owner turns it on.

22 October 2026

The cart doesn’t get lost

Closed the app by accident and the cart is empty? Not any more.

The cart lives for three hours after the last change. When the guest comes back, we check that everything is still available and say so honestly if something had to be removed.

11 October 2026

Order for the time you need

The guest chooses when to pick up the order: for lunch, for the evening or for tomorrow.

How many days ahead one can order and how much time the kitchen needs is up to the venue, and free slots are calculated from its working schedule.

The owner turns the feature on.

August — September 2026

First clients

Real venues in Lithuania started using the product. Their daily work showed us what to build next.

29 September 2026

Couriers work in the bot

A courier doesn’t need a separate app.

The order comes straight to their Telegram bot: “Taking it” and “Delivered” buttons, directions in Google Maps or Waze with one tap. The guest can send their location instead of an address.

And if nobody accepts an order for a while, the sound in the panel repeats and the owner gets a reminder.

16 September 2026

Sets, stock, regular guests

September was the busiest month in the project’s history.

Sets: the guest builds a combo from catalogue items.
“Price on request”: a request instead of a purchase, for made-to-order cakes and bouquets.
Stock tracking: two people can’t buy the last portion at once.

And the panel now remembers regular guests: right in the order you can see how many times the person has ordered before and what they usually get.

3 September 2026

Two ketchups instead of one checkbox

Add-ons for dishes: sauces, sizes, “no onion”. Required choices, quantity limits, some can be included in the price: “first two sauces free”. Groups are created once and attached to any product.

And the next day, “lunch of the day”: a product can be given days and hours of sale. Outside its schedule the card stays in the menu, it just can’t be ordered.

24 August 2026
Good to know

A QR code made for print

We optimised the QR code for print: it is now dark on a light background, as the standard intends, and reads reliably in both colour and black-and-white print.

And a tip: there’s no need to print the QR code on a whole A4 sheet. It reads from about ten times its own width, so 6–10 cm is enough for a table sticker or a flyer.

20 August 2026

Delivery, couriers, payment on delivery

Pickup and delivery in one menu. The venue sets the delivery price, and the team got a separate role: courier.

In the same days we added payment on delivery (cash or your own terminal) and a second payment provider, SumUp.

A shop can now work without online payment at all.

April — August 2026

Getting ready for real orders

The team grew and work sped up. Everything a venue can’t do without, day after day.

7 August 2026

Ready-made themes and opening hours

We removed manual colour picking. Instead of a palette there are ready-made themes: a theme always looks neat, and setup takes a minute.

Along the way the storefront learned opening hours: orders are taken according to the venue’s schedule, and when it’s closed the guest sees when they can order.

21 July 2026

Broadcasts and promotions

Your guests stay with you.

You can message subscribers right in Telegram, each in their own language, and attach products on a members-only promotion. The price holds until the date you set and then goes back by itself.

A free channel instead of paid advertising.

15 July 2026

Statuses for the guest, a chart, an order sound

A busy two weeks.

The guest gets a Telegram message at every order status change, in their own language. The panel got a sales chart.

A new order can now be heard: you can set your own sound so the kitchen never mistakes it for anything else.

Plus a guest list and order history for the customer.

4 July 2026

A new panel for the phone

A big rework of the panel.

Venues are run from a phone: between orders, in the kitchen, on the go. So the panel is made for the phone first: big buttons, everything important at hand, nothing extra.

Our new team member doesn’t seem to have slept at all these days 🤖

27 June 2026

QR codes · the project turns one

Exactly a year after the first line of code, the storefront stepped into the real world.

A QR code on a table, package, shop window or door opens the menu straight away, without searching for the bot or extra steps. The code is made in the panel and is ready to print.

23 June 2026

Order statuses

Every order now has a clear path: accepted → cooking → ready → handed over.

The status changes with one tap, and at any moment you can see what is happening in the kitchen.

22 June 2026

The panel in several languages

Not just for the guest, for the team too.

The control panel is now translated as well: each staff member sees it in their own language, even if guests see the menu in another.

29 May 2026

Trying a new design

Trying a new design. In the change history: “Design test commit”, “v2” and “v2” again.

We want the menu to look neat in any venue, even one without its own designer.

We’ll show what came of it very soon.

8 May 2026
Optimisation

The checkout button

The checkout button and a loading indicator: while the order is being sent, the guest sees that things are moving and doesn’t tap a second time.

A small thing that keeps two identical orders from landing in the kitchen.

2 April 2026

The new-order message

We started small: we rewrote the new-order message.

Items, total, how the order is collected — everything the kitchen needs is visible at a glance, with no extra lines.

1 April 2026
The team

A new team member

On 1 April a new member joined the team 🤖

Doesn’t drink coffee, doesn’t go on holiday, doesn’t argue about spaces versus tabs, and reads code faster than we write it.

Who is it? Guess for yourself. Hint: look at how much appeared in Storegram over the following months.

(And no, it wasn’t an April Fools’ joke.)

October 2025 — March 2026

A panel for the venue

A guest could already put an order together. Now someone had to accept it.

15 March 2026

Payments are set up in the panel

The owner can now connect online payment themselves. The payment provider’s keys are entered in the panel settings, without a programmer and without touching code.

The money goes straight to the venue’s account.

22 February 2026
From the change history

Holly saints and Payment seems achieved

February, from the change history.

16 February: “Holly saints it's working!” That is the name, typo of joy included, of the change in which the product window finally worked.

22 February: “Payment half way achieved”, then “Payment seems achieved”, v1, v2, v3 and v3.1.

Payment, it seems, was achieved 🙌

8 February 2026

A storefront in several languages

The storefront started speaking several languages.

In the Baltics a menu in one language loses some of its guests: some read Lithuanian, others Russian, tourists English. The guest picks the language, and dish names and descriptions are shown in it.

In the change history it is the “Big multilinguality commit”, in five versions.

29 January 2026

The venue learns about an order instantly

A new order shouldn’t wait for someone to refresh the page.

Since January the manager and the owner get a Telegram notification the same second, and the order list in the panel updates by itself.

6 December 2025

An order only after payment

A rule we haven’t changed since: an order appears only after the payment has really gone through.

No “I paid but there’s no order” and no “there’s an order but no money”. The kitchen cooks what has already been paid for.

2 November 2025

The menu in the venue’s hands

The menu is now in the venue’s hands. Products and categories are created and edited right in the panel, with filters and search.

And most importantly, the switch. Out of soup: one tap and the dish is off sale. Back in stock: one more tap.

17 October 2025

The first manager panel

A guest could already put an order together. Now someone had to accept it.

In October the first manager panel appeared: a list of orders, status changes and roles in the team. You can see who runs the venue and who is working the shift.

June — September 2025

The beginning

The first line of code, the first screens and the first attempt to connect payments.

23 September 2025
Optimisation

SOME VERY STRANGE FIX

The smallest number on the screen is the item count on the cart badge. It took three changes called “SOME VERY STRANGE FIX” and a fourth one, “Counter fixed”.

Sometimes what looks simplest takes the most patience. But now the number is always honest.

18 August 2025
From the change history

First try to implement payments v4.6

That is exactly what the change history says: “First try to implement payments”. Then v2, v3, v4, v4.1, v4.2… and finally v4.6.

The first attempt to connect payments turned out to have a lot of versions 😅

Online payment is a place where “almost” doesn’t work: the money has to arrive and the order has to appear. So we took our time.

15 July 2025

Catalogue, cart and a guest via Telegram

The first screens you could actually touch.

In early July the catalogue and cart appeared, followed by search, categories and big photos. The menu started to look like a menu.

And on 15 July the cart learned to recognise the customer: Telegram itself tells us who opened the storefront. No sign-ups, passwords or forms. Open it and order.

27 June 2025

The first line of code

This is where it all began. On 27 June 2025 we wrote the first line of Storegram code.

The idea was simple: a venue’s menu right inside the messenger. No aggregator between you and your guest and no commission on every order. The guest opens the menu where they already spend their time, and the order goes straight to the venue.

In this log we tell how Storegram grew: from the first line of code to ordering from the table.