# File Storage Locations

RestocksAIO saves data in a working directory (StartupPath) next to the app. Below are the key folders and files created by different features.

## Folders

* **Delivery PDFs/** – Proof of Delivery (PoD) files from carriers. One PDF per tracking number.
* **Labels/** – Generated labels. Sites may create subfolders (e.g., `Labels/StockX/`). Files can be PDF, GIF, or HTML depending on the site.
* **Sales/** – CSV exports created from the Sales and analytics flows (e.g., `all_sales.csv`).
* **Profiles/** – One JSON per saved account/profile.
* **DatabaseBackups/** – Encrypted database backups with timestamped filenames.

{% hint style="info" %}
If you can’t find a recent export, sort the working directory by “Date modified” to surface the most recent folders/files (e.g., Delivery PDFs, Labels, Sales).
{% endhint %}

## Files at the root (working directory)

* `database_<uid>_mp.enc` – Main encrypted database.
* `invoice_presets.bin` – Saved Invoice Dialog presets (languages/labels/toggles).
* `invoice_profiles.bin` – Saved billing profiles for invoices.
* `proxies.bin` – Saved proxy groups.
* `tasks.bin` – Saved tasks configuration.
* `actions.bin` – Saved Smart Actions configuration.
* `fees.bin` – Preloaded fee settings.
* `viewed_items.bin` – Recently viewed cache for research.

## User-chosen export paths

Some exports are saved where you choose via a file picker:

* CSV templates: `listings_import_template.csv`, `inventory_import_template.csv`
* CSV exports: `exported_items.csv`, `listing_errors.csv`, other ad‑hoc exports

These do not live in the working directory unless you point the file dialog there.


---

# 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://docs.restock.gg/features/file-storage-locations.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.