Eleven Tenants, Eleven Email Lists, Zero Hall-Level Customer Relationship
I have walked through twenty food halls in the last twelve months, and the same thing is true in every single one. The hall has eleven tenants, or sixteen, or thirty-four. Each tenant has its own POS, its own Mailchimp list, its own punch card. And the hall itself, the brand on the door and the rent on the leases, has zero direct relationship with the customer who comes in three times a week.
The ramen regular has been in forty-seven times this year and has never tried the Thai stall two doors down, even though it serves a flavor profile she would love. The Tuesday lunch-only customer has no idea there is live music on Wednesday nights. The couple that came in for the dumpling pop-up last month has no way to hear about the next pop-up. The discovery that should be happening every visit is not happening, and nobody is fixing it because nobody owns the relationship.
This is the structural problem wallet passes solve for food halls. One pass for the entire hall. One push channel that reaches every enrolled member at a 99% read rate (Square 2025 Loyalty Report). One operator-owned customer profile that knows which of the eleven tenants the customer has tried, and which they have not. The hall stops being a landlord with food tenants and starts being a curated experience brand with a direct line to its visitors.
Why Wallet Passes Specifically for Food Halls
Wallet passes are the right channel for food halls for reasons specific to the multi-vendor format. First, the structural one: the operator gets ONE pass for the entire hall, not eleven separate vendor passes. That single artifact lives on the lock screen, carries the hall's branding, and updates dynamically with visit count, favorite vendor, and tier. No tenant can replicate that alone.
Second, economics and read rate together. Wallet push costs zero per send (Apple Wallet and Google Wallet documentation, 2025) and is read 99% of the time on the lock screen (Square 2025 Loyalty Report). Email opens at 22% for restaurant marketing (Toast Restaurant Trends Report 2025); SMS at $0.02 to $0.04 per send (Telnyx and Twilio public pricing, 2025) opens around 90% but loses click-through. A hall with 5,000 members can push its full base for free, every week, forever, and have it read by essentially everyone.
Third, and the category-defining feature for halls: cross-vendor recommendation routing. The pass is a live data object. It knows which tenants the customer has bought from, which they have not, what they ordered, and how often. The hall's engine reads that profile and pushes a per-customer recommendation: "If you bought ramen at Saffron last week, here is khao soi at Forge today, same flavor profile, free dumpling on the side." A $0 message, 99% read, vendor-specific, generated from the customer's own data.
The structural payoff: the hall, not the tenants, owns the relationship. When a tenant leaves, their data does not walk out with them. The pass is hall-branded, the CRM is hall-owned, the push channel is hall-controlled. Every tenant gets a tenant-level dashboard showing their visits, discovery rate, and incremental revenue from cross-vendor pushes. But the underlying relationship belongs to the hall. That is the moat, and it compounds every month the engine runs.
Three Example Flows for a Food Hall
Here is what this looks like in practice.
Capture Flow
A customer is at any vendor's counter. There is an NFC sticker on the menu board: "Tap your phone, get a free fountain drink with today's order, and we will text you when your favorite vendor drops a special." She taps. A Safari sheet opens. She enters her name, phone, and which vendor she came in for today (the favorite-tier signal that seeds the recommendation engine). The wallet pass is added in under 30 seconds, showing the hall logo, her visit count (1), vendors tried (1 of 11), and her welcome reward.
If there is no NFC available, the same flow runs off a QR on the receipt. Every tenant POS prints it at the bottom of the ticket. NFC is faster (about 65% completion versus 40% for QR per our internal capture-flow data across 14 venues), but the hall should run both because they capture different customer behaviors.
First Push
A week later, on a Tuesday at 11:45 AM, the engine fires its first push to the new member: "Hey Maya, you tried Saffron last week. Today only, Forge is doing a khao soi pop-up 11:30 to 2. Same flavor profile as the tonkotsu you ordered. Free crab rangoon if you mention the pass." The push lands on her lock screen. She is half a block from the hall, on her lunch break. She walks in, orders the khao soi, redeems the rangoon, and the pass updates to show 2 of 11 vendors tried. The hall captured an extra $14 in tenant revenue, on a $0 message, on a customer who would have walked past Forge twelve more times before ever trying it on her own.
This is the cross-vendor engine in one customer's life. Multiply it by 5,000 members and 12 vendors, and you have the discovery gap closing in real time, every week, with no human marketer composing the messages.
Mature Loyalty
Six months later, Maya has been in 23 times. Her pass shows 7 of 11 vendors tried, a "Hall Regular" tier (unlocked at 20 visits), and a streak counter showing she is two vendors away from "Local Legend" (try all 11 by year end, get a $50 hall credit). On Sunday at 4 PM, the pass updates: "Two more vendors and you unlock Local Legend. The two you haven't tried are Mission Tacos and Avery Donuts. Avery is open right now until 6." She walks over for a donut. Pass updates to 8 of 11.
Mature loyalty for food halls is not a punch card. It is a dynamic discovery streak, a hall-wide tier system that rewards breadth, and event invites layered on top (live music, vendor anniversaries, new-tenant launches). Off-peak vendor pushes from low-traffic stalls go to high-frequency members who have not yet tried that vendor. Everything is targeted, per-customer, and runs on the pass.
Cross-Vendor Discovery Ratio (CVDR) Benchmarks
Regulr proprietary metric. CVDR = (unique vendors tried per visitor per year) ÷ (total vendors in hall).
Every 0.10 point improvement is worth roughly $80-$120 per visitor per year.
The ROI Math
Let me walk through a single worked example. The full methodology lives in our food hall cross-vendor playbook, which introduces the Cross-Vendor Discovery Ratio (CVDR) framework.
A 12-vendor hall sees 4,500 unique weekly customers (typical for a mid-size urban food hall, per Cushman & Wakefield 2024 Food Hall Market Report). NFC stickers go on every vendor's counter. QR codes print on every receipt. A hall-level table tent sits on every seating-area table. Capture rate at this density lands at 12%, the median we see in halls that deploy NFC plus QR plus table tents (internal Regulr capture cohort, 2024 to 2026). That is 540 wallet passes added per week, 28,000 over a full year, with most halls hitting 5,000 active passes inside 90 days.
Now apply the CVDR lift. Pre-engine, the average customer at a 12-vendor hall tries 1.4 vendors per visit (JLL 2024 Food Hall Operator Survey). Post-engine, after 12 months of cross-vendor pushes, that ratio climbs to 2.6 (Regulr cohort data, 2024 to 2026). The lift is 1.2 additional vendors per visit, every visit, across the entire enrolled base.
Each additional vendor visit attaches roughly $8 in incremental hall-wide spend (an order, a side, a drink at a different stall). For a customer who visits 6 times a year, that is $48 in additional annual revenue per enrolled member. For 5,000 enrolled members, that is $240,000 in additional annual hall-wide vendor revenue. The hall operator typically captures 25% of that lift through percentage-rent and shared marketing fees (National Restaurant Association 2024 Multi-Vendor Operations Report), which is $60,000 to the operator's bottom line on tooling costs of roughly $12,000 a year. Five-to-one return, before event-driven pushes or new-vendor welcome campaigns. At 12,000 members (typical 18 to 24 months in), the same math produces $144,000 to the operator on a $0-per-message channel (Apple Wallet and Google Wallet documentation, 2025).
Implementation Walk-Through: The Five Capture Points
The capture stack matters. A hall that puts a single QR code on a menu board will get a 2% capture rate. A hall that runs all five touchpoints below will hit 12% to 15%. The difference is the difference between a working engine and a dead one.
1. NFC stickers on every vendor's counter. The single most important touchpoint. The customer is at the register, paying. A sticker that says "Tap for a free [item], get hall updates" converts at 8% to 12% of transactions on its own. One sticker per vendor, placed to the right of the POS. Full mechanics in our NFC stickers walk-in capture playbook.
2. QR on every receipt. Every tenant POS prints the hall's enrollment QR at the bottom of the receipt. Catches the card-paying customer who walked away with the slip. Converts at 3% to 5% of transactions and stacks on top of NFC capture for another 30% to 40% of total enrollments.
3. Hall-level table tents with QR for the seating area. A small printed tent on every table. "Get the hall in your wallet. Free drink today, vendor specials forever." Customers waiting for food scan it. Quiet workhorse at 2% to 4% of unique table sittings.
4. NFC sticker on the menu board near the entrance. Larger sticker on the central menu board or directory near the front door. Catches customers in their first 60 seconds in the hall, drives a different cohort than register stickers (more first-time visitors).
5. Wallet pass link inside SMS receipts. If a tenant uses Toast or Square SMS receipts, include a one-line CTA: "Add the hall pass to your phone, get a free drink on your next visit." Converts at 6% to 9% of SMS receipt opens, a high-intent moment right after a positive experience.
Run all five and the capture rate compounds. Run only one and you leave 60% of potential enrollments on the table.
The Hall Operator's Three Strategic Levers for CVDR
Every intervention that raises CVDR falls into one of three levers. Top halls pull all three simultaneously.
Every non-enrolled visitor cannot contribute to CVDR. Target 40%+ enrollment within 90 days.
AI-composed per-customer pushes are load-bearing. Generic hall-wide offers do not move CVDR.
Require vendor participation as a condition of leasing. Hall sends them customers they cannot acquire alone.
Push Notification Cadence Rules for Food Halls
Cadence is where most halls accidentally torch their list. The rule is simple and load-bearing: at most one push per customer per ten days, hall-wide. Not per vendor. Per customer. If Saffron, Forge, and Avery all want to push the same customer in the same week, only one goes out, and the engine picks the one with the highest expected lift based on the customer's behavioral profile.
This is the hall-level cadence governance tenants cannot do on their own, and it is the reason hall operators have to own the channel. A vendor running its own push would happily message every member every Friday. Eleven vendors doing that means eleven pushes a week, which means a 30% pass-deletion rate within 60 days. The hall's job is to be the cadence cop.
For vendor-recommendation pushes, the engine uses the favorite-vendor pattern. The push references the vendor the customer has bought from most often as the comparison anchor: "You loved the tonkotsu at Saffron, so try the khao soi at Forge." Single-operator venues use the favorite-order pattern instead, but multi-vendor halls use favorite-vendor because it surfaces the comparative recommendation logic the customer already has in their head. Quiet hours matter too: no pushes before 9 AM or after 9 PM in the customer's local timezone, no more than two in any 21-day window. Cadence discipline keeps the channel healthy at 99% read (Square 2025 Loyalty Report).
FAQ
Do tenants share the customer list? The hall operator owns the customer list. Tenants get a tenant-level dashboard showing their own visit data, their own cross-vendor discovery contribution, and their own incremental revenue attribution from hall pushes. They do not get the raw list, and they do not push the base directly. That is the structural deal that makes the engine work.
What about vendor-specific loyalty programs that already exist? Wallet pass loyalty complements them, it does not replace them. A tenant can keep its own punch card or per-stall app. The hall pass operates at the hall level (visit count across all vendors, cross-vendor discovery, hall-wide tier). Most tenants find hall enrollment drives more traffic to their stall through cross-vendor pushes, so the two reinforce each other.
Will tenants see each other's customers? Aggregated, yes. Per-customer, no. A tenant dashboard shows, "127 customers who buy from Saffron also bought from Forge in the last 30 days," which is the kind of insight that drives smart vendor-pair pushes. Customer-level data stays at the hall. If tenants had per-customer access, they could build their own list off the hall's enrollment and defeat the operator's moat.
How is this different from email or SMS marketing? Read rate, cost, and persistence. Email opens at 22% (Toast Restaurant Trends Report 2025), SMS at roughly 90% open but lower click-through, wallet push at 99% read (Square 2025 Loyalty Report). Email is roughly $0.001 per send and SMS is $0.02 to $0.04, while wallet push is $0 marginal (Apple and Google Wallet documentation, 2025). The pass itself is a live artifact on the lock screen, not a one-time message.
Can the pass show favorite vendor? Yes. Once the customer has 3+ visits, the engine populates a "favorite vendor" field based on visit frequency, and the pass surfaces it: "Maya, Saffron Regular, 7 visits, 4 of 11 vendors tried."
How fast does enrollment scale? Most halls hit 5,000 wallet passes within 90 days at 12-vendor scale with NFC plus QR plus table tents deployed. Halls that only deploy QR take roughly 9 months to reach the same number. Capture-stack density matters more than customer-volume-per-week.
What if a tenant leaves the hall? Their customer data goes with the hall, not the tenant. When a tenant exits the lease, the hall keeps every customer who ever bought at that stall, and the engine re-routes those customers' recommendation logic toward the remaining vendors or the new tenant who replaces them.
Where to Go From Here
For a live deployment example of a food hall plus pickleball complex running this exact stack, see the Relish capture kit, the physical signage and capture flow we built for them. For the underlying cross-vendor engine math and the CVDR framework, read the food hall cross-vendor engine playbook. The wallet pass marketing guide is the channel-architecture hub. The NFC stickers walk-in capture playbook covers the capture layer, Apple Wallet loyalty programs covers the iOS specifics, and SMS marketing for local business covers the layer that complements wallet push. For your specific numbers, run the retention calculator and the CLV calculator.
If you run a food hall and want to see what your CVDR lift looks like with a wallet-pass engine deployed, that is what we do at Regulr. The capture stack ships in 14 days. The cross-vendor engine starts pushing within 30. Most halls see their first $10,000 of incremental tenant revenue inside the first quarter, on a channel that costs $0 per message and reads at 99% (Square 2025 Loyalty Report).
Free: Customer Retention Checklist
A printable checklist with the strategies from this article, plus message templates you can copy-paste today.
No spam. Unsubscribe anytime. Your email stays private.
Get weekly retention tips
One actionable idea every Tuesday. No fluff, no spam.
Join 2,400+ local business owners. We respect your inbox.
Founder of Regulr & City Curated
Regulr is the customer retention layer for local businesses. It plugs into your POS, learns every customer's behavior, and runs personalized retention campaigns automatically — SMS, email, wallet pass updates, and RCS sentiment routing. Built for restaurants, coffee shops, salons, med spas, fitness studios, and other independent local businesses where every customer is a name and every visit matters.