Retail accounting rollout: 7 common mistakes

Why store automation fails to launch: 7 mistakes that most often stop entrepreneurs

Retail automation is the transfer of inventory, financial and personnel accounting into a single system governed by common operating rules. This material is intended for store owners who have already purchased software or are only planning to do so and do not want to repeat other people’s mistakes. Below are seven scenarios in which implementation comes to a halt, along with specific actions that bring accounting into a workable state.

Most unsuccessful implementations have one thing in common. The software is installed, but the store’s way of working remains unchanged: data is not prepared, staff permissions are not separated, and procedures for administrative operations are not defined. Two or three months later, the owner sees discrepancies in stock balances and blames the software. In reality, the process has not yet been built at this stage.

What currently complicates the operation of a retail outlet

The conditions in which Ukrainian retail operates in 2026 make each of the mistakes described below more costly.

Add to this the constant losses experienced by retail outlets. According to estimates from the Global Sources of Shrinkage study cited by the Retail Association of Ukraine, global retail loses around 1.5 per cent of turnover due to administrative errors, employee theft, write-offs and external theft. The figure is higher in the grocery segment. When records are kept in spreadsheets and notebooks, these losses remain invisible until inventory is taken.

Problem 1. Starting without a demo version and with unverified data

These are two mistakes that almost always occur together. The first is purchasing the software without a trial period and testing business scenarios directly in the live database. The second is importing a supplier’s price list from Excel without cleaning it first. This results in duplicate barcodes, items without product categories and discrepancies in item numbers. Product records are duplicated, and cost price calculations become incorrect. When very large files are imported, the software may freeze or report insufficient memory.

Another aspect of the same problem is the attempt to use all functionality from the first day: multi-stage production, team-based payroll schemes, automatic supplier orders and in-depth financial analytics all at once. Staff do not have enough time to master the basic modes, resulting in resistance or chaotic data entry.

What to do

1. Use the 30-day demo version and test your own scenarios in it: goods receipt, sale, return and transfers between outlets.
2. Clean Excel spreadsheets before importing: remove duplicates, standardise names, and check item numbers and barcodes.
3. Split import files into sections of approximately 500 items to control the mapping of fields and characteristics.
4. Master the software step by step: first the product category tree and directories, then goods receipt and inventory to enter actual stock balances, and only after confident use of sales and returns — complex schemes, discounts and analytics.

Problem 2. Expecting accounting functionality from inventory software

Torgsoft is built around the income-and-expense logic of a real retail business. It does not contain accounting entries or a chart of accounts. Attempts to record purely financial transactions without linking them to products, account for construction projects or calculate the percentage of vegetable shrinkage in a storage warehouse create a methodological conflict and disappoint the owner.

The correct arrangement is different. Tax and statutory accounting are maintained separately. Torgsoft is responsible for accurate stock balances, personnel control, checkout fiscalisation, prices and real-time management decisions. Businesses in specialised sectors should test their scenarios in the demo version before purchasing licences.

Problem 3. Connecting online channels without preparing the catalogue

Expecting synchronisation with a website or marketplace to work automatically results in lost orders. Typical causes of failures include missing dynamic product characteristics required by the marketplace; synchronisation sections and product groups not being configured in the software; and an excessive volume of unused files accumulating on the website’s FTP server and blocking data exchange.

The correct order of actions is the reverse of what is commonly expected. First, characteristics, product groups and synchronisation sections are organised in Torgsoft, and only then is data uploaded to the platform.

What to do

• Complete the dynamic characteristics of products according to the requirements of the specific platform before starting the upload.
• Configure synchronisation sections and product groups in the software. Changes made on the website will not fix the data exchange.
• Periodically remove old photographs and unused files from the FTP server.
• Check that stock balances match after the first uploads until the data exchange becomes stable.

Problem 4. Starting automation with the software while ignoring equipment and power supply

A typical failure scenario looks like this. The software is installed on a touchscreen all-in-one computer with automatic Windows updates enabled. A week later, the system enters a restart loop. The receipt printer, label printer and scales are connected through a cheap passive USB hub without an external power supply, so they periodically lose connection. The outlet’s internet connection is unstable, and printing from a remote server through RDP stops halfway through a receipt.

Power outages create a separate group of problems. In January 2026, some retail chains in Kyiv and the surrounding region suspended operations because their checkout systems were not functioning, and customers were advised to carry cash. A store without backup power and the ability to sell offline simply cannot trade in such circumstances.

What to do

• Disable automatic Windows updates on touchscreen all-in-one computers and update the system manually outside business hours.
• Connect retail equipment through externally powered USB hubs. Passive hubs are unsuitable for printers and scales.
• Connect a payment terminal on a remote server via Wi-Fi. A standard COM port causes communication errors in this configuration.
• If the printer temporarily disappears from the RDP session, end the server connection session and reconnect.
• Provide the server and checkout workstation with an uninterruptible power supply and the outlet with a backup internet connection.

Problem 5. Sales staff have more permissions than they need to make sales

Excessive permissions cause accounting data to stop reflecting reality faster than technical failures do. If a salesperson can change wholesale and retail prices, profit data becomes unreliable. Without control, fictitious returns can be processed under someone else’s user account while cash is removed from the till. Another common scheme is manually entering a discount card number using the keyboard: the sale is made to an unrelated customer, while the discount benefit remains with the cashier.

In Torgsoft, permissions are separated under Settings — Users. Each user has an individual login, password and role that restricts access to functions and information. The mode without role restrictions is intended only for the owner or administrator.

What to do

• Create a separate account with the salesperson role for each employee. Shared logins must not be used during a shift.
• Under Settings — Parameters — Access, enable the restriction on entering discount card numbers from the keyboard so that cards can only be read with a scanner.
• Regularly review the User Activity Log and warehouse document change logs.
• Prevent sales staff from changing prices and recalculating stock balances.

Problem 6. Administrative operations are performed during business hours

The sudden disappearance of products from a warehouse is usually explained by the sequence of user actions. A software failure is not the cause. The owner starts closing an accounting period or recalculating stock balances while sales are still taking place at the outlets. Data changes simultaneously from two sides, and discrepancies appear in the warehouse status form.

In Torgsoft, closing a period checks unfinished rental documents, orders and reservations, recalculates cost prices, updates statistics and indexes, and automatically creates a restore point. This is a resource-intensive administrative operation. It should not be started during active sales.

Another typical situation from the same group is when a cashier automatically changes the product price in the warehouse status form before adding the item to an internal transfer document. The result is incorrect item classification and lost markup.

What to do

1. Establish a written rule: closing periods and creating restore points may only be performed outside business hours.
2. Appoint a person responsible for administrative operations and set one day each month for carrying them out.
3. Prevent restricted salesperson accounts from recalculating product quantities in warehouses.

Problem 7. The database is neither maintained nor archived

This mistake appears later than the others and is the most expensive. Over time, the SQL database grows, and refreshing tables in sales and invoiced sales forms begins to take a noticeable amount of time for every action. The situation worsens if the minimum selling price control setting uses the option that prompts before selling below cost price: Torgsoft documentation explicitly states that values other than allowing sales below cost may cause delays when adding a product to a sale because of additional calculations.

The second part of the problem is the absence of backups. The database may be encrypted by ransomware, damaged by an emergency power outage or corrupted by a disk failure. Archiving errors may also occur when there is insufficient free space on the system drive for temporarily unpacking files.

What to do

1. Regularly perform the administrative operations Restore and Reorganise Indexes and Update Statistics and Database Optimisation outside business hours.
2. For large data volumes, disable resource-intensive cost price checks during sales.
3. Configure automatic scheduled backups with uploads to cloud storage.
4. Monitor free space on the system drive and keep the server connected to an uninterruptible power supply.

Examples from Ukrainian retail

The most illustrative examples were recorded in winter 2026. As of the morning of 13 January, around 17 Novus supermarkets in Kyiv and the surrounding region were closed: the company explained that sales floors, refrigeration equipment and checkout systems could not operate normally without electricity. At the same time, chains that had invested in autonomy in advance continued trading. Supermarkets belonging to Retail Group and Epicentr shopping centres operated on generators, while the EKO Market chain transferred ultra-fresh products to refrigerated chambers with stable temperature conditions after stores were closed.

These are large chains with different budgets. The same principle applies to a small store without modification: first, backup power for the checkout workstation and server; then the ability to accept payments and record sales when the connection is interrupted; and only then everything else. A single store needs three things: an uninterruptible power supply for the checkout workstation, backup mobile internet and an offline sales mode.

Where to start if discrepancies already exist in the records

1. Record actual stock balances. Conduct a full inventory outside business hours and enter actual data as the starting point. Without this, subsequent steps will not produce results.
2. Separate permissions. Create individual accounts with roles, prevent sales staff from changing prices and manually entering discount card numbers, and enable review of the user activity log.
3. Define administrative operation procedures. Determine who closes periods, optimises the database and checks backups, and when these actions are performed. Communicate the procedure to all outlets in writing.

Complete checklist before and after launch

Frequently asked questions

Conclusion

None of the mistakes described is caused by a lack of budget. They are caused by the absence of rules: who has access, when administrative operations are performed, what data enters the database and who is responsible for backups. A store that has written answers to these four questions receives accurate stock balances, clear cost prices and control over checkout operations from automation. A store without these answers receives another software package that nobody uses.