Edit a Magento product XML feed in Excel

Why you shouldn't edit Magento XML by hand

A Magento export has one node per product with dozens of fields: SKU, price, stock quantity, status, attribute sets, categories, images, SEO data… often wrapped in HTML entities and CDATA blocks inside descriptions. Editing that in a text editor risks a single malformed tag causing the whole file to be rejected on import.

In Excel, each product becomes a row and each field a column. You get the spreadsheet comfort back: sort by category, filter out-of-stock products, recompute a pricing grid with a formula, or find-and-replace across 10,000 descriptions.

Edit your Magento export in 3 steps

1. Export your products to XML from Magento (via an export profile, the API, or your usual export extension) and drop the file on the ExcelifyXML Upload page.
2. You get a CSV where each product is a row. Open it in Excel, Numbers, Google Sheets or LibreOffice and make your edits: prices, stock, enabled/disabled status, attributes, SEO text.
3. Drop the edited CSV on the Reconstruction page: the original XML is regenerated exactly, ready to re-import into Magento.

Common tasks on a Magento catalog

• Apply a discount or price increase across a whole category with a formula.
• Mark a batch of SKUs out of stock or disabled in a single operation.
• Fix or translate product titles and descriptions in bulk.
• Clean up inconsistent attribute sets before a migration or redesign.
• Prepare a stock import from a supplier file.

Re-import without breaking the structure

The tricky part of a Magento catalog is keeping the exact same XML structure on re-import. That's the whole point of the round-trip: ExcelifyXML records the field order, namespaces and nesting in a manifest, and rebuilds the file in its original format. You only change values, never the skeleton.

Values containing special characters (ampersands, angle brackets, quotes) are automatically re-encoded correctly, for a file that stays valid on import.

Security and privacy

Your catalog isn't kept longer than necessary: the file is processed in memory on servers located in the European Union, then deleted immediately. No file and no metadata is retained (GDPR-compliant).