Transactions
Revenue
Period:
—
Product:
|
Vertical:
|
Acquirer:
GMV
AED 5.8M
+14%vs prev period
Transactions
31,240
+11%avg/day: 1,041
ATV
AED 186
−2vs prev period
Txn / FMI
17.0
+1.2median: 11.4
Active FMI
1,840
+94≥1 txn in period
Active FLI
2,310
+1181.26 loc/FMI avg
GMV over time
Weekly · by product
POS
TablePay
Loyalty
Active merchants
Weekly · count & % of base
POS
TablePay
Loyalty
% base
Peak: —
Avg share of base: —
Top merchants by GMV
Ranked by transaction volume
| # | Merchant (FMI) | Tier | Vertical | GMV | Txns | ATV | % total | Cumulative % |
|---|
GMV tiers — merchant portfolio segmentation
Ranked by cumulative GMV contribution · boundaries: 50% / 80% / 95%
Adjust boundaries ⓘ
GMV distribution — percentiles
How GMV spreads across the merchant base
GMV per merchant — spread
Count of merchants by GMV band
Tier-based merchant segmentation Phase 3
T1 = simplest → T4 = most complex · Placeholder data — segmentation logic ships in Phase 3
MERCHANT COUNT
GMV CONTRIBUTION
GMV / MERCHANT
| Tier | Definition | FMI | % base | Total GMV | % GMV | Avg GMV/FMI | Avg txns | ATV |
|---|---|---|---|---|---|---|---|---|
| T1 | Simple · 1 location · manual ops | 920 | 50% | AED 0.9M | 15% | AED 978 | 5.8 | AED 169 |
| T2 | Catalog active · 1–2 locations | 552 | 30% | AED 2.1M | 36% | AED 3,804 | 18.4 | AED 207 |
| T3 | Multi-location · sales module active | 276 | 15% | AED 2.0M | 35% | AED 7,246 | 38.2 | AED 190 |
| T4 | Complex · multi-brand · high sales volume | 92 | 5% | AED 0.8M | 14% | AED 8,696 | 61.4 | AED 142 |
⚠
Revenue data is partially availableSaaS subscription data lives in the billing system (not yet connected). TRX markup estimated from GMV × acquirer margin rates.
ℹ
Two revenue streamsSaaS subscriptions (annual, billed per FMI) and TRX markup (only when Fortis is the acquirer).
SAAS SUBSCRIPTIONS
Active subscriptions (FMI)
1,840
across all tariffs
Est. ARR (SaaS)
AED 2.4M
Active FMI × avg plan price
EstimateChurn MRR (FMI)
AED 22K
39 FMIchurned MTD
New subscription MRR
AED 31K
94 new FMI × avg tariff
EstimateNet new MRR
+AED 9K
New − Churn MRR
EstimateSubscription mix by tariff
Active FMI and estimated annual revenue per tariff
| Product | Tariff | SaaS AED/yr | Active FMI | % base | Est. ARR | TRX markup |
|---|---|---|---|---|---|---|
| POS | Basic | 0 (free) | 480 | 26% | — | ~0.1% when Fortis acquirer |
| POS | Smart | 990 | 660 | 36% | AED 653K | ~0.1% when Fortis acquirer |
| TablePay | Basic | 690 | 310 | 17% | AED 214K | ~0.1% in-person · ~0.2% QR |
| TablePay | Full | 1,290 | 210 | 11% | AED 271K | ~0.1% in-person · ~0.2% QR |
| Loyalty | — | 2,200/loc | 180 | 10% | AED 396K | No TRX revenue |
| Total | 1,840 | 100% | ~AED 1.53M | |||
TRX MARKUP REVENUE
⚠
TRX markup applies only when Fortis is the acquirerNI, Neopay, Paymob (in-person) and NI + MyFatoorah (QR). ~0.1% soft ceiling; MF up to ~0.2%.
Fortis-acquired GMV
AED 3.1M
54% of total GMV
Est. TRX markup revenue
AED 3.1K
Fortis-acquired GMV × ~0.1%
Estimate · monthlyEst. TRX ARR run rate
AED 37K
Monthly × 12
EstimateNon-Fortis GMV
AED 2.7M
46% · no markup revenue
Revenue composition — estimated
SaaS vs TRX markup · monthly run rate
SaaS subscriptions
98.5%
~AED 200K/mo · dominant revenue stream
TRX markup
1.5%
~AED 3.1K/mo · grows with Fortis-acquired GMV
Period:
—
Product:
Core entity
Sale
Every transaction in the system starts as a Sale — regardless of payment status or item type.
Payment status
A sale can be
PaidUnpaid / pending
Payment status alone does not determine catalog adoption.
Catalog dimension
A sale can be
Catalog sale — ≥1 item position references a catalog_item_variation_id
Manual / custom — direct amount, no catalog item attached
What we measure here
Catalog sales share — what fraction of all sales have ≥1 catalog item. This is the product adoption signal.
Retention is calculated the same way: cohort = merchant's first-sale week; retained = had ≥1 catalog sale in week N.
Catalog adoption — North Star
Last 7 days · All products
Catalog sales share
78%
of all sales have ≥1 catalog item
+4ppvs prev 7d
Total sales in period
23,620
18,420 catalog · 5,200 manual
+12%vs prev 7d
% active merch with catalog sales
71%
219 of 309 active merch
+3ppvs prev 7d
Catalog sales / active merchant
84.2
+6%vs prev 7d
Merchants w/ catalog sales
219
+8vs prev period
Unique terminals (TID)
341
+14vs prev period
Catalog sales over time
Daily · all products combined
Catalog sales retention
Cohort = week of merchant's first sale · Retained in week N = had ≥1 catalog sale that week
W0 — catalog sales rate at activation
68%
of cohort had ≥1 catalog sale in their first-sale week
+4ppvs prev cohorts avg
W1 retention
52%
of those with a catalog sale in W0
+3ppvs prev cohorts avg
W4 retention
38%
of cohort active at month 1
+2ppvs prev cohorts avg
Steady-state (W12+)
29%
retention plateau, avg W12–W16
+4ppvs 3mo ago
Cohort retention heatmap
Row = cohort week · Column = weeks since activation · Cell = % with ≥1 catalog sale
0%
100%
Retention curves by product
Average across all cohorts · Y = % of cohort with ≥1 catalog sale in week N
POS
TablePay
Loyalty
Users & activity
Feature health
Users & activityA1
Dimension
Totals — merchant IDs
Merchant IDs
1,284
Unique active merchant locations
New this period
148
↑14%vs prev — with ≥1 completed action
Activity — rolling window · merchant IDs
MAU
924
Rolling 30d active merchant IDs
WAU
611
Rolling 7d active merchant IDs
DAU / MAU
0.24
Stickiness — 0.2+ healthy for backoffice
By surface
| Surface | Merchants (IDs) | Users (emails) |
|---|---|---|
Portal — Desktop web backoffice · ≥1 session in period | 840 | 2,180 |
Portal — Mobile mobile web · manager on-the-go | 510 | 840 |
POS App terminal · workplace accounts active in period | 1,102 | 1,920 |
| ↳with transaction any payment type processed | 1,102 | 1,920 |
| ↳with catalog sale ≥1 sale containing a catalog item variation | 780 | 1,340 |
Gap of 580 users (1,920 − 1,340) ran transactions with no catalog item — POS used as payment terminal only.
Feature healthA3
| Feature | Enabled | Active | Active / Enabled | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
POS ≥1 workplace activated · ≥1 sale in period | 1,284 | 1,102 | 86% | ||||||||||||||||
| |||||||||||||||||||
Loyalty program configured · ≥1 top-up OR ≥1 loyalty spend | 510 | 340 | 67% | ||||||||||||||||
TablePay extension + table configured · ≥1 sale via table_pay source | 320 | 198 | 62% | ||||||||||||||||
AI assistant feature flag on · ≥1 query sent in period | 184 | 96 | 52% | ||||||||||||||||
Core
Catalog & inventory
Sales
Online shop
Reporting
F&B
Retail
POS — CoreB1
Merchant activity
Transaction-based
1,102
Merchants with ≥1 payment processed — any type. Includes manual, custom, and catalog sales.
Sales-based (catalog)
780
Merchants with ≥1 sale where at least one position references a catalog_item_variation_id.
Total transactions
84,200
All sale records in period
Catalog sales
12,840
Sales with ≥1 catalog item
Total GMV
AED 5.2M
Sum of completed sales
AOV
AED 61.7
GMV / completed transactions
Avg catalog sales / merchant
32.9
Among merchants with ≥1 catalog sale
Payment method mix
Card
49%
Cash
18%
AANI
10%
Payment link
7%
Manual / custom
12%
Other
4%
Health signals
Refund rate
1.4%
Discount rate
8.2%
Cancellation rate
2.8%
Manual / custom in payment mix = transactions where no catalog item was selected.
Catalog & inventoryB1 · Catalog & Inventory
Catalog
With catalog
1,098
Merchants with ≥1 active item
Catalog in use
780
Item appeared in ≥1 sale
Avg items
34
Active variations per merchant
Median items
18
p50 — less skewed than avg
Image coverage
54%
Items with image / total active
Inventory activity
Inventory active
284
Merchants with any stock quantity change in period — up or down
Of all merchants
22%
Warehouse exists for all — only 22% have actual movement
Stock events / merchant
4.6
Avg delivery notes + audits per active merchant
Inventory active = any stock quantity change via delivery note (grew) or audit document (corrected). Warehouse existence alone does not count.
SalesB1 · Sales
Framing: a sale is the core transaction entity — it always happens. Within sales, two types exist: catalog sales (where ≥1 position references a catalog item) and manual/custom sales (direct amount, no catalog). The key metric is catalog sales share — what portion of all sales are catalog-driven.
Volume
Catalog sales
12,840
Sales with ≥1 catalog item in period
Merchants active
390
Merchants with ≥1 catalog sale
Avg catalog sales / merchant
32.9
Among merchants with ≥1 catalog sale
Avg catalog sale value
AED 84
Avg sale amount for catalog-driven sales
Catalog vs. all sales
Catalog sales share
78%
Of all sales, share where ≥1 position references a catalog item — vs. manual/custom
Catalog sale completion
84%
Of catalog sales initiated, share that reached completed status
Payment type distribution — catalog sales
How catalog sales are paid
On-site (at the store)
54%
Payment link
38%
Self-service (online)
8%
Merchant adoption — catalog sales share
Merchants segmented by what share of their total sales are catalog-driven. Measures how deeply catalog is embedded in daily operations.
No catalog sales
0% catalog share
450
Manual only
All sales are manual / custom amount — catalog not in use
Low adopters
<25% catalog share
218
Occasional use
Catalog items appear in some sales — not the default workflow
Mid adopters
25–74% catalog share
148
Mixed workflow
Catalog-driven and manual sales coexist — partial adoption
High adopters
≥75% catalog share
124
Catalog-first
Most sales flow through catalog — strong signal for upsell and delivery integrations
Online shopB1 · Online shop
Online shop ON
480
Merchants with shop toggled on
Active shops
210
≥1 self-service sale placed in period
Menu views
48,200
Unique sessions on online menu
Sales placed
6,840
Self-service sale completions
Cart conversion
14.2%
Sales / menu views
Avg sale value
AED 74
Online self-service sales only
Gap: 270 merchants have online shop ON but zero sales placed — live catalog not driving traffic.
ReportingB1 · Reporting
Dashboard active
642
Merchants with ≥1 dashboard load
Reports active
418
Merchants with ≥1 report downloaded
Downloads / merchant
4.2
Avg in period — ≥3 = habitual user
Top date filter
This month
Financial review pattern
Report downloads by type
Raw data
1,840
Sales by items
1,325
Cash flow
1,067
Sales by employee
754
Sales by location
534
Stock balance
331
Raw data dominates — merchants have outgrown prebuilt reports.
POS — F&BB1 · IndustryFood & Beverage
Restaurant operations
F&B merchants
680
Merchants on F&B tariff
Tables configured
412
Merchants with ≥1 hall/table set up
Tables active
318
≥1 table-sourced sale in period
Avg tables / merchant
14
Configured tables per restaurant
Inventory — F&B
Inventory active
184
F&B merchants with ≥1 stock movement
Adoption rate
27%
Of F&B merchants — vs 52% retail
Stock events / merchant
3.2
Avg delivery notes + audits
Audit rate
48%
Active merchants running ≥1 stock audit
POS — RetailB1 · IndustryRetail
Catalog & scanning
Retail merchants
380
Merchants on retail tariff
Barcode scanning active
214
≥1 barcode sale position in period
Items with barcode
68%
Variations with barcode / SKU configured
Avg catalog size
84
Active variations — vs F&B avg of 28
Inventory — Retail
Inventory active
198
Retail merchants with ≥1 stock movement
Adoption rate
52%
Of retail merchants — vs 27% F&B
Stock events / merchant
5.8
Avg delivery notes + audits
Suppliers configured
2.4
Avg active vendors per merchant
TablePayB2
Reach
Merchants enabled
320
Extension + ≥1 table configured
Merchants active
198
≥1 sale with source = table_pay in period
Volume
Total transaction volume
AED 810K
Sum of all table_pay sales
Transactions
5,473
Completed table_pay sales
Avg transaction value
AED 148
Total volume / completed transactions
Session behaviour
Sessions initiated
8,420
QR scans opening pay-at-table
Completion rate
65%
↓4%vs prev period
Tip attach rate
38%
Completed sessions with tip > 0
Session funnel
Initiated
8,420
Reached payment
80%
Completed (sale)
65%
Split method mix
Full payment
52%
Equal split
24%
By item
16%
Custom amount
8%
External POS integrations
| Integration | Purpose | Connected | Status |
|---|---|---|---|
Foodics Restaurant POS · order routing | Online menu sales → Foodics POS | 148 | Active |
Syrve (iiko) Restaurant management · TablePay source | TablePay sales sourced from Syrve POS | 62 | Validate |
⚠ Syrve count should be validated against integration service records.
Adoption depth
Not enabled
964
Not configured
No extension or tables set up
Enabled, not used
122
Zero sales
Tables exist — no table_pay sales this period
Minimal use
88
1–10 sales
Trying — convert to regular is the lever
Regular use
110
>10 sales / period
Sticky — upsell candidates
122 merchants enabled but zero activity — most actionable segment.
LoyaltyB3
Reach
Merchants enabled
510
Loyalty program configured (any type)
Merchants active
340
≥1 top-up OR ≥1 loyalty spend in period
Active / Enabled
67%
↑5%vs prev period
Enrollment
Total enrolled
24,180
Cumulative card holders
New enrollments
1,840
↑22%vs prev period
Enrollment rate
40%
Enrolled / customers with ≥1 sale
Engagement
Wallet installs
9,840
Apple + Google Wallet activations
Redemption rate
18%
Loyalty spend txns / total loyalty txns
Enrollment channel
QR self-signup
62%
Staff created
29%
Bulk import⚠ validate
9%
Program type — merchant share
Points
74%
Stamps
26%
⚠ Bulk import: confirm whether this exists for loyalty enrollment specifically, or only general CRM import.
Adoption depth
Not enabled
774
No program
Loyalty not configured
Enabled, not used
170
Program on, zero events
No top-up or loyalty spend this period
Minimal use
120
1–20 enrollments
Early traction
Regular use
220
>20 enrollments
Active — upsell to campaigns
AI assistantB · AI
Reach
Merchants enabled
184
Feature flag on per company
Merchants active
96
≥1 query sent in period
Adoption rate
52%
Active / enabled merchants
% of merchant base
7.5%
Active AI users / total merchant base
Usage volume
Total queries
3,240
All messages sent in period
Queries / merchant
33.8
Avg per active merchant
Conversations started
640
Distinct conversation IDs opened
Queries / conversation
5.1
Depth per session
Quality
No-answer rate
14%
Low-confidence / empty responses
⚠ no_answer_rate requires dedicated logging — not yet instrumented in the analytics service.
Scope limitation: AI assistant currently has access to sales data only. Inventory, customer, and loyalty queries inflate the no-answer rate.