---
description: Here we explain how the transfer process works and where data comes from.
---

# Manage Transfers Bunches

UNOSOF contains great tools to manage transfers with, but for successful results its a must to have clear policies and processes in place. Without that, transfers are extremely difficult to manage. Here we shall explain how transfers work in UNOSOF, what factors are involved and we shall give you some tips for efficient results.&#x20;

{% hint style="info" %}
The physical inventory HAS to match the digital inventory. Before you start with transfer management, make sure that you fully control your inventory well.&#x20;
{% endhint %}

## Transfer definition

### **Single RUC vs Multi-RUC transfers**

Practically it should not matter if you transfer units within the same RUC or between Multiple RUC's, however technically it makes a big difference and it's important to understand why. Each RUC has its own database with its own barcodes. Therefor making a transfer of units within the same database is different than transferring units between two RUC's (different databases).&#x20;

Single RUC: we can work with the same barcode and no remote calls to other databases are a need for reporting. \
\
Multi-RUC: we exit the barcode from the database where the units leaves from and we reenter this barcode automatically at the new location (new database). Remote calls are a need for reporting.&#x20;

### Process location and Packaging location.&#x20;

A process location, is where you process the bunches. \
A packing location, is where you pack the bunches in boxes.\
\
The process- and packing location get chosen in our purchase order (PO) page. These locations are very important to choose well, based on where the product is available. When the bunches are been processed (live inventory), you can analyze quickly where you should pack the box. \
\
However its more difficult to choose your packing- and process location when you place a pre-book or standing orders, this requires a deeper analyze into the future availabilities to where the product shall be availabe at. UNOSOF realizes that new tools need to be developed to make those kind of decisions fast and easy, with accuracy.&#x20;

{% hint style="info" %}
Analyze our future availability page at least once a week. Anticipate your needs, see where you need the flowers at the right time, at the right place. Don't wait till the day of delivery. &#x20;
{% endhint %}

Lets learn more about process- and packing locations. When you build a purchase, you select from the "live inventory" or via the "product list" the bunches you'd like to sell, this decides the process location. \
\
In this example each process location (FM and San Enrique) have to process 4 bunches.&#x20;

![Process location](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0JOeyzHzdFZ2DaTIOW%2F-M0JYkKYK8aqp8IAJEY8%2FScreen%20Shot%202020-02-17%20at%201.14.44%20PM.png?alt=media\&token=e1bfaf68-f592-4346-be95-f231f3309134)

Here we explain how you select your packing location, where you decide to pack the box. In this example we decide to pack 8 bunches at San Enrique.&#x20;

![Packing location. ](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0JOeyzHzdFZ2DaTIOW%2F-M0JYtVYVHRxMGpgP-cm%2FScreen%20Shot%202020-02-17%20at%202.09.51%20PM.png?alt=media\&token=60da2efa-72bf-4a8e-9123-b64c20cd8cfd)

#### Before processing bunches:

The PO request generates the following inventories: **Farm Processing Dispo**. There we indicate that each postharvest has to process 4 bunches.

![Process location -4 and -4](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0Sr8TmcTW50PYvyFAt%2F-M0SrokMjg7IGUt7aSay%2FScreen%20Shot%202020-02-19%20at%209.34.23%20AM.png?alt=media\&token=7d0b6c31-fe7a-4d58-85fd-8c6c9b245df8)

On the other side we have the request to pack the box at San Enrique. that we inventory we call: **Bodega Packing Dispo**. We show that San Enrique needs 8 bunches to pack.&#x20;

![Packing location -8](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0Sr8TmcTW50PYvyFAt%2F-M0StpaeLkqINaxE_Lu2%2FScreen%20Shot%202020-02-19%20at%209.43.12%20AM.png?alt=media\&token=a2b48b88-e521-411d-9bb7-adc27dc6406f)

#### After processing bunches:

If the bunches are being processed by the post-harvest via station 2 (S2), the **Farm Processing Dispo** inventory shall look as follows:&#x20;

![Process location 0 and 0.](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0JOeyzHzdFZ2DaTIOW%2F-M0JpVXvuZf8uTaYHhNw%2FScreen%20Shot%202020-02-17%20at%203.26.51%20PM.png?alt=media\&token=b35519da-8a57-4330-8654-117eed409223)

However, eventhough the bunches are all being processed, we cannot pack the box yet. 4 bunches shall have to be transfered to the other location in order to complete the need. This we visualize in the **Bodega Packing Dispo** as follow&#x73;**:**

![Packing location -4 and +4](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0JrZaG210TyRIwZDBA%2F-M0JtdVVEkOAQcWm64OJ%2FScreen%20Shot%202020-02-17%20at%203.45.11%20PM.png?alt=media\&token=7ee63e98-1e80-4e2a-8b53-2d60bb747b95)

Sales works with an inventory page that does not contain any balance left to sell. This inventory is based on the process location balances.&#x20;

![Inventory view on purchase order page.](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0JrZaG210TyRIwZDBA%2F-M0Js5j8QcFqShIL60R7%2FScreen%20Shot%202020-02-17%20at%203.38.47%20PM.png?alt=media\&token=fe750983-7b7e-40ed-b56f-9547eb6ff282)

Because the bunches are physically not at the location to pack the box with, we do not allow to confirm the box. This avoids that the box sticker can get printed, and this avoids that the "sortidor" would look for flowers to pick that don't exist physically at the packing location in the coldroom.&#x20;

![Box confirmation page](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0JrZaG210TyRIwZDBA%2F-M0Jv8e8DmRGILcSCMKw%2FScreen%20Shot%202020-02-17%20at%203.47.43%20PM.png?alt=media\&token=34f163eb-d529-42ef-91d3-1fb89767cc24)

{% hint style="info" %}
The priority box confirmation page is based on **packing location**. \
Until the 4 units are not been transferred, the box cannot be confirmed to pack.&#x20;
{% endhint %}

### Transfer Bunches

To transfer bunches from one location to another location we use the following module and pages.

![Transfer Module](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0SvdCGFp3AAdmFi29d%2F-M0SwZPjgrZtwaB98pSv%2FScreen%20Shot%202020-02-19%20at%209.54.43%20AM.png?alt=media\&token=b2efc5bf-e8ec-4a73-8688-1eaaf27f4177)

#### Manage Inventory Transfers.

Go to: Inventory > Transfer Inventory > Manage Inventory Transfers

Here we show which bunches (SKU by aging) need to be transferred, and to which packing location.&#x20;

![](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0SxT7oiKH2R-G13gZY%2F-M0T5TbcS3eRv75Vgfa3%2FScreen%20Shot%202020-02-19%20at%2010.11.52%20AM.png?alt=media\&token=e45952d7-61fc-4c63-95f7-c57d61bdafc2)

{% hint style="info" %}
Separate the bunches that you wish to transfer from the general inventory by placing them phiscally at a marked spot in the coldroom.&#x20;
{% endhint %}

#### Send Transfer Scan by ID

Go to: Inventory > Transfer Inventory > Send Transfer Scan By ID

Time to scan the bunches out of inventory and to put these bunches in-transit status. This process will exit the bunches out inventory.&#x20;

![Send Bunches to another packing location.](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0SxT7oiKH2R-G13gZY%2F-M0T85YmdH4Jxzmt9vX_%2FScreen%20Shot%202020-02-19%20at%2010.48.32%20AM.png?alt=media\&token=f14853c0-b4e9-4f61-8d6f-e486984267e3)

{% hint style="info" %}
We recommend to scan the bunches out of inventory to transfer inmediatly after you placed them in the marked spot in the coldroom. Eventhough those bunches leave hours later with the truck the coldroom, the scan avoid that sales will sell those bunches while they wait to get transferred.&#x20;
{% endhint %}

#### Bunches In-Transit

Go to: Inventory > Transfer Inventory > Manage Inventory Transfers

Here you have to select the report **View Inventory In-Transit** and hit search. This report shall present you a list of all the bunches that are been exited from the original location and that have not arrived yet at the transfer location.&#x20;

![In-Transit Inventory](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0SxT7oiKH2R-G13gZY%2F-M0TAFkf3Z1xNFecwt3m%2FScreen%20Shot%202020-02-19%20at%2010.56.26%20AM.png?alt=media\&token=ca08d347-69af-4e94-a506-4b1dde1523d0)

This list scrinks when bunches are being scanned as **received** or when bunches never arrived and get **returned** to its original location. You scan all the phisical bunches as received when the truck arrives with the bunches being transfered. Any bunch that was scanned out of inventory, but that never got arrived, has to be returned to its original location.&#x20;

Hit the red button RETURN to sent the bunch back .This you only do, if the bunch was never received.&#x20;

![Red button, Return. ](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0SxT7oiKH2R-G13gZY%2F-M0TCq7P9gTSR6NjjeEw%2FScreen%20Shot%202020-02-19%20at%2011.10.32%20AM.png?alt=media\&token=f69b8009-e640-4d9f-8859-40aecaea6aa7)

{% hint style="warning" %}
&#x20;We recommend to clean this list every day. If bunches were not received, those bunhces need to get returned. Document and communicate well internally all the bunches that get returned.&#x20;
{% endhint %}

While the bunches are In-Transit, we show this status also in the View Inventory Packaging List.

![Yellow Lines, bunches in Transit.](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0SxT7oiKH2R-G13gZY%2F-M0TD8DrVzlQvSk8l7SI%2FScreen%20Shot%202020-02-19%20at%2010.55.45%20AM.png?alt=media\&token=66a8e393-ba33-41a3-962a-924b92846592)

#### Receive Transfer By ID

Go to: Inventory > Transfer Inventory > Receive Transfer By ID

Once the bunches arrive at the packing location, the bunches shall need to get received via the following page:

![](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0SxT7oiKH2R-G13gZY%2F-M0TEt6DZ9-MgET8td5R%2FScreen%20Shot%202020-02-19%20at%2011.16.34%20AM.png?alt=media\&token=285a5c3d-c9a6-4e6e-bb01-41c9c7f837b1)

If your scan pistol is broken, its also possible to receive by clicking the green RECEIVE button in the **View Inventory In-Transit** page.

![](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0SxT7oiKH2R-G13gZY%2F-M0TCq7P9gTSR6NjjeEw%2FScreen%20Shot%202020-02-19%20at%2011.10.32%20AM.png?alt=media\&token=f69b8009-e640-4d9f-8859-40aecaea6aa7)

{% hint style="warning" %}
We recommend to scan the received bunches inmediatly on the moment of arrival. This shall add the bunches to the inventory and provides the possibility to confirm the boxes for packing and/or to sell those bunches.&#x20;
{% endhint %}

{% hint style="info" %}
For efficiency we recommend to anticipate the transfers for the Standing orders and Prebooks as much as possible. The need is known days in ahead of time, don't wait untill the day of delivery to transfer those bunches. For (pre)-packing the boxes, the bunches need to be at the packing location.&#x20;
{% endhint %}

{% hint style="info" %}
For efficiency we recommend to apply a time limit policy to transfer bunches. Its not good to sell bunches that need to get transfered, after the limit passed. This causes organizational problems, time delays and in the worse case you have to brake your promise torwards your client.&#x20;
{% endhint %}

{% hint style="danger" %}
NEVER hit the button RECEIVE on the **View Inventory In-Transit** page if the bunches phiscially have not arrived yet.
{% endhint %}

### Force transfers from sales or not?&#x20;

What do forced transfer mean? Lets go back to our example, the need is to have 8 bunches at the packing location and each farm has to process 4 bunches.&#x20;

![Process location -4 and -4.](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0Sr8TmcTW50PYvyFAt%2F-M0SrokMjg7IGUt7aSay%2FScreen%20Shot%202020-02-19%20at%209.34.23%20AM.png?alt=media\&token=7d0b6c31-fe7a-4d58-85fd-8c6c9b245df8)

![Packing location -8.](https://4099088335-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M-BV4YRkYBYw5A4UAJL%2F-M0Sr8TmcTW50PYvyFAt%2F-M0StpaeLkqINaxE_Lu2%2FScreen%20Shot%202020-02-19%20at%209.43.12%20AM.png?alt=media\&token=a2b48b88-e521-411d-9bb7-adc27dc6406f)

Its possible that each farm processes 4 bunches, that we process the transfer and that we complete the need of 8. But its also possible that San Enrique processes the total need of 8, because they have the same variety and they "over processed" the need of 4 bunches. The question is then, do we still transfer 4 bunches over from FM to San Enrique, or not. This we call: Do we force transfers from sales, or not.&#x20;

At some farms we applied forced transfers, this means that whatever is been defined in the PO page, we followup up on the transfer page. But its also possible to not force the transfer and to let UNOSOF Auto-Calculate if the transfer is needed or not. At single-RUC transfers, both options are possible: Forced and not-forced. However if the transfer is done between two RUC's, we can only apply the forced transfer method.

### Transfer for processing or packaging?

In case of transfering bunches, we always transfer for packing location purpuse. However its also possible to transfer mallas, that always has a process location purpuse. This process we explain in the following section of this manual:

{% content-ref url="manage-transfers-mallas" %}
[manage-transfers-mallas](manage-transfers-mallas)
{% endcontent-ref %}







&#x20;



