↑↓ selectEnter openEsc close

    1. Elbuz
    2. Manual matching

    How to save manual matches to a file and import them back

    3 min readUpdated

    Elbuz exports confirmed “catalog product — price list row” pairs to an XLSX file and imports pairs from CSV. Use it to make a backup before a mass cleanup and to restore manual work.

    When you need this:

    • Before the “Delete” button in the list — the file becomes the only copy of the pairs, because there is no undo.
    • Pairs were deleted by accident — you import the saved file back.
    • Pairs were prepared in a spreadsheet — the import links catalog products to price list rows by SKU and name.

    Where to start: “Matched products list” → the down arrow “Export matches to XLSX file”.

    What exchanging pairs through a file can do

    • Export — the whole list for the window's scope: a price list, a supplier, or the shop; ten columns, newest pairs first.
    • Import — with column mapping, a check before import, and a report for every row.
    • Retry — rows that failed are downloaded as a separate CSV with the reason.

    Automatic pairs found by rules aren't stored in the list and don't go into the file. How the list itself works — Matched products list.

    How to export pairs to XLSX

    Button tooltip: “Export matches to XLSX file”. After “Generating the file, please wait...” the file downloads on its own. Ten columns: “Catalog product ID”, “Catalog: Manufacturer SKU”, “Catalog: Name”, “Price: Manufacturer SKU”, “Price: Name”, “Price: manufacturer”, “1 price list product matched to several catalog products”, “Matched via AI”, “Username”, “Date added”. Sorted by date added, newest first.

    Two things to know in advance. The export takes the whole list for the scope, not what you see on screen: neither filtering in the list nor the toggle position affects the file. And automatic links never go into the file — they aren't in the list, and the export takes exactly the list.

    The file has the same scope as the “Delete” button: from the source header, the file gets that price list; from the supplier's “All products” tab — the supplier's entire list; from the top “All sources” node — the shop's entire list. So an export before a cleanup is exactly the right copy: their scopes match.

    How to import pairs from CSV

    Button tooltip: “Import manual product matches from a CSV file”. It opens a separate “Import matches from file” window. The workflow is: choose a file → “Upload and check” → map the columns → “Import” → review the report → if needed, click “Download failed rows”.

    Only .csv is accepted. The program detects the delimiter from the first line — semicolon, comma, or tab; the is UTF-8 or CP1251; there's a “First row is a header” checkbox.

    You can map eight fields: “Catalog product UUID”, “Catalog product MPN”, “Catalog product SKU”, “Catalog product name”, “Supplier (name/address)”, “MPN (price list)”, “Supplier SKU (price list)”, “Name (price list)”.

    The required minimum is two columns.

    Catalog side: “Catalog product UUID”, “Catalog product MPN”, or “Catalog product SKU” — not just “Catalog product name”. Price list side: “MPN (price list)” or “Name (price list)” — not just “Supplier SKU (price list)”. Otherwise the import won't start: “Specify a column for the catalog product (UUID or SKU).” or “Specify a price list column (SKU or name).”.

    The report after import shows six numbers: “Total rows”, “Imported”, “Skipped (duplicates)”, “Catalog product not found”, “Catalog product ambiguous”, “No price data to match”. Rows that failed are downloaded as a separate CSV with a reason column — you can fix it and import it again.

    Pairs imported from a file are never visible in single price list mode. They're saved without a price list number, and in this mode the list always filters for records of its own price list — neither the toggle nor column filters help here.

    Look for them in the supplier scope. If the file had the “Supplier (name/address)” column mapped and the program found the supplier by that value, the record is visible in its scope. Without that column, the record is saved without a supplier and is visible in any supplier's scope and from the top “All sources” node.

    The pair still starts working on the next price list import: matching goes by the product hash, which depends on neither the price list number nor the supplier.

    Scenarios

    Back up manual matches and restore them

    What to do. Click the down arrow “Export matches to XLSX file”. To bring the pairs back, save the file as CSV in Excel or LibreOffice, click the up arrow, and in the “Import matches from file” window map the columns:

    • “Catalog: Manufacturer SKU” → “Catalog product MPN”, “Catalog: Name” → “Catalog product name”;
    • “Price: Manufacturer SKU” → “MPN (price list)”, “Price: Name” → “Name (price list)”;
    • don't map the “Catalog product ID” column: it's the product number, and the import expects a .

    What you get. The catalog product is looked up first by the SKU + name pair; the report shows “Catalog product ambiguous” only when no lookup step found exactly one product. The pairs go into the list without a supplier.

    What won't happen. The import recognizes a price list row by a fingerprint of manufacturer SKU and name. If “Consider uniqueness” in the price list columns isn't set on exactly this pair, the report says “Imported”, but the pairs won't link to rows. Then it's safer to check “Manufacturer SKU” in the “Search for manually matched products” type, without “Supplier”.

    Some rows failed to import

    What to do. After the import, click “Download failed rows”, fix the file using the reason column, and import it again.

    What you get. The fixed rows are imported; the ones already in the list show up in the report as “Skipped (duplicates)”.

    What won't happen. A row for which no catalog product was found, or several were found, won't pass again without new data: you need a more precise SKU or UUID.

    FAQ

    I imported pairs from a file, but they're not in the list. Where are they?

    They were saved without a price list number, so they're never visible in single price list mode. Open the list from the supplier's “All products” tab or from the “All sources” node (importing from CSV).

    The exported file is empty. Why?

    The window's scope has no list records at all: the list showed only automatic links, and those aren't stored in the list. Pin the pairs you need with the floppy disk icon and export again.

    Does filtering in the list affect what goes into the file?

    No. The export takes the whole list for the window's scope; neither column filters nor the “Show lost links” toggle affect the file (export).

    The report says “Imported”, but the pairs didn't link to price list rows. Why?

    The import recognizes a price list row by a fingerprint of the manufacturer SKU and name. If “Consider uniqueness” in the price list columns is set on other fields, the fingerprints don't match (backup scenario).

    Why is the export in XLSX, but the import only in CSV?

    That's how the buttons work: the export produces , and the import accepts only .csv. Open the exported file in Excel or LibreOffice and save it as CSV.

    Where it is and who has access

    Other entry points
    “Matched products list” → the down and up arrows on the toolbar
    Access right
    the “Matched products directory” window; for import, also “Product matching”
    Prepare
    for import, a .csv file in or CP1251

    What goes into the file depends on where you opened the list from: the source header, the supplier's tab, or the “All sources” node (three scopes).

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free