Support

Troubleshoot Posnic and Protect Shop Data

When something goes wrong, preserve evidence first: version, operating system, screen, sale, device, log, backup and exact step.

Menu path
Support routine plus app logs and backup procedure
Verified from
Posnic demo and current POS source reviewed on 2026-09-08
Technical source evidence

POS app log locations, settings and device setup screens, backup and restore docs

Device setup evidenceCapture device settings and exact printer or scanner behavior before changing a live till.
Core settingsMany checkout issues come from settings, permissions or device-specific options.
Known starting pointAfter recovery, confirm dashboard, items, sales history and reports are present.

Collect Evidence Before Changing Anything

A live till issue becomes harder to solve when staff keep changing settings without recording the original problem.

  • Record Posnic version and operating system.
  • Write the exact screen and menu path.
  • Take a screenshot of the error or wrong result.
  • Record the sale bill number, item SKU/barcode, customer or payment method involved.
  • For hardware, record printer, scanner, drawer or scale model and connection type.
  • Copy the app log before reinstalling or clearing data.

Log Locations

PlatformLog pathUse
Windows%APPDATA%\posnic\app.logAttach when reporting crashes, startup failures, database issues or hardware errors.
macOS~/Library/Application Support/posnic/app.logAttach with version and OS information.
Linux~/.config/posnic/app.logAttach with distribution, package type and device details.

Backup Discipline

A local POS system gives the shop control, but the shop must protect its own data. A backup is useful only when it can be restored.

  1. Create a backup before live use, after setup changes and after day close.
  2. Copy at least one backup away from the till computer.
  3. Restore a backup on a clean installation before go-live.
  4. Check restored items, customers, sales, stock and reports.
  5. Keep a written owner for backup and restore decisions.

Common Problems

ProblemFirst checkDo next
Cannot log inUsername, password, role and correct local data folder.Use owner recovery process; do not delete data.
Sale screen cannot find itemItem name, SKU, Barcode and Track inventory settings.Edit item or create proper catalog record.
Barcode scanner failsDoes it type into the search field? Does Barcode match?Fix item barcode or scanner suffix/Enter behavior.
Printer failsManual print, Print Type, OS printer, cable/network.Fix printer path, then reprint from Sales History.
Stock is wrongInventory Logs, sales, returns, purchases and adjustments.Run a counted correction with owner approval.
Reports look wrongDate range, sale date changes, unpaid sales, payment labels and edits.Reconcile with Sales History and register close.

Related Manual Pages

Settings Receipt Printing Receipt settings control what prints after a sale and how staff can reprint it. Catalog SKU and Barcodes Make products scannable by giving each item a clean SKU/barcode setup, then print labels with the right label size and fields. Registers Daily Close A sale is not fully controlled until the register and payment totals are closed and explained. Inventory Stock Control Stock control starts when items are created and continues through every sale, return, purchase, adjustment and low-stock review. Reports Reports and Export Reports are the owner's review surface for sales, purchases, stock, customers, payments, tax and close evidence. Settings Employees and Roles Staff access starts with named employees, branch assignment, a role or custom matrix, POS action authority, and a review habit.