Created by potrace 1.16, written by Peter Selinger 2001-2019

Miva Developer Docs

These provisioning files set up a complete feed for each channel. Download one, edit a few placeholders, import it, and the feed is ready. To get every file at once, download miva-feed-builder-provisioning.zip.

The files#

Channel Feed Builder only With Data Builder Writes
Google Merchant Center (XML) google-merchant-center.xml /google-merchant-center.xml
Google Merchant Center (tab) google-merchant-center-tab.xml google-merchant-center-tab-data-builder.xml /google-merchant-center.txt
Microsoft Merchant Center (XML) microsoft-merchant-center.xml /microsoft-merchant-center.xml
Microsoft Merchant Center (tab) microsoft-merchant-center-tab.xml microsoft-merchant-center-tab-data-builder.xml /microsoft-merchant-center.txt
Meta (Facebook and Instagram) meta-catalog.xml meta-catalog-data-builder.xml /meta-catalog.csv
Pinterest pinterest-catalog.xml pinterest-catalog-data-builder.xml /pinterest-catalog.csv
ChatGPT chatgpt-product-feed.xml chatgpt-product-feed-data-builder.xml /chatgpt-product-feed.csv

google-merchant-custom-fields.xml creates the product custom fields the Google and Microsoft files read: brand, gtin, mpn, identifier_exists, gender, age_group and google_product_category. See Product identifiers and custom fields.

Use the Feed Builder only file unless the catalog is large. See Which module to use. For Google and Microsoft, use either the XML or the tab file, not both.

What every file sets up#

  • A Feed Builder feed that saves a file in the web root, so the channel can fetch it from https://www.your-domain.com/<file>.
  • Products: Available (active and in no availability group), with a price above 0.
  • Variants on, with item_group_id and the color, size, material and pattern attributes.
  • Main Image from the image type with code main, and Additional Images from images with no image type.
  • Prices as amount and currency, for example 15.90 USD.
  • sale_price, left out when there’s no discount.
  • A scheduled task that rebuilds the feed nightly at 2:00 and after product, stock, variant or image changes.

The -data-builder.xml files also set up a Data Builder field with the same fields, its Queued Products and All Products tasks, and a feed that writes the stored rows. The feed’s rebuild waits 5 minutes after a change so the stored rows are updated first.

Before importing#

Open the file and change:

  1. YOUR_STORE_CODE in <Store code="YOUR_STORE_CODE"> to your store code.
  2. For Google and Microsoft, create the custom fields first: import google-merchant-custom-fields.xml, or point source= at fields you already have. See Product identifiers and custom fields.
  3. source="brand" to your brand custom field code, if it isn’t brand. If every product has the same brand, use a constant instead:

    <Field source="__constant__" output="brand" constant="Your Brand" />
    
  4. The image types, if your main image type isn’t coded main, or your extra images have types. List up to 10 type codes in image_types, comma-separated. __untyped__ means images with no type.

  5. The attribute codes, if your store’s attributes aren’t coded color, size, material and pattern.
  6. For ChatGPT, YOUR_STORE_NAME in seller_name.
  7. For the -data-builder.xml files, the column line in the feed’s <HeaderText> if you change the field list.

Each file’s comment at the top lists the same steps and the channel’s own notes.

Import#

  1. Install Feed Builder, and for a -data-builder.xml file Data Builder, under Settings > Utilities. The import doesn’t install them.
  2. Go to Data Management > Import > XML Provisioning and import the file.
  3. For a -data-builder.xml file, run the Rebuild … (All Products) task once: Settings > Store Settings > Scheduled Tasks, select it, Run Scheduled Task(s). Wait for the Update … (Queued Products) task to stop starting itself. See Scheduled tasks.
  4. Run the feed with Process Now, or wait for its nightly task.
  5. Open the file URL in a browser to check it, then register the URL with the channel.

Prices and sale prices#

price is the product’s (or variant’s) price with the store’s currency code, for example 15.90 USD.

sale_price is the price a shopper without an account pays after price group discounts. It covers the discount modules that change a product’s price (legacy price group discounts, Product Discount, Specific Sale Price, Volume Pricing) and not basket discounts. It’s left out of the row when it isn’t lower than the price.

On a large catalog, run Miva’s Pre-Calculate Discount Prices task so stored discount prices are read instead of worked out per product.

Shipping dimensions#

The Google and Microsoft files map shipping_length, shipping_width and shipping_height from each product’s shipping rules, with the store’s dimension unit, for example 12.00 in. A variant uses its own shipping rules, or its product’s. Each is left out when it isn’t set.