# Retail Store Performance

**Retail Store Performance** brings together **all available retail POS and wholesale data** at the **native market granularity** provided by each source—store/door, DC/warehouse, region/DMA, banner/retailer, or corporate total. The explore preserves each source’s grain and enables blended roll-ups for consistent analysis.

**Examples of source granularity**

* **ULTA**
  * **ULTA Portal:** Total-corporate–level POS with full history for long-horizon trends.
  * **ULTA EDI:** Store-level POS beginning on the data-setup start date. Use this for door-level analysis that does not require full historical coverage; long-horizon trend completeness accrues as the pipeline runs (e.g., 2+ years). EDI store-level weekly sales also supports downstream weeks-of-supply calculations.
* **Sephora**
  * Mixed granularity depending on feed: some corporate/region aggregates and some store-level by door.

***

### What’s Included

#### 1) POS Sales Performance

Retailer-provided sales by door (e.g., Walmart, Target, Sephora, Ulta, Kroger) at a weekly cadence, including:

* **Dollar Sales**
* **Unit Sales**
* **Stores Selling**
* **Avg Weekly $ per Store Selling per Item ($/S/W/I)**
* **Avg Retail Price (ARP)**
* **Baseline / Incremental / Promo / Non-Promo Sales Volume** *\* (calculated)*

#### 2) Wholesale Performance

Internal shipment (“sell-in”) and distributor/partner sales or depletions (“sell-through,” when provided) are integrated alongside POS to complete the picture at the door, DC, region, and account levels. This supports operational alignment between what was shipped, where it landed (DC/Warehouse or store allocation), and how quickly it is selling through. Key metrics include:

* **Wholesale Dollars** – revenue booked on wholesale shipments
* **Wholesale Units** – units shipped to wholesale partners
* **Wholesale Cases** – case-level volume (computed from item master case packs where available)

#### 3) Store & Geography Dimensions

* **Store ID / Store Name**
* **Retailer**
* **City, State, ZIP**
* **Region / DMA**
* **DC/Warehouse** (Wholesale / Distributor data-specific)

### Key Metrics & Dimensions

<table><thead><tr><th width="199.4296875">Name</th><th>Definition</th><th width="110.76953125">Type</th></tr></thead><tbody><tr><td>Sales Dollars</td><td>POS revenue by store and week</td><td>Metric</td></tr><tr><td>Sales Units</td><td>POS units by store and week</td><td>Metric</td></tr><tr><td>Wholesale Dollars</td><td>Revenue on wholesale shipments</td><td>Metric</td></tr><tr><td>Wholesale Units</td><td>Units shipped to wholesale partners</td><td>Metric</td></tr><tr><td>Wholesale Cases</td><td>Cases shipped (units ÷ case pack) to wholesale partners</td><td>Metric</td></tr><tr><td>Store ID / Name</td><td>Retailer door identifier and label</td><td>Dimension</td></tr><tr><td>Retailer</td><td>Retail banner/account</td><td>Dimension</td></tr><tr><td>City/State/ZIP</td><td>Store location attributes</td><td>Dimension</td></tr><tr><td>Region / RMA</td><td>Regional grouping for roll-ups; Retailer Marketing Area</td><td>Dimension</td></tr><tr><td>DC/Warehouse</td><td>Receiving DC/warehouse for routing and allocation</td><td>Dimension</td></tr></tbody></table>

> Time series supports week, month, quarter, and year, including prior-year comparisons when history is available.

### Core Use Cases

* **Top/Bottom Store Analysis:** Rank doors by sales and growth; spotlight best practices and target laggards.
* **Regional Trend Tracking:** Roll up by state/region/DMA to guide field marketing and distribution strategy.
* **New Store Launch & Expansion:** Measure ramp-up after new placements and confirm distribution execution.
* **Coverage & Opportunity:** Compare current selling doors vs. target doors to size upside.
* **Sell-In vs. Sell-Through Alignment:** Compare **Wholesale Units/Cases/Dollars** to store-level **Sales Units/Dollars** to detect slow-moving regions, pipeline fill events, and re-order needs.
* **Operational Alerts:** Flag doors with sudden sales drops or persistent zero sales to investigate OOS, scan issues, or discontinued items.

#### **Note: Inventory data is not included in this explore.**

Inventory is **not** included in this explore: **all inventory is modeled in** [**Omnichannel Inventory**](https://help.daasity.com/core-concepts/data-models/data-explores/omnichannel-analytics/omnichannel-inventory), which provides store-level Quantity on Hand and combines the latest inventory levels with a adjustable rolling sales metric across URS and UOS channels for weeks-of-supply calculations (latest week inventory divided by average weekly sales for that product + location over the last 4–12 weeks).&#x20;

### Data & Modeling Details

* **Sources:** Retailer portals/EDI “sales by door” feeds for POS; internal ERP/order data for shipments; distributor/partner depletions where available.
* **Grain:** Date and Market granularity will vary by source (typically Daily or Weekly, and Store-level or Corp and/or Region-level), depending on the data source; wholesale shipments aligned at DC/Warehouse, account, region, and store (when all allocations are provided).
* **Alignment:** Shipments without store-level allocations are reported at **DC/Warehouse** or account level and remain analyzable alongside store POS via regional and account roll-ups.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.daasity.com/core-concepts/data-models/data-explores/retail-analytics-unified/retail-store-performance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.