Date	Transfer	Item	Qty	Location

Date	Event	Closed By	Returned To	Action

• Add products from the POS grid.
• Choose payment method: Cash, GCash, or Not Paid.
• Cash sales require amount received and show change.
• Not Paid sales require payment notes and customer details.
• Sales deduct recipe/inventory stock from the selected location.
• Custom sale date/time is restricted to Manager, Owner, Power User, or backdate_sale permission.
• Sales can save offline and sync later when online.

• Use Sales History to review completed sales.
• Online badge means the sale exists in Supabase.
• Failed/Pending means the sale is saved locally and still needs sync.
• Use Sync Pending if internet dropped or Supabase session was unavailable.
• Refund/void actions should be done by authorised staff only.

• Inventory List tracks items, stock, unit, type, cost, and low-stock level.
• Stock In adds inventory with reason/location.
• Stock Out deducts inventory and requires authorised reasons.
• Transfers move stock between locations without creating/destroying stock.
• Daily Inventory is used for physical count and variance checks.
• Low-stock warnings are allowed but should be reviewed daily.

• Products are POS menu items with category, price, status, emoji/image, and sauce settings.
• Recipes connect products to inventory deductions.
• Sauces/options can be linked to inventory items and quantities.
• Hiding a product/sauce removes it from daily use without deleting history.
• Power User setup changes auto-sync online when connected.
• Other approved devices auto-load shared setup updates.

• Use Better Inventory, Products, and Recipes templates from Settings.
• Import order: Inventory → Products → Recipes.
• Inventory type is case-insensitive: Packaging, packaging, and PACKAGING all work.
• Product, inventory, and location matching is case-insensitive.
• Preview imports before applying.
• After import, setup changes auto-sync online for Power User when connected.

• Every location requires a unique sale prefix.
• Sale numbers use location prefix, for example MAIN-000001 or BAZ1-000001.
• Use locations for Main Store, events, storage, and in-transit stock.
• Event devices should be approved as Event or POS devices.
• Stock transfers should be used before and after events.

• Staff use PIN login.
• Permissions control visible pages and allowed actions.
• Attendance can be restricted to approved attendance/store/POS devices.
• Staff Pay tracks attendance, adjustments, cash advances, bonuses, and payroll checks.
• Managers/owners should review overtime and unusual attendance records.

• Only approved devices can use the app.
• New device opens Device Authorization screen and requests approval.
• Owner/Power User approves devices in Admin → Device Access.
• Device types: Owner, POS, Store, Event, Attendance.
• Staff should not time in/out from personal devices unless the device is approved for attendance.
• Device approval is separate from Supabase connection session. Staff access still uses PIN.

• Sales sync online automatically when Supabase session is connected.
• Offline sales stay local and sync later.
• Shared setup sync updates products, inventory, recipes, sauces, and locations across approved devices.
• Sync Pending pushes unsynced sales/actions.
• Sync Shared Setup refreshes setup data manually.
• Supabase cleanup SQL is used for controlled online test-data clearing.

• Export Full Backup File before resets/imports.
• Selective Reset/Test Cleanup is Power User only.
• Clear Products + Inventory Setup clears local products, inventory, recipes, and sauces before real import.
• Online test-data cleanup should be done carefully using the included Supabase SQL file.
• Do not clear online setup after real sales are already active unless you understand the impact.

• If device is blocked, request approval and ask owner to approve in Device Access.
• If Online says not logged in, Supabase connection session is not connected yet.
• If a sale is pending, use Sync Pending.
• If co-owner does not see products, use Sync Shared Setup or wait for auto-refresh.
• If mobile layout looks cramped, use landscape/tablet where possible while we continue polish.
• If import fails, check column names, numbers, and inventory type values.

Current Official App Version

v1.3.5

Apollo POS

POS • Inventory • Staff Management

Created by Erwin Pogi

New features should always be checked against permissions before release.

• Device Access: Power User only.
• App Info / Change Log: Owner, Manager, and Power User access.
• Setup push/sync actions: Power User only unless specifically allowed.
• Custom sale date/time: Manager, Owner, Power User, or backdate_sale permission.
• Cleanup/reset tools: Power User only.

Use this before real operation or after testing. Choose exactly what to reset. Requires typing RESET.

Open Selective Reset Tool Clear Products + Inventory Setup

Clears local products, inventory, recipes, sauces, and pending product/inventory setup data before real import.

Online Supabase test rows should be cleaned carefully from Supabase or with a future online cleanup tool.

App Name Current User Placeholder

Temporary only while there is no login yet. Later this will become real user/access tracking.

Upload Logo Upload Login Banner

The login banner appears on the full login page after logout. If blank, the app uses the black/orange default banner.

Save Branding

Export All Data Export Full Backup File

Export All Data downloads a full JSON backup plus readable CSV files for reports/spreadsheets. Full Backup JSON is still the safest restore file.

Import Full Backup File Import Full Backup Import Inventory CSV Preview Inventory Import Import Products CSV Preview Products Import Import Recipes CSV Preview Recipes Import

CSV exports are for viewing in Excel/Google Sheets. Templates help you format imports. Full Backup JSON is the safest restore file.

Current default location:

Main Store

Sales and stock movements now save location data. Later we can add Bazaar/Event locations and stock transfers.

Selective Reset Tool

Power User only. Choose exactly what test data to reset. Requires typing RESET.

Restore Starter Template

Power User only. Restores the starter template and replaces current local data.