For restaurant groups, cloud kitchens and shops
Munim runs your counter, kitchen and ledgers, then explains what happened, finds money leaking out and drafts the fix. Nothing changes until you approve it.
The live demo is Cobnut Bakehouse, a synthetic business: sample data, simulated suppliers, payments recorded, not processed.
@catalogueThe supplier's paneer price went up ⟨snap · row 4 · unit_cost⟩ and Tuesday's waste ran above its usual level ⟨snap · row 2 · waste_qty⟩.
Cannot verify the delivery-app payout for that week: its file has not been imported yet.
The One Guarantee
What Munim does
Each feature says honestly where it stands today.
Point of sale, a kitchen display with short ticket numbers and timers, and QR or web ordering with pickup windows. Prices and totals are worked out on the server, and order status only moves through allowed steps.
Catalogue, kitchen, purchasing, finance, people, customers, compliance and market specialists explain what happened, find money leaking out, and draft fixes. The Manager routes your question to the right desk.
Ask a hard question and Munim plans an investigation across specialists, step by step or on a plan you approve. Every finding carries the rows it came from.
Surplus food goes to food banks and NGOs instead of the bin, and businesses can offer surplus to each other. The AI spots it; you approve every listing.
Each business gets its own ordering website over the public storefront API: menus, pickup windows, checkout with pay-at-the-counter, and order status.
Brand colours, layout presets and a visual editor so an owner can shape their storefront without a developer.
Run two to five outlets, or several brands from one cloud kitchen, with each outlet's books kept apart and rolled up for the owner. Managers see only their own outlet.
When stock runs short, Munim asks suppliers for quotes, reviews every deal against your rules and drafts the purchase order for you to approve.
Currency, tax lines, receipts, time zones and compliance calendars come from a country pack, not from the code. A business in Australia runs on the AU pack — same code, different country pack. Country is fixed when the business is onboarded.
The team behind the desk
Fixed rules find the problem first; the model only explains it, with a reference beside every number. Address any desk directly, like @finance.
True dish margin from recipe, supplier price and waste; price-change drafts.
@catalogueTicket-time drift, remakes and prep-time proposals with evidence.
@kitchenShortfalls, price creep, waste spikes and purchase-order drafts.
@inventory_purchasingPayouts reconciled to orders, unexplained fees, month-end close.
@financeLabour against demand, overtime drift and roster drafts.
@peopleCoupon leakage, lapsing regulars and campaign drafts — never auto-sent.
@customersLicence expiry, missed temperature logs and checklists.
@complianceGoals, forecast notes and the surplus picture for Munim Cares.
@marketThe Manager reads your question, sends it to the right specialists, and brings back one answer with its sources. A forecast service sits behind them all, measured against a simple seasonal baseline.
How it works
Orders, tickets, stock, cash and payouts land in append-only books, one business and one outlet at a time.
Watchers and fixed rules flag margin leaks, missing payouts, waste spikes and expiring stock.
A specialist explains the finding with the rows behind it and drafts the fix, a source beside each number.
Approve or reject in one tap. The change runs under your name, with its audit entry, or not at all.
Munim Cares
Munim spots surplus and near-expiry stock, drafts a donation listing for your approval, matches it to a food bank or NGO, and records the hand-over in your books.
For developers
curl https://<this-site>/mock/v1/storefront/outlets \
-H "X-Munim-Storefront-Key: <a mock key from the developer portal>"Country packs
Everything that differs by country lives in a pack, so the code never branches on it.
Tell us how you work today. We'll show you Munim on a synthetic business like yours.