# Transactional Data

### Which Data Does Each Module Need?

| Module                         | Sales Data         | Inventory | Supply Plans |
| ------------------------------ | ------------------ | --------- | ------------ |
| Sales Collaboration            | ✓                  |           |              |
| Long Term Planning             | ✓                  |           |              |
| Forecast Workbench             | ✓                  |           |              |
| Inventory Workbench - Partner  | ✓                  | ✓         |              |
| Inventory Workbench - Internal | ✓                  | ✓         | ✓            |
| Make Planning                  | ✓ History/Forecast | ✓         | ✓            |
| Crop Supply Planning           |                    |           | ✓            |

### Sales Data

Sales data is stored against Item @ Customer Group combinations and categorized by Sale Type (e.g., History, Budget, Forecast).

**Where to import:** Settings > Transactional Data > [Sales](https://docs.claret.app/transactional-data/sales)

**Import methods:**

* **Manual entry** — Add individual records via the UI
* **Bulk import** — Upload CSV/Excel files using the claret-sales-import-example.csv template
* **API** — Use the [Sales API](https://docs.claret.app/apis/public-apis/sales-data) for automated integrations

**Used by:**

* **Sales Collaboration** — Enter and manage sales plans
* **Long Term Planning** — Reference history when building annual plans (Growth % feature)
* **Forecast Workbench** — Historical data is required to generate statistical forecasts
* **Make Planning** — Sales demand drives WIP production requirements
* **Inventory Workbenches** — Demand/depletion data drives DOH calculations

### Inventory

Inventory data is stored against Item @ Location combinations and tracks current stock levels.

**Where to import:** Settings > Transactional Data > [Inventory](https://docs.claret.app/transactional-data/inventory)

**Import methods:**

* **Manual entry** — Add individual records via the UI
* **Bulk import** — Upload CSV files using the claret-inventory-import-example.csv template
* **API** — Use the [Inventory API](https://docs.claret.app/apis/public-apis/inventory) for automated integrations

**Used by:**

* **Make Planning** — Starting inventory for WIP and finished goods
* **Inventory Workbench - Internal** — Current stock at your locations
* **Inventory Workbench - Partner** — Current stock at partner locations

### Supply Plans

Supply plans represent planned production, shipments, or sourcing volumes. They're stored against items (and optionally locations) and categorized by Supply Type.

**Where to import:** Settings > Transactional Data > [Supply Plans](https://docs.claret.app/transactional-data/supply-plans)

**Import methods:**

* **Manual entry** — Add individual records via the UI
* **Bulk import** — Upload files using the template
* **API** — Use the [Supply Plans API](https://docs.claret.app/apis/public-apis/supply-plans-data) for automated integrations
* **Generated by Claret** — Inventory Workbench can generate supply plans automatically

**Used by:**

* **Make Planning** — WIP production plans
* **Crop Supply Planning** — WIP plans drive dependent demand; crop supply plans track harvest volumes
* **Inventory Workbench - Internal** — Production planning and supply plan generation

### Data Freshness

How often should you update transactional data?

| Data Type       | Recommended Frequency | Notes                               |
| --------------- | --------------------- | ----------------------------------- |
| Sales History   | Weekly or Monthly     | Depends on your data availability   |
| Sales Forecasts | Monthly or Quarterly  | Update as plans change              |
| Inventory       | Daily or Weekly       | More frequent = more accurate DOH   |
| Supply Plans    | As needed             | Update when production plans change |

{% hint style="info" %}
Transactional data can be updated manually, via bulk import, or automated through the API. Many organizations set up scheduled API imports to keep data current.
{% endhint %}