Warehouse and Inventory Automation: Barcodes, Data Terminals, and Stock Control

Why manual tracking breaks down as you grow

While a company has one store and a few thousand SKUs, the warehouse survives on a notebook, Excel, and the storekeeper's memory. But once a second branch, wholesale shipments, and tens of thousands of SKUs appear, manual tracking starts costing money: misgrades, lost goods, gaps between physical stock and the database, shipments of the wrong item. In Uzbekistan this is made worse by the fact that many companies run "official" accounting in 1C alongside operational tracking in Excel or on paper — two realities that never reconcile.

Warehouse automation isn't about "buying a scanner." It's about every goods movement (receiving, transfer, shipment, stocktaking) being recorded at the moment the operation happens and landing immediately in a single database. Then the quantity in the system equals the quantity on the shelf, not a report from a week ago.

Barcoding as the foundation

A barcode is a machine-readable identifier for an item. Without it, any automation collapses into manual entry of item codes — and therefore errors. A basic starter set:

• EAN-13 / EAN-8 — factory barcodes on consumer goods. If the supplier already labels the product, use their codes; don't invent your own.
• In-house labeling — for weighed, packed, or unbarcoded products you print labels yourself (Code-128, EAN-13 based on an internal item code).
• QR / DataMatrix — for labeling bins, pallets, and cases where you need to fit more data (batch, expiry date).

Location-based storage: the warehouse as a map

Location-based storage means every storage spot has its own address code: zone, rack, level, bin (e.g., A-12-03-2). Goods are "registered" not vaguely "in the warehouse" but in a specific bin. This delivers three effects:

• A new employee picks an order along a route without knowing the warehouse by heart — the system guides them from bin to bin.
• Receiving is placed deliberately: fast-moving goods near the shipping zone, seasonal items in the far rows.
• Stocktaking runs by bins rather than "the whole warehouse at once" — you can recount by zones without stopping work.

Location-based storage makes sense once the catalog exceeds a few thousand items or the warehouse is physically large. For a small, fast-turnover warehouse it can be overkill — assess your scale honestly.

Data terminals and scanners: how to capture data

A data collection terminal (DCT) is a rugged industrial "smartphone" with a built-in scanner and a warehouse client app. Unlike an ordinary USB scanner, a DCT works autonomously over Wi-Fi: the storekeeper walks the floor, scans, and sees the task and stock right on the screen.

In Uzbekistan's reality, a sensible start is pairing affordable Android DCTs with a custom mobile app we build around the client's specific business processes. This is far cheaper than off-the-shelf solutions and avoids buying expensive imported software for every terminal.

Stocktaking without halting the business

The classic annual "close the warehouse for three days" stocktake is painful and still produces discrepancies. Automation lets you switch to selective counts:

• Cycle counting — a small zone is recounted each day on a schedule; over a month the whole warehouse is covered without downtime.
• Blind counting — the scanner doesn't show the recorded quantity; the employee enters the actual count and the system flags the discrepancy itself. This removes the temptation to "fudge" the numbers.
• Bin-level control — a discrepancy is immediately localized to a specific address, not "somewhere in the warehouse, minus 40 units."

Integration with 1C and CRM

The warehouse doesn't live in isolation. Salespeople need stock in CRM, accounting needs it in 1C, retail needs it at the register. Integration is critical here; otherwise you automate one segment while data is still copied by hand.

In Uzbekistan, 1C remains the standard for accounting and trade. The warehouse is therefore most often synced with it: the item catalog and barcodes come from 1C, while movements (receiving, shipments, stocktaking results) flow back. Possible scenarios:

• Exchange via 1C mechanisms (HTTP services, 1C web services) — when the warehouse system is external and 1C remains the accounting core.
• CRM integration — so a manager sees the real stock at the moment of closing a deal and doesn't sell what isn't there.
• Link to checkout and online storefront — a single stock figure across all sales channels to prevent double-selling the same item.

It's important to agree upfront which system "owns" the data. Usually the catalog and prices live in 1C, while operational warehouse actions live in the warehouse app. A clear split of responsibility ends the eternal question of "whose numbers are correct."

Where to begin the rollout

Don't try to automate everything at once. A working sequence: clean up the item catalog → introduce barcoding → automate receiving and shipping → add location storage and bin-level stocktaking → connect integrations. Each stage delivers value on its own and reduces the risk of the project stalling on one big overhaul.