POS operations guide

Ice cream batch stock control with billing software

Ice cream stock is hard because the sale happens as scoops, cups, cones, shakes and toppings, while the purchase often arrives as tubs, litres, packets and cartons. A useful POS setup connects these two worlds without making staff count every gram during rush.

Practical workflow

Where this setup helps

This guide helps ice cream parlours, dessert counters, gelato shops, frozen yoghurt shops and quick-service dessert brands that want better flavour planning and less dead stock.

How the workflow should run

Receive flavour tubs and packing material, mark opening stock, sell structured items with flavour modifiers, record wastage and samples, close the shift, then compare flavour movement with remaining tubs before the next purchase.

What to decide before buying hardware

Decide which stock is worth tracking daily, whether flavours are modifiers or items, how wastage is recorded, who can mark samples, and when a flavour is hidden from kiosk or QR menus.

Reports or checks after rollout

Review flavour movement, top toppings, wastage, samples, packed tub sales, low stock, closing stock variance and sales by time slot.

Ice cream stock flow

The counter should stay fast while the owner still learns which stock actually moves.

Step 1

Receive tubs and packs

Enter tubs, cups, cones, toppings and retail packs as stock items before service.

Step 2

Sell by menu item

Staff bills one scoop, sundae, shake or tub, then selects flavour and add-ons as controlled choices.

Step 3

Record wastage

Melted stock, samples, staff food and damaged cones are recorded with simple reason codes.

Step 4

Close the batch

At day close, staff counts remaining high-cost flavours and toppings.

Step 5

Plan purchase

Owner compares sales, wastage and closing stock before ordering the next batch.

Hardware and software required

Hardware

  • Touch POS or computer at the dessert counter.
  • Receipt printer or token printer.
  • Barcode scanner for retail tubs and packed desserts.
  • Label printer if packed tubs are labelled in-house.
  • Weighing scale only if the business can maintain weight-based stock discipline.

Software and data

  • Item groups for scoops, sundaes, shakes, tubs, toppings and packing.
  • Modifier groups for flavour, cone, cup size and topping.
  • Stock items for tubs, cones, cups, spoons, sauces and high-cost toppings.
  • Wastage, sample and staff-consumption reason codes.
  • Reports for flavour movement and closing variance.

Setup sequence

  1. Start with the top ten flavours and costly toppings before tracking everything.
  2. Keep scoop items simple and use modifiers for flavour names.
  3. Set sold-out controls so staff can hide unavailable flavours from kiosk or QR menus.
  4. Create reason codes for melt, sample, staff food, damage and owner use.
  5. Count opening and closing stock for selected flavours for two weeks.
  6. Use the report to adjust purchase, not just to admire sales.

What each person sees

Cashier

Selects product, flavour and topping without typing long notes.

Prep staff

Sees a clear token or receipt for each dessert.

Owner

Compares flavour sales, wastage and closing stock before purchasing.

Mistakes to avoid

Avoid these during rollout

  • Trying to track every ingredient before staff can maintain the basics.
  • Creating hundreds of scoop and flavour combinations as separate items.
  • Not recording samples and wastage.
  • Leaving sold-out flavours visible on kiosk or QR menus.
  • Ordering based only on memory instead of flavour movement reports.

Questions

Should ice cream stock be tracked by weight?

Only if the counter can maintain that discipline. Many parlours should start with tubs, packs and high-cost toppings.

What is the simplest useful report?

Flavour movement, wastage, packed tub sales and closing variance.

Can kiosk ordering use the same stock?

Yes. The kiosk menu should hide unavailable flavours from the same POS availability rules.

Where Posnic fits

Posnic Community Edition is the free open-source local POS for billing, stock, tax setup and daily operations. Posnic Cloud is only needed when a business wants branch sync, managed backups, remote dashboards or connected ordering workflows.

Download Community Edition/Contact Posnic