> 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/shipments.md).

# Shipments

What you ordered, shipped, and the retailer received, the sell-in side of retail.

Shipments are the sell-in side of retail: what was ordered, what you shipped, and what the retailer received. Comparing this to sell-through tells you whether inventory is building up or drawing down at your partners.

**Use it to:**

* Reconcile orders, shipments, and receipts by retailer.
* Compare sell-in to sell-through to spot inventory building up or running short.
* Track shipment value alongside units and cases.

## Shipment metrics

| Metric                      | What it tells you                    | Notes                                        |
| --------------------------- | ------------------------------------ | -------------------------------------------- |
| **Ordered (units & cases)** | What the retailer ordered            | Where the retailer reports orders            |
| **Shipped (units & cases)** | What you shipped in                  | Cases where the retailer reports them        |
| **Shipped value ($)**       | Dollar value of what shipped         | Gross and net where reported                 |
| **Received (units & $)**    | What the retailer confirmed received | Retail value; cost value also where reported |

Shipments are tracked from origin to destination, so you can see where product was shipped from and which retailer location received it.

{% hint style="info" %}
**Why sell-in and sell-through differ.** In any given week, what ships into a retailer rarely equals what sells through to shoppers. The difference is inventory. Watching the two together is the fastest way to catch a partner over- or under-stocking.
{% 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/shipments.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.