sc_store_locations

In this article

• Summary
• Supported Use Cases
• When not to use the view

Summary

The sc_store_locations view serves as the central location for store location information.

• View Grain: Store-level information. Each record holds unique information related to stores.
• Primary (Composite) Key(s): 
  • scid
• Foreign Key(s): 
  • store_id
  • open_date/close_date

A store may not necessarily equate to a fulfillment location. As such, be careful when attempting to join sc_store_location to another view or table via store_id, as the other side of the join may refer to a fulfillment location or warehouse. Generally speaking, locations (or location_id values) in an orders dataset likely relate to specific stores (thus are compatible with the store_id in sc_store_locations), whereas locations (or warehouse_id values) in an order fulfillment dataset likely relate to fulfillment locations. These fulfillment locations may or may not be actual stores. 

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_store_locations and other tables and views. This list should not be assumed to be comprehensive.

• I am interested in understanding whether a particular store’s performance is due to its location or other factors.
• What is the impact of a region’s sales when a specific store closed, and how could that potentially impact our future store opening/closure decisions?

When not to use the view

This view is a dimensional view that enriches order data by providing more information about where purchases are made. Most non-spatial analysis is likely unsupported with just this dataset.

Return to SoundCommerce Retail Modules