Introduction
The Containers feature on the Ventory platform introduces a structured way to store, manage, and track products using containers. A container serves as a storage location for products or other containers, improving stock organization, transaction processing, and inventory visibility.
Key Features
1. Container Basics
A container is a storage unit for products or other containers.
Each container is assigned a Container Type (e.g., Pallet, Box) for categorization.
Containers can have custom fields that allow additional metadata to be stored.
A container can inherit custom fields from an order, provided the order custom field's entity child type is set to "Container."
2. Container Locations & Transactions
A container is generally stored in a bin within a stock location.
When a container is outbounded, it moves to a virtual bin, which is invisible to users.
A container in a virtual bin can be inbounded again into a physical bin.
Quick Actions, Order Processing, and Counting must now account for product locations within containers, not just bins.
3. Working with Containers in Orders
Inbound Orders:
Users can create containers on the fly and assign products to them.
Containers are automatically associated with the inbound order.
Outbound Orders:
Users select existing containers without needing to manually assign products.
The system automatically processes transactions for all products in the selected containers.
4. Container Transactions & Processing
Transactions related to a container can be processed individually.
If a container transaction is open (status: "Created"), the container is reserved (products cannot be added or removed until processing is complete).
5. Task Management with Containers
Users can create tasks based on Containers or Lots.
This allows counting or validation based on selected containers or the products within them.
Scanning and manual selection of containers is supported.
Common Questions & Issues
1. What is a Container Identifier?
It is a unique string that identifies a container, similar to a bin name or product number.
2. Where can I create Container Types?
Settings > Company > Advanced Settings > Container Types.
3. What are examples of Container Types?
Common types include Pallets, Boxes, Crates, etc.
4. Why do I need a Container Type before creating a Container?
This ensures proper categorization and tracking of containers within the inventory system.
5. What does "Delete on Outbound" mean?
If checked, the container will be deleted when processed in an outbound transaction.
If not checked (default), the container moves to a virtual bin for potential future use.
6. Why does a container move to a Virtual Bin after Outbound?
Some outbound containers remain within the company (e.g., reusable pallets). Keeping them in a virtual bin allows reusability.
7. Why can’t I select a container for an Inbound Order?
Possible reasons:
The container is already in a physical bin (it must be in a virtual bin to be inbounded).
There is an open product transaction for the container in another order.
8. How do Custom Fields propagate from an Order to a Container?
If a custom field is created for Entity Type: Order and Entity Subtype: Outbound, and the Entity Child Type is set to Container, then when the container is processed in that order, the custom field value is applied to the container.
9. What is a Parent Container?
A container that holds other containers or products.
Parent-child relationships allow grouped transactions (moving a parent container moves all child containers/products).
10. Do I need to select products when selecting a Container for an Outbound Order?
No, selecting a container automatically includes all its contents in the order.
The next step is for adding loose products (not inside containers).