In this article
Summary
The sc_inventory_by_location view is the centralized place for order-inventory information by store or fulfillment location. In this view, you will find granular information about SKU inventory at your company’s stores and/or fulfillment locations. This view will also provide you with product information for items in stock to help aid in cost analysis.
- View Grain: Location and SKU (Stock Keeping Unit of item) - level information. Each record holds unique information on sku at a specific location and gets updated over time.
- Primary (Composite) Key(s):
- uid
- sku
- location_id
- Foreign Key(s):
- common-sku
The sc_inventory_by_location view is time-based. Metrics cannot support all aggregations at the time level (i.e., averaging is acceptable, but summing is not). The metrics included in this view include a point-in-time record for product quantities and cost for inventory and cost management. The location_id and SKU fields can be used to relate this view with the rest of the SoundCommerce data model.
Supported Use Cases
The following use cases are examples and only provide a subset of all potential use cases that can be addressed with data found in sc_inventory_by_location and other tables. This list should not be assumed to be comprehensive.
- I am interested in understanding inventory levels and availability in my distribution centers and how that compares with my store fulfillment locations. This can help me support sales campaigns and provide insight into inventory stock-out and procurement timelines.
When not to use the table
This view contains data on fulfillment location inventory levels across all locations in your network. As such, the data collected in this table may have some limitations. Notably, certain types of aggregations are not supported with this dataset. For example, summing inventory levels across days will provide inaccurate inventory levels over a given period. Take caution when joining this view with other views in SoundCommerce to avoid duplication or inaccurate aggregations. This view does not necessarily contain specifics about the following:
- Campaign-related metrics (i.e., clicks, impressions, conversions)
- Fulfillment-related metrics (i.e., shipment partner, tracking number, fulfillment breakdown of constituent items)
- Customer PII-related values (i.e., first and last names, emails, phone numbers, addresses)
- Order-related metrics (i.e., sales, profitability)
Return to SoundCommerce Retail Modules
Comments
0 comments
Please sign in to leave a comment.