Guides
Ice cream shop software: nine named systems and twelve tests to score them
Named nine ice cream shop software systems and twelve requirements with a demo test for each, plus a pass/fail scoring method and buying advice for seasonal shops.
What to take away
- Nine named systems cover most scoop shopsSquare, Clover, Toast, Shopify POS, Lightspeed, SpotOn, TouchBistro, Revel and Delaget.
- Judge every one on four testsoffline trading, a timed two-scoop sale, flavor-level reporting, and the total cost in your quietest month.
- Square and Clover suit a single counter. Toast, TouchBistro and Revel earn their cost in a shop with a kitchen and a queue.
- Nothing here replaces your accountant, your attorney or your local health department.
The shortlist, by name
Square runs on its own reader and an iPad. It suits a single counter with no kitchen. Pricing is a card rate plus a monthly plan, published on its site.
Clover sells through bank resellers, so hardware and support terms vary by who sells it to you. Good fit if your bank already bundles it.
Toast is built for food service: coursing, kitchen tickets, and reporting by menu item. It suits shops with a full production kitchen. Hardware is proprietary.
Shopify POS links the counter to an online store, which matters if you ship pints. Weakest of the nine on offline trading.
Lightspeed handles inventory and purchasing well. Suits a multi-location operator tracking stock across sites.
SpotOn competes on support and card rates. Suits owners who want a person on the phone on a Saturday.
TouchBistro is iPad-based and strong on table and queue service. Suits a shop with seating.
Revel is the heaviest of the nine and the most configurable. Suits a high-volume shop with staff who will learn it.
Delaget is reporting and loss-prevention software that sits on top of another point of sale. Suits an owner with more than one store.
The wider question of which jobs you are buying software for is set out in the four systems a shop actually needs. Settle that before you demo anything.
The twelve requirements, with a test for each
| # | Requirement | The test to run in the demo |
|---|---|---|
| 1 | Sales recorded by product line and flavor | Ring a cone, a cup, a pint and a cake, then split them in one report |
| 2 | Time-stamped sales by hour | Ask for yesterday by hour and by day of week, on screen |
| 3 | Works offline and reconciles later | Disconnect the network mid-transaction and keep trading |
| 4 | Survives the counter | Ask what the hardware is rated for and who replaces it |
| 5 | Fast enough for a queue | Time a two-scoop sale, cash and card, tap to receipt |
| 6 | Voids and refunds with a reason and an audit trail | Void a sale as a junior and see what is recorded |
| 7 | Staff accounts, individually | Create three logins with different permissions live |
| 8 | Exports your own data in an open format | Ask for last month's full export and read the file |
| 9 | Off-counter sales tagged separately | Record a wholesale delivery and an event, report them apart |
| 10 | Off-season cost is bearable | Ask the total in your quietest month, minimums included |
| 11 | Support answers on a Saturday in summer | Call the support line on a weekend during the demo |
| 12 | You can leave | Ask what happens to your data if you stop paying |
Requirements three, five, ten and eleven are the trade-specific ones. The rest apply to any small retailer.
Twelve requirements and demo tests
- Sales by product line and flavor
- Time-stamped sales by hour
- Works offline and reconciles later
- Survives the counter
- Fast enough for a queue
- Voids and refunds with audit trail
- Staff accounts, individually
- Exports your own data in open format
How to score them
- Score each requirement pass or fail, not out of ten. Half-marks let a salesperson talk you past a gap.
- Run the tests yourself. A vendor's demo on their data proves nothing about your counter.
- Do it with whoever works the Saturday shift, not only with you.
- Any failure on three, five, ten or twelve ends the conversation.
- Keep the scorecards. In two years you will want to know why you chose this.
What the system has to produce
Whatever you buy, it has to produce the records a small business is expected to keep. The Internal Revenue Service: What kind of records should I keep? page lists the sales and purchase records in question. Hand it to a vendor as a specification: show me how your system produces these.
Food safety records are separate and belong to your regulator. If you want temperature or cleaning logs in an app rather than on paper, ask the agency that issued your permit whether that form is acceptable. That sits with the licensing questions this trade raises.
The part nobody demonstrates
The system will hold card transactions, staff records and your bank connection, and nobody on your payroll is watching that. Ask the vendor how accounts are protected, whether multi-factor authentication exists, where data is held, and what happens in a breach.
The National Institute of Standards and Technology: NIST Small Business Quick-Start Guides are written for businesses this size. The Cybersecurity and Infrastructure Security Agency: Cyber Guidance for Small Businesses pages cover the practical controls. Neither endorses a product, which is the point.
Buying for the shop you have
A shop that dips bought tubs needs Square or Clover and bookkeeping, little else. A shop that makes its own product also wants batch and stock records, which pushes toward Toast or Lightspeed.
Which shop are you buying for?
Do you make your own product?
Toast or Lightspeed
Square or Clover
A shop doing events and wholesale needs requirement nine badly. Otherwise the winter line vanishes into counter numbers, and nobody can tell whether trading beyond the counter works.
Whoever runs a shift has to use it under pressure without you. That is a training question as much as a purchase, and it belongs in what the crew is taught before the season starts.
Skip marketing automation and customer-insight add-ons for now. In a shop whose customers arrive because it is warm outside, those tools solve a problem you do not have. The honest levers are in the marketing arc for a seasonal shop.
Common questions
Why these nine and not a longer list?
These nine cover the range from a single iPad counter to a multi-store operation, and all nine publish pricing or quote it on request. A longer list would repeat the same three or four feature sets under different logos.
Should I take the system my card processor offers?
Score it against the twelve like anything else. Bundled convenience is real, and so is the difficulty of leaving when the till and the payments sit in one contract.
Is free software good enough?
Sometimes, for a single counter. Test requirements three, eight and twelve hardest, because free tiers are where offline mode, exports and exit terms are thinnest.
How long should this take?
An afternoon of demos and a week of thinking. Longer and you are avoiding a decision; shorter and you have not run the tests.
