Vision AI · Operations

Why the corner store is the hardest place to get retail AI right

For eighteen years, my father has owned and operated a gas station and convenience store. I have worked in the business for most of that time, and I have spent years talking with other store owners about the same problems. What I know about budgets, vendor pitches, and what actually gets used at the counter comes from being inside those decisions, not from reading reports.

That is why I think the corner store is one of the hardest places to make retail AI work.

For years, retail vision mostly made sense for big brands and big retailers. Field teams took photos, those photos were sent to the cloud, and the results went back to headquarters. In many cases, large CPG brands were the ones paying for that visibility inside big retailers because the sales volume justified it. That was never a good fit for the neighborhood gas station or convenience store.

Most retail still happens in places like this, but the software model was built around very different buyers and very different budgets.

You can already see that shift happening. In July 2025, Trax launched its On-Device IR product. To me, that was a clear sign that even companies built around cloud-based retail vision were moving toward something stores could actually run locally.

The problem is simple: small stores do not have much room in the budget for extra software. The same monthly spend has to cover the POS, payments, cameras, and everything else needed to keep the store running. If your product adds a processing bill every time someone scans a shelf, it is already too expensive for most stores.

That is why running the model on the device matters. It cuts out the extra cost tied to every scan and makes the product cheap enough to fit the reality of the store.

But that still does not make the product work.

Starbucks is a good example. NomadGo’s system ran on the device, and Starbucks still shut it off after using it in stores. Starbucks had every reason to make it work, and it still did not. If a system can break down there, it says something about how hard this problem is in practice, even before you get down to smaller stores with tighter margins and less room for error.

And the problem was not where the model ran. The problem was trust. If workers scan a shelf and the system confuses similar items, misses products, or gives a count they do not believe, they still have to stop and count it again by hand. Once that happens, the software has not removed the work. It has added another step before the real work gets done.

That is the part that matters most to me. In a real store, nobody cares whether the model is running in the cloud or on the device if the answer is wrong. They care whether they can trust the result enough to move on with their day. If they cannot, the product breaks down right there.

That is why I think the hard part is no longer just the model. It is the product data behind it.

A general retail model is becoming easier to get. What you cannot just buy is a product gallery that can reliably tell Marlboro Red apart from Marlboro Red 100s under fluorescent lighting, from the angle a convenience-store shelf is actually seen, and still hold up when the packaging changes a few months later.

Anyone who has worked in one of these stores knows how small those differences can be. That kind of product data gets better slowly and store by store. Every shelf image helps. That is the part that is hard to shortcut.

I also think a lot of people are looking at the wrong problem. In convenience stores, the labor is already there. Cashiers and stockers already restock shelves, count product, and keep the place moving. The real problem is that they are doing it without good information, and getting that information usually takes too much manual work.

That is the gap we care about.

I started Trasio in October 2025 because we kept coming back to the same conclusion from inside the store: the software in small stores is not bad. The problem is that most of it runs separately unless the operator does the work to tie it together. Lottery inventory, invoices, bills of lading, and payment records all end up being checked and rechecked by hand.

The first thing we are building is the part of the day that has cost my father the most: shift change. Every time one cashier hands the register to the next, both of them can spend half an hour counting cigarettes and lottery. If something is off later, no one knows which shift it happened on. A tablet pointed at the shelf can do that count in a few minutes, both cashiers can sign off, and accountability stops being a guess.

So far we have labeled 5,500+ shelf images across nine locations, covering 112 SKUs in two categories.

That is where we started. Over time, the same system can cover more of how a small store actually runs.

If you run or manage stores like this, or you are building in this space, I would like to hear from you — trasio.app.

Close shifts in 5 minutes. Verified. Documented. Done.

Join Founding Stores