Windows service for automated ATOL MarkUnit marking-code verification
Validate Chestny ZNAK marking codes through ATOL MarkUnit hardware and persist results in CouchDB using a background Windows service. fmu-api, produced by Automation for retail automation, runs as the ds-fmu-api-couchdb service and exposes an API for integration. The package includes an install.bat installer and a central monitor called Fmu-Api-Central. It targets retailers, developers, and system administrators who need programmatic verification of product markings in Russian retail workflows.
What does fmu-api check and how it connects to ATOL hardware?
fmu-api performs automated verification of product marking codes by communicating with the ATOL MarkUnit (MU) system, then records verification results to CouchDB. The tool acts as a bridge between point-of-sale or inventory systems and the MU device, exposing an API-driven interface for third-party software to request checks and receive status codes and stored records.
Does running the service affect workstation performance?
fmu-api runs as a lightweight background Windows service named ds-fmu-api-couchdb, which minimizes overhead on retail workstations according to the distributed service design. CouchDB handles persistence, so the service itself keeps operational state while delegating storage; this design keeps runtime activity focused on verification requests rather than heavy local data processing.
Is the application safe to deploy in a production environment?
The tool is designed with operational safety in mind: it installs via an automated script that requests elevation to create the system service, and data handling is explicit through CouchDB storage. The project is open source on GitHub, enabling inspection of how fiscal data is processed and logged, which supports auditability for compliance-sensitive deployments.
How much technical knowledge is required to operate and monitor it?
Technical setup and monitoring require system administration skills: installation uses the provided install.bat and creating the service needs privilege elevation; centralized oversight is available through the companion Fmu-Api-Central application. Developers can integrate verification calls via the API, so some programming and server management experience is necessary to deploy and maintain the service.
Clear fit for technically staffed retailers, with one operational caveat
fmu-api suits retailers and integrators who need automated, auditable checks of Chestny ZNAK markings and can run a CouchDB-backed Windows service. The open-source repository supports transparency and integration work. The main caveat is that deployment and monitoring assume in-house technical skills for service management and API integration, so nontechnical staff will need assistance to operate it reliably.
