> For the complete documentation index, see [llms.txt](https://docs.sizebay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sizebay.com/size-and-fit-data-integration/product-integration-xml-feed.md).

# Product Integration (XML Feed)

1. **Requirements**

To ensure a successful integration, your XML file must adhere to the **Google Shopping standard** (RSS 2.0 or Atom 1.0) and utilize the [Google namespace for the product attributes](https://support.google.com/merchants/answer/160589?hl=en), following the tag specifications below.

{% hint style="info" %}
For the `g:product_type` field, it’s essential to provide values that allow our system to accurately match products with the correct size charts.

We strongly recommend using one of the following standardized values:

* **Top**
* **Bottom**
* **Full Body**
* **Top Underwear**
* **Bottom Underwear**
* **Shoe**

We understand that adjusting this field in your feed may not always be simple. However, please note that sending non-standardized values increases the effort required from our team and may delay the integration process or lead to incorrect chart associations.

If you have any questions or need guidance on how to structure this field properly, please don’t hesitate to reach out to us.
{% endhint %}

2. **XML Tags & Descriptions**

| **Tag**                      | **Description**                                                                                | **Format** |
| ---------------------------- | ---------------------------------------------------------------------------------------------- | ---------- |
| `<g:id>`                     | Parent Product ID (Unique identifier for the product, not for individual size/color variants). | Text       |
| `<title>`                    | Product Title                                                                                  | Text       |
| `<g:product_type>`           | Product Category                                                                               | Text       |
| `<g:brand>`                  | Product Brand                                                                                  | Text       |
| `<link>`                     | Product Permalink                                                                              | URL        |
| `<g:image_link>`             | Product Image URL                                                                              | URL        |
| `<g:gender>`                 | Valid values: `male`, `female`, `unisex`                                                       | Text       |
| `<g:size>`                   | Clothing/Shoe Size (e.g., `"S"`, `"XL"`, `"34"`)                                               | Text       |
| `<g:age_group>`              | Valid values: `newborn`, `infant`, `toddler`, `kids`, `adult`                                  | Text       |
| `<g:size_type>` *(optional)* | Valid values: `regular`, `petite`, `plus`, `big and tall`, `maternity`                         | Text       |

3. **Handling Size Variants**

You can choose to submit **all size variations under a single item** or **each size variation as a separate item** in the XML.

**➡️ Best Practice:** To improve recommendations, **include all available sizes** for a product, even if some are currently out of stock.

**Example 1: Single Item with All Size Variants**

<div align="left"><figure><img src="/files/4mrgXA7N82KL0X22579G" alt=""><figcaption></figcaption></figure></div>

**Example 2: Separate Items for Each Size Variation**

<div align="left"><figure><img src="/files/II4tYHGvUXehsNmdt0zZ" alt=""><figcaption></figcaption></figure></div>


---

# 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.sizebay.com/size-and-fit-data-integration/product-integration-xml-feed.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.