Buyer's guide
If you run a multi-branch chain in Saudi, UAE, Qatar, Kuwait, Bahrain, or Oman, the right wallet platform depends on what you operate, what you've already wired, and what you're trying to get to. This is what to evaluate, not which logo to pick.
01 · The rubric
Most loyalty platforms compete on rule expressiveness and integration breadth. For a GCC chain, the durable differences sit further down the stack. These are the six we'd weight first.
A wallet is stored value the merchant owns: customers top up, the cash lands in the treasury that day, redemptions debit a real balance. Points are a contingent liability denominated in something abstract, redeemed against future spend that may never happen. The cashflow shape is different. The customer-side trust shape is different. The accounting shape is different.
For a multi-branch chain, "Maryam at Olaya" and "Maryam at Tahlia" must be the same record. Some platforms tie identity to the POS terminal; others to the operator chain; others let identity drift per-location. If you have 6+ branches, identity continuity is not optional.
Can you answer "did Diriyah cannibalize Olaya last week, or net-new the network?" without exporting CSVs and joining them in a spreadsheet? Most platforms report network totals well. Many report per-branch ok. Few connect campaign → wallet event → till swipe → cohort in one query.
A POS-bundled loyalty platform locks you to that POS. Switching costs accumulate every quarter. A POS-independent wallet platform lets you keep the POS you have, and switch POS later without losing customer history.
Arabic copy that reads as Arabic, not Google-translated. Mada and STC Pay as first-class rails. Branch chains as a top-level model, not a workaround. SAMA-aware data residency. Two-week onboarding, not two-quarter.
In 2026, your marketing lead should be able to ask "give SAR 10 to anyone dormant 21+ days at our top three branches" in English or Arabic, see the scoped impact, approve, and ship. If the platform requires SQL or a BI export to do that, it's not where the industry will sit by 2027.
02 · How the options compare
A snapshot of how each platform sits against the six dimensions, sourced from each vendor's own published docs as of May 2026. Verify directly; vendor capabilities change quarterly.
| Dimension | Feddi | Loyverse | Smile.io | Lightspeed Loyalty | Foodics Loyalty |
|---|---|---|---|---|---|
| Model | Wallet (stored value) | Points | Points | Points | Points + stored value (per Foodics Loyalty docs) |
| Cashflow timing | Top-up upfront, redemption debits | Redemption-time only | Redemption-time only | Redemption-time only | Configurable per program |
| Branch identity | One wallet ID across the chain | Per-store database (multi-store paid tier) | Network-wide via Shopify customer record | Per-location, joined via Lightspeed Retail | Per-Foodics-account; multi-branch native |
| Branch-level attribution | Per-branch, per-till, per-campaign, real-time | Per-store sales reports | Network-level cohorts | Per-location sales | Per-branch Foodics analytics |
| POS coupling | Independent (integrates with Foodics, Lightspeed, Loyverse via standard payment APIs) | Loyverse POS-bundled | Shopify-bundled (eCommerce primary) | Lightspeed POS-bundled | Foodics POS-bundled |
| GCC localization | Built in the region, Arabic + Mada native | Global product; Arabic UI; Mada per processor | Global product; Arabic limited | Global product; Mada via integrations | GCC-headquartered, Arabic + Mada native |
| Operator agent (plain language) | Plain-language queries + audited actions (English + Arabic) | Reports + rule builder | Reports + rule builder | Reports + automation rules | Reports + rule builder |
| Pricing posture | Contact-gated, tiered by branch count | POS subscription + add-ons | Free tier + paid plans | Bundled with Lightspeed POS | Subscription on Foodics plan |
Sources: vendor pricing and feature pages reviewed May 2026. Loyverse: loyverse.com. Smile.io: smile.io. Lightspeed Loyalty: lightspeedhq.com/loyalty. Foodics Loyalty: foodics.com. Capabilities change; verify against current vendor docs before deciding.
03 · Fit guidance
No platform is universally correct. The honest read-out, per operator shape.
Pick when: 6+ branches, you want stored value (cashflow upfront, not points liability), per-branch attribution honesty matters, and you want the operator agent layer. Keeps your POS (Foodics, Lightspeed, Loyverse), adds the wallet stack on top.
Not the pick when: 1–2 branches and the loyalty-bundled-with-POS model is enough; or fully Shopify-native eCommerce with no physical retail.
Pick when: small chain (1–5 branches), already on Loyverse POS, points-model is sufficient, free tier covers your usage.
Not the pick when: you want wallet (stored value), you're not on Loyverse POS, or you need plain-language operator queries.
Pick when: Shopify-native, primarily eCommerce, want a clean points + rewards UI for online-shoppers, ok with English-first product.
Not the pick when: your spine is physical retail (POS, branches), or you operate in Arabic with Mada-first checkout.
Pick when: already running Lightspeed Retail / Restaurant, want loyalty bundled with POS, single-vendor preference.
Not the pick when: you want wallet (stored value), POS-independence, or the operator agent layer.
Pick when: already on Foodics POS, the bundled loyalty stack meets your rules-engine needs, single-vendor billing preference.
Not the pick when: you want a wallet stack with the deeper per-branch attribution and operator-agent surface Feddi adds on top. Note: Feddi integrates with Foodics, so you can keep Foodics POS and the Foodics loyalty rules, and add Feddi as the wallet rail.
04 · The Feddi position
Most loyalty platforms shipped from US / EU SaaS DNA: points engines bolted onto a POS, redemption-time accounting, marketing-lead-first surfaces. They work, and for many operators they're enough.
For a multi-branch chain in the Gulf, we think the durable shift is to wallet: customers top up upfront, the merchant gets cash that day, redemptions debit a real balance, every till sees the identified customer, every branch's attribution is honest, and the marketing lead can ask the system questions in plain Arabic or English. This is what Feddi is.
We integrate with the POS you already have. We don't replace Foodics or Lightspeed or Loyverse. We add the wallet rail and the intelligence layer on top.