> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/import-data/import-concepts/import-fields.md).

# Import fields

Understand import fields and how Channable uses them during mapping.

When you [import product data](/import-data/readme.md) into Channable, either by connecting an eCommerce platform, or by uploading a data source like an XML file, Channable will use the information in your import to structure your product data in Channable.

We call this ‘mapping’. Essentially, it’s the process of looking at the data you provide and saying “Okay, in your source, you call this piece of information ‘country’, but in Channable we call it ‘shipping country’, and that’s what Google Shopping (or another export channel) will expect it to be called when we send it to them. Let’s make sure we match the data you’ve provided to what the channel will receive”.

Mapping makes it possible for Channable to process and standardize product data from a variety of sources so that you can list your products on any supported channel.

### Import fields <a href="#h_01jcdkzvvs1exe53r7d3wcrryt" id="h_01jcdkzvvs1exe53r7d3wcrryt"></a>

Regardless of the import method you use, Channable will look at your imported data and automatically separate and organize all of the information into what we call ‘import fields’. For example, you might have import fields that look like this:

* shipping country
* price
* Image Src


---

# 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://helpcenter.channable.com/import-data/import-concepts/import-fields.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.