Find the right evidence before changing configuration or code.
Reviewed 12 July 2026
Check lighting, screen brightness, the full code, camera permission, HTTPS, and the scanner keyboard layout. Staff can use a phone camera, fixed 2D reader, customer search, or a known member code as the documented fallback.
Use the staff scanning guide for the complete decision path.
Check the configured mail service, sender identity, credentials, domain authentication, queue or scheduled work where relevant, application logs, provider response, spam placement, and the member’s email preferences for the message type.
Start with email configuration and the health center.
Stop repeated production attempts. Preserve the error and logs, confirm the backup, review requirements and release notes, reproduce the update on staging, and check custom source changes and file permissions.
Use the updating guide and report suspected software errors with the license key, release, environment details, exact error, and steps already tried. Your host or developer handles server setup and custom code; see the support scope.