Dashboard
Quick Actions
Today's Performance
Business Insights
Low Stock
Point of Sale POS
Current Cart
Change: MWK 0
Recent Sales
Products & Stock
Add Product
📋 Stock Movement History
Purchase / Restock
Expenses
Business Reports
Cash Flow
Expense Breakdown
Profit Trend
Best Sellers
Slow-Moving Products
🎯 Business Targets
📈 Sales Trend & Period Comparison
🏆 Top Products
💰 Most Profitable Products
🐢 Slow-Moving Products
💼 Stock Money Tied Up
🚨 Restocking Priorities
💡 Business Recommendations
Business Insights
More
About
Mtumbuka Shop Manager is designed to grow from your own grocery shop into a professional tool for other small businesses.
Cloud & SaaS Center
Mtumbuka Cloud v6.2 ☁️
Real online identity, real cloud database and secure synchronization.
1. Cloud Project ☁️
Enter your Supabase Project URL and publishable key.
🔌 Connection Test
First save your Supabase configuration, then use this button to check the real online database connection.
2. Online Account Identity
3. Live Sync ☁️
Automatic backup runs after local changes when connected.
Never
Replace this device with the latest online copy.
🏪 Business & Team
Mtumbuka Shop
Set your business phone and details.
Owner
Business Profile
Shop Accounts
Create separate local profiles for owners, managers and cashiers on this device.
Businesses
🛡️ Security & Session
Protect the shop when the device is left unattended. Choose how long an inactive login can remain open.
🧾 Activity & Audit Log
Recent important actions are recorded with user, time and action for accountability.
☁️ Backup & Restore
Export a copy of your shop data or import a previously saved backup. Use the Cloud & SaaS Center for online backup and restore.
MTUMBUKA Founder Dashboard
Founder Control Center
Platform oversight for growth, subscriptions, technical health and security. This first test screen is a safe prototype; it does not yet connect to platform-wide business or billing records.
Founder Rules
1. Customer privacy
No routine browsing of customers' detailed sales, stock, debts or customer lists. Any exceptional support access must be justified, authorized, limited in scope and audit-logged.
2. Data protection
Never silently delete or overwrite customer records. Backups and recovery must be verified before any risky change.
3. Fair subscriptions
Use the planned 30-day trial and clear renewal rules. After expiry and the agreed grace period, restrict transactions to read-only while retaining records; never delete data just because payment is late.
4. Separate permissions
Founder, support staff, business owner, manager and cashier must have distinct least-privilege permissions enforced by the server, not only by buttons in the browser.
5. Account and shop isolation
Each account can access only its authorized businesses. Database policies must enforce ownership and prevent one shop from seeing another shop's data.
6. Security and accountability
Protect privileged accounts with strong authentication and MFA where supported. Log privileged actions; keep audit logs tamper-resistant and avoid logging passwords or secrets.
7. Controlled releases
Build and test separately, test success and failure paths, verify on both phones, then seek explicit approval before release. Stable v6.2 must not be changed by this prototype.
8. Honest reporting
Show only metrics actually supplied by a trusted backend. Label unavailable or unverified information clearly; never invent business counts, revenue or system health.
Next implementation stage
Connect this screen to a dedicated, protected platform registry and server-side founder role. Keep it separate from each shop's ordinary business data. Until then, this screen is design/testing only.