Supported XML shapes
The XML layouts Product XML Import recognises automatically: generic product feeds, Google Merchant Center RSS and Atom, nested and flat variants, and multi-file catalogues.
Reviewed by Koray Sarı
Docs
Generic product XML
The most common shape: a root element containing one child element per product, with fields as child elements or attributes. Element names vary by supplier (product, item, urun, artikel) and are detected from the content, not the name.
Google Merchant Center feeds
RSS 2.0 or Atom feeds with fields in the g: namespace (g:id, g:title, g:price, g:sale_price, g:availability, g:image_link, g:item_group_id and so on). Items sharing an item_group_id become variants of one product. See Google Merchant feeds.
RSS and Atom catalogues
Plain RSS or Atom feeds where each item carries product data in custom or Dublin Core elements. Prices and stock are taken from any element that looks like a price or quantity.
Variant shapes
- Nested: variants listed under the product element.
- Flat: every variant is its own product element with a parent or group code.
- Attribute-based: size or colour given as attributes rather than elements.
Multi-file catalogues
Some suppliers split data across files: one XML with product details, another with stock or prices, sometimes a third with images. These are configured by support as a composite feed and behave like a single feed in the app.
Encodings and namespaces
UTF-8, ISO-8859-1 and Windows-1254 declared in the prolog are handled. Namespaced elements are matched by local name, so g:price and price are treated alike where appropriate.
Frequently asked questions
My feed has a custom structure. Will it work?
Probably. The app scores the feed against known layouts and picks the closest. When nothing fits well enough, our team adds a profile for your feed, usually within a business day.
Do you support JSON or CSV feeds?
No. The app reads XML only. Ask your supplier whether they also publish an XML or Google Shopping feed; most do.