A POS workflow for a man’oushe bakery in Lebanon

Give your regular products clear names: zaatar, cheese and whichever combinations you actually serve. Keep separate products when that makes preparation and pricing easier to understand. Use choices and paid extras for details that belong to an existing item.

Do not make every variation a free-text note. If extra cheese has a set charge, give it a clear price so the counter does not need to remember it. Keep preparation requests separate from price-changing choices.

Ask the person at the oven to read the menu with you. Two labels that sound similar at the counter can mean very different work in preparation. The menu choices guide shows how to test required options and extras.

Rehearse an order for four pieces: two zaatar, one cheese and one cheese with an extra. The plain cheese and the cheese with the extra should be distinguishable; a vague note saying “one extra” beside a quantity of two invites a question.

Read the order back before saving it. Confirm quantities, paid additions and whether it is takeaway or another service type you support. Check the final amount using the prices on your menu.

If someone orders for colleagues, keep their whole order together while preserving the differences between pieces. A clear order is more useful than a short one that requires the baker to remember a conversation. This exercise also reveals menu choices that take too long to find.

Decide how the oven hears about a new order: a shared screen, a printed document or a spoken handoff backed by a written record. Choose the method you can use consistently during your busiest period.

Use an order number or another identifier your team can repeat without confusion. If you print, check that the quantities and choices are readable and that the ticket reaches the person preparing the food. The receipt-printing checklist covers testing the actual setup.

Agree how changes are handled after preparation starts. A second ticket should not silently create a second batch. The counter must tell the baker what changed and check whether it is still possible.

Choose one place for finished orders and one person to confirm what leaves the counter. Match the order identifier to the bag, check the piece count and confirm payment using your normal process.

For the four-piece example, count four before handing over, then check the special piece is in the right bag. An order being ready does not automatically mean it has been collected or paid. Keep those steps distinct in your team’s routine.

For phone or message orders, decide who enters the details and confirms acceptance. If you use an online menu, test a real order from another phone and confirm who notices it. Only offer pickup timing that your oven and current queue can support.

Before opening, check toppings, drinks and packaging against what is actually available. Nominate one person to update sold-out items or options and confirm the change on the ordering screen.

Treat availability as an operational decision. A menu item being visible does not prove you have enough cheese or dough for the next rush. Likewise, a recipe cost does not by itself tell the counter how many pieces are left to sell.

If only one topping runs out, check what happens to every product that uses it. Avoid marking the whole menu unavailable when a narrower change would be clearer. Restore items only when the baker confirms they can be prepared again.

Prepare your counter device while online and practise your usual orders without internet. Include the actual sizes and extras you depend on, rather than testing only a plain item. Check what remains available on your setup.

Simplrr can save supported counter orders on the device and send them when the connection returns. Separate screens and incoming online orders need a connection, so keep an agreed oven handoff for outages. Do not clear the browser while orders are waiting to send.

The offline checklist provides the full test. This rehearsal is about keeping the bakery’s own service clear, rather than assuming every connected tool continues working.

What sold? What was left? Which orders needed clarification? Record those answers after a busy morning, along with any topping shortages or collection mix-ups. Use them to adjust tomorrow’s preparation and menu labels.

Keep recipe costing as a separate exercise. On Simplrr plans with inventory, recipes and shared preparations can help organise ingredient costs. Physical counts, real portions and waste records still matter; do not assume each extra automatically deducts the right ingredient quantity.

Our bakery recipe costing example explains the maths. For your counter, try the demo with the four-piece order, then explore Simplrr for bakeries.

UNESCO’s description of al-man’ouché provides cultural background. The counter routine here is a practical example for your team to test.