Convert a supplier price list to a Xero items CSV

What Xero actually needs

• The exact header row:ItemCode, ItemName, PurchasesDescription, PurchasesUnitPrice, PurchasesAccount, PurchasesTaxRate, SalesDescription, SalesUnitPrice, SalesAccount, SalesTaxRate, InventoryAssetAccount, CostOfGoodsSoldAccount — spelled exactly as in the template you download from Business › Products and services › Import.
• ItemCode is the key:the only mandatory column. Xero matches by it on every import, so the supplier part number belongs there — stable codes mean next month's price list updates prices with zero duplicates.
• Purchase vs sales price:the supplier's price goes to PurchasesUnitPrice; SalesUnitPrice is optional and can carry your own selling price when you already know it.
• Untracked items: leave InventoryAssetAccount empty and the items import as untracked — no stock counts demanded, which is what a price reference list should be.

Why supplier files break the import

A real supplier price list is a long PDF with section banners, merged cells where one description covers five variants, prices in mixed formats — sometimes a photographed printed page. Retyping that into Xero's template by hand takes hours per supplier, every time the price list changes, and one shifted row puts the wrong price on the wrong item code.

The fast way: upload the file, get the CSV back

The MicroCity engine reads the supplier file as it arrives — PDF, Excel, scan or photo — and returns a CSV in Xero's own Import Items layout, part numbers as ItemCode, supplier prices in PurchasesUnitPrice. The layout is certified against a real Xero company: a converted supplier file imported 3 of 3 items, zero errors, and a re-import updated them by ItemCode with no duplicates. Anything the engine can't read properly gets flagged, not guessed.

Honest limit: the engine returns the import file — it does not connect to your Xero organisation or write to it. You import the CSV yourself and review every line before it goes in. That is by design.