XMLSlice
Local processing · No uploads
Catalog workflow

Turn product feed XML into catalog-ready CSV.

Inspect supplier feeds, marketplace exports, and ecommerce catalogs in a spreadsheet before cleaning, comparing, or importing product data.

Open the private converter
Typical row
Product or variant
Common ID
SKU / GTIN
Validation
Preview first
Direct answer

The reliable conversion model

Choose the repeated product or item element as the row boundary, then map identifiers, names, prices, stock, categories, and image URLs to columns. Variants should be exported as their own record group when each variant needs a separate row.

01

Understand the structure

What matters before conversion

Choose product or variant granularity

One product per row works for simple catalogs. If size, color, SKU, price, or inventory differs by variant, selecting the repeated variant element produces a more useful import table.

Retain price context

Map currency attributes, tax flags, sale prices, and effective dates alongside the numeric amount so the spreadsheet value is not ambiguous.

Treat repeated categories intentionally

Multiple category or image leaves can be joined in one cell for inspection. Systems that require one relationship per row may need a separate export of the repeated child group.

02

Practical workflow

Convert in four clear steps

  1. 01

    Identify the feed's item element

    Look for repeated product, item, offer, entry, or variant candidates and compare their counts.

  2. 02

    Map stable identifiers first

    Start with supplier ID, SKU, GTIN, MPN, or another key needed to reconcile rows.

  3. 03

    Add commercial fields

    Select names, descriptions, price and currency, stock, brand, category, and URLs needed by the target workflow.

  4. 04

    Validate a sample

    Check missing values, decimal formats, and repeated fields before importing the complete CSV into another platform.

03

Worked example

Supplier catalog example

Attributes and nested price data remain associated with each product row.

Input XML
<catalog>
  <product sku="NOTE-01">
    <name>Field Notes</name><brand>Northstar</brand>
    <price currency="USD">14.90</price><stock>42</stock>
  </product>
  <product sku="INK-04">
    <name>Ink Set</name><brand>Northstar</brand>
    <price currency="USD">24.00</price><stock>8</stock>
  </product>
</catalog>
Resulting CSV
'@sku,name,brand,price/@currency,price,stock
NOTE-01,Field Notes,Northstar,USD,14.90,42
INK-04,Ink Set,Northstar,USD,24.00,8
Selected fields@sku, name, brand, price/@currency, price, stock

A CSV conversion does not validate a marketplace's required schema. Compare the selected columns and value formats with the destination platform before import.

04

Quality control

Conversion checklist

  • Decide whether one row represents a product or a variant.
  • Keep a stable identifier in every export.
  • Include currency and stock context with numeric values.
  • Check destination-specific required columns after conversion.
05

Questions and answers

Product feeds FAQ

Can XMLSlice convert Google Shopping or marketplace feeds?

It can flatten XML feeds into CSV when they contain repeating records and scalar fields. It does not certify that the result meets a marketplace's current import specification.

How are multiple product images handled?

Repeated image leaf values are joined with a pipe separator in one cell unless the image element is selected as a separate record group.

Should variants be separate rows?

Usually yes when variants have independent SKU, price, barcode, or stock values. Select the repeated variant element in that case.