STOKA
ESEN中文
Contact usJoin STOKA

STOKA / Warehouse processes

When the system inventory does not match the warehouse floor

Inventory differences rarely start at the count. They start with a receipt logged late, an internal move nobody confirmed, or a storage location the system does not know about. STOKA corrects the source of the error first, and only then builds the cycle counting program that keeps it under control.

Tell us your problem

The system inventory is no longer enough to decide a purchase or a delivery

In a warehouse, inventory stops being reliable long before the difference reaches the balance sheet. What changes first is how people work. These are the five symptoms STOKA reviews on its first visit to the site, together with the person who runs the operation.

  • The system sells what is not there

    Available quantity shows in the system and the aisle is empty. The order ships short, and the customer notices it before management does.

  • Deliveries are promised only after counting

    Nobody confirms a date from the screen. Someone walks the warehouse and checks by hand what the system should already be saying.

  • Closing adjustments always go one way

    Month after month the inventory is corrected in the same direction. A systematic adjustment, rather than a random one, points to a process that under-records.

  • The same item shows in two locations

    A pallet moved position and nobody confirmed it. The system keeps both storage locations, and whoever picks the order takes the closer one.

  • Nobody signs off on the final number

    When the count closes, the number has no owner: finance distrusts the warehouse, the warehouse distrusts the system, and replenishment is decided by judgment.

What STOKA does about inventory control

STOKA works on the origin of the data, not on the recount. The project surveys the five points where inventory changes state —receiving, internal moves, picking, returns and shrinkage— and defines who records each one, with what evidence and at what moment. STOKA then designs the storage location scheme, classifies products by turnover and by value, builds the counting plan, and delivers the written procedure, the training and the indicators with their measurement basis.

How inventory control is built, step by step

Four steps, in this order. The first three create the condition without which counting is pointless. The schedule is set after the survey, driven by the number of product references, the state of the product master and how many storage locations have to be defined.

  1. 01

    Storage locations defined and labeled

    The STOKA team surveys the layout with the person responsible for the warehouse and codes every position: aisle, bay and level. Labeling is done before any count, because counting without locations measures packages, not inventory.

  2. 02

    A single product master

    STOKA checks with the client's systems team that every product has one code and a clear unit of measure. If the same item is entered by unit in one area and by case in another, the balance is not comparable.

  3. 03

    Confirmation of every movement

    Every transfer, issue and re-entry is confirmed by the person who performs it, at the moment and in the place where it happens, in the system your company already uses. STOKA defines the mandatory record for each step and trains the team that performs it.

  4. 04

    A cycle counting plan

    Products are classified by turnover and by value, and each class gets its frequency and its counting window. The warehouse staff does the counting, with the operation running, and a responsible person signs off on each close.

What the inventory control project includes and what it does not

What it includes

  • Diagnosis of the five sources of inventory difference
  • Design and coding of the storage location scheme
  • Classification criteria by turnover and by value
  • Cycle counting plan by class and by zone
  • Written recording procedure for every movement
  • Team training and indicators with their stated basis

What it does not include

  • The physical count itself, if your team does not run it
  • Cleaning up the product master inside your ERP, the company's administrative system
  • Implementing a new warehouse management system, the software that tracks where every item is
  • The inventory audit required to close the books

A full physical count for closing the books is signed off by an audit, with a different scope and a different owner: if that is the urgency, it is better handled outside this project, and this work comes after. Asking for this project just to count more often does not help either: without correcting the five sources, each count documents the problem in more detail.

Where inventory differences come from, and in what order they are corrected

An inventory difference is the end of a chain, not its beginning. There are five sources, and each one leaves its own trace. Receiving logged late shows up when you compare the time on the delivery note with the time of entry in the system. An unconfirmed internal move appears as inventory in a location that is already empty. Picking without closure leaves the order shipped and the unit still allocated. A return without re-entry shows the credit note issued and the position not replenished. Undeclared shrinkage only shows up as a shortfall.

The order of correction is not negotiable: the source first, the count after. STOKA surveys the five points with the person responsible for each, defines the record that is mandatory at every step, and writes the procedure that holds when the staff changes.

What inventory accuracy is reasonable to expect, and what it is measured against

Inventory accuracy is not a number on its own: it changes with what is being measured. Measured against units shipped, against lines picked or against system movements, the same operation produces three different results. That is why STOKA does not publish a bare percentage: the target is set with you, against system movements confirmed at the moment they occur, and always measured against that basis.

The target is not copied from a table. It is set with you against the value measured at the start of the project, and by turnover class and value class, because a shortfall in a routine consumable and a shortfall in a traceable product do not cost the same. One rule holds for every operation: without a stated basis, an accuracy percentage is not published and is not accepted in a report.

When it makes sense to automate inventory control

Inventory stays accurate when every movement is recorded by the person who makes it, at the moment they make it. As long as that depends on someone writing it down later, the difference comes back. Automation changes where the data comes from: in an automated system the machine performs the movement, and the record is the same order that produced it, with its location, its time and its quantity. Counting stops being a campaign and becomes a sample check of what the system already knows. Accuracy is measured against confirmed movement lines, and without that basis a percentage says nothing.

what changes when the machine performs and records the movement

what a warehouse management system actually solveshow a cycle counting plan is builthow inventory accuracy is measured

Frequently asked questions

How often does inventory have to be counted?

Frequency is set by turnover and by value: what moves most and what is worth most is counted more often, and the rest goes into a wider rotation. Cycle counting replaces the annual physical count as an everyday control, with zones and owners assigned.

Does the operation have to stop in order to count?

No. Cycle counting is done with the operation running, by zone and in defined windows: one zone is counted while work continues in another, and the position being counted is blocked only while that lasts. Stopping the whole warehouse is justified only for a full physical count.

What inventory difference is acceptable?

There is no universal percentage that works for every product. The target is set with you against the value measured at the start of the project, and by class: what is tolerated in a routine consumable is not tolerated in a traceable product.

Is sample counting worth it?

It is worth it when storage locations are defined and movements are confirmed as they happen: in that case the sample represents the whole. Without firm locations and confirmation, sampling measures the disorder rather than the inventory, and two counts of the same zone give different results.

What inventory accuracy can be reached?

With the movement confirmed by the person who performs it, at the moment it happens, accuracy rises and can be sustained. The number is only worth something with its basis: measured against lines picked or units shipped it gives a different value.

The other warehouse processes

Back to the six processes
01Space and layout02Receiving process03Order picking05Order shipping06Returns and reverse logistics07Warehouse diagnostic

Send us the inventory adjustment history of the last few months

With that history, the location list and the product master, STOKA will tell you which of the five sources each difference comes from. We assess your case with the data from your operation. We reply within 24 business hours.