The problem is the count, not the baking
A small bakery lives on knowing how many. Guess low and you turn people away; guess high and you throw money in the bin at closing. Pre-orders fix that, but only if collecting them is easier than the guessing.
Collecting them in a chat your customers already read is about as easy as it gets. You post the week's bake, they order from the same message.
A menu that changes weekly
You are not building a permanent catalogue. You are publishing this week: six items, maybe eight, with what is different this time. Next week you edit the same list. Categories help once you sell both bread and pastry, and a featured card at the top is for the thing you want to move.
Pickup slots and cut-off times
Bakery orders need a when as much as a what. A bookings block can carry pickup windows so a customer chooses a slot rather than writing to ask. Put the cut-off in the shop description: orders by Thursday for Saturday, and the shop says so before anyone asks.
Allergens and ingredients belong on the product
Every bakery answers ingredient questions, and they are exactly the questions you do not want to answer at six in the morning. The description carries them, and an FAQ block on the shop page takes the rest.
What it costs
The free plan holds up to 10 products and 150 orders a month, which fits a weekly bake for a small bakery. If you outgrow the order count the Starter plan at $19 a month raises it to 1,500, and card payments inside Telegram become available with your own bot.
Several ready-made designs suit food sellers, with the warm palettes and large photography the category needs.