{"section":"tutorials","requestedLocale":"en","requestedSlug":"inventory-data-pipeline-beta","locale":"en","slug":"inventory-data-pipeline-beta","path":"docs/en/tutorials/beta/vtex-data-pipeline-beta/inventory-data-pipeline-beta.md","branch":"main","content":"The inventory dataset is composed of two tables: `item_inventory` and `warehouses_latest`. Together, they provide information about item availability, reservations, stock configuration, account metadata, and warehouse attributes.  \n\nThis section includes the following information:  \n\n- [Inventory data characteristics](#data-characteristics)\n- [Table: item_inventory](#table-item_inventory)\n- [Table: warehouses_latest](#table-warehouses_latest)\n- [Analyses with inventory data](#analyses-with-inventory-data)\n- [Correlations with other data](#correlations-with-other-data)\n\n## Data characteristics\n\n| **Characteristic** | **Description** |\n|:---:|:---:|\n| **Data source** | Obtained from information in the logistics module. |\n| **Availability** | VTEX Admin. |\n| **History** | We have made historical data available since June 2022. For customers who already use the VTEX platform, data is retained for two years starting in 2024. |\n| **Minimum update interval** | One hour. |\n\n## Table: item_inventory\n\nThe table fields are described below:\n\n| **Column Name**| **Column Type**| **Description**|\n|--------|------------|---------------|\n| main_account | character varying(200) | Name of the merchant's main account. Identifies the top-level VTEX account that the store/entity belongs to. |\n| account_name | character varying(200) | Name of the account to which the inventory belongs. Together with `warehouse_id` and `item_id`, it uniquely identifies an inventory record. |\n| warehouse_id | character varying(400) | ID of the warehouse where the stock is located. |\n| item_id | character varying(300) | Identifies the item whose stock is being quantified (SKU ID). Part of the natural key for the inventory record. |\n| is_unlimited_quantity | boolean | Indicates whether the item can have infinite stock (`true`) or not (`false`). |\n| quantity | bigint | Total quantity of items in stock for the item in the warehouse (physical quantity). |\n| reserved_quantity | bigint | Number of active reservations for the item. |\n| last_update | timestamp without time zone | The last time this specific item stock was updated. |\n| parent_account_name | character varying(200) | Name of the parent account. It is the topmost account in the hierarchy; it falls back to `main_account` when parent data is unavailable. |\n| batch_id | character varying(13) | Identifies the last ingestion batch that updated this row. Used for traceability and data quality. |\n| record_created_at | timestamp without time zone | Timestamp when the record was first inserted in the Lake House. |\n| record_updated_at | timestamp without time zone | Timestamp when the record was last updated in the Lake House. |\n\n## Table: warehouses_latest\n\nThe table fields are described below:\n\n| **Column Name**| **Column Type**| **Description**|\n|--------|------------|---------------|\n| warehouse_id | character varying(100) | Identifier for the warehouse. |\n| warehouse_name | character varying(200) | Warehouse name as defined in Admin. |\n| account_id | character varying(38) | Identifier for the account. |\n| account_name | character varying(100) | Account name. |\n| is_active | boolean | Indicates whether the warehouse is active. |\n| warehouse_docks | super | Docks linked to the warehouse. |\n| pickup_point_ids | super | Pickup points linked to the warehouse. |\n| priority | integer | Tiebreaker criterion used when warehouses have the same route score. |\n| is_deleted | boolean | Indicates whether the warehouse was deleted. |\n| record_created_at | timestamp without time zone | Internal log of when the warehouse entity was first created. |\n| record_updated_at | timestamp without time zone | Internal log of when the warehouse entity was last updated. |\n| parent_account_name | character varying(50) | Name of the parent account. It is the topmost account in the hierarchy; it falls back to `main_account` when parent data is unavailable. |\n\n## Analyses with inventory data\n\nSome of the analyses that can be run using inventory data are listed below:\n\n- **Inventory level analysis:** Assess whether the inventory meets demand and identify items at risk of running out of stock.\n- **Inventory reservation trends:** Analyze the number of items that have been reserved over time to identify patterns and adjust inventory management strategies.\n- **Inventory distribution analysis by account:** Optimize inventory management across multiple accounts and understand how inventory is distributed.\n\n## Correlations with other data\n\nInventory data correlates with order and product sets, and provides a more comprehensive analysis for purchases, sales, and marketing. Some examples are: \n\n- **Interaction with order data:** Joint analysis with order data offers insights about how efficiently is customer demand being met and helps forecast restocking needs.\n- **Relationship with SKUs:** Integration with SKU data helps manage inventory based on product popularity and availability.\n- **Purchase and supplier data:** Coordination with purchase data allows you to maintain an ideal inventory balance, which avoids overstocking or shortages.\n- **Sales and marketing analysis:** Understanding inventory directly impacts marketing and sales strategies, which allows aligning promotions and campaigns with product availability.\n\n### Discover other Datasets\n\n- [Navigation](/en/docs/tutorials/navigation-data-pipeline)   \n- [Payments](/en/docs/tutorials/payments)  \n- [Orders](/en/docs/tutorials/orders-data-pipeline-beta) \n- [Prices](/en/docs/tutorials/prices-data-pipeline-beta)\n- [Promotions](/en/docs/tutorials/promotions)\n- [Gift cards](/en/docs/tutorials/gift-card-data-pipeline)\n- [Bridge logs](/en/docs/tutorials/bridge-logs-data-pipeline)"}