Diagnose safely without damaging the trading record.

Readiness check

Record the StamPOS version, Windows version, free storage, database status, printer availability, payment connection, network state and backup result. Resolve critical warnings before the terminal enters service.

Diagnostic evidence

Capture exact error wording, timestamps, operator actions and the affected transaction or workflow. Export only the logs needed for the investigation and review them for personal information, credentials or payment-sensitive data before sharing.

Database maintenance

Perform optimisation, repair or migration only through supported StamPOS tools and only after creating a verified backup. Do not directly edit production database files unless following a documented recovery procedure.

Payment incidents

Preserve the StamPOS transaction reference, Linkly/provider reference, terminal identity, amount and displayed status. Resolve an unknown outcome before permitting another attempt for the same sale.

Printer faults

Separate Windows driver problems, network reachability, paper/cutter issues and StamPOS configuration. Confirm printing with a sample receipt that exercises the same path used by the application.

Reset and rebuild

A reset is a last resort. Confirm what will be deleted, export required records, verify backups and obtain approval from the responsible business representative. After rebuilding, repeat the full readiness and reconciliation checks.

Escalation package

Include the build number, device and hardware details, issue severity, reproduction steps, expected and actual results, logs and business impact. State whether trade can continue safely and whether money, data integrity or security may be affected.