Farm-to-farm stock transfers

What this action helps you do

Send stock to another farm transfers a quantity from one farm’s physical batch to a different farm in the same Farmlync organisation. Use it for real redistribution, such as moving feed or supplies to cover a shortage. It reduces the source balance and creates a new batch at the destination while retaining traceability.

Use Move stock within this farm when stock remains on the same farm. Use Stock takes for a measured difference between Farmlync and the shelf. Do not use an inter-farm transfer to correct a count.

Prepare both farms

Before opening the action, confirm all of the following:

• source and destination are active farms in the same organisation;
• you have inventory-management permission on both farms;
• the source batch is Available, has not passed its farm-local expiry day and has enough unreserved quantity;
• the destination already has an active product with the same product code as the source product; and
• the quantity and physical transport have been agreed.

The matching code is deliberate. Farmlync will not silently create a destination product because deciding that two catalog entries represent the same item is a catalog-management decision. If the destination is missing the product, switch to that farm and adopt or create the correct catalog item first.

Open the transfer

Open Product detail or Stock Batches on the source farm and choose Send farm, Send to farm or Transfer for the required batch.

The Send stock to another farm panel identifies:

• product name;
• batch number, or a dash if none was recorded;
• available quantity after reservations; and
• unit cost when it exists.

Farmlync prefills Quantity with the full available balance, which supports the common “move everything available” case. Review this value before saving a partial transfer.

Complete every control

Control	Accepted value and effect
Destination farm *	Required farm from the first 100 active farms available to this account, excluding the current farm. Type in the picker to find a displayed option. It must belong to the same organisation and contain an active product with the source code shown below the control.
Quantity *	Number greater than zero, up to the batch’s displayed available quantity, with a 0.01 input step. Reserved stock is excluded from the maximum.
Transfer date *	Required farm-local date; defaults to today. Enter the date the physical transfer applies.
Reason	Optional, up to 200 characters. State the business reason, for example redistribution or shortage coverage.
Notes	Optional, up to 500 characters. Record transport, handover or other internal audit context.

Cancel closes the panel without moving stock. While Send to farm is processing, the controls remain locked to prevent a second submission.

What Farmlync saves

The source deduction and destination receipt commit together. A failure cannot leave one farm changed while the other is unchanged.

On the source farm, Farmlync:

• deducts the quantity from the selected batch;
• marks the source batch Depleted if the full remaining quantity left;
• writes an outgoing Transfer movement dated with the selected transfer date; and
• includes the transfer reason and notes in its audit text.

On the destination farm, Farmlync:

• finds the active product with the same code;
• uses the destination’s active default stock location, creating the standard default location if that farm has none;
• creates a new received batch for the transferred quantity;
• retains the source lot number, supplier details, supplier reference, expiry date, unit cost and semen-sire metadata when present; and
• names the new batch with the source batch number plus -T, or generates a transfer batch number when the source had none.

The destination’s incoming history is derived from that received batch and appears as a Receipt in Stock movements. The source history shows the outgoing Transfer. The current data model does not create a second destination Transfer transaction row, because that would count the receipt twice.

Verify the result

After the success message:

1. On the source farm, open the product and confirm the new available/on-hand balance.
2. Open Stock movements and filter to the product and date; inspect the outgoing Transfer reason and notes.
3. Switch to the destination farm.
4. Open the matching product and confirm the new -T batch, inherited evidence, default location and received quantity.
5. Check the destination ledger for the incoming Receipt.
6. If stock is physically stored somewhere other than the default location, use Move location at the destination to preserve a separate location-movement trail.

Understand refusals and retry safely

Farmlync refuses the transfer when:

• source and destination are the same farm;
• the destination is missing, outside the current organisation or not permitted for this user;
• inventory-management permission is missing on either farm;
• the source batch is expired, quarantined, otherwise unavailable or changed while the form was open;
• the requested quantity exceeds the current unreserved balance; or
• the destination product code is absent or inactive.

If the source changed concurrently, close the panel, reload the batch and review the latest quantity before trying again. The request uses a stable operation identity for safe submission retry; after a visible success, verify both farms instead of pressing the action again.

Operational cautions

• Farmlync records the stock and audit effects; it does not manage the vehicle, chain of custody or external transport document.
• The destination location is not selected in this form. The new batch initially uses that farm’s default location.
• Cost and expiry evidence follows the stock. Confirm those inherited values against the physical package at handover.
• A catalog code is the cross-farm product match. Correct code governance before transferring stock between large farm estates.