WMS system: what it is, when a warehouse needs one and when 1C is enough

A WMS (Warehouse Management System) is software that runs a warehouse in real time: it knows what sits in every bin, sends the picker a task on a handheld terminal, builds the route through the aisles and confirms every action by scanning. An accounting system answers the question "how much stock do we have"; a WMS answers "where is it and who is working with it right now".

Below: how a WMS differs from 1C, the accounting and ERP platform most Russian companies run on, and from ERP in general; what it actually does inside a warehouse; the seven signs that a warehouse has outgrown its current setup; and, most importantly, when it is overkill and it is cheaper to extend what already works. That last question rarely comes up in industry overviews — they are usually written by the people selling WMS.

What is a WMS system in plain terms?

In short: the system manages the movement of goods inside the warehouse; recording arrivals and departures stays with the accounting software.

Picture a warehouse through the eyes of a picker with no WMS. An order comes in, the picking list has ten lines, and the person walks the racks recalling where each item lives. They choose the route themselves, take whichever batch they come across, and spot a mistake at the packing station if they are lucky.

The same order with a WMS: the system decides which bins to pick from, taking expiry dates and stock levels into account, lays out a route in a single pass, pushes the task to the handheld terminal and requires every line to be scanned. Picking the wrong bin or the wrong batch becomes physically hard.

Hence the essence: a WMS manages what people and equipment do in the warehouse at the moment they do it, while end-of-day accounting stays with other systems. That is the dividing line between it and the rest of the warehouse software stack.

How does a WMS differ from 1C and from ERP?

In short: 1C and ERP work with documents after the fact, a WMS works with tasks at the moment of execution.

The difference is one of timing, and neither quality nor price has anything to do with it. The accounting layer faithfully reflects what has already happened: the receipt is entered, the write-off is posted, the balance is recalculated. A WMS steps in earlier — at the moment the picker decides which rack to walk to.

The practical consequence: a WMS does not replace 1C. The two are deployed side by side and linked through an integration: accounting stays in the accounting system, control of physical operations moves to the warehouse system. For how such an exchange between systems works at all, see our breakdown of how to connect 1C, CRM, your bank and Telegram into a single loop. For how ERP differs from both, see ERP system: what it is in plain terms.

What does a WMS actually do inside a warehouse?

In short: it assigns goods to addresses, issues tasks and verifies every action by scanning.

The functions it is bought for:

• Bin-level storage. Every bin has a code, every batch has its place. Searching "from memory" disappears as a category.
• Tasks on a handheld terminal. The employee gets a sequence of actions with a route, instead of a plain list of items.
• Put-away and picking rules. Where to place a new delivery and where to pick from: by expiry date, by turnover, by weight.
• Scan-based verification. Every step is confirmed by barcode, so mis-picks are caught immediately, long before the stock count.
• Staff and equipment management. Who is free, where the forklift is, how to spread the load across shifts.
• Stock counts without shutting the warehouse. Individual zones are counted in the background instead of stopping everything.
• Traceability. For any unit you can see who received it, moved it and shipped it.

Almost every item on that list is about what people do. That explains why the effect of a WMS shows up most clearly where a warehouse has many people and many operations.

What are the signs a warehouse has outgrown its setup?

In short: when the bottleneck has moved out of accounting and into the physical movement of goods.

Seven signs, each worth checking against your own warehouse:

1. Goods are found from memory. Throughput depends on who is on shift today.
2. Mis-picks surface at the stock count. Which means the error lives in the system for weeks before anyone notices.
3. A new hire takes weeks to reach normal speed. Knowledge about the warehouse is written down nowhere but in people's heads.
4. The picking sequence has started to affect delivery times. Volume has grown to the point where the route through the warehouse costs money.
5. Stock counts bring work to a halt. The warehouse closes for counting and shipments stand still.
6. Batches and expiry dates are tracked by hand. Write-offs for expired stock have become a visible line item.
7. There is now more than one warehouse. Transfers between them are needed, and the picture of stock levels drifts apart.

Three or more signs is a reason to run the numbers. One or two usually has a simpler cure, which is the next section.

When is a WMS overkill and it is cheaper to extend what you have?

In short: as long as there is one warehouse, a moderate range of items, and the pain sits in the processes around the warehouse, a full WMS will be an expensive answer to the wrong question.

This section rarely appears in industry overviews, because those are usually written by WMS vendors and integrators. Yet bin-level storage, tasks pushed to handheld terminals and scan-verified picking are by no means the privilege of dedicated warehouse systems. All of it can be built in the accounting layer, and that route wins in three cases:

• One warehouse, relatively small. The gain from route optimisation does not cover the cost of a separate system and its support.
• Process specifics matter more than depth of warehouse logic. You have a non-standard way of working with clients or production, and the real value is tying it into a single loop.
• The bottleneck is not in the warehouse. Shipments slip not because the picker walks slowly, but because the order sat unprocessed in an inbox for two hours.

The third case is the most common one, and that matters. In our wholesale case the problem looked like a warehouse problem: constant mis-picks and missed shipments. The analysis showed something else — orders were coming in by email and messengers, sales reps checked stock levels by phoning the warehouse, reservations went missing, and 1C lived separately from sales. The answer was a single order-intake loop with automatic reservation and two-way integration with 1C: an order immediately sees real stock levels and places a hold. Order processing dropped from hours to minutes and shipments stopped slipping — with no WMS involved.

In the retail chain case the logic was the same: automated stock accounting covering receipts, sales, returns and balances, plus shift tracking across locations, closed a task that formally "called for" a warehouse system. The result — one merchandiser position was removed from the payroll and human error in stock records was cut to a minimum.

That is why we at INCUBE AI start by working out where exactly the money is leaking. If you count the benefit honestly, the right answer is sometimes to extend the loop you already have instead of buying a new system.

What does the Russian WMS market show?

In short: the market is mature, the emergency replacement of foreign software is over, and demand has shifted towards replacing systems that are already running.

According to a TAdviser review — TAdviser is a Russian IT market research publication — released in December 2025, the picture is as follows:

• The publication's database holds roughly 2,300 WMS implementation projects.
• Axelot leads by number of implementations, with 490 known projects. Second place goes to 1C with more than 230 projects, third to EME.
• The market leader's revenue passed 1 billion rubles for the first time, and the companies featured in the last two rankings grew by an average of 27%.
• Over 65% of all implementations are in retail and wholesale trade, logistics and distribution, and food production. In 2025 the sector grew in food production, with a spike in the medical industry.

One observation from the review deserves a separate mention: migration away from foreign systems is gradually losing momentum — those who planned an emergency switch to a domestic product have already completed it. What is growing instead is demand for replacing an existing WMS, meaning the market now has a layer of companies that implemented a system and were left unhappy with the result.

I will not quote a single figure for the size of the market: public numbers differ between sources by multiples, and citing any one of them would be misinformation.

What breaks during a WMS implementation?

In short: what usually fails is not the technology but data preparation and discipline on the warehouse floor.

The typical reasons a project does not deliver what was promised:

• The warehouse layout is not documented. Bin-level storage is impossible without a map of racks, bins and zones. That work is physical and cannot be done from an office.
• Master data is a mess. Duplicate items, inconsistent units of measure, missing barcodes. The system inherits the chaos and loses trust in its first week.
• Staff have not accepted the rules. A WMS works only if everything is scanned, every time. A single "optimisation" of the "I will mark it later" kind destroys the reliability of stock figures.
• The integration runs one way only. The accounting system and the warehouse system drift apart and you end up with two versions of stock levels — exactly the problem the whole project was meant to solve.
• Only the implementation was budgeted. Equipment, labels, terminals, training and support never made it into the estimate.

The first three points are organisational, and they are what decides the outcome. Technically, dozens of teams implement WMS today; the difficulty lies in preparing the warehouse, while installing the software has long been routine.

How do you connect a WMS to 1C and the rest of your systems?

In short: through a two-way exchange where each system has its own area of responsibility and every piece of data has one owner.

A working split of responsibilities looks like this:

• The accounting system remains the owner of items, counterparties, prices and documents.
• The WMS becomes the owner of what happens inside the warehouse: bins, tasks, actual movements.
• The exchange runs both ways: the shipping order goes out to the WMS, the fact of picking and shipping comes back into accounting.

The main rule is that every entity must have one source of truth. The moment stock figures start being edited in both places, the systems drift apart, and from then on disputes are settled by a physical count.

A separate question is how fresh the data is: if the exchange runs once an hour, a sales rep sees hour-old stock levels and promises the client something that is already gone. That is why the exchange for critical entities is made event-driven.

Where do you start if the warehouse has outgrown its setup?

In short: by measuring your current losses and documenting the warehouse; the vendor is chosen last.

1. Work out what the current arrangement costs you. Hours spent looking for goods, the cost of mis-picks, the volume of expiry write-offs, the time a stock count takes. Without that number, any implementation will be discussed on gut feel.
2. Document the warehouse physically. Zones, racks, bins, storage schemes. You will have to do this work anyway — do it before choosing a system, and the conversation with contractors becomes concrete.
3. Clean up your item master data. Duplicates, units of measure, barcodes.
4. Establish where the bottleneck actually is. The warehouse, or the processes around it. The answer decides whether you need a WMS at all.
5. Compare the two scenarios in money. A separate system versus extending the loop you already have — over a three-year horizon, with the cost of ownership included.
6. Start with one zone. A pilot in a single area gives you an honest answer faster and cheaper than rolling out across the whole warehouse.

Points one and four are the ones skipped most often. And they are exactly what determines whether, a year from now, you end up among the companies shopping for a replacement for the system they have just implemented.

Sources

• TAdviser. WMS — Warehouse Management System, review dated 19.12.2025 — a database of 2,300 projects, the vendor ranking, the industry split of implementations, market dynamics
• TAdviser. Enterprise management systems (the Russian ERP market) — context on the adjacent market for enterprise systems
• ComNews. Study by SberAnalytics and Sber Business Soft, 22.01.2026 — the structure of automation in Russian companies