Built for Filipino food businesses

The kitchen brain for multi-branch Filipino food businesses.

Quesina PH runs your commissary, POS, attendance and franchise royalties in one BIR-accredited platform — even when the internet drops.

BIR-accredited
POS + Z-Reading
Offline-first
Sells without WiFi
Multi-tenant
HQ + N branches
HQ Dashboard · today

Gross sales today

₱48,250

▲ 12.4% vs yesterday

Receipt #482

Cash · 14:32

₱185.00

Receipt #481

GCash · 14:28

₱412.00

Receipt #480

Cash · 14:24

₱267.50

Receipt #479

Bank · 14:20

₱1,205.00

Live · Ube ingredient running low at LR-MNL-001. Reorder triggered.

Built with — and battle-tested by — Filipino food operators

Lucia's Recipe

Founding partner

Tindahan Co.

Pilot

Halo Café

Pilot

Adobo House

Pilot

Bibingka Bros.

Pilot

Four modules · one platform

Everything a multi-branch food business needs.

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

Commissary Inventory

Recipe-aware ingredient deduction.

  • Multi-unit conversions (kg ↔ g, L ↔ mL)
  • Stock movements: receipts, production, spoilage, transfers
  • Auto-deducts ingredients when a recipe-linked item sells
  • Reorder alerts + supplier price history

POS+

Point of Sale (BIR)

Touch-optimized POS with BIR receipts.

  • Sequential per-branch receipt numbers (zero gaps)
  • Senior / PWD / Promo / Manual discounts
  • Cash · GCash · Bank · Charge-to-account payments
  • X-Reading anytime · Z-Reading closes the day

ETAS

Employee Time & Attendance

Shifts, attendance, leaves and payroll.

  • QR / PIN / biometric clock-in
  • Late detection + overtime accrual
  • Leave requests + manager approval flow
  • SSS / PhilHealth / Pag-IBIG payroll-ready exports

FMS

Franchise Management

Applications, branches and royalties.

  • Application Kanban: lead → vetting → contract → open
  • Royalty statements auto-generated per branch per month
  • Promo + menu rollouts targeted by branch
  • HQ rollup of every branch in real time

The transaction lifecycle

One tap. Six BIR-clean operations.

Every sale flows through these six stages — all inside one atomic database transaction. If anything fails, the whole thing rolls back: no half-deducted ingredients, no orphan receipts, no gap in the sequence.

  1. 01

    Customer orders

    Cashier taps menu items on the touch-optimized POS. Cart updates instantly with running subtotal.

    Mobile (tablet) or web · 44 px touch targets · category filter + SKU search

  2. 02

    Discount + payment

    Apply Senior / PWD / Promo / Manual discount. Choose Cash, GCash, Bank transfer, or Charge-to-account.

    Senior · PWD require OSCA / PWD ID for audit · 20% off computed server-side

  3. 03

    BIR receipt number allocated

    BIR-critical

    Backend takes a row-lock on the per-branch counter and assigns the next sequential number — zero gaps even under 60 concurrent transactions.

    SELECT … FOR UPDATE inside prisma.withTenant transaction

  4. 04

    Ingredients deduct

    Recipe components multiply by quantity. Ube paste, condensed milk, sugar — each draws down in the commissary in the same transaction.

    Atomic with the receipt insert · insufficient stock → CONFLICT, full rollback

  5. 05

    Grand Total Accumulator increments

    BIR-critical

    The branch running total goes up by the transaction amount. Monotonic — voids reverse stock but never lower the accumulator.

    Database CHECK + trigger enforce monotonicity — application bugs cannot violate it

  6. 06

    HQ dashboard updates live

    Socket.IO broadcasts pos.transaction.created to the tenant room. HQ sees the receipt within milliseconds.

    Receipt prints locally · audit log records cashier, branch, recipe, payment

Offline-first sync

Patchy WiFi? Brownout? You still sell.

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.

  1. Phase 1 · Online

    Every operation syncs in real time

    The branch tablet is online. Cashiers transact and HQ sees every receipt within milliseconds. Receipt numbers are assigned live by the server.

    Sync latency
    ~120 ms
    Receipt #
    Server-assigned
    HQ visibility
    Live
  2. Phase 2 · Network drops

    SyncFacade flips to offline mode

    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.

    Sells
    Continues
    Queue
    expo-sqlite
    Detection
    <2 s
  3. Phase 3 · Provisional receipts

    Cashiers keep selling with PROV-### numbers

    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.

    Local cap
    10,000+ txns
    Provisional #
    PROV-001…
    Cashier UX
    No change
  4. Phase 4 · Reconciled

    Server assigns official BIR numbers

    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.

    Idempotent
    clientId UUID
    Mapping
    PROV → BIR #
    Audit
    recordedAt + syncedAt

Three rules that keep sync safe

1

Idempotent by client ID

Every operation carries a UUID generated client-side. Re-sending the same op produces no duplicate row.

2

Server allocates receipt numbers

BIR sequence is owned by the server, not the device. Provisional numbers are local-only and replaced on sync.

3

Audit preserves both timestamps

recordedAt (when sold) and syncedAt (when posted) are stored. Reports use recordedAt — sales attribute to the right day.

BIR Accreditation

Compliance baked in at the database layer

Three BIR invariants are enforced by Postgres CHECK constraints and triggers — not by application code that could have bugs.

Sequential receipt numbers

Receipts allocated per-branch with database row-locks — no gaps even under 60 concurrent transactions.

Immutable Z-Readings

Z-Reading rows are blocked from UPDATE/DELETE by a database trigger. Once the day closes, it stays closed.

Monotonic Grand Total

Grand Total Accumulator only increases. Voids reverse stock but never decrease the accumulator — BIR requirement.

Full audit trail

Every transaction, void, void-reason and operator is logged with a tamper-evident audit log.

Branch app

Run the floor from any tablet.

The Quesina PH Branch app turns any Android tablet into a BIR-clean POS, time-clock and inventory station — fully offline until the internet comes back.

v0.1.0 · 98 MB · Android 8.0 (Oreo)+ · Updated 2026-06-02

  • Offline-first POS

    Queue receipts locally, sync the moment connectivity returns.

  • BIR-clean receipts

    Sequential, gap-free receipt numbers and an immutable Z-Reading.

  • Time clock & attendance

    Face capture, payroll-ready logs, no manual edits.

  • Cash drawer + Z-Reading

    Open, count, close — all from the cashier tablet.

  • iOS — coming soon. Reach out if your branches use iPad.

Pricing

Subscription + one-time setup. No hidden fees.

Setup is ₱20,000 per branch / franchisee — includes a 10" tablet, 80mm thermal receipt printer, on-site data setup, and cashier training. Devices are yours to keep. Subscriptions are month-to-month — cancel anytime.

Already have a tablet and receipt printer? Software-only setup is ₱8,000 per branch.

Starter

Single branch with a commissary.

₱2,500/ month

+ ₱20,000 one-time setup

Best for

Solo café · single-branch eatery

  • 1 branch · 5 user accounts
  • POS+ with BIR-compliant receipts
  • CIMS with recipe deduction
  • ETAS attendance (manual + QR)
  • Offline-first mobile + web POS
  • Email support
Get started
Most popular

Growth

For the 2nd to 9th branch.

₱6,500/ month

+ ₱20,000 × branches one-time setup

Best for

Multi-branch operator · expanding chain

  • Up to 9 branches · 25 user accounts
  • Everything in Starter
  • Full FMS (royalties + applications)
  • Promo + menu rollouts by branch
  • X / Z Readings + Profit & Loss
  • Priority support (8h SLA)
Get started

Franchise

Unlimited branches, white-glove.

₱18,000/ month

+ ₱20,000 × locations one-time setup

Best for

Franchisor with 10+ outlets

  • Unlimited branches · unlimited users
  • Everything in Growth
  • Dedicated Customer Success Manager
  • Custom royalty rules per branch
  • API access · SSO · white-label receipts
  • 24×7 incident response
Get started

Need on-prem or custom integrations? Talk to sales →

FAQ

Questions operators ask before signing.

Is Quesina PH BIR-accredited?
Yes. POS+ ships BIR-compliant — sequential receipt numbers, immutable Z-Readings, and a monotonically increasing Grand Total Accumulator are enforced at the database layer (CHECK constraints + triggers), not just in application code.
What happens when the internet goes down?
The branch mobile app and the web POS both queue operations locally (expo-sqlite on mobile). Cashiers keep selling and customers get provisional receipts. When the network returns, the SyncFacade batches the queue and the server assigns official BIR receipt numbers. Each op has a client-side UUID so duplicate sends are safe.
How long does onboarding take?
A single-branch Starter is typically operating within 5 business days from contract: data import (1–2 days), staff training (1 day), BIR paperwork (parallel), go-live with one-on-one support (1 day). Franchise deployments scale with branch count.
Can it run on the hardware I already have?
Yes if the tablets are Android 10+ or iPad iOS 15+, and your printer is ESC/POS compatible (most thermal receipt printers are). We provide a compatibility check during the setup engagement and recommend hardware add-ons if needed.
How do royalty statements work?
FMS computes royalties monthly per branch using either a flat percentage of net sales or a tiered formula. Statements are auto-generated, reviewed at HQ, and sent to franchisees with a one-click PDF export. Voids and senior discounts are factored correctly.
Does payroll integrate with SSS / PhilHealth / Pag-IBIG?
ETAS produces payroll-ready exports that match standard PH government remittance schedules. Direct e-filing integrations are on the roadmap. Hourly + monthly + per-shift pay structures are supported.
Can we white-label the customer receipt and the franchisee dashboard?
On the Franchise tier, yes — logo, brand colors, and receipt header/footer text are customizable per tenant.
What if we outgrow the platform?
We export your entire data set on request: transactions, recipes, employees, royalties — in CSV and JSON. There is no lock-in. Most operators do not leave; the BIR + offline + multi-tenant combination is unusual in PH.

Ready to see Kusina in your branches?

Book a 30-minute walkthrough. We will demo the modules that match your operation and quote a setup plan.