Warehouse transfer rules that prevent stock shrinkage
Site-to-site transfers are where 30–40% of material shrinkage hides. Five rules Uzbek construction firms use to keep transfers visible and accountable.
A warehouse manager once told me: "I can tell you exactly what came in and exactly what went to the prorabs. What happens between our two sites — I don't know." That gap between sites is where 30–40% of all material shrinkage hides. Deliveries arrive, requests are fulfilled, but transfers between sites drift through informal channels and vanish from the books. Here are five rules that seal the leak.
Rule 1 — Every transfer gets a number before the truck leaves
The single biggest cause of transfer shrinkage is the "I'll write it up later" transfer. By the time the paperwork catches up, the quantity is a rounded memory and the destination is approximate. Enforce a rule: no material leaves a warehouse bay without a transfer number generated first, even for 5 bags across the road. A mobile-issued transfer number is fine; a piece of paper is not.
Rule 2 — The receiving site confirms the count, not the sending site
Sender and receiver rarely disagree when they are the same person's friend. Confirm transfer at the receiving end only. If the receiving prorab counts 48 and the transfer says 50, the missing 2 is on the record. The warehouse manager reconciles weekly: senders with consistent gaps get flagged, and the pattern becomes data instead of rumor.
Rule 3 — Transfers cost the receiving site at the sending site's batch price
If the receiving site uses average or re-priced costing, transfers hide cost arbitrage. A site with cheap cement sends it to a site that was going to buy expensive cement, and the transfer price gets lost. Use the original batch cost at the sending site. The receiving site inherits that cost on the SMETA line. Both sites see the real number.
Rule 4 — Back-to-back transfers require a reason
When material arrives at site A and leaves for site B within 48 hours, something is wrong. Either the delivery was routed to the wrong site, or A was the "convenience warehouse" for B. Both cases need to be named. Force a reason field on quick-turnaround transfers. The audit will find patterns — usually one project that reliably "borrows" from another to hide budget overruns.
Rule 5 — Monthly transfer reconciliation is non-negotiable
Once a month, the warehouse manager lists every transfer between sites: source, destination, material, quantity, value. The director compares against planned material movement. Unplanned transfers above 2% of monthly consumption get reviewed — not punished, reviewed. The exercise takes two hours and usually finds one systemic issue that has been costing real money for months.
The behavior this creates
Once transfers are numbered, receiver-counted, cost-carrying, reason-justified, and monthly-reviewed, the informal transfer channel dies. Prorabs stop asking for transfers that cannot be justified, because the reason field is now visible. Warehouse managers stop accepting transfers without paperwork. Directors see real consumption per site for the first time.
None of this requires software — it requires five rules and one weekly reconciliation meeting. The software version is faster because the transfer number, the receiver count, and the batch price are already automatic. But the discipline comes first, and the discipline is what saves the money.