Dashboard

What it does: Pulls transaction data from the Olsera POS system for the selected date range across all configured stores. Fetches order details, payment methods, line items, customer data, and loyalty points. Runs on the server (Cloud Function) so you can close the browser during sync.

Sync Orders: Incrementally syncs new orders only (skips already-synced order IDs). Splits into weekly chunks per store — each gets the full server time budget.

Force checkbox: Bypasses the sync index and re-fetches ALL orders in the date range, including ones already synced. Use when order details are incomplete (e.g. after a budget timeout) or data looks wrong.

When to use: Run at month-end to capture all transactions. Set dates to the full month. After sync, check the dashboard to verify totals match Olsera.

Warning: Large date ranges with Force enabled will re-fetch all orders and may take 30-60 minutes due to Olsera API rate limits (429 throttling). Do not run Force unless needed.

What it does: Applies payment correction rules to transactions in the selected date range. Two rule types are available:

Apply Rules: Opens a confirmation modal showing which rules will run. Points Burn reclassifies loyalty redemptions as free cups and deducts the drink value from cash expected. Delivery Override reclassifies EDC/transfer payments as GoFood/Grab/Shopee when the order source indicates delivery. Rules are configured on the API & Connections page.

Rollback: Reverts all rule-applied adjustments in the date range back to original Olsera values. Use if rules were applied incorrectly or rules have been updated and need re-applying.

Warning: Apply Rules modifies transaction payment methods and amounts. Always run after Olsera sync (Step 1) and before Cash Reconciliation (Step 5). Rollback will undo all adjustments — you must re-apply rules after rolling back.

What it does: Manages the cloud backup of all local data tables to Google Cloud Firestore.

Audit Data: Read-only check — scans all tables and shows which are in Firestore, their last updated time (WIB), and flags any that are stale (>24h for frequently-updated tables). Does not modify anything.

Force Sync All: Writes ALL local data tables to Firestore via REST API. Large tables are automatically chunked. Essential before switching computers or after major data changes.

Cleanup Legacy Docs: One-time maintenance — deletes orphaned short-name documents from Firestore left over from the old dual-namespace system. Only needs to be run once.

Warning: Force Sync overwrites Firestore with local data. If another user has made changes on a different device, their changes will be overwritten. Cleanup Legacy Docs permanently deletes old documents — run Audit first to verify data is healthy.

What it does: Syncs financial data from Xero accounting. Three actions available:

Sync Chart of Accounts: Pulls all account codes and names from Xero. Maps them to P&L sections (revenue, COGS, OpEx) for reporting. Only needed when new accounts are added in Xero.

Sync Bank Transactions: Pulls all bank deposits from Xero. These are matched against pending cash settlements in Step 5. Must be run before cash reconciliation.

Pull P&L: Pulls the profit and loss report for the selected date range. If the range spans multiple months, automatically splits into individual monthly pulls and stores each separately. Used for the P&L page.

Warning: Xero token refreshes automatically. If sync fails with an auth error, go to API & Connections and re-connect to Xero. P&L data overwrites existing data for the selected months — ensure Xero entries are finalised before pulling.

What it does: Matches pending cash settlements (from Olsera transactions) against bank deposits (from Xero) to confirm that cash was received.

Auto-Reconcile Matched: Scans all pending settlements and finds high-confidence matches — same amount within 0-5 days. Matched items are automatically marked as "confirmed". Ambiguous matches (multiple candidates, >5 day gap) are flagged for manual review on the Cash Management page.

Rollback: Reverts auto-reconciled settlements in the selected date range back to "pending". Use if reconciliation was run with incorrect or incomplete Xero bank data and needs to be re-done.

Warning: Run Steps 1, 2, and 4 (Sync Bank Transactions) BEFORE reconciling. Auto-reconcile marks settlements as confirmed — once confirmed, they are protected from overwrites. Rollback date range must be set to target only the period you want to undo.

Xero Data Sync

If Firestore data was accidentally reset to defaults, use this button on the device that still has your correct data to push it back to the cloud.