Features
Four modules deliver core capability. Eight platform features keep everything trustworthy, fast and compliant.
Four modules · one platform
Each module ships fully wired to the others. Sell an Ube Halo-Halo at the front and CIMS deducts ube paste from the commissary — automatically.
CIMS
Recipe-aware ingredient deduction.
POS+
Touch-optimized POS with BIR receipts.
ETAS
Shifts, attendance, leaves and payroll.
FMS
Applications, branches and royalties.
Expo React Native on iOS + Android. Touch-optimized POS, kitchen display, offline queue.
Next.js dashboard for HQ admins, managers and accountants. Real-time updates via Socket.IO.
Receipt sequence + Grand Total monotonicity + Z-Reading immutability enforced at the database.
Every transaction, void, void-reason and operator captured. Immutable. Queryable.
X / Z Readings, Profit & Loss, royalty statements, sales by item, sales by cashier — exportable.
Low-stock warnings, late clock-ins, void thresholds, royalty due — push to phone + dashboard.
Tenant isolation via Postgres RLS. Encrypted secrets. Retention policies configurable.
HQ_ADMIN · HQ_MANAGER · BRANCH_MANAGER · CASHIER · COMMISSARY_STAFF — granular permissions.
Offline-first sync
Filipino retail reality: the internet drops. Kusina was designed offline-first from day one — your branches never stop transacting, and reconciliation is automatic when the network returns.
The branch tablet is online. Cashiers transact and HQ sees every receipt within milliseconds. Receipt numbers are assigned live by the server.
Internet goes down — rural area, brownout, ISP outage. The branch app detects the drop and routes every operation to the local SQLite queue instead of the network.
Each transaction is queued locally with a clientId UUID for idempotency. Customers receive a provisional receipt clearly marked PROV. Stock deducts locally so kitchen runs uninterrupted.
Network restored. The SyncFacade batches the queue and POSTs to /v1/sync. Each op carries its clientId — duplicates are de-duplicated, retries are safe. The server allocates official sequential receipts and returns the mapping. Customer-facing reprints are available.
Every operation carries a UUID generated client-side. Re-sending the same op produces no duplicate row.
BIR sequence is owned by the server, not the device. Provisional numbers are local-only and replaced on sync.
recordedAt (when sold) and syncedAt (when posted) are stored. Reports use recordedAt — sales attribute to the right day.
BIR Accreditation
Three BIR invariants are enforced by Postgres CHECK constraints and triggers — not by application code that could have bugs.
Receipts allocated per-branch with database row-locks — no gaps even under 60 concurrent transactions.
Z-Reading rows are blocked from UPDATE/DELETE by a database trigger. Once the day closes, it stays closed.
Grand Total Accumulator only increases. Voids reverse stock but never decrease the accumulator — BIR requirement.
Every transaction, void, void-reason and operator is logged with a tamper-evident audit log.
Book a 30-minute walkthrough. We will demo the modules that match your operation and quote a setup plan.
