Skip to main content
If your webshop doesn’t generate a good XML feed by default, tools like Channable, Producthero, or DataFeedWatch can help you create and manage high-quality feeds.

​
Why a good XML feed matters

When you connect an XML feed to Watermelon, your Agent uses this feed as a source of truth for product data. If information is missing, unclear, or inconsistent, your Agent may give incomplete or incorrect answers.

​
General requirements for an XML feed

Before looking at specific fields, your XML feed should meet these basic requirements:
  • The feed must be publicly accessible via a URL
  • The feed format must be XML
  • The feed must contain structured product-level data
  • Each product should appear once in the feed
  • The feed should be updated when products change

​
Required fields in an XML feed

To work properly with Watermelon, your XML feed must contain at least the following fields for each product.
  • Product ID: A unique identifier for each product.
    • Must be unique per product
    • Should not change over time
    • Can be a SKU, internal ID, or database ID
    • Example: <id>12345</id>
  • Product title / name: The name of the product as shown to customers.
    • Clear and descriptive
    • Avoid internal codes/names only
    • Prefer the full product name
    • Example: <title>Wireless Noise Cancelling Headphones</title>
  • Product description: A textual description of the product.
    • Can be short or long
    • Plain text is preferred
    • Avoid HTML where possible
    • This field is crucial for helping your Agent explain what a product is and what it’s used for.
    • Example: <description>Wireless headphones with active noise cancellation and 30 hours of battery life.</description>
  • Product URL: The direct URL to the product page on your webshop.
    • Must be a full URL (including https)
    • Should lead to a live, accessible page
    • Example: <link>https://www.example.com/products/headphones</link>
  • Price: The current selling price of the product.
    • Use a consistent format
    • Clearly define the currency
    • Exclude additional text
    • Example: <price>199.99</price> or <price currency="EUR">199.99</price>
  • Availability: Indicates whether the product is available for purchase.
    • This helps your Agent avoid recommending unavailable products.
    • Example: <availability>in stock</availability>
While not strictly required, these fields greatly improve the quality of your Agent’s answers.
  • Brand: Helps distinguish similar products and improves filtering.
    • Example: <brand>Sony</brand>
  • Category: Helps your Agent understand how products relate to each other.
    • Example: <category>Audio > Headphones</category>
  • Variants (if applicable): If your product has variants (size, color, material), include them clearly.
    • Use separate variant entries or
    • Include structured variant fields
    • Example: <color>Black</color> or <size>Medium</size>