Overview

                    LAKUYO DOCS          LAKUYO CONTROL PLANE
                 Product narrative    Specs + Contracts + Status
                          │                      │
                          └──────────┬───────────┘
                                     │
              ┌──────────┬───────────┼───────────┬──────────┐
              ▼          ▼           ▼           ▼          ▼
          Backend    Android       iOS       macOS     Windows
                          │           │           │          │
                     Local SQLite Local SQLite Local SQLite Local SQLite
                          │           │           │          │
              ┌───────────┴───────────┴───────────┴──────────┘
              │                                              │
              ▼                                              ▼
      Personal Cloud Backup                      optional Pro services
    Google Drive (all clients)                        Lakuyo Cloud
   (merchant-owned storage)                    (subscription / backend)

At the product/domain level, Lakuyo has two first-class core domains in Phase 1 (founder-agreed architecture, 31 Aug 2026):

Lakuyo
├── POS
│   ├── Cart
│   ├── Checkout
│   ├── Payment
│   ├── Receipt
│   └── Sale / transaction history
│
├── Inventory
│   ├── Product catalogue
│   ├── Stock quantity
│   ├── Receiving / adjustment
│   └── Stock movement history
│
└── Customer membership (Phase 3, POS-024)
    ├── Member registry
    ├── Member vs walk-in pricing
    ├── Admin membership discounts
    └── Member purchase history
 
Order Management
→ separate domain
→ expands later
→ Order ≠ Sale

Order Management is intentionally outside the Phase 1 Lakuyo tree above: a separate domain that expands later for customer Orders, tables, waiter/Sales order-taking, and fulfilment. An Order exists before checkout; a Sale is the completed commercial transaction. See Product/Domain Terminology.

Customer membership (POS-024, Phase 3) is a merchant-run store membership program — member vs walk-in pricing, admin-configurable discounts, and purchase history scoped to registered members only. It is not Lakuyo Pro subscription and not gym/class membership apps.

Core POS + Inventory (Phase 1) runs fully offline on one active operational device. Two optional networked capabilities have deliberately different boundaries:

• POS-008 Personal Cloud Backup (Drive Backup) — merchant-owned Google Drive on Android, iOS, macOS, and Windows; backup/restore only, ≈ Rp100.000 one-time unlock or active-Pro inclusion, no Lakuyo backend, no multi-device sync.
• Pro Lakuyo Cloud — Lakuyo-operated backend for subscription features such as coordinated multi-device sync and Lakuyo cloud backup.

Personal Cloud Backup uses a versioned Lakuyo backup format on Google Drive for both platforms (SQLite data + product images and related payload). Automatic backup is enabled by default after Google Drive authorization for entitled users.

To protect against competing writers without adding backend DRM, Personal Cloud Backup maintains backup lineage and one active cloud-backup writer per lineage in Google Drive metadata. Restoring on another installation explicitly transfers writer ownership; the previous installation remains usable locally but cannot silently overwrite that lineage until ownership is reclaimed.

Personal Cloud Backup must never become an implicit sync transport. Core operation remains local even when Google Drive authorization or connectivity is unavailable.

Detail: control-plane architecture · thermal printing (POS-023) · Architecture/Offline First · Product/Plans and Entitlements.