Skip to main content

Troubleshoot the counter safely

Preserve the last confirmed state before retrying an action. A timeout or blank screen does not prove that a sale, refund, shift close, or stock operation failed.

First response​

  1. Read and retain the visible error without capturing customer data or credentials.
  2. Note the current employee, location, device, time, and operation.
  3. Check whether the action appears in history before submitting again.
  4. Use refresh or the product’s retry control once the existing state is understood.
  5. Escalate with a record identifier, not a screenshot containing sensitive data.

Sign-in or wrong-counter problem​

  • Confirm the employee account is active.
  • On PIN login, choose the intended permitted location.
  • On Owner/Manager login, read the resolved-counter confirmation before continuing.
  • If the location is not available, ask an authorized person to review employee assignments.
  • Do not borrow another person’s account.

Network or synchronization problem​

Android surfaces can show queued or failed work in Sync center where supported. Keep the device signed in, restore a stable network, and inspect each queued item. Resolve a permanent validation or permission error instead of retrying it indefinitely.

flowchart TD
  A[Action did not confirm] --> B{Visible in history?}
  B -->|Yes| C[Do not resubmit]
  B -->|No| D{Queued in Sync center?}
  D -->|Yes| E[Restore network and inspect queue]
  D -->|No| F[Refresh once and retry carefully]
  E --> G{Permanent error?}
  G -->|Yes| H[Correct input or permission]
  G -->|No| I[Allow supported retry]

Checkout or refund timed out​

Search invoice or sales history using the time, customer, and total before attempting the transaction again. If a record exists, open it and continue from its recorded state. Separately confirm external payment status; Nox Billings does not infer settlement from a network timeout.

Printer problem​

  1. Confirm the receipt exists digitally.
  2. On Android, check Bluetooth permission, printer power, pairing state, and the default printer profile.
  3. Keep the printer nearby and ensure it is not actively paired to another device.
  4. Retry printing the existing receipt; do not recreate the sale to obtain paper.

Data or permission problem​

  • Confirm the selected location and role.
  • Reload the underlying record.
  • Check whether another manager completed or changed the operation.
  • Use the audit surface when available.
  • Never edit local storage, database rows, or generated identifiers to bypass the product.

What to include in escalation​

  • product surface and app version;
  • web URL path or Android screen name, without query data;
  • approximate time and timezone;
  • role and location, without credentials;
  • safe record identifier;
  • exact error text;
  • whether the action appears in history or Sync center;
  • steps already attempted.

Expected result​

The operator determines whether the action was recorded, avoids duplicate work, and provides enough redacted evidence for an authorized reviewer to continue.