Differentiating Virtual Package and Non-Serialized Model with Accessories
In our setup we have a Virtual Package called "Sound System" which contains consoles, speakers, cabling etc as children. We also have Non-Serialized Models like amp racks that contain amplifiers as children.
Both the sound system and amp rack appear the same on the pull sheet, so how do we properly communicate to our warehouse staff that the sound system is a collection of the elements listed in the dropdown and the amp rack is a stand alone case?
Related to this, we have some cases that have a mix of accessories that live within the same case/rack and on their own. For example, we have a rack that contains a RIO, amp, and drawer of accessories; but we also have Cat5 snakes that are packaged separately but are organized as children of the RIO rack. So how do we communicate that the RIO/amp/drawer all live in the same case whereas the snake is on its own when they're all listed the same on the pull sheet? I could list the snake as a next-sibling, but it is convenient to have as a child of the RIO so that if the RIO is removed from the pack the snake isn't left behind.
-
Official comment
Hey Brian,
Thank you for reaching out, and your question is very insightful. Allow me to direct you to a comprehensive video that provides an overview of our inventory structure and availability. Specifically, at the 7-minute and 40-second mark, you'll find an example featuring an amp rack.
Regarding your inquiry, it appears that your Virtual Package is functioning as intended. Thus, I'll focus on optimizing the settings for downstream packages. There are several approaches to designating a package as a child, and I recommend configuring the amp rack case as your "Serialized Package." This setup allows for the inclusion of permanent "contents," such as amplifiers, within the rack. Subsequently, you can either incorporate the amp rack into the suggestions for the Sound System or, if it's already listed on the pull sheet independently, simply drag the amp rack package into the Sound System. Flex will recognize this association as specific to the job, without affecting global settings. Additionally, employing a serialized package for this purpose streamlines the workflow for your warehouse team, as they need only scan the case barcode, and Flex will automatically include all inventory items within that case in your manifest.
For your RIO rack and snakes, I recommend a similar approach: designating the RIO rack as a serialized package and, in turn, suggesting a serialized storage (e.g., snake case) with the snakes listed as "contents" of that case.
If you find that you or your team could benefit from further assistance, feel free to contact us at training@flexrentalsolutions.com, and we'll be happy to arrange personalized one-on-one training sessions for you!
Jacob Wise - Training Specialist
Comment actions -
Hey Brian Smith,
Another factor potentially influencing Flex's behavior could be related to your Suggestion Types. Navigate to Inventory > Suggestion Types and examine the "Association Type" for the Amp Rack, currently set to "Use Default Sorting Method." By changing this to "As Child," you'll seamlessly integrate this item into the Sound System as a component included within it.
Jacob Wise - Training Specialist
Please sign in to leave a comment.
Comments
2 comments