wiki/nutapos-android-flows.md

Nutapos Android Flows

Summary: Consolidates the main Android-side operational workflows in Nutapos, from registration and outlet opening to cashiering, inventory actions, finance, reporting, and synchronization.

Sources:

Last updated: 2026-04-17

---

The Android app is the operational surface for outlet activity. The source describes detailed flows for onboarding, cashiering, products, purchasing, stock adjustment, finance, reporting, settings, login, profile, and synchronization (source: data-source.md).

Onboarding and account linkage

The Android app supports both first-time registration and login using an existing cloud account. Registration requires company, outlet, address, username, password, email, and phone number, followed by SMS and email verification. After successful verification, the system automatically logs into the default Admin app user (source: data-source.md).

Existing cloud users can also log in from the Android app by entering company name, username, password, and selecting or creating an outlet. During login, data is downloaded from cloud storage to Android SQLite, after which the app again logs in as the default Admin app user (source: data-source.md).

Outlet lifecycle

After registration or login, the app user must perform buka outlet before operating the cashier. Opening an outlet includes entering initial cash or confirming cash remaining from the previous shift. After saving, the app enters the cashier screen (source: data-source.md).

The close cycle is handled through tutup outlet, where the app shows shift totals, drawer values, differences between actual and system cash, and optionally prints a close summary. After saving or saving and printing, the app user is automatically logged out (source: data-source.md).

See also outlet-and-access-management.

Cashier flow

The cashier flow is one of the most detailed areas in the source. Core behaviors include:

  • product selection into a receipt/cart area (source: data-source.md)
  • customer selection and management (source: data-source.md)
  • table handling when enabled (source: data-source.md)
  • support for product variants and extra choices (source: data-source.md)
  • search and barcode scan support (source: data-source.md)
  • edit operations at line-item and total level, including discount and tax handling (source: data-source.md)
  • save order, down payment, floating unpaid-order handling, split bills, and final payment flows (source: data-source.md)
  • printer integration for cashier, kitchen, and bar outputs (source: data-source.md)

The document also describes total and subtotal rules in detail, including modifiers, markup, discount handling, tax inclusion/exclusion, and special handling for online-driver sales types (source: data-source.md).

Product and item input

From the Android app, users can create and edit products or stock items with fields such as name, photo, prices, unit, barcode, category, variants, ingredients, and extra choices depending on enabled modules. The source also ties product setup to kitchen/bar print routing, stock ingredient composition, and optional linking of extra choices to stock ingredients (source: data-source.md).

Sales history and financial entries

The app provides sales history with date filtering, reprint, edit, and delete capabilities when permissions allow (source: data-source.md).

Separate Android flows also exist for:

  • uang masuk, including account selection and income classification (source: data-source.md)
  • uang keluar, including account selection and expense classification (source: data-source.md)

Purchasing and stock adjustment

If purchasing and stock modules are enabled, the Android app supports:

  • purchase history and purchase creation/editing (source: data-source.md)
  • supplier selection and management (source: data-source.md)
  • item-level purchasing with editable quantity and purchase price (source: data-source.md)
  • stock adjustment against stock-type items only (source: data-source.md)

These flows connect directly to inventory-and-purchasing.

Reporting and settings

The Android app includes reports for sales, category sales, stock, payment recap, cash or account balances, and sales type summaries. These reports rely on web service data and include period filters (source: data-source.md).

The settings section includes printer configuration, module toggles, tax, discount, table, payment-type, sales-type, user-access, and data-copy settings (source: data-source.md).

Login, profile, and sync

App-user login and logout are distinct from cloud-user linkage. Logging out does not disconnect the outlet from the linked cloud account. App users log back in with app-level usernames and passwords, and can recover passwords by email (source: data-source.md).

Profile management supports app-user email and password changes (source: data-source.md).

Synchronization runs automatically in the background after cloud registration/login, syncs changes to Nutacloud web services, forwards multi-device updates through Firebase where needed, and pulls data from the server when needed (source: data-source.md).

Related pages