ice cream, cup, whipped cream, wafer, sweet-shop, whipped cream, whipped cream, whipped cream, whipped cream, whipped cream, wafer, wafer, wafer. Ice cream shop software: the records to keep
Photo by katerinavulcova on Pixabay

Guides

Ice cream shop software: the records to keep

A practical guide to ice cream shop software: the four jobs a shop must cover, the records to keep, and what to verify before choosing a system.

What to take away

  • Buy ice cream shop software for jobs, not for features. A scoop shop has four: take money and record what was sold, track stock and waste, schedule and pay people, and keep the books. Everything else is optional.
  • The value is in the records, not the dashboards. A till that records sales by line and by hour turns every later argument about the menu into arithmetic.
  • Measure against the same month last year, never against last month. In a seasonal trade a fall from August to September is weather, not performance.
  • These systems hold card data, supplier logins and staff records. Treat that as part of the buying decision rather than as something to think about later.

The four jobs

Take money and record the sale. The till is the most important system in the shop because it is the only one that captures what actually happened. Set it up by product line from day one, because retrofitting the categories later loses the season you most wanted to understand. Counter systems sold to food service include Square, Toast, Clover, Lightspeed and Shopify POS. Do not assume a system records sales at the level you need: verify that its configured reports capture each field below and can export it.

Fix the four jobs in order

  1. 1. Take money and record the sale
  2. 2. Track stock and waste
  3. 3. Schedule and pay
  4. 4. Keep the books

Track stock and waste. Deliveries in, counts, and what was discarded from the case at close. This can be paper for a small shop and often should be, as long as somebody totals it weekly.

Schedule and pay. Rosters against the hourly curve, hours worked, and payroll. Payroll for a shop this size almost always runs through a payroll service such as ADP, Gusto or QuickBooks Payroll rather than inside the till itself. In a business with a seasonal crew and a lot of young workers, accurate hours records matter more than the convenience of the tool.

Keep the books. Purchases, sales, payroll and the bank, reconciled monthly in bookkeeping software such as QuickBooks or Xero, or in a spreadsheet your bookkeeper keeps. This is where the annual picture comes from.

A single system that does all four badly is worse than four simple ones that each do their job. The order to fix them in is the order above, because everything downstream is built from what the till recorded.

What the till must capture

FieldWhy it matters in this tradeWhat goes wrong without it
Product line, not just totalMenu decisions are made per lineYou know sales rose and not which line did it
Flavor, where practicalWaste and popularity are per flavorThe case plan stays a guess forever
Time of saleThe hourly curve drives staffingSchedules are built on the clock instead of the trade
Vessel typeCup, cone and pint have different costsVessel costs get averaged and disappear
Voids and refunds, with a reasonSmall leaks are visible only hereDiscrepancies get called shrinkage and ignored
Off-counter sales, taggedEvents and wholesale behave differentlyThe winter line looks like noise in the counter numbers

None of that requires an expensive system. It requires deciding the categories before the first week and then not changing them mid-season.

What the till must capture

  • Product line, not just total
  • Flavor, where practical
  • Time of sale
  • Vessel type
  • Voids and refunds, with a reason
  • Off-counter sales, tagged

The measurements worth keeping

The short list: sales by product line, sales by hour of the day, waste weight by flavor, stock counts, hours worked against the roster, and the purchase, sales and payroll records behind the books. Each one answers a decision: what to cut from the menu, who to roster on a Saturday, how big a batch to churn, what a portion should cost.

These are also the fields and totals to demand from any system you look at. Whatever the software will not produce, you keep by hand, and you decide that before you pay for it rather than after.

Measurements worth keeping

  • Sales per trading day, warm vs cool
  • Sales by line
  • Average sale
  • Waste weight by flavor
  • Labor hours against sales
  • Take-home and order counts in cold months

The rule that makes them meaningful is comparison to the same period a year earlier. Month-on-month comparison in a seasonal business produces nonsense in both directions: a triumphant June and a catastrophic October that both mean nothing.

The second rule is that a measurement nobody acts on should be deleted. A number produced monthly and never used is a small tax on attention.

Waste weight is the one people skip and it is the most informative thing the shop produces, because it is a direct message from the case about the menu, the batch sizes and the hold times.

Records the authorities expect

Two sets of records exist whether or not you have software.

The tax and business set is described in the Internal Revenue Service: What kind of records should I keep? page: purchases, sales, payroll and the documents behind them. Read it once as a specification for what any system you buy has to be able to produce.

Your regulator owns the food safety set: temperature logs, cleaning records, supplier documentation, and whatever your state requires of a retail food business. In California those requirements are the California Retail Food Code, checked by your county environmental health department at inspection. Whether you may keep the logs digitally, and in what form, rests with that state agency.

The U.S. Food and Drug Administration: State Retail and Food Service Codes and Regulations directory names it for your state. Ask before you replace a paper log with an app. Settle it alongside the other licensing questions this trade raises.

Security, because these systems hold real things

A small shop's systems hold card transactions, supplier accounts, staff personal data and your bank access. That is a genuine target and the shop has no technical staff.

The National Institute of Standards and Technology: NIST Small Business Quick-Start Guides are written for businesses of exactly this size and cover the basics in plain language. For the practical checklist side, the Cybersecurity and Infrastructure Security Agency: Cyber Guidance for Small Businesses materials cover the same ground from the defender's point of view.

Three habits do most of the work.

First, separate accounts for each person with no shared password. Second, multi-factor authentication on anything touching money. Third, know where your data lives so you can get it back when a supplier or tablet disappears.

Buying, and what to leave alone

  1. Write down the four jobs and which one you are solving. If you cannot name the job, you are shopping rather than buying.
  2. Ask whether the till hardware survives the environmentwet hands, cold, a counter that is hosed down.
  3. Ask what happens when the internet drops on a Saturday. A till that cannot take a payment offline is a business risk in this trade.
  4. Ask how you export your own data, in what formata CSV or spreadsheet file you can open yourself, or an API if you have someone to work with it — and what happens on the day you leave.
  5. Ask what it costs in the off-season, and get the monthly minimum in writing. Monthly minimums that were nothing in July are the whole bill in February.
  6. Start with the smallest thing that captures the fields above, and add later.

Leave alone, for now: customer relationship systems, loyalty platforms that need someone to run them, forecasting tools that need more history than you have, and anything sold on the promise of insight rather than record keeping.

Six questions before buying

  • Which of the four jobs are you solving?
  • Does the till hardware survive wet, cold, hosed counters?
  • What happens when the internet drops on a Saturday?
  • How do you export your own data, and what on leaving?
  • What does it cost in the off-season?
  • Start with the smallest thing that captures the fields

What the numbers connect to

Measurement is only worth the effort if it changes a decision. The hourly curve changes the roster, where the labor half of a trading day is settled.

Sales by line and waste by flavor change the menu and pricing ladder, which a price has to clear across the year is built from. Off-counter sales show whether the wider growth argument works.

Card and internet reliability are building properties. They belong in the survey of the premises you are taking on, not in a later software decision.

The format of the business decides how much of this you need. A dipping counter needs far less than a lab making its own mix. That is another consequence of the shape of business you chose.

Living with it

Set a monthly hour to look at the numbers, on the same day each month, and write one sentence about what changed and one about what you will do. That single habit is worth more than any tool on the market, and it is the thing owners abandon first when the season starts.

Keep the categories stable across years. Every renaming of a product line is a year of comparison thrown away.

Common questions

Do I need a point of sale system at all?

You need a record of what was sold, by line and by hour. A modest till that does that beats an expensive one that does not, and it is the fields rather than the brand that matter.

Can I run stock on paper?

Yes, for a single shop, provided someone totals it weekly and the waste weights are written down. Paper that is read beats software that is not.

How many measurements should I track?

Six or so, kept for years. A long list is abandoned in July and never restarted.

What is the first thing to fix if everything is a mess?

The till categories. Everything else can be reconstructed later; the sales record cannot.

More in Guides

Latest from Value Desk