Implementation Details:

Table of Contents

Jell-O Shot – This is a type of transfer created by R2 to send inventory back to the owner site. System will create a transfer automatically based on user defined defaults.

Jell-O Shot rule – During the batch return process, if an asset is scanned that does not belong to current site (scanned branch) and it has no planned return, it will be placed on the transfer (Jell-O Shot). The asset will not be available to current site but will show as available based on the transfer receive date. Following criteria will be used to place the item in Jell-o Transfer...

1. Scanned item does not belong to the site, where it is scanned (Owner & Current sites are different)

2. Item is not on any Return Transfer from scanned site to owner site

3. Item is not on any Transfer Order, which is target to a different site

How Jell-O Shot rule works?

When R2 observes that the scanned item follows the Jell-O Shot rule, system looks for whether that asset is on any Return Transfer from current site. If nothing is fount, system will check if the asset is on any other transfer. If the item is found (Some other site to Owner Site), the transfer will be canceled and the item will be added to open Jell-O Shot.

How Jell-O Shot Transfer Order created?

When Jell-O shot criteria is met and there is no open Jell-o Transfer, R2 will create a transfer with Type as Jell-O Shot. The dates and other shipping information will be defaulted from Jell-O Shot configuration.

Exceptions -

1. Even when the Jell-O Shot rule is met, R2 will not create the Transfer if... the scanned asset is already prepped on any Order or Transfer Order.

2. If Force fill is used to prep an item that is already in Jell-O Shot, the force fill will fail.