Callback
  • From a market stall to a store

  • -

  • From a store to a retail chain

  • -

  • From retail to manufacturing

Shoe Store Chain Automation: Case Study

Client case study

Automation of a shoe store chain: from one license to 158 workplaces

A shoe retail chain needs to control models, size ranges, seasonal stock and transfers between cities at the same time. This story shows how the owner expanded the accounting system step by step: from the first full license in 2016 to 158 workplaces on a terminal server in 2026. The case is based on real long-term use of Torgsoft. We preserved the logic of the business decisions without disclosing client details.

2016year of first implementation
158workplaces on a terminal license
50+stores in the chain, according to the owner in 2024
18options reissued to a new license in 2025

How it started

The first contact with the program happened at a footwear industry exhibition in autumn 2016. After several demo licenses, the first full Torgsoft Ultra license was issued in December. In the same month, product photography with a webcam and the mobile app were connected.

In February 2017, the database was moved from a local computer to a server, and the chain switched to terminal mode: three workplaces at the start, seven in summer and twenty-eight by the end of the year. Later, the number of connections was regularly increased together with the chain.

Sales floor of a shoe store: shelves with boxes and a checkout area with a laptop, barcode scanner, receipt printer, label printer and bank terminal

How the system developed

2016

Demo version and first full license

Several demo licenses were issued in autumn, and in December — a full Torgsoft Ultra license. Product photography with a webcam and the mobile app were connected first.

Result: the owner moved from testing the program to a permanent license and began building a configuration for the store’s processes.
2017

Switch to a terminal server

In February, the license was moved to a server and terminal connections were configured for the retail locations. During the year, the number of workplaces grew from three to twenty-eight. Payroll and staff motivation, as well as bulk customer messaging, were connected that year.

Result: the database and product photos were moved to the server, and new workplaces were later added to the terminal license.
2018

The year of the service circuit

During the year, cloud data archiving, online store synchronization, bank statements, Nova Poshta integration, discount card verification by SMS, gift certificates and the «Refer a Friend» promotion were activated. In March, a service maintenance agreement for eight or more workplaces was signed. The number of workplaces reached thirty-seven.

Result: delivery, an online storefront, customer database work and regular backups appeared around the checkout core.
2019

Checkout, payments and traffic

In June, bank terminal integration and visitor counting were activated. By September, the number of workplaces had grown to forty-eight.

Result: the receipt amount began to be transferred from the program to the payment terminal, and store traffic became a measurable metric.
2020–2021

The chain keeps growing

The number of workplaces increased from forty-nine to sixty-eight. In autumn 2021, the universal version of the Torgsoft mobile app was connected. Discount cards were ordered in batches of two and a half thousand cards, with a separate barcode range created for each batch.

Result: managers gained access to indicators from a smartphone, and card issuing became a planned procedure.
2022

Fiscalization and address-based storage

At the beginning of the year, the chain was already working with software RRO and gradually increased the number of fiscal workplaces. In August, the «Product Storage Location» option was connected. By October, the terminal license had grown to eighty-five workplaces.

Result: software RRO began to scale together with cash desks, and boxes received address-based search by storage location.
2023–2024

Stock and customer database

In December 2023, automatic warehouse stock calculation was activated. In May 2024, update 2022.0.36 introduced the SMS-code confirmation for bonus write-offs requested by the chain. In February 2024, the owner described the business as a chain of more than fifty stores across Ukraine. The number of workplaces grew from one hundred and nine to one hundred and thirty-one.

Result: stock calculation based on sales and protection of bonus operations were added to size-based and warehouse accounting.
2025–2026

License reissue and current configuration

At the beginning of 2025, the full set of eighteen additional options was reissued to a new license. In June 2026, the number of workplaces reached one hundred and fifty-eight. The chain receives program updates, the latest at the time of preparing the case being 2026.0.5.

Result: the terminal license recorded the current scale of the chain, and the options were moved to the new license number without changing the working scenarios.

The principles behind the system’s development

Eight management decisions repeat in this story year after year. Each of them is visible in the service records, and each can be reproduced in another chain.

1

One database from the second year of operation

The chain started with standard licenses, but already in February 2017 moved the license to a server and switched to terminal mode. After that, all retail locations were connected to one accounting circuit.

Tip: before opening the next location, determine whether stores need shared up-to-date stock balances. If yes, plan the server, backups and terminal connections in advance.
2

The license grows in small steps

Over ten years, more than fifty separate increases in the number of workplaces were recorded. Most often, one or two workplaces were added; in some orders, several connections were added at once.

Tip: add workplaces for a specific cash desk, warehouse or role and maintain an up-to-date connection map. This simplifies permission setup in a large chain.
3

Access rights are configured by roles

Service records regularly mention the roles «seller», «cash desk», «senior cashier», access restrictions by accounting centers and regions, and work with the user action log.

Tip: describe access through roles. When a seller changes, the new workplace receives a ready set of rights without manual configuration.
4

Loyalty is managed as a separate process

Discount cards have been ordered regularly since 2016 in batches from five hundred to five thousand cards. A barcode range was created for each batch, and discount card verification by SMS has been working since 2018.

Tip: plan card issuance in advance and assign a separate range to each batch. This keeps the customer database organized at any scale.
5

Each option is purchased for a specific task

The set of options was built over ten years. First came product photography and the mobile app, then payroll and messaging, then delivery and the online storefront, and later fiscalization, address-based storage and stock calculation.

Tip: before buying an option, describe the operation, the responsible role and the expected document or metric. This makes it easier to check whether the option covers the required scenario.
6

Requests are documented in writing

The owner and the team sent detailed requests with a description of the goal and screenshots. SMS verification of bonus write-offs was implemented in update 2022.0.36, and improvements based on the chain’s requests also appeared in updates 2026.0.3 and 2026.0.5.

Tip: formulate requests as business tasks. A description of the goal and several steps an employee must go through reaches the development team faster than a description of a single screen.
7

Support became a permanent process

Since 2017, the chain has used technical support packages, and since March 2018 it has renewed its service maintenance agreement every year.

Tip: define who in the company collects store requests, checks them and passes them to support. For a chain, this reduces duplicate requests and preserves the history of decisions.
8

The database is maintained on schedule

Cloud data archiving was connected in January 2018, and deletion of closed-period statistics — in September. In 2025 and 2026, the chain separately contacted support about the maintenance procedure for accumulated data.

Tip: configure scheduled backups, check backup restoration and agree deletion of statistics with technical support. The frequency depends on the volume of documents and the state of the database.

The common denominator of these decisions

One database
Roles and rights
Option for a task
Written request
Program update

The system developed consistently: a specific process was described, a tool was selected for it, rights were configured and the work procedure was fixed. As a result, size-based accounting, fiscalization and work with the customer database remained in one accounting circuit while the chain scaled.

Want to see how this works with your stock

The demo version includes size-based accounting, search for model sizes across the retail chain and label printing. It can be installed on one computer, where you can enter a test footwear delivery.

Chain business processes in the accounting program

Receiving and labeling

A model is entered as a size range in one step, characteristics are inherited, and a shared photo is attached to the article. Each size receives its own barcode, and the label is printed with the size in a visible place.

Checkout sale

The seller scans the box and, using the barcode of the display sample, opens the availability of the model’s sizes across the retail chain. The receipt is fiscalized through software RRO, and the amount is transferred from the program to the bank terminal.

Warehouse and assortment

A storage location is fixed for each size. The Assortment Management Center shows sales and balances of models by location and helps transfer remaining sizes to where the model sells more actively.

Staff and motivation

Sales are assigned to sellers, and salaries and bonuses are calculated in the payroll sheet. Roles restrict access to other accounting centers, and user actions are recorded in the log.

Customers and loyalty

Discount cards are issued in batches with their own barcode ranges. Bonuses are written off with SMS-code confirmation, and gift certificates and a referral promotion are used.

Online channel and delivery

The website receives stock balances by accounting centers, so the buyer can see which city has the required size. Shipments are created as Nova Poshta waybills directly from the program.

Support as part of the methodology

Transparent accounting of services

After support requests, the chain receives a report with the list of completed work and time spent. This preserves the history of settings and consultations.

Service format

Since March 2018, the chain has worked under a service maintenance agreement and regularly renews it.

Working scenarios become updates

The chain’s request for SMS-code confirmation of bonus write-offs was released in update 2022.0.36. In 2026.0.3, a more detailed progress indicator for payroll sheet calculation was added, and in 2026.0.5 — changes for maintaining large volumes of closed-period data.

Fine-tuning of business processes

How a seller sees which sizes of a model are available in the chain

In the sales window, the «Availability of model sizes in the retail chain» mode works with the Alt+W key combination. The seller scans the barcode of the display sample and sees the sizes of this model in their warehouse and in other accounting centers.

How to redistribute footwear between cities before the season ends

The menu item «Analysis — Assortment Management Center» shows model movement with photos and balances by retail location. An internal transfer to the required location can be created directly from this form.

How to plan purchasing of size ranges for the next season

The report «Analysis — Product Sales Rating» shows sales of each size for the selected period and accounting center. «Sales Analysis by Season» compares seasons, while automatic warehouse stock calculation accounts for actual sales and delivery lead times.

How to reduce the time spent searching for a box in the warehouse

The «Product Storage Location» option assigns a specific rack or cell to each size. The seller sees the storage address directly in the product card and goes straight to the required pair.

How to carry out inventory in parts

A separate inventory sheet is created for a specific product group or accounting center. For the seller role, the setting «Hide warehouse quantity for a product under inventory» can be enabled so that the employee enters the actually counted quantity. Data is collected with a scanner or data collection terminal.

How to process a return without manually searching for the sale

The seller scans the receipt barcode and selects the required item from the purchase list. If the receipt was not kept, the sale can be found by the customer’s discount card or in the list of sales. The return remains linked to the original sale.

How to combine sizes of one model in an online store product card

For size-range products, a shared model ID is filled in and the «Size» field is sent during synchronization. Products with the same ID are grouped as variants of one model, and the buyer selects the required size within one product card.

Solution ecosystem

Automation scheme for a retail shoe store chain: terminal server, retail locations, warehouse, online store, bank, tax authority and Nova Poshta

Torgsoft accounting architecture

A terminal server with a database, workplaces for retail locations and the central warehouse, separate accounting circuits by accounting centers and regions.

Licenses

Torgsoft Terminal — 158 workplaces in the chain. The first full license in 2016 — Torgsoft Ultra.

Checkout and payments

Fiscalization of sales and returns, transfer of the receipt amount to the payment device, reconciliation of incoming payments.

Software RRO
Bank terminal integration
Bank statements

Warehouse and assortment

Address-based storage of boxes, order calculation based on actual sales, model photo in the product card.

Product Storage Location
Automatic warehouse stock calculation
Product photography with a webcam

Customers and loyalty

Discount cards with barcode ranges, bonus write-off confirmation, certificates and referrals.

Discount card verification by SMS
Gift certificates
«Refer a Friend» promotion
Bulk customer messaging

Online channel and delivery

Uploading stock balances to the website by accounting centers, creating shipments from the program.

Online store synchronization
Nova Poshta integration
as well as synchronization with an external CRM

Staff, analytics and data

Calculation of seller motivation, manager access from a smartphone, traffic measurement, database maintenance.

Payroll and staff motivation
Torgsoft mobile app
Visitor counting
Cloud data archive
Deleting closed-period statistics

External circuit: fiscal server of the tax service, bank acquiring, delivery service, SMS messaging service, the chain’s website. Conditions for stable operation of this configuration: stable internet at each location, a separate computer with the database sized for the chain’s load, a valid qualified electronic signature for fiscal operations and regular database backups.

Who this automation model suits

The described architecture is designed for a business where shoe store accounting has already grown beyond one location. It suits a chain if several of these conditions are relevant.

  • You have two or more stores, and goods are regularly transferred between cities.
  • The assortment is managed by models with size ranges, and one sample is displayed in the sales area.
  • The season is short, and stock needs to be redistributed before it ends.
  • Several seller shifts work in the stores, and each sale must be assigned to a specific employee.
  • The customer database is measured in thousands of cards and requires bonus protection.
  • In addition to the sales floor, there is an online channel with delivery.

For this profile, the accounting program for a store chain is built around one database on a terminal server. If there is only one store for now, a standard license with the same set of options is sufficient, and the switch to terminal mode can be made when the second store opens.

Automation of a retail chain starts with one database

See how Torgsoft handles size-based accounting, size search across the retail chain and fiscalization of sales. The demo version works on one computer, and a consultant will help assemble a configuration for your number of locations.