Inventory Management feature overviewEdit on GitHub
Thr Inventory Management feature refers to warehousing and managing your store’s stock. In this context, a warehouse is the physical place where your products are stored, and stock is the number of products available in the warehouse. See Warehouse management and Stock management for details about how to manage them. Stock does not always reflect the real availability of products, as not all the items available in stock are available for sale. For example, if items are reserved, that is, there are pending orders with these items, they can not be ordered, even though physically, they are still in stock. The value that reflects the difference between the current quantity of products in stock and the quantity of these products in the pending orders, is referred to as the availability of products. The availability is calculated per store. For details about how to manage availability, see Availability management.
A warehouse can be assigned to a single store or shared between several stores. For the warehouse and stock management scenarios you can set up for your project, see Managing stocks in a multi-store environment: Best practices. You can manage relations between stores and warehouses in the Back Office or by importing the warehouse and store data. For details about how you can manage warehouses and stores in the back office, see Managing warehouses. For details about how you can import the warehouse and store data, see File details: warehouse_store.csv.
Defining a warehouse address
You can define the warehouse address that will be used as the shipping origin address by importing the warehouse address data. For details about the import file, see File details: warehouse_address.csv.
Warehouse assignment to order items (with Avalara integration only)
By default, a warehouse is not linked to a sales order item. The logic described below applies only when Avalara is integrated into your project. That is, it is used to get warehouse addresses to calculate taxes in the USA.
During the checkout, once a buyer entered delivery addresses for all order items, be it a single delivery or a split delivery, the order items are assigned to warehouses to fulfil them.
By default, if a buyer orders several items of the same SKU, the requested item’s stock is checked in all the warehouses of the store. Based on the item stock, the warehouses are sorted in descending order, for example:
- Never out of stock
- 1000 items
- 999 items
- 2 items
- 0 items
If the requested quantity of the item is available in the first warehouse, that is, the one holding the biggest stock of the item, this warehouse is assigned to fulfill the order item.
The warehouse with the never out of stock item quantity is always assigned to the item.
If the first warehouse’s stock is insufficient to fulfil the order item, this warehouse and the next one is assigned to the order item to fulfill the remaining quantity.
Schematically, the process looks like this:
When order is made, stock is not updated automatically in the system, you have to set it manually. You can define stock only for concrete products. You can set stock by:
- Editing product stock in the Back Office. For details, see Editing stock.
- Importing the quantities of items stored in each of the warehouses. For details, see Stocks.
In contrast to stock, availability considers not just the number of products in the warehouse but also current open orders.
When a buyer places an order, the products in the order become reserved, and the product availability changes. The changes are reflected in the Back Office: The availability is equal to the stock before the order is placed, and after the order is placed, the availability decreases, but the stock remains the same.
Product availability before the order:
Product availability after the order:
For details about how you can check product availability in the Back Office, see Checking availability.
Availability of a product bundle is defined by the availability of each product in the bundle. If at least one of them is out of stock, the entire bundle is unavailable.
In the state machine, a developer can use the
reserved parameter to define the states at which the order items are reserved. There can also be states that release an item. For example, when payment fails and order is cancelled, the item is not reserved anymore:
State machine example
For SEO purposes, products that are not available can still be displayed on the Storefront with the inactive Add to cart button.
Related Business User articles
|BACK OFFICE USER GUIDES|
|Create a warehouses|
|Manage product availabilities|
Are you a developer? See Inventory Management feature walkthrough for developers.
For submitting the form