A security company running more than one site moves bulk stock between them constantly: uniforms heading to a new deployment, radios reissued from a site that is winding down, torches sent to cover a shortage. A stock transfer form is the record that stops that movement from becoming a guess. It captures where stock came from, where it is going and who signed off on both ends, so a missing box of radios is a lookup instead of a mystery.
A stock transfer form is a record of bulk stock moving between locations: the origin and destination sites, the items and quantities involved and a dispatch and receipt sign-off at each end, kept separate from a one-off issue to a single person.
The problem with moving stock between sites informally
Most security companies move stock between sites the easy way: a supervisor puts a box of uniforms in a van and tells the receiving site it is coming. Nobody logs the quantity. Nobody confirms it arrived in full. A week later the sending site’s stock count looks wrong. The receiving site insists they never got the missing items, and there is no record either way to settle it.
This is the same problem a per-location inventory system is built to prevent, but only if the transfer itself is logged, not just the stock levels before and after it.
Why it matters
Bulk stock sitting at the wrong site or quietly short at the site that needs it is an operational problem before it is a financial one: a site running low on uniforms or radios cannot cover a shift properly. A transfer form also protects both ends of the move. If a dispute comes up about what was sent versus what arrived, the form is the record, not someone’s memory of a phone call.
How it works in AVES
AVES tracks stock per location, with a minimum threshold set for each item at each site, so a site running low is visible before it runs out. Moving stock is handled as one of several defined actions: add, remove, transfer, send-to-location or return-to-main. Each of these actions is kept as part of the item’s movement history, not just a changed number.
A transfer between locations goes through an approval queue rather than updating silently: it is requested, then approved, before the stock levels at either site change. Where stock is issued to a named person rather than moved between locations, the system separately tracks an expected return date and the condition the item comes back in. A sync/reconcile endpoint keeps the recorded levels lined up with what a stocktake confirms is actually on site.
What a stock transfer form must record
- Origin location. The site or store the stock is leaving, so the sending location’s count can be reduced correctly.
- Destination location. The site or store the stock is going to, so it lands in the right place’s count, not just “somewhere else.”
- Items and quantities. Exactly what is moving and how much, matched against what each site actually has on its shelves.
- Transfer type. Whether this is a transfer between two locations or a send-to-location/return-to-main movement, since each affects stock levels differently.
- Approval status. Whether the transfer has been requested, approved or is still pending, since stock levels should not change until it clears the approval queue.
- Movement history entry. A record of the action itself, kept against the item, not overwritten the next time it moves again.
- Minimum threshold check. Whether the move drops the origin site below its minimum stock threshold, which should trigger a restock conversation before it becomes a shortage.
Common mistakes with stock transfers
- Treating a transfer like a casual favour between sites. If it is not logged as a transfer, the stock levels at both ends go out of sync the moment it moves.
- Skipping the approval step. Letting stock levels update before a transfer is approved means a mistaken or unauthorised move is already baked into the record.
- Mixing up transfers with issuing to a person. A transfer moves stock between locations; issuing an item to a named person is a different action with its own expected return date and condition. Recording one as the other breaks both histories.
- Only checking stock levels, never the movement history. A level tells you what is there now. The movement history tells you how it got that way, which is what you need when a dispute comes up.
- Letting a site run below its minimum threshold without transferring in time. The threshold exists to flag a shortage before a shift is short-staffed on equipment, not after.
Why a transfer form earns its place next to a spreadsheet
A spreadsheet can list what a site is supposed to have. It cannot show who moved what and when, or whether the receiving site actually confirmed the delivery. A transfer form exists precisely to close that gap: it ties a single movement to an origin, a destination, an approval and a receipt, so the record survives even after the supervisor who carried the box has moved on to something else. For a company running several sites with shared stock pools, that record is often the only thing standing between a clean handover and a finger-pointing exercise over missing uniforms.
Frequently asked questions
Is a stock transfer form the same as a gate pass? No. A transfer moves bulk stock between two sites or stores inside the inventory system. A gate pass covers items physically leaving through a site’s gate, with issue and return photos. If stock is crossing a site boundary through a gate, see our gate pass format guide.
Does a transfer need approval before stock levels change? Yes, in AVES a transfer goes through an approval queue. Stock levels at the origin and destination only update once the transfer is approved, not the moment it is requested.
What is the difference between a transfer and issuing stock to a person? A transfer moves stock between locations. Issuing stock to a person is tracked separately, with an expected return date and the condition the item comes back in, because the accountability sits with an individual rather than a site.
How does a transfer affect minimum stock thresholds? Each location has its own minimum threshold per item. A transfer that drops the origin site below its threshold should be visible immediately, so a restock can be arranged before the shortage affects a shift.
Can a transfer be reconciled against a physical count? Yes. The sync/reconcile endpoint lines up what the system recorded through transfers and other movements with what a physical stocktake actually finds on site. See our inventory reconciliation guide for how that check works.
Who should be able to approve a transfer? AVES does not fix this to one role; the approval queue is simply a required step before stock levels change. In practice, most security companies route approval to whoever is accountable for the receiving site’s stock, so the person confirming receipt is the same person confirming the count is correct.
Where stock transfers fit in your wider inventory operations
A stock transfer form is one part of the per-location stock picture covered in our inventory management software overview. It sits next to inventory reconciliation for checking that transfers landed correctly, and alongside the serialised-equipment tracking in our asset tagging software guide and the financial view in our fixed asset register guide. The same discipline of logging a move rather than assuming it happened is worth comparing with how AVES handles daily guard activity in the security guard logbook.
If your sites are moving bulk stock between each other without a shared record, book a 30-minute demo and we will show you the actual transfer request, approval queue and movement history screens.