Directory errors: causes of failures and financial losses
Errors in reference directories = hidden costs: how missing data increases time and money losses
A large share of critical failures, trade stoppages, and incorrect financial reports results from careless maintenance of reference directories. What at first seems like «bureaucracy» (filling in item cards, SKUs, barcodes) is actually the foundation of a business’s financial security.
The «Million Stock» effect: scanning a barcode into the quantity field

One of the most common and most dangerous operator mistakes is scanning a product barcode into the «Quantity» field during receiving or inventory counts.
-
Situation. The user accidentally scans a barcode (for example, EAN13) into the quantity field. Instead of 10 units, the stock shows 482000... units.
-
Consequence:
-
System failure. When trying to calculate cost or close a period, the program returns a critical error Arithmetic overflow error converting expression to data type int (integer data type overflow).
-
Work stoppage. Automated tasks (cost calculation, period closing) are blocked. The program starts to «slow down» or freeze when opening reports.
-
Hidden cost. Hours of staff work and support time spent finding the specific «problem» document among thousands of invoices from previous years.
«Zero» cost: losing real profit

Incorrect price entry in product directories or invoices distorts financial results.
-
Situation. Users with limited permissions (for example, storekeepers) create goods receipt invoices, but due to a restriction on viewing purchase prices the program automatically sets the purchase price to UAH 0.00. Or the «By last purchase price» method is used, and goods arrive via internal transfers without a specified price.
-
Consequence:
-
Report distortion. In «Profitability analysis» reports, profit is overstated (because cost = 0).
-
Selling at a loss. If minimum markup control is not configured, goods may be sold below the real purchase cost.
-
Hidden cost. The business owner makes management decisions based on false data about windfall profits that do not actually exist.
Chaos in the item catalog: duplicates and the «Item vs Model» mix-up

Lack of standards for entering item names creates problems during inventory and online store synchronization.
-
Situation. Importing items from Excel leads to duplicates («asterisks» in names) or confusion when an item is mistakenly entered as a «Model» without a barcode.
-
Consequence:
-
Inventory becomes impossible. The item exists physically, but the scanner cannot find it or finds a different card.
-
Synchronization errors. Items are not exported to Prom/Rozetka due to duplicate names or missing required fields (manufacturer, description).
-
Hidden cost. Lost online orders and «dead» stock in the warehouse that cannot be found and sold.
Fiscal risks: errors in software ECR directories

Incorrect item settings can lead to tax penalties.
-
Situation. An attempt to sell fiscal and non-fiscal items in one receipt, or an item with an incorrect VAT/excise rate.
-
Consequence:
-
Cash register blocked. Receipt validation errors occur (DocumentValidationError), the receipt is not fiscalized, and the checkout stops.
-
Non-compliance. For example, the word «CHANGE» or required details are missing due to incorrect template or directory settings.
-
Hidden cost. Penalties for violations of cash discipline and store downtime while resolving the issue.
«Trash» in the database: slower performance

Ignoring cleanup procedures for directories and logs leads to technical degradation of the system.
-
Situation. Gigabytes of logs accumulate, old photos are stored in the database (instead of a folder), and statistics for closed periods are not removed.
-
Consequence:
-
Limits reached. The database reaches the 10 GB limit (for SQL Express), after which the program stops working.
-
Slowdowns. Item search and opening forms take a critically long time.
-
Hidden cost. Emergency specialist intervention, trade stoppage, and potential data loss during disaster recovery.
Recommendations: how to avoid losses
-
Data entry control. Disable manual input in fields intended for the scanner and use the «Disallow selling below zero» setting.
-
Regular diagnostics. Use the «Merchandising - Error diagnostics» tool to detect duplicate barcodes and items.
-
Correct cost calculation. Use the «By delivery batches» method instead of «Last purchase price» for accurate profit accounting.
-
Directory standardization. Use unified directories (Entity/Process) to avoid chaos in metadata and settings.
-
16.04.2026
Why there is a discrepancy of a few kopecks in invoices and how to fix it
What to do if the amount in Torgsoft differs from the invoice by 2–3 kopecks: reasons, rounding settings and correction options
-
07.04.2026
Inventory management: how to avoid duplicates, limit staff rights, and track changes
How to bring order to the product database in Torgsoft: fixing names, searching for duplicates, access rights, auditing changes and controlling sellers
-
06.04.2026
Product delisting: how to hide irrelevant items and speed up search
How to delist a product in Torgsoft: conditions, 2 ways to hide irrelevant items, where to find deleted products and how to restore









Go back to the previous step