Use case · RetailOS

Paper receipts → Telegram-native cash close.

A small bakery in Cairo used to track everything on paper. We deployed RetailOS — multi-tenant POS + inventory + customer engagement — and wired the daily summary into the owner's Telegram. The result: zero-login operator UX, auditable receipts, the day's numbers on the owner's phone.

The reality

Every small retailer in Egypt we've met has the same stack: a WhatsApp, a book of customers, paper receipts, and an end-of-day pile that someone reconciles on Thursday. Western POS vendors show up with Shopify + Stripe + English UIs. None of that matches the ground truth.

The owner doesn't want a dashboard. The owner wants to know, before bed, whether today beat yesterday. That's a Telegram message, not a web app.

What we shipped
  • Arabic-first POS (RTL, Arabic digits, colloquial copy)
  • Real-time inventory with rolling demand forecasting
  • Customer engagement workflows over Telegram + WhatsApp
  • Multi-tenant architecture — one RetailOS, many shops
  • Per-product tax + returns/RMA shipped Apr 2026
  • Owner gets the daily summary as a Telegram message
Numbers

Numbers that matter.

22:00
Daily close pushed to Telegram
18
PRs shipped in one week (Apr 2026)
Zero-login
Owner reads the day on Telegram
OPERATOR.LOOP · Mr. Donutevery day · 22:00 EET
ingestPOS · receipts · inventory deltas
summaryLLM-summarized daily Telegram digest
alertStockout risk → next-day reorder draft
ownerReads on phone · approves with 1 emoji
FAQ

What MENA retailers ask first.

We replace the paper with a tablet-first UI. The owner sees the day's numbers on Telegram without logging in. That's the whole design goal — zero-login operator experience.
Product: RetailOSService: MENA automationService: AI Agent Development
Next step

Running a retail shop and want this setup?

20-min fit call. Bring your current workflow and one metric you want to know without logging in.

18–24h reply · Cairo + EU hours · honest scoping