Blog · For anyone running a route · 3 min read

Could you automate an ice cream van?

An ice cream van's real problem is that demand is invisible until you are already parked. A QR sticker on the side points at a live map and a text list, so parents know you are five minutes out. Same truck, same freezer, customers already waiting.

Clay diorama of a soft-serve machine, a stack of cones, a chest freezer, and a phone propped against the van's window

Published August 29, 2026

I was on a walk this morning and had a weird thought. Could you automate the ice cream van business?

Not the driving, and not the scooping. The part that actually loses money.

Here is the real problem with that business. You pull into a neighbourhood, you play the music, and then you hope somebody heard it. That is the whole model. A guy in a truck betting that the right kid is in the right yard at the right moment with a parent who has cash. Everything else about the business is fine. The product sells itself. The margins on a Rocket Pop are not the issue. The issue is that demand is invisible until you are already parked and it is too late to go somewhere else.

So you fix the invisible part.

Put a big weatherproof QR sticker on the side of the van. It says track my van live and get a text when I'm close. That is it. That is the whole pitch, and it is written on the side of a vehicle that drives past hundreds of houses a day, which means your acquisition channel is already paid for.

The sticker points at a one-page site. You can build that free on Carrd. It needs two things: a live map showing where the van is right now, and a box where a parent puts their phone number and their street. Nothing else. No account, no app to download, no login.

The map updates itself because of Glympse, which shares your phone's location into a page while you drive. You start it when you leave in the morning and you forget about it. The van moves, the dot moves, and any parent who bookmarked the page can see you coming without you doing a thing.

The phone numbers go into an SMS tool, grouped by neighbourhood. That grouping is the part that matters. Before you turn into a specific area you tap one button, and everyone on that list gets a text: the van is entering Oak Bay now, see you in five minutes. Five minutes is enough time to find shoes and get to the curb. You are not hoping anymore. You are announcing.

The other half of this is stock, which is the quiet way a truck business bleeds. You run out of the thing everyone wants and you keep driving around with a freezer full of the thing nobody wants.

Square's free POS app on an iPad, with a cheap Bluetooth reader, handles it. Load your menu in, enter your starting counts at the beginning of the day: 50 Rocket Pops, 40 Drumsticks. Every tap on a sale subtracts one. Square already sends a low stock alert on its own, so you are not building that part. A free Zapier rule catches that alert and turns it into a pre-written order email to your supplier when the Rocket Pops drop under ten. You never place the order. You just approve one that was already written.

There is an AI part too, if you want it. You could vibe code the tracker yourself instead of assembling it from Carrd and Glympse and an SMS tool. The map page, the phone broadcasting its location, the alerts firing at the right street, all of it built rather than bought. Whether that is worth doing depends on how much you like building things, because the off-the-shelf version works either way.

What I keep coming back to is that none of this changes the ice cream. Same truck, same freezer, same product, same route. What changes is that you have customers waiting before you park. The old version of the job is drive and hope. The new version is drive and tell people you are coming.

I have no idea what an ice cream truck actually brings in. That is the number that would decide whether any of this is worth a weekend, and I do not have it.

Want this built into your business?

These posts are the do-it-yourself version. A Discovery Sprint walks your real workflows and ranks what to automate first, by effort and impact.