Most MENA fast-casual operators who decide to launch a loyalty app spend the first 60 days in platform selection, the next 30 in negotiation, and then discover they have no implementation plan. The 90-day window from signed contract to active loyalty program running across multiple locations is achievable, but only if the sequence is right. This is that sequence, written for the operator or marketing lead who owns the project, not an IT department.
The target outcomes for this playbook: 50% or higher enrolment among repeat guests by day 90, a 35% or higher lift in second-visit conversion rate for enrolled versus non-enrolled guests, and 60% or higher push notification open rate on segmented sends. These are not aspirational benchmarks, they are the figures a well-run pilot using Habitu's implementation cadence has consistently hit in the MENA market.
Weeks 1-2: POS Integration and Segmentation Setup
The first action is POS integration, not app design. The temptation is to start with the consumer-facing product, what the app looks like, what the reward structure is, because that's the visible output. That is backwards. The POS integration is the foundation that makes every subsequent step work. Without it, identity capture at the counter is manual, enrolment friction is high, and staff follow-through is inconsistent.
Foodics integration setup takes approximately 2-4 business days end-to-end when both the operator and the platform have their configuration ready. The Foodics API exposes transaction webhooks and a customer-facing loyalty integration point at the terminal. The Habitu Foodics connector handles the authentication, the webhook subscription, and the identity resolution logic, the work on your side is providing API credentials and confirming your menu taxonomy is clean. If your Foodics menu has items without SKUs or with duplicate names across locations, clean that first. Dirty POS data produces dirty loyalty data.
During Weeks 1-2, also establish your segmentation baseline. Before the app goes live, connect your POS transaction history (most Foodics accounts have 12-24 months of data) to the loyalty platform and run an initial RFM pass. This tells you three things: how many repeat guests you already have (your most capturable audience), what the natural visit cadence looks like in your market (sets your RFM frequency thresholds, see the RFM calibration methodology), and which locations have the highest concentration of repeat guests (these are your pilot locations). If you have 6 locations and two of them account for 60% of your repeat-guest traffic, those are your pilot sites.
Staff briefing in Weeks 1-2, not Week 4. The most common point of failure in loyalty pilots is staff who don't know what the program is, can't explain it in one sentence, or don't ask for enrolment at the counter. Your counter staff are your highest-leverage enrolment channel. Brief them before the app is live, not during launch week when everything else is happening simultaneously. The staff pitch needs to be one sentence: "Download our app, scan it here, get your first reward after three visits." That's it.
Weeks 3-4: App Build and Brand Alignment
The consumer app build, on a platform with configurable branding, takes 5-10 business days for a standard MENA fast-casual configuration. The decisions you need to make before the build starts: primary loyalty mechanic (stamps or points, stamps are recommended for MENA fast-casual because they are immediately legible to guests across all demographic segments), reward ladder (what does a guest earn at 5, 10, and 20 visits), primary language (Arabic or English first, depending on your dominant guest demographic, see the Dubai vs Riyadh framing in the previous post), and push notification opt-in copy.
Brand alignment is not decoration. In a market where operators frequently cite "it looks generic" as the reason they haven't launched a loyalty app, the consumer-facing app must carry your visual identity without compromise: your primary and secondary brand colors, your typeface, your logo in its correct form, and photography that matches your brand register. The Habitu branded-app build uses token-driven theming that propagates brand settings across every screen simultaneously, a color change on the brand settings screen updates the app's header, reward card, stamp grid, and notification template in one operation.
App Store submission for iOS and Google Play takes an average of 2-5 business days if the submission is clean. Common rejection reasons for restaurant loyalty apps: incomplete privacy policy (must explicitly cover push notification data), missing app screenshots at all required resolutions, and terms of service that don't cover the loyalty mechanic. Submit in Week 3 so that if there is a rejection, you have buffer to respond without delaying the Week 5 pilot launch.
Weeks 5-8: Pilot Launch at 1-2 Locations
Pilot launch is a coordinated one-day event, not a soft rollout. Coordinate counter staff briefing, QR code placement (counter display, table tents if applicable, carry bag inserts), and social media announcement on the same day. The first 48 hours of a pilot generate disproportionate enrolment if they are treated as a launch event; a "we just quietly turned this on" rollout generates a fraction of the enrolment with the same infrastructure.
Week 5-6 measurement priority: enrolment rate among repeat guests. Pull your Foodics transaction data for the two pilot locations and identify guests who have visited more than once in the prior 30 days. Compare that number to your enrolled guest count at the end of Week 6. Target: 50% of identifiable repeat guests enrolled within the first two weeks. If you're below 25%, the enrolment mechanic has a problem — either the QR code placement is low-visibility, the staff aren't asking, or the first-reward threshold is too high (guests can't see the value quickly enough).
Week 7-8 measurement priority: second-visit conversion lift. Compare the second-visit conversion rate of enrolled guests versus guests who transacted at the pilot locations during the same period but did not enrol. Target: enrolled guests should be converting to a second visit within 14 days at a rate 35% higher than non-enrolled guests. If the lift is below 20%, review the post-enrolment welcome campaign, the push notification or in-app message that fires in the first 48 hours after enrolment is the highest-leverage touch in the entire program.
Capture density measurement is the other Week 5-8 deliverable. Capture density is the percentage of your total transaction volume at pilot locations that is now attributed to a named guest profile. At the end of the pilot window, you should be able to say: "Of the 4,200 transactions at Location 1 in the last four weeks, we can attribute 1,890 of them to a named guest." That 45% figure becomes your benchmark for the full rollout, and it's the number that tells your CFO how much of your customer base you now own.
Weeks 9-12: Full Rollout and Campaign Tuning
Full rollout to all locations uses the pilot as the operational template. Replicate: counter QR placement, staff briefing script, App Store download card in carry bags, day-one social announcement. The pilot's learnings, which enrolment prompts worked best, what the staff Q&A most commonly produced, which reward tier generated the most enthusiasm, inform the rollout briefing. Don't repeat the pilot's friction at every location; apply what you learned.
By Week 10, your enrolled guest base is large enough to run the first segmented campaign. The six behavioral segments , champions, loyal visitors, promising newcomers, at-risk regulars, needs-attention, and dormant, will have started to populate. Your first campaign priority is Promising newcomers: guests who have visited 2-3 times in the last 30 days but haven't crossed the frequency threshold that makes them "loyal." A targeted push offering a bonus reward for their next visit is the highest-ROI campaign in the first 90 days, because converting a Promising guest to Loyal is the single most valuable transition in the lifetime value curve.
Success criteria at Day 90:
- 50% or higher enrolment among guests with 2+ visits in the pilot period
- 35% or higher second-visit conversion lift for enrolled vs non-enrolled guests
- 60% or higher push notification open rate on segmented sends (non-blast)
- Capture density above 40% of total dine-in transaction volume at pilot locations
- At least one full reward redemption cycle completed by enrolled guests (validates the reward ladder is calibrated correctly)
If all five are met, the program is working and the next stage is campaign calendar depth, building out the Ramadan playbook, the second-visit automation trigger, and the at-risk win-back flow. If one or two are missed, the playbook above contains the diagnostic: enrolment rate issues trace to the counter experience; conversion lift issues trace to the post-enrolment campaign; push open rate issues trace to send timing or segment quality. Habitu's implementation team works through this exact sequence with every new MENA operator, the 90-day timeline is the standard, not the aspiration.