livePoint of sale
Sales and return invoices, automatic stock deduction, invoices tied to the customer record, receipt printing, and it runs on a phone. Money is calculated on the server, never in the browser.
Your whole business, in one system
Point of sale, inventory, accounting, staff and an online store — not five programs someone reconciles in a spreadsheet every night, but one system on one shared database. Built for Iran: Jalali calendar, Persian interface, servers inside the country.
Pre-launch — the first business is already running on it
The problem is not missing software — it is software that does not talk
You have a point of sale, an accounting package, a spreadsheet for stock, and a webshop that knows about none of them. Every night someone has to reconcile those four versions of reality. Mohaseb 365 is one system from the start.
- One dataset, not four islandsAn invoice rung up at the till drops stock in the same instant, lands in the income ledger, and attaches itself to the customer record. There is no nightly sync and no export-import dance.
- Jalali calendar, built inDates are stored in Gregorian and shown in Jalali — never the other way round. Reports line up with the Iranian fiscal year, and the interface is right-to-left by design, not a mirrored Latin layout.
- Each business, its own dataEvery tenant gets a separate database. One customer's data leaking into another because a WHERE clause was forgotten is not rare here — it is structurally impossible.
- No outside dependenciesFonts, icons and libraries all sit on our own server, and the server sits in Iran. When international connectivity drops, your till does not.
- Mobile, not a shrunken desktopHeavy tables turn into cards on a phone without scrambling the reading order, and counter sales run through an app that keeps working offline.
- Permissions at action levelRoles go down to "who may edit a price". Two-step login, a register of open sessions and remote sign-out are part of it.
13 areas, from the till to the financial statements
The dashboard is split along these areas. Each business switches on only what it needs; the rest never appears.
- Sales dashboardThe pulse of the day, week and month; best sellers and drops
- Product dashboardCatalogue health, incomplete and unpublished items
- Orders and shipmentsFrom order entry to courier delivery, with live status
- Stock and supplyReorder points, suppliers and purchase invoices
- Warehouse and logisticsMultiple warehouses and branches, issues, receipts, transfers
- Finance and accountingIncome and expense ledgers, cheques, petty cash, fixed assets
- Financial statementsP&L, balance sheet, cash flow, changes in equity
- Marketing and CRMLoyalty club, SMS, promotions and campaigns
- Content and SEOMetadata, articles, rank tracking, price-comparison feeds
- People and HREmployees, roles, payroll and hiring
- Attendance and shiftsClock-ins, leave, team board and monthly hours
- System settingsBusiness identity, backups and hardware connections
- Self-serviceThe employee's own desk: my devices, my leave, my payslip
What already works today
This is not a roadmap and not a wish list: every item below is in daily use by a real business, on real data.
liveProduct information management
A catalogue at tens-of-thousands scale, an approval gate before anything reaches the storefront, a duplicate-review queue, product variants, barcode and shelf-label printing.
liveOnline store
Product, category, brand and search pages — all fed by the same stock data. Customer login by SMS, a cart, and SEO-ready category and brand pages.
liveIncome and expense ledger
Daily entries on the Jalali calendar, a full history for every row, and voiding instead of deleting; no financial record ever leaves the system.
liveFinancial statements
Four standard statements built straight off the general ledger: profit and loss, financial position, cash flows, and changes in equity.
livePayroll
Labour-law formulas, payslips, and each month stored as a frozen snapshot — changing this year's parameters never rewrites last year's payroll.
liveSMS and loyalty club
Campaigns and bulk sending, one-time login codes, delivery reports, and automatic failover between operators when one stops answering.
liveMarket and competitor radar
Competitor prices, undercut alerts and pricing suggestions, plus a map of nearby potential customers with distances from the store.
Of the 72 modules defined in the dashboard, 46 are built and in use; the rest are shown right there marked "planned", so nobody has to guess what exists and what does not.
The businesses this was built for
Retail with real stock
A shop with both walk-in customers and online orders, where stock has to be one number for both. Till, warehouse and storefront on one dataset.
Distribution and wholesale
Tiered pricing, purchase invoices from suppliers, several warehouses and branches, stock transfers, and shipment tracking to the customer's door.
A business outgrowing itself
The point where headcount has passed the level at which "everyone can see everything" still works: roles, permissions, attendance and payroll.
Where the project actually is
Mohaseb 365 has not launched publicly. We would rather state the real position than make promises.
First business, live
A real shop with a catalogue of tens of thousands of items, a working till and a financial ledger runs on this exact codebase. It was not built in a lab.
Code separated from customer
Each business's name, domain and identity come from one central registry, not from inside the code. Adding the next customer is a settings row, not a new build.
Pre-release environment
Every change is tested in a separate environment before it reaches real businesses. The release gate is shut: no code reaches the live server without an explicit go-ahead.
Onboarding the second business
Sign-up, automated provisioning and billing — that is what is being built right now. Note that the product interface is Persian today; English and Arabic are on the roadmap, and we will not pretend otherwise.
Be the second business on Mohaseb 365
Public sign-up is not open yet, and the number of early businesses is kept deliberately small so each one is rolled out properly. To talk about a rollout, use the form below.
"One codebase. Separate data." The rule the whole architecture stands on.