Bakery and pastry shop software in Algeria (2027): the day's production, unsold goods, shortages and cakes to order, for when you throw away in the evening what was missing at four o'clock

“I run a bakery and pastry shop with a kitchen and two shops. Every evening we throw away or give away pastries, and on the same day we turned customers away at four o'clock because there were no millefeuilles left. Cake orders are in a notebook: last week we forgot an engagement cake. Butter has gone up and I do not know what a croissant costs me. Which software do I need?” A till records what was sold. Here you also have to note what was not sold and what ran out, keep orders with their deposit and their date, and know what each recipe costs.

Symloop13 min read
Bakery and pastry shop software neither too much nor too littleThe day’s production, unsold goods and shortages, cakes to order with a deposit, cost per recipeBAKERY AND PASTRY · ALGERIA · 2027Bakery and pastry shop softwareneither too much nor too littleThe day’s production, unsold goods and shortages, cakes toorder with a deposit, cost per recipeBY GUESSWORKtoo much here, not enough thereBY THE FIGURESunsold and shortages noted every eveningsymloop.com

Short answer. Bakery and pastry software is judged on four things a till does not do. Two figures per product, every evening: the unsold and the time it ran out; the next day's quantity comes from them. Orders: date, time, portions, flavour, inscription, model, deposit and balance due, filed in the kitchen's schedule. The recipe sheet for each recipe, which gives the cost per piece and recalculates it when an ingredient changes price. Dispatch between the kitchen and the shops, with returns. Around these: a fast counter sale, by the piece, by weight and by the tray.

This guide is for the manager of a bakery and pastry shop, a made-to-order pastry shop or a kitchen that supplies several shops, and for the founder based in France who follows the family business. The notions quoted come from public sources: the stockout, the bill of materials, and the so-called newsvendor model, which deals precisely with a perishable product with uncertain demand. The quantities, batches and prices in the figures are a constructed example, not market prices. This guide covers neither regulated prices nor hygiene and labelling rules: those are matters for the relevant authorities.

One day, two products: too much of one, not enough of the other

The figure follows the stock of two products, from opening to closing.

Figure 1 · The stock of two products, from opening to closing. Croissants, made in three batches, end the day with twenty-four unsold, one in five. Millefeuilles, made in one go, run out before 5 p.m., and twelve requests are refused. The shop makes both mistakes on the same day, and neither is written down anywhere. Quantities, batches and requests are a constructed example.

The croissants. Sixty at opening, forty at 9 a.m., twenty at 2 p.m.: 120 made. Ninety-six sell; twenty-four remain, one in five, and it is about the same every evening. The third batch was one too many, but nobody knows, because the unsold goods are written down nowhere. The millefeuilles. Forty made in the morning, all sold, and none left before 5 p.m. A stockout is the event that exhausts the stock; it causes lost sales and dissatisfies customers, and it leaves no trace: for three hours, twelve people asked for a millefeuille.

The evening record. At closing, for each product, two entries: what is left, and the time at which there was none. One minute. After a week, the software knows that on Tuesday you need a hundred croissants and not a hundred and twenty, and fifty-five millefeuilles on Saturday. The batch plan. It starts from the sales of the same weekday, corrects with the unsold and the shortages, adds the orders, and takes last year's feast days into account. The chef reads it in the morning; they remain free to change it, and the software notes what they changed. For ingredients, flour, butter, eggs, the logic is that of the guide to replenishment.

«The unsold shows in the bin; the shortage shows nowhere.»
01

Bakery and pastry software, in five layers

The accented layer is the day's production: it is the one no till does.

Figure 2 · The accented layer is the day’s production: it is the one no till does. It feeds on counter sales, above, and on orders, below; recipes say what it costs, and shops say what becomes of it.

Counter sales. There is no barcode on a croissant: buttons with the photo of the product, sale by the piece, by weight for dry cakes, by the tray for assortments, and a till that carries on when the internet drops, as in the guide for the mini-market. The till is closed every evening following the guide to till sessions. The day's production, then orders.

Recipes and ingredients. The recipe sheet says what a batch needs; multiplied by production, it says what should have been used, to be compared with what was. Shops and steering. The kitchen dispatches; each shop sells, returns its unsold goods and reports its shortages. The schedule of the kitchen teams, who start before dawn, is kept as in the guide to team scheduling. A loyalty card, the tenth coffee free, reuses the guide to loyalty programmes.

02

A cake to order, in six steps

The first step is accented: what is written down when the order is taken will not be asked again.

Figure 3 · The accented step is the first: date, time, portions, flavour, inscription and model are written down once, completely. An order only enters the kitchen’s schedule with its deposit; it only closes at collection, when the balance is paid.

Write it down. The date and time of collection, the number of portions, the flavour, the inscription letter by letter, the photo of the chosen model, the customer's name and phone number. In a notebook, this information fits on one scribbled line; in the software, none of it can be missing. Take the deposit. The receipt is handed over, the balance due is shown, and the order only enters the schedule once the deposit is received.

Schedule and make. The kitchen sees, for each day, the orders to turn out, with the photo and the inscription; a feast week can be read three weeks ahead. Hand over and settle. The customer is told the day before; at collection, the balance is paid and the order closed. Keep. Next year, on the same date, the software knows that this customer ordered a cake for twenty people.

03

A recipe sheet: what a croissant costs

The figure adds up the ingredients of a batch of sixty croissants, then splits the selling price.

Figure 4 · The recipe sheet for a batch of sixty croissants: 2,400 DZD of ingredients, that is 40 DZD a piece. Sold at 65 DZD, the croissant leaves 25 DZD before labour and overheads. If butter goes up by a quarter, the margin falls to 17.50 DZD, 30 % less. The quantity marker, 38 %, comes from the so-called newsvendor model. Quantities and prices are a constructed example, not market prices.

The recipe sheet. A bill of materials is the list of raw materials and of the quantities needed to make a product; in pastry, it is the recipe, with its yield. In the example, the batch of sixty croissants uses 2,400 DZD of ingredients, that is 40 DZD a piece; sold at 65 DZD, the croissant leaves 25 DZD before labour and overheads. When butter goes up. It weighs 1,800 DZD out of 2,400. If it rises by a quarter, the cost becomes 47.50 DZD and the margin 17.50 DZD: 30 % less, with nothing changing in the shop. The sheet says so on the day of purchase.

How many to make. The so-called newsvendor model deals with a perishable product, with a fixed price and uncertain demand. Its solution comes down to one ratio: the price minus the cost, divided by the price. For the croissant, 25 ÷ 65, that is 38 %: you aim for the quantity that demand exceeds only 38 days in 100. In other words, when the unsold costs a lot relative to the margin, running out on some evenings is the right setting, and never running out means too much is thrown away. For a millefeuille with 60 DZD of ingredients sold at 150 DZD, the ratio rises to 60 %: you accept fewer shortages. It is a marker, which counts neither the disappointed customer nor the unsold goods sold the next day; the evening record does the rest.

«If a product never runs out, some of it is being thrown away.»
04

Six bakery and pastry situations

The figure compares, for six situations of the week, what happens today and what the software does.

Figure 5 · Six situations of the week. In the left column nothing is done badly: only two figures are missing, the unsold and the shortages, and a place where orders cannot get lost. The right column asks no more work at the counter, except one minute at closing.

Feast days. Eid, the Mawlid, the start of the school year, summer weddings: demand doubles or triples, and preparation is done from memory. The software keeps the sales of the same feast last year, product by product, and the orders already taken: the week is prepared with figures. The shops. The kitchen sends; the shop receives, sells, returns. A dispatch slip and a return counted per shop are enough to know where a product sells and where it piles up.

What the software does not do. It replaces neither the chef nor their eye on the dough; it gives them the two figures they never had, the unsold and the shortages, and the cost of what they make. If you also serve at tables, taking orders in the dining room belongs to the guide to restaurant software.

05

A bakery and pastry shop equipped in 2027, in weeks

Five weeks in the example; the second is the one that changes decisions.

  • What the manager sees: per product, the quantities made, sold, unsold and the time it ran out; the orders for the coming days; the cost and margin per piece; sales per shop.
  • What the shop no longer does: produce by guesswork, throw away without counting, say “there is none left” without noting it, forget an order, discover an ingredient increase at the end of the month.
  • What is measured: unsold as a percentage of production, times of shortage, orders handed over on time, difference between ingredients used and ingredients planned.
  • What Symloop does: the counter till, the evening record and the batch plan, orders with a deposit, recipe sheets with your chef, dispatch between shops, then upkeep.
Figure 6 · Five weeks in the example. The accented week is the second: seven evenings of records are enough to produce the first batch plan, and that is when the quantities start to change.

Week 1, products and counter. Week 2, unsold and shortages: the closing record every evening; after seven days, the first batch plan. Week 3, orders: the notebook is taken over, deposits and the kitchen schedule follow.

Week 4, recipes and ingredients: the sheets for the twenty best-selling products. Week 5, shops and steering: dispatch, returns, margin per product, and the board the manager reads on their phone, including from France, as in the guide to running your shop remotely.

Which software for a bakery and pastry shop in Algeria?
Software that adds to the till the record of unsold goods and shortages, the day's production plan, orders with a deposit and recipe sheets. A till alone says what was sold; it says neither what was thrown away nor what ran out.
How do you know how much to produce each day?
By starting from the sales of the same weekday, corrected by the unsold and the shortage times of the previous weeks, plus the orders. The software proposes; the chef decides. One week of records is enough to correct the biggest gaps.
How do you reduce unsold goods?
First by counting them, product by product, every evening. They often concentrate on a few products and on the last batch; you reduce or drop it, and see whether a shortage appears. What is left can be transformed or sold differently the next day, but that is decided product by product.
Is it normal to run out?
On a same-day product, yes, on some evenings. If a product never runs out, some of it is being thrown away; if it runs out every day at four o'clock, too little is being made. The marker is the ratio between the margin and the price: the more the unsold costs relative to the margin, the more acceptable a shortage is.
How do you manage cake orders?
Each order carries the date and time of collection, the portions, the flavour, the inscription, the photo of the model, the deposit and the balance due. It appears in the kitchen's schedule on the right day, and the customer is told the day before. The notebook is only a fallback.
How do you calculate the cost of a cake?
From its recipe sheet: the list of ingredients and their quantities for a batch, multiplied by the last purchase price, divided by the number of pieces. That gives the ingredient cost; labour and overheads are added afterwards. The sheet is recalculated at every purchase.
How do you manage several shops with one kitchen?
With dispatch slips from the kitchen to each shop, and a return of unsold goods counted per shop. You then see where each product sells, and the next day's dispatch is adjusted shop by shop.
Does the software work without barcodes?
Yes: sales go through buttons with the photo of the product, by the piece, by weight or by the tray. Packaged products can carry a label printed on site.
How long does it take to set up the software?
Five weeks in our example: the till in the first week, the record of unsold goods and shortages in the second, orders in the third, recipe sheets in the fourth, shops in the fifth. Decisions change from the second week.
How much does bakery and pastry software cost?
It depends on the number of tills and shops, the volume of orders, and the number of recipes to put on sheets. The most useful work is not the till screen, it is the evening record and the recipe sheets, done with your chef. We quote after a day spent in your kitchen and at your counter.
For one week, note for your five main products what is left in the evening and the time there is none left: we show you the batch plan that comes out of it

A bakery and pastry shop, a made-to-order pastry shop, a kitchen supplying several shops, or a founder in France following the family business: we build the till, the evening record, orders with a deposit and the recipe sheets

Two figures per product every evening, a batch plan in the morning, orders that are no longer forgotten, a cost per recipe. We work from Algiers and Sétif, in French, Arabic and English.