EvoShop support

Installation and access

Open the web administration platform at the address supplied for your business. For desktop or mobile applications, ask your administrator or EvoShop support for the authorized installation and access method. Installing an app does not create a business account or server.

Application availability and installation method depend on the platform, the authorized distribution channel and the arrangements for your EvoShop installation. Use only a store listing or direct installer supplied or approved for your business.

If installation or an update fails, note the operating system, app version and displayed error. Do not uninstall or clear local data while transactions are waiting for synchronization.

Connection and login

For the web platform, use your installation’s browser address and account. For an application, enter the configured EvoShop HTTPS server address and use the sign-in method enabled for that client. Paired POS access and cashier methods apply only where supported.

If a session expires, reconnect and sign in again with the relevant cashier account. Contact your administrator for password, PIN or permission problems; never send these credentials to support.

Device pairing

This guidance applies to POS applications that support this workflow; it does not imply that every platform has identical capabilities.

An authorized administrator supplies a pairing code for the intended installation. Enter it in the POS and give the device a recognizable name. Cashier access and any bracelet login must be configured by the administrator.

If pairing is rejected or revoked, ask the administrator to check the device's authorization. Resolve queued sales before replacing a pairing. Keep pairing codes and bracelet credentials private.

Offline operation and pending sales

This guidance applies to POS applications that support this workflow; it does not imply that every platform has identical capabilities.

Previously loaded data can support checkout during a connection interruption. Some actions still need the server; an initial connection and usable session are necessary. An offline receipt marks the sale as awaiting synchronization.

Reconnect to the same installation and use the synchronization queue to check pending or rejected sales. If asked, sign in again as the original cashier on the relevant device. Automatic retries and the manual synchronization action send pending sales when access is available.

Do not enter the same sale again just because confirmation is uncertain. A rejected item can block later items. Keep the original device and records intact and ask your administrator or support to review the displayed error.

Receipts and printing

Printing depends on the platform, application and connected equipment. For Windows POS, check that Windows recognizes the printer, select it in POS settings, choose the matching paper width and run a test print if permitted. Ask support about the printing workflow for other devices.

An offline receipt is provisional. Synchronization does not automatically print another receipt. Use the official sale history to reprint a confirmed transaction when authorized, and check whether a ticket already printed before trying again.

Getting the right help

For account access, server settings, device authorization or business records, start with your installation administrator. Use the contact form or the support details below for product assistance. Select a general inquiry and describe what happened.

Include your business name, platform and operating-system version, application version, the action attempted, time of the issue and displayed error. Where available, the POS information screen helps identify the installation and device. Share only necessary details; remove customer information from screenshots and never send passwords, PINs, pairing codes or tokens.

For privacy questions or the conditions of use, see the links below. Support availability and scope follow the arrangements for your installation.