CloudScaff questions and answers
Transfers yards and supplier stock
Answers to 10 questions about transfers yards and supplier stock.
10 questions
Questions in this topic
10 answersCan we transfer equipment directly between sites?
Yes. Site-to-site transfers let you record equipment moving from one project to another without routing it through the yard in the system.
The transfer should identify the sending site, receiving site, components, and quantities. Completing the appropriate handoff keeps both site balances aligned with the recorded movement and provides a trail if a later return needs investigation.
Does a site transfer need a request from the receiving site?
The transfer process can begin from the operational need to move equipment, including a move initiated by the sending side. Configure the process around who is authorised to create and complete the transfer.
Even when the receiving site did not request it, the movement still needs a clear destination and an accurate quantity. Avoid treating informal borrowing as an exception that never reaches the stock records.
Can the receiving team acknowledge a transfer?
Yes. Transfer workflows can include the receiving side of the handoff. This helps distinguish equipment intended for another site from equipment actually accepted there.
Train both ends of the process. If a transfer is created but not completed, review its status before assuming the stock is available at the destination or missing from the origin.
Can we move equipment between yards?
Yes. Yard-to-yard transfers record stock moving between storage locations. This helps each yard retain a meaningful local balance while supporting a wider view of the operation.
Use the transfer process for a real movement. Simply increasing one yard and decreasing another through unrelated edits can make the physical handoff harder to trace later.
Can each yard have its own stock view?
Yes. Stock can be viewed by location so the team can distinguish local availability from equipment held elsewhere in the business.
This matters when head office sees a large overall quantity but a particular branch cannot fulfil an order. The location-level view helps identify whether the solution is a transfer, a return from site, or a new supply arrangement.
Explore our multi-yard management features.
Can one site receive equipment from several yards?
Yes. A project can receive stock from multiple source locations. Maintaining the source detail helps your team understand how the site was supplied and investigate later returns or discrepancies.
For mixed loads, check the component and source combinations carefully. Two identical-looking items may still need to remain distinguishable in the records because they came from different yards or suppliers.
Can we track equipment hired from another supplier?
Yes. CloudScaff supports cross-hired supplier stock. This helps you track third-party equipment alongside your own stock while retaining the supplier context.
Set up the supplier and item records carefully so equipment is not mistaken for company-owned inventory. Your team should be able to identify what came from the supplier, where it was allocated, and what still needs to be returned or reconciled.
Can a delivery contain both owned and cross-hired equipment?
Yes. A delivery can be prepared using the relevant stock sources. This supports jobs where part of the requirement comes from your yard and the remainder is supplied through cross-hire.
Keep the source and quantities accurate on each line. The distinction is useful when returning equipment and reviewing supplier exposure, even when the components serve the same purpose on site.
Can supplier equipment be tracked even if we do not own that item type?
Supplier equipment can be represented in the catalogue and associated with the appropriate source. You do not need to treat it as company-owned stock simply because it is needed on a project.
Confirm the item details and ownership context during setup. If several suppliers use different names or codes for similar equipment, agree how those differences will be represented before creating movements.
Are multiple yards and multiple branch accounts the same thing?
No. Multiple yards are storage locations within an operation. Separate branch accounts may be appropriate where branches need independently managed data or account access.
Discuss the structure before migration. Consider shared stock, cross-branch transfers, user access, reporting, and commercial requirements. An account-switching arrangement should not be assumed to provide every form of consolidated group reporting without checking the intended report.
No matching questions. Try another search or topic.