Automating Store Operations: From Process Mapping to Launching Inventory Management

Start automating your store with one complete process: receiving goods, tracking stock, making sales, processing returns, and reconciling results. The owner needs to assign responsibilities, organize the catalog, count opening stock, and configure the software with a specialist. After that, employees should run trial transactions and compare documents, physical goods, and payment amounts.

Extend the new workflow to the entire store after a successful trial run. Create a backup in advance, train each employee on their operations, and agree on what to do in case of a failure. Measure the results using your own metrics: time to process a delivery, number of errors, stock accuracy, and system maintenance costs.

Choose a process and define the automation outcome

For the first launch, choose one store location and a limited product group that lets you run through the full work cycle. Include an ordinary product, different sizes or colors, an item without a barcode, and an item a customer might return. This selection will help you catch errors before expanding inventory management.

The owner, together with a salesperson and the employee who receives deliveries, should describe the actual workflow. Record who receives the delivery note, who counts the goods, who sets the price, and how the salesperson learns about a price change. For each handoff, specify a document or record that tells the next employee they can begin their part of the work.

Below is an example process map. Adapt it to your store: in the “Before” column, record the actual workflow; in the “After” column, record the agreed employee actions.

Before launch, measure how long these tasks take. Compare deliveries and sales of similar complexity: creating new product cards involves different tasks from receiving familiar items. Separately count the errors that had to be corrected and the time spent finding them.

Assign employee responsibilities and access

Prepare a short operating procedure that lists each operation, who performs it, what actions are permitted, the expected result, and how to request help. The owner approves this document, and the specialist configures access accordingly. In a small store, one person may perform several roles, but responsibility for each action should still be clear.

• Owner approves the catalog, prices, discount limits, data access, and the decision to launch fully.
• Employee who receives goods counts the delivery, records the receipt, and reports discrepancies with the delivery note.
• Salesperson records sales and returns within their authority and refers cases they cannot resolve independently to the manager.
• Shift manager or inventory clerk reconciles documents, stock, and payments and organizes corrections.
• Implementation specialist configures the software, equipment, and backups, and helps test restoration.

A practical approach to access is to give employees the capabilities they need for their tasks. For example, a salesperson can be limited to sales and returns, while changes to purchase prices and access settings are assigned to the owner. After setup, sign in with each role’s account: permitted actions should work, and restricted actions should be unavailable.

Prepare the catalog, article numbers, and barcodes

Assign one person to oversee the rules for creating product cards. First, agree on which characteristics distinguish one inventory item from another. For example, T-shirts of the same model in different sizes or colors need to be distinguished so the salesperson deducts the exact variant sold.

SKU means a separate inventory item. An article number helps identify a model or its variant according to your catalog rules, while a barcode lets employees find a product by scanning it. Decide in advance whether a code represents one piece, a package, or another sales unit: an error here will affect every receipt and sale.

1. Set a consistent naming convention. For example: product type, brand, model, color, size. Store characteristics that have separate fields in those fields.
2. Look for possible duplicates. Compare identical barcodes, article numbers, and similar names. A responsible employee should review every match.
3. Determine why an entry is duplicated. Two cards may describe the same product or different configurations. Do not merge them based only on similar names.
4. Prepare labels. For goods without a usable code, arrange to print and apply labels before putting them out for sale.
5. Test scanning. Scan the products in the trial group and compare the name, variant, unit, and price with the physical goods.

Before transferring the full catalog, upload a small sample. Check that leading zeros in barcodes have not disappeared, characteristics have been assigned correctly, and duplicate cards have not appeared. Transfer the remaining data only after correcting these errors.

Record opening stock and prepare a backup

Choose a transition period with light workload, when the responsible employees and specialist can be reached. Agree on the exact time for recording stock. While counting the trial group, pause its movement or separately record every receipt, sale, and return so you can account for them during reconciliation.

An employee counts the physical goods at each storage location, and a second responsible person compares the total with the data prepared for upload. Set aside items in question until they are clarified: do not guess how to record an unknown size, damaged packaging, or goods with an unclear unit of measure.

Keep opening stock separate from a new delivery. Goods already owned by the store at the time of transition should be entered as opening stock without creating a supplier debt a second time. Agree with the inventory clerk and specialist on how to enter this data before uploading it.

Before transferring data, save the source spreadsheets and create a backup of the existing database if one is already in use. With the specialist, test restoring the backup in a separate environment isolated from the live database. Open the restored data and compare several products, documents, and totals. Record where the backup is stored, who has access, and who is responsible for restoration.

Run a trial cycle: receiving, sales, and returns

First, run training scenarios in a separate database with the live fiscalization channel disabled. Fiscalization means registering a settlement transaction and generating a fiscal receipt. The specialist must confirm these settings before exercises begin. During real sales, record each transaction in one live system of record, and use a control entry in a spreadsheet or on paper for independent reconciliation. That control record must not register the sale a second time or generate another fiscal receipt.

This procedure is for organizing the trial. Before the live launch, discuss with your accountant and specialist whether a cash register (РРО) or software cash register (ПРРО) applies to actual sales and how it should be configured.

Illustrative quantity reconciliation: opening stock was 20 units, 10 more were received, 7 were sold, and a customer returned 2. If there were no other movements, expected stock is 20 + 10 − 7 + 2 = 25 units. The employee should compare this figure with the software and a physical count.

Reconcile payment amounts separately from product quantities. Compare cash transactions with the actual cash, accounting for the opening amount, cash added, and cash removed. Compare card payments with the totals from the relevant payment channel. Record discrepancies with a reference to the specific transaction so the responsible person can find the cause.

Train employees and agree on what to do if something fails

Training is complete when an employee can perform a task independently. The salesperson should make a sale, correct an error before completing it, record a return, and explain whom they will contact if the result is unclear. The receiving employee should find an existing product card, distinguish a new product from a repeat delivery, and show how they will report a shortage.

Prepare short instructions for each workstation: the steps to follow, the result to look for, and the contact person responsible. Include scenarios for an unknown barcode, an incorrect price, a quantity discrepancy, and an interrupted transaction. Before repeating an interrupted action, the employee should check whether the previous transaction was saved, to avoid creating a duplicate.

Before launch, the owner and specialist should agree on conditions for pausing the transition. These may include unresolved stock discrepancies, duplicate documents, or inability to complete a sale safely. The plan should state who makes the decision, how employees record new transactions, and how those transactions will later be entered into the live inventory system.

If real sales or returns took place after a backup was created, restoring that backup will remove later entries from the database. Therefore, decide whether to restore it together with the specialist after saving the current state and a list of all transactions from that period. Any settlement transactions already completed must be accounted for when restoring inventory records, without being fiscalized again.

Manage stock, customer purchases, and slow-moving goods in Torgsoft

Before purchasing, determine the number of workstations and inventory centers: an inventory center in Torgsoft is a store or warehouse with its own separate stock records. The paid “Start” license is designed for one store with one or two cash registers and does not support multiple inventory centers or warehouse transfers. “Ultra” supports work over a local network; a terminal license is provided for remote locations to access one server database over the internet at the same time.

Compare your process with the license capabilities and current payment and support terms, agree on employee roles, and test the scenarios in the demo version. For a consultation, use the public contacts on this page; confirm the scope of included assistance and subsequent paid maintenance for your plan.

For reconciliation, open “Склад — Стан складу” (“Warehouse — Stock status”): here you can review quantities and prices, and use “Картка складського обліку” (“Inventory record card”) to trace stock after a receipt, sale, return, or transfer at the current warehouse. Purchases and returns recorded against a customer appear in the “Придбання” (“Purchases”) tab of the customer card. To assess slow sales, use “Аналіз — Аналіз товару, що залежався” (“Analysis — Analysis of slow-moving goods”): select a period, inventory center, and sales-count threshold.

The threshold applies to the number of units sold, not the number of receipts. For individually sold goods, a value of 1 selects items with no sales during the period; for goods sold in fractional quantities, the results will also include positive values below 1. If needed, include only goods that were in stock at the start of the analysis. After reviewing the results, the owner decides on future purchases and prices.

To keep a separate copy in Google Drive, you can add the paid annual “Хмарний архів даних” (“Cloud data archive”) option. With a specialist, check the licensing terms for your network, authorize your Google account, and configure an active task using the archiving instructions. The process requires an internet connection and a running application server. Agree on a schedule alongside local archiving, set a retention period and procedure for deleting old copies, and assign an employee to check the log and confirm that a fresh archive appears in Google Drive. Before the live launch, test restoration in a separate environment: the presence of a file alone does not confirm that the required data can be restored.

Protect customer data during transfer and operation

If the store maintains a customer database, determine the purpose and legal basis for processing personal data before uploading it, in accordance with Ukraine’s Law “On Personal Data Protection.” Articles 6 and 11 provide for specific lawful purposes and legal bases for processing, including consent, performance of a transaction, a legal obligation, and other cases defined by law. The data collected must match the purpose and must not be excessive. For every field in the customer card, determine why the store needs it.

When an employee collects data directly from a customer, inform the customer of the data controller, the data being collected, the purpose of collection, their rights, and the people to whom the data will be transferred. Under Article 12, this notice is given when the data is collected; if the data was obtained another way, it is given within 30 working days, except in cases established by law. Before using contact details for another purpose, determine the appropriate legal basis separately. Changing the purpose to one incompatible with the original requires the customer’s consent unless the law provides otherwise.

Under Article 24 of this Law, data must be protected against accidental loss or destruction, unlawful processing, and unauthorized access; an individual entrepreneur must personally ensure the protection of the data they control. In practice, this means defining access to the live database, transfer files, and archives, as well as the procedure for revoking access when an employee leaves. Set up a process for handling customer requests: Article 8 provides, among other things, rights to access data, withdraw consent, and submit a reasoned request to change or destroy data if it is inaccurate or processed unlawfully.

Calculate costs and possible return on investment

Prepare a budget before choosing software. Include the license, required equipment, catalog transfer and cleanup, configuration, training, and employees’ paid time among initial costs. Include a subscription or rental, annual options, service maintenance, hosting or storage if needed, and consumables among recurring costs.

Separately assess benefits you can measure after launch. Saved working time produces financial savings if it reduces paid hours or frees up capacity for work with a measurable result. If shift length and expenses remain the same, record the freed-up time as a separate metric.

Illustrative example, not a tariff or forecast: the license costs UAH 12,000, configuration UAH 4,000, training UAH 3,000, and equipment UAH 5,000. Initial costs total UAH 24,000. Suppose the store saves 20 paid hours per month at a rate of UAH 150: 20 × 150 = UAH 3,000. Recurring support and other service costs are an illustrative UAH 1,000 per month. The net monthly benefit is UAH 2,000, and the estimated payback period is UAH 24,000 ÷ 2,000 = 12 months.

This result is possible only under the assumptions used in the example. After the trial run, substitute actual costs and measured benefits. If monthly savings do not exceed recurring costs, there is no positive payback period under this formula. The owner should then review the scope of the solution or assess the benefits of inventory accuracy and control separately.

Use a checklist to decide whether to launch fully

The owner reviews the results together with the employees who performed the trial operations. Before expanding inventory management, go through this list and record the result for each item:

• Every product in the trial group can be found under the correct code; there are no unresolved duplicates.
• Opening stock matches the physical count at the agreed time.
• Receipts, sales, and returns correctly change quantities.
• Prices, discounts, and payment totals match the control calculations.
• Employee permissions match the approved roles.
• Employees can perform their operations independently and know how to report an error.
• The backup is available, and a test restoration has completed successfully.
• Each discrepancy has an identified cause, a responsible person, and a correction method.
• Conditions for pausing operations and actions to take with the specialist have been agreed.

After acceptance, add the next product groups or workstations following the same procedure. Repeat data and access reconciliation for every expansion. Set a date to review actual performance metrics and decide which settings or work steps need to change.

Official act governing personal data

Law of Ukraine “On Personal Data Protection” dated 01.06.2010 No. 2297-VI: Article 6 — requirements for processing and data retention periods; Article 8 — a person’s rights regarding their data; Article 11 — legal bases for processing; Article 12 — notice at collection; Article 24 — ensuring data protection.