Skip to main content
Product import

Map supplier CSVs automatically Header rules first, AI for the rest

To automate product mapping from supplier CSVs with titles and SKUs, use a PIM with an automatic column mapper. In WISEPIM, an AI-powered PIM for e-commerce, headers it knows, such as item_sku, EAN or Artikelnummer, map by rule and AI proposes a field for the rest. You check every row before a product is written, the mapping is saved for the next file, and SKU or EAN matching updates existing products.

  • 5 import sources
  • Scheduled imports via automations

What WISEPIM maps in this file

5 mapped by rules, 2 skipped, 1 for AI

item_sku: a header WISEPIM knows, so it maps to SKU by rule, before any AI runs.

The mapper's real output for these headers on a new project. Every row stays editable before import.

Try it on your own file

Key features

  • Import files and feeds

    CSV, Excel and XML files, plus API integrations and supplier feeds. Add an automation to re-run an import on a schedule.

  • Reuse a saved mapping

    Known headers map by rule and AI proposes a field for the rest. Save the result and the next import from that source starts already mapped.

  • Set the rules before it runs

    Match duplicates on SKU or EAN, pick which fields may be overwritten, and choose the status new products arrive in.

Sources

Every place your products already live

A file, a platform, a supplier feed, a URL or the page you have open. All five land in the same importer and the same mapping step.

  • Files you already export

    CSV, Excel (XLS/XLSX) and XML, uploaded straight from your machine.

  • Platforms and ERPs

    Shopify, WooCommerce, Magento 2, Lightspeed and CCV Shop connect over API. Each import runs when you start it, or on a schedule you set in an automation.

  • Any webshop URL

    Paste a category page, a sitemap or a list of URLs and WISEPIM walks the pagination to find every product.

  • The page in your browser

    The extension imports from a page your own browser loaded, including sites that turn away server-side crawlers.

How it works

Three steps from source to catalog

The same flow whether the products come from a spreadsheet, an API integration or a competitor's category page.

  1. 01

    Pick your source

    Upload a file, choose an integration or supplier feed, paste a webshop URL, or import with the extension from the page you have open.

    WISEPIM reads the source and shows you what it found before anything is written.

  2. 02

    Review the mapping

    Headers WISEPIM knows map by rule. For the rest, AI reads the header and sample values and proposes a product field. Change any row, then save the mapping.

    The mapping is stored against that source, so the second import never asks again.

  3. 03

    Set the rules and run

    Choose the duplicate match key, which fields may be overwritten, and the status new products arrive in. Then start the run.

    The import works through the queue in the background while you carry on.

Field mapping

Drag a column onto its field

WISEPIM does the first pass, with header rules and AI. When a column has no obvious home, such as a supplier's own spec code or a second price, you place it yourself.

Drag a column onto a field, or select a column and pick its field.

5/8 fields mapped

Columns without a field

WISEPIM product fields

  • SKU

    art_nrMatched by WISEPIM
  • Product name

    prod_titleMatched by WISEPIM
  • Description

  • Price

    price_ex_vatMatched by WISEPIM
  • Stock

    qty_on_handMatched by WISEPIM
  • Brand

  • Color

  • EAN

    ean13Matched by WISEPIM

After the run

Gaps surface here, not on your channel

Post-import cleanup lists what came in short, whether that is weight, images or price, grouped by field instead of by product.

  • See what is missing

    Every product that arrived without a required field, counted per field so you know which gap blocks the most SKUs.

  • Fix a group in one pass

    Send a group straight to bulk edit or AI enrichment rather than opening products one at a time.

  • Re-run without doubling

    The saved mapping and the SKU or EAN match key mean a second run updates the products already there.

Cleanup after an import: each row is a missing field and the number of products waiting on it.

Browser extension

Import straight from your browser

Some catalogs never expose a file or an endpoint, and some sites turn away anything that isn't a real browser. The WISEPIM extension imports from the page you already have open, so those sources stop being dead ends.

  • Works on Chrome, Edge and Firefox, plus Chromium browsers like Brave and Arc
  • Imports a single product or a whole category page, with images, specs and the source URL
  • Reads the page your own browser loaded, so bot protection isn't in the way
  • Connect a browser once and pick which project its imports land in

Connect your shops, marketplaces, and PIM

Import products from where they live, improve them in WISEPIM, and push them back to every channel you sell on.

FAQs

Product import questions

What teams ask before they run their first import.

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

Shop platforms such as Shopify import CSV files in their own fixed template, so a supplier file usually has to be reshaped first. A PIM with an automatic column mapper takes the supplier file as it is. In WISEPIM, known headers such as SKU, EAN and title columns map by rule, AI proposes a field for unknown columns, and you confirm each row. The saved mapping is reused for the next file from that supplier, and a SKU or EAN match key updates existing products instead of duplicating them.

CSV, Excel (XLS/XLSX) and XML, uploaded directly or fetched from a URL your supplier keeps current. Shopify, WooCommerce and the other platform integrations connect over API instead. There is no PDF or image importer: a catalog that only exists as a document has to be exported to one of those formats first, or imported from its web pages instead.

On upload WISEPIM first matches the headers it knows, such as item_sku, EAN or Artikelnummer, by rule. Columns no rule recognises go to AI, which reads the header and a sample of values and proposes a product field or a skip. You confirm or change any row before a single product is written, and the mapping is saved against that source for the next run. It proposes a mapping; it never commits one on its own.

Yes, in two ways. Paste a webshop URL and WISEPIM walks the pagination and extracts each product with AI. Or install the browser extension for Chrome, Edge or Firefox and import from the product page you already have open, which also works on sites that block server-side crawlers.

Yes, through an automation. Give it a schedule trigger (hourly, daily, weekly or monthly) and an import step: re-import from a connected platform such as Shopify or WooCommerce, or fetch a CSV, Excel or XML file from a URL your supplier keeps current. Repeat runs match products on your duplicate key, so existing products are updated instead of duplicated. Without an automation, an import runs once, when you start it.

You choose the match key, whether that is SKU, EAN or another unique field, and what a match does: skip the row, update the existing product, or merge into it. Without a match key every row is treated as new, so set one before the first run.

Next step

Import your first catalog and see the gaps

Start with one file, one integration or one URL. The mapping you save on that run is the one every later import starts from.

4.7