01
Daily ledger
Record sales, expenses, supplier purchases, corrections, cash, bank and mobile-money activity in one structured operating view.
Biloo MezgebBiloo financial operations
Mezgeb · መዝገብBiloo Mezgeb.Every birr, clearly recorded.
A mobile-first business ledger for Ethiopian operators—bringing sales, expenses, Dube customer credit, receipts, payment channels, inventory and reporting into one professional Biloo workspace.
Connected foundation
AuthSupabase SSR
DataRLS-isolated
CurrencyETB-first
InterfaceMobile-first
Professional daily records
Built around Ethiopian business reality.
Biloo Mezgeb keeps the familiar product purpose—sales, expenses, Dube, receipts and operational clarity—while introducing Biloo’s Midnight Graphite, Royal Sapphire Blue and Ivory White identity.
The migration preserves the existing Supabase authentication and data foundation. It changes product ownership, interface branding, navigation and deployment source without renaming database tables or breaking existing account relationships.
Platform capabilities
One business record from opening time to closing balance.
02
Dube customer credit
Track customer balances, repayments, overdue credit and settled accounts without relying on paper notes or memory.
Biloo Mezgeb03
Receipts and VAT
Prepare numbered receipts with VAT-aware totals and keep the payment channel connected to the underlying sale.
Biloo Mezgeb04
Reports and performance
Review sales, spending, profit direction, category movement and VAT position from the same business record.
Biloo Mezgeb05
Inventory and operations
Organize products, operational records and daily workflows in a mobile-first workspace designed for Ethiopian businesses.
Biloo Mezgeb06
Secure business accounts
Use Supabase authentication, protected owner workspaces and Row Level Security across the existing Mezgeb data namespace.
Biloo MezgebContinuity without data migration
Existing accounts and data stay connected.
The Biloo migration preserves technical identifiers that existing users, authentication sessions and database policies already rely on.
1
Existing Supabase project and mezgeb_* database tables remain unchanged
2
Existing user accounts, email confirmation and password recovery remain connected
3
Existing Vercel project remains the production deployment target
4
Authentication callback routes and environment-variable contracts are preserved
5
The original MezgebOfficial repository remains available as the migration source snapshot
6
Biloo Mezgeb is maintained from the Biloo monorepo after cutover
Production integrity
Authentication and business onboarding are live; transaction persistence remains staged.
Supabase authentication, protected dashboards and business workspaces are connected. The inherited `/app` transaction screens still contain browser-local prototype storage for selected ledger, Dube, receipt, inventory and reporting workflows. Those screens should use sample data until their existing Mezgeb tables are fully connected.