> For the complete documentation index, see [llms.txt](https://help.canoa.supply/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.canoa.supply/docs/for-brands/format-your-data-for-upload.md).

# Format your data for upload

This article will outline the necessary steps to ensure successful onboarding of your brand’s data. You will learn how easy it is to upload product details, images, 2D vector drawings and attachments.

#### **Format Your Data for Upload**

Once you’ve decided what to publish and gathered your data, the next step is formatting it for upload. Canoa uses CSV files to organize product information in bulk. This section will help you structure your spreadsheet for success—whether you’re uploading 10 SKUs or 100,000.

***

**📄 What is a CSV file?**

A CSV (Comma Separated Values) file is a universal spreadsheet format used to import structured data. It works with Excel, Google Sheets, Airtable, and most database tools.

You’ll upload your catalog as a single `.csv` file through your Canoa Brand Dashboard.

> 📁 Need a starting point? Download our \[CSV template] for a pre-formatted version with example rows.

***

**🧱 Required Fields**

To publish a product, each row in your CSV must include these core fields:

| Column Header     | Description                       | Example                                        |
| ----------------- | --------------------------------- | ---------------------------------------------- |
| `product_name`    | Display name of the product       | “Lounge Chair 001”                             |
| `sku`             | Unique identifier                 | “LG-CHAIR-001”                                 |
| `thumbnail_image` | Direct image link (JPG or PNG)    | `https://yourcdn.com/images/lg001.png`         |
| `description`     | Short summary (1–3 sentences max) | “A modern lounge chair with a walnut base.”    |
| `category`        | General category or type          | “Seating”                                      |
| `product_url`     | Destination URL for backlinks     | `https://yourbrand.com/lg001?utm_source=canoa` |
| `brand_name`      | Your brand or manufacturer name   | “Modern Form”                                  |

> ✅ Be sure all links are live and publicly accessible—no login walls or expired file paths.

***

**🧩 Optional (Recommended) Fields**

While not required, these help improve product discoverability, search relevance, and downstream specification:

* `price` (MSRP or base pricing)
* `dimensions` (e.g., W x D x H in inches or mm)
* `materials` (e.g., powder-coated steel, recycled PET)
* `finish_options` or `variants`
* `tags` (keywords for filtering, e.g. “outdoor”, “stackable”)
* `collection` (e.g., “Spring 2024”)
* `downloads` (direct links to PDFs, DWGs, or SIF files)

***

**🔧 Formatting Guidelines**

* Save the file as `.csv`, UTF-8 encoded
* Use consistent headers—no merged cells or blank rows
* Avoid extra formatting (bold text, cell shading, etc.)
* Keep columns in a consistent left-to-right order

> 🔎 Tip: Use Google Sheets or Airtable if you’re having trouble with Excel formatting or file encoding.

***

**🧪 Test Before Uploading**

Before uploading your full catalog, we recommend testing with a sample file (10–20 rows). This helps surface any formatting errors before doing a bulk push.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.canoa.supply/docs/for-brands/format-your-data-for-upload.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.