From a QR scan to a store visit: designing a better mall journey

A mall visit isn't a sale

A mall brings people in, but each tenant still has to get someone through its own door. The visitor is often just browsing. The mall wants them to stay longer. The store wants people who might actually buy, not another impression on a dashboard. Those goals overlap, but they aren't the same.

A recent conversation about camera-native augmented reality made that gap clearer for us. The product was described as already running in casinos in Las Vegas and Canada, with other kinds of venues being explored. The technology interested us less than the question behind it: how could a venue tie a playful guest experience to something it can measure in money?

From scan to store to payment

Imagine walking into a mall and scanning a QR code. A short game sends you toward a participating store. You walk there, complete a small task, pay with the QR payment app you already use, and get a reward.

Every step does a job. The scan gets you started, and the game gives you a reason to walk somewhere. The visit helps the tenant. The payment shows whether anyone actually bought anything, which is the number the tenant cares about, and the reward is something the visitor keeps. Mall, tenant and visitor all get something out of the same journey, so it isn't just another marketing stunt.

The point isn't AR. It's linking discovery to a result you can measure.

Why Southeast Asia is interesting

This could suit malls, resorts and theme parks in Southeast Asia particularly well. In many markets there, people already scan QR codes and pay by QR without thinking about it. Nobody has to learn a new way to pay.

The casino deployments are useful context, but they don't prove a shopping center will see the same demand. The audience is different, people come at a different frequency, and the game design and the economics change too. Any rollout has to test whether foot traffic and tenant sales actually move.

The economics still decide

A good demo isn't a business model. Operators will ask what happens on a busy Saturday, how the backend copes with the load, who pays for the system and how the value gets split. The answers shape both the technical architecture and the pricing.

A useful pilot would count how many people start the journey, how many finish it, how many store visits it drove, how many transactions followed and how many rewards were redeemed. That tells you whether the system produces sales or only engagement numbers. Pricing and deployment would still need working out before an operator could make a serious decision.

Start with one journey

You don't need a venue-wide program on day one. One corridor, a handful of stores and a small reward budget would show whether the idea works.

If it does, what you've built is a link between people finding a store, the store making money, and a visit worth repeating. The AR is just how you get there.