> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/suppliers-and-purchasing/demand-planning/data-sources.md).

# Data Sources

The Pakk Demand Planner primarily uses the sales data from your Pakk account as its source of historical sales data. There’s nothing you need to do to make that work, all the data is extracted in the background. However, we get that you probably have years worth of sales data from previous systems that you’d like to use with the demand planner.

That’s no problem - you’ll find the option to ‘Upload Historical’ data, which allows you to upload an unlimited history of sales from your legacy system or systems.

Historical data needs to be in standard CSV format with just 4 columns (no header row necessary): SKU, year, week, quantity. The sheet can contain as many rows as necessary, one for each “data point” which is a weekly sales number for a product

The SKU needs to match the product SKU as it appears in Pakk. The year is just a number with the full year, like “2019”. The week is the ISO standard week number, like 12 or 34. The quantity is just the number of units sold that week.

Your old system might not produce a report exactly like this, but you should be able to wrangle the data with Excel to get something workable. If you need help, just ask. You only need to do this once: after you’ve uploaded your historical data set, it is saved and combined with your live Pakk data forever more.


---

# 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.pakk.io/suppliers-and-purchasing/demand-planning/data-sources.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.