Ice cream shop software

A three-flavour tub is a single item

In an ice cream shop the product is not an item: it is a combination. The tub asks for three flavours, the cone for one, the cup for two. That is set up once as a question with its possible answers and how many can be picked, and whoever is serving taps what was asked for instead of writing a note somebody has to interpret later.

Sizes work the same way and each one carries its own price difference, so there is no need to create a separate item for every possible combination. The system will not close an order with more or fewer flavours than that size allows.

The topping adds up and stock drops in the right place

Toppings — sauce, sprinkles, cream, a dipped cone — are ticked and add their amount, or subtract it if the customer takes something out. And every choice touches the recipe: if the flavour chosen is dulce de leche, what comes off stock is dulce de leche, not an average of the tub.

Allergens follow the same rule, and this one is not cosmetic: a flavour with nuts adds the allergen to the order and a gluten-free one stops showing it. At a counter where somebody asks about an allergy with a queue behind them, that difference matters.

The queue keeps moving

An ice cream sale is a counter sale: order, pay, hand over, no table involved. The tab opens and closes on the spot, with whichever payment method you use, and is logged against the shift till. At closing, the total comes out on its own, broken down by payment method.

And the sales reports by hour say when the wave arrives: Saturday at nine at night looks nothing like Tuesday at midday, and the counter roster is built from that rather than from a hunch.