Salesfire Product Feed Schema

How to create a Salesfire Product Feed Schema

Providing a Salesfire Product feed allows Salesfire to use its AI to offer more advanced features. See below what is required in our product feed. We have provided an example alongside field definitions beneath.

We have put a lot of effort in to ensure the product feed is simple and easy to put together. In most instances it will take a developer less than an hour to put together.


<?xml version="1.0" encoding="utf-8" ?>
<productfeed site="http://local.example/" date-generated="2020-01-21T16:21:58+00:00">
<category id="category_4">
<product id="product_339">
<title><![CDATA[Retro Chic Eyeglasses]]></title>
<description><![CDATA[Acetate frame. Polycarbonate lenses.]]></description>
<price currency="NZD">295</price>
<sale_price currency="NZD">295</sale_price>
<category id="category_18" />

Field definitions:

product feed

  • site attribute - (required) - this should be the URL of your site.
  • date-generated attribute - (required) - the date the feed was generated.

You should then include an array of categories and products.


  • id attribute - (required) - this is a feed reference which is used by products further down. We recommend using the category ID prefixed with category_. For example: category_5 when the id is 5.
  • id - (required) - the ID of the category.
  • name - (required) - the name of the category.
  • breadcrumb - (required) - the breadcrumb of the category. Nested categories should use > as the divider.
  • link - (required) - the permalink of the category.


  • id attribute - (required) - this should work the same as a category. We recommend using the product ID prefixed with product_. For example: product_234 when the id is 234.
  • id - (required) - the ID of the product. (This is not variant ID.). This should match the parent_sku field that you use for Order Tracking.
  • title - (required) - the name of the product.
  • description - (required) - the description of the product.
  • price - (required) - the price of the product. It should be a number and can have decimal points. Ensure you provide the currency as a currency attribute.
  • sale_price - (required) - similar to the price, this is the current price of the product. If it's not on sale, it should be the same as price. Ensure you provide the currency as a currency attribute.
  • mpn - (required) - the mpn for the product.
  • gender - (recommended) - the gender of the product. Options: Male | Female.
  • categories - (required) - this should be an array of category elements which reference the categories list based on the ID attribute, for example, category_5.
  • variants - (required) - you must provide at least one variant for each product. See below for variant definition.
  • skus - (optional) - an array of skus which are associated with the product.


  • id - (required) - the ID of the variant. This should match the sku field that you use for Order Tracking.
  • link - (required) - the permalink to the product variant. If there isn't one, you can provide the product permalink.
  • image - (required) - the URL of the product variant image.
  • colour - (recommended) - the colour of the variant. You can see a list of supported colours in your Dashboard, and you can also map colours.
  • mpn - (recommended) - the mpn for the product.
  • stock - (recommended) - how many of this variant is in stock.
  • skus - (optional) - an array of skus which are associated with the product.

Rate our guide below