> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/data-integrations/retail-data.md).

# Retail Data

See how your products sell through your retail partners: sales, inventory and availability, and shipments, all in one place.

Retail Data shows how your products sell **through** your retail partners' stores, places like Sephora, Ulta, Kohl's, Walmart, Target, and grocery and mass chains. It is separate from your own D2C site. It answers the questions you can't see from your own orders: how fast a product is selling at each retailer, whether stores are stocked, and how shipments into those retailers compare to what's actually selling.

## What you can do with it

* Track sell-through (units and dollars) by retailer and, where reported, by individual store.
* Spot out-of-stocks and low-stock stores before they cost you sales.
* Compare what you shipped in against what sold through, so you can see where inventory is piling up or running thin.
* Report on any retail calendar your partners use, without rebuilding the numbers by hand.

## What it covers

Retail Data is organized into three areas:

| Area                         | What it answers                                                           | Page                                                                                     |
| ---------------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| **Sell-through**             | How much sold to shoppers, at what price, and at what margin              | [Sell-through](/data-integrations/retail-data/sell-through.md)                           |
| **Inventory & availability** | What's on hand, on order, and in transit, and how many stores are stocked | [Inventory & availability](/data-integrations/retail-data/inventory-and-availability.md) |
| **Shipments**                | What you ordered, shipped, and the retailer received (sell-in)            | [Shipments](/data-integrations/retail-data/shipments.md)                                 |

{% hint style="info" %}
**Sell-through vs. shipments.** Sell-through is what shoppers bought off the shelf. Shipments (sell-in) are what moved into the retailer. They rarely match in a given week, and the gap between them is inventory sitting in stores and warehouses.
{% endhint %}

## Time periods and calendars

Every area is available at three time grains, so you can zoom from a single day out to a full month:

| Grain       | Details                                                 |
| ----------- | ------------------------------------------------------- |
| **Daily**   | The finest view, where a retailer reports at that level |
| **Weekly**  | Saturday week-ending                                    |
| **Monthly** | Exact calendar month                                    |

You can also slice the same numbers by the retail calendar your partners plan against: standard **calendar month**, the **NRF 4-5-4 retail calendar**, or **Walmart weeks**.

## Retailer vs. store detail

Retail Data comes at two levels of detail:

* **By retailer (banner):** one line per retailer, for every partner. Example: all of Sephora.
* **By store/location:** broken out to the individual store, available **where the retailer reports store-level data**.

## Getting connected

Retail Data populates once a retailer is connected. Connecting a retailer requires the **Wholesale Add-On**. For the list of supported retailers and step-by-step setup, see [Retailer Integrations](/data-integrations/retailer-integrations.md). To work with the data directly in the warehouse, see [BigQuery](/data-integrations/bigquery.md).

{% hint style="warning" %}
**Some metrics depend on the retailer.** Retailers report different things. When a partner doesn't send a metric, it comes through blank, never estimated or filled in. If a column looks empty for one retailer, it usually means that retailer doesn't report it.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.drivepoint.io/data-integrations/retail-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.