Every Import Format Explained: One-Link Imports vs CSV vs API Feeds

Getting products into your catalog should not be the hardest part of running an e-commerce business. Yet for most teams, product import methods in e-commerce are a daily source of friction — wrong formats, failed uploads, mismatched fields, and hours spent cleaning data that should have arrived clean in the first place. MicroPIM supports four distinct import methods, each designed for a different source, workflow, and technical context. This guide explains every one of them, when to use each, and how to avoid the most common failure points.

The Four Import Methods: A Quick Overview

Before going into the detail of each method, here is the landscape. MicroPIM provides four ways to bring product data into your catalog:

1. One-Link Import — paste a supplier or manufacturer URL, and MicroPIM scrapes and imports the products automatically using AI-powered data extraction
2. CSV/Excel Upload — upload a structured file with your product data mapped to a standard template
3. Product Feed Import — connect a live XML, JSON, or custom-format feed that updates on a schedule
4. API Integration — connect directly to an ERP or external system (NetSuite, SAP, Dynamics 365, Odoo) for real-time or scheduled data ingestion

[SCREENSHOT: MicroPIM import dialog showing the four import method options]

Each method appears in the Import section of MicroPIM alongside your Import List and Import History, so you always have a full audit trail of what came in, when it arrived, and whether it succeeded. The right method depends on where your data lives, how often it changes, and how much technical control you want over the process.

One-Link Import: Paste a URL, Import Thousands of Products

One-Link Import is MicroPIM’s most distinctive feature, and for many users it is the one that first demonstrates what automated data ingestion can actually look like in practice.

How It Works

You paste a URL — a supplier catalog page, a manufacturer’s product listing, a competitor’s storefront, or any publicly accessible web page with structured product data — and MicroPIM does the rest. The platform’s scraping engine crawls the URL, traverses paginated listings, extracts product names, descriptions, prices, images, variants, and attributes, and delivers a clean structured catalog into your MicroPIM account.

The entire process runs in the background. You do not need to wait, and you do not need to prepare any file. For large catalogs, the scrape job is queued and you are notified when it completes. The Import History view shows the job status, the number of products extracted, and any records that could not be parsed cleanly.

AI-Powered Data Cleaning

Raw web data is rarely clean. Supplier pages have inconsistent formatting, variable attribute naming, fragmented descriptions, and encoding artifacts. MicroPIM’s AI layer processes every extracted record before it enters your catalog, standardizing field formats, correcting encoding errors, normalizing attribute values, and flagging products where confidence in extraction quality falls below threshold.

In practice, this delivers approximately 95% precision on well-structured supplier pages. Products that fall below the confidence threshold are flagged in your Import History for manual review rather than imported with potentially incorrect data. This keeps your catalog clean without requiring you to review every record individually.

Duplicate Detection

If you import from the same supplier URL twice, or if a product already in your catalog matches one being imported, MicroPIM’s duplicate detection layer identifies the overlap. You can choose to skip duplicates, overwrite existing records, or merge incoming data with the existing record. This is particularly useful when importing partial catalog updates from a URL that covers only a subset of a supplier’s full offering.

When to Use One-Link Import

One-Link Import is the right choice when:

• You are onboarding a new supplier and want to pull their catalog without requesting a data file
• You need to scrape product information from a manufacturer’s website for data migration
• You want to monitor a supplier’s catalog and detect new or changed listings
• Your supplier does not provide a structured feed or API but maintains a public product catalog online
• You are doing initial catalog population and speed of import is the priority

For a complete walkthrough of automated import and export workflows in MicroPIM, see how to automate imports and exports in MicroPIM.

CSV/Excel Upload: Structured Files with Full Field Control

CSV and Excel upload is the most universally supported product import method in e-commerce, and MicroPIM’s implementation is built to handle the full range of file structures that arrive from real-world sources — not just perfectly formatted templates.

Templates and Field Mapping

MicroPIM provides a downloadable CSV template that defines the expected column structure for a standard product record: name, SKU, description, short description, price, sale price, stock quantity, weight, dimensions, category, tags, image URLs, and any custom attributes your catalog uses.

[SCREENSHOT: CSV upload interface with field mapping columns]

If your source file does not match the template exactly — because it came from a different platform, an ERP export, or a supplier’s own format — the field mapping interface handles the translation. You upload your file, and MicroPIM displays each column header from your source alongside a dropdown of destination fields in the MicroPIM product model. You map each column once. For recurring uploads from the same source, MicroPIM saves the mapping so you do not repeat the work on subsequent uploads.

Validation and Error Handling

Before any data enters your catalog, MicroPIM validates every row against the product schema. Common validation checks include:

• Required field completeness — SKU and product name must be present on every row
• Data type conformance — price fields must be numeric, image fields must be valid URLs
• Duplicate SKU detection — rows with SKUs already present in your catalog are flagged
• Category matching — categories in the import file are matched against your existing taxonomy, with unmatched values listed for review

Rows that fail validation are collected into an error report that you can download, correct, and re-upload without affecting the records that passed. You are never forced into an all-or-nothing import where one bad row blocks a thousand clean records.

What CSV Import Handles Well

CSV import is well suited for:

• One-time data migration — moving a product catalog from one platform to another during a replatforming project
• Supplier-provided price lists — regular price file updates from suppliers who deliver data via spreadsheet
• Manual catalog additions — adding a batch of new products prepared by your buying team in a spreadsheet
• ERP export ingestion — importing product master data exported from an ERP system as a structured file

For managing the custom attribute fields that often appear in supplier CSV exports, see the guide to product attributes and custom fields in MicroPIM.

Product Feed Import: Live Feeds with Scheduled Ingestion

Product feed import bridges the gap between one-time file uploads and full API integration. It is the right method when your data source provides a structured, machine-readable feed at a stable URL — but does not offer a full API with authentication and real-time webhooks.

Supported Feed Formats

MicroPIM’s feed import engine supports:

• XML — the most common format for supplier feeds and price comparison platforms
• JSON — increasingly common for modern supplier integrations and marketplace feeds
• CSV via URL — a flat file at a stable URL, treated as a feed for scheduled ingestion
• Custom formats — feed structures that deviate from standard schemas can be mapped using MicroPIM’s field mapping layer, which handles non-standard tag names, nested attribute structures, and multi-value fields

Scheduled Feed Imports

The primary advantage of product feed import over file upload is automation. Instead of downloading a file and uploading it manually each time the feed updates, you configure the source URL once and set a schedule. MicroPIM fetches the feed, parses new and updated records, applies your field mapping, and ingests the changes on the schedule you define — hourly, daily, weekly, or at any interval your operations require.

Every scheduled run is recorded in your Import History with a timestamp, the number of records processed, the number of new records added, the number of existing records updated, and a log of any rows that could not be processed. This gives you a complete audit trail of every catalog change without any manual logging.

Feed Import for Dropshipping and Multi-Supplier Operations

For dropshippers and retailers working with multiple suppliers, product feed import is often the primary data ingestion mechanism. Each supplier feed is configured as a separate import source with its own schedule, field mapping, and category assignment rules. When a supplier updates their catalog — new products, price changes, stock level changes — the next scheduled import run picks up the changes automatically and propagates them to your catalog.

This eliminates the recurring manual work that makes multi-supplier catalog management expensive. For a deeper look at feed import workflows, see how to import product feeds into your online store.

API Integration: Direct Connection to ERP Systems

API integration is the highest-fidelity import method available in MicroPIM. It is designed for businesses whose product master data lives in an ERP system — NetSuite, SAP Business One, Microsoft Dynamics 365, Odoo, or similar — and who need that data to flow into their e-commerce catalog without manual export and re-import steps.

How API Integration Works

MicroPIM connects to your ERP via its native API. Authentication is configured once using API keys or OAuth credentials specific to your ERP system. Once connected, MicroPIM can pull product master data, pricing, stock levels, and attribute data from the ERP on a scheduled basis or in response to webhook triggers from the ERP side.

The field mapping layer translates ERP data structures — which vary significantly between systems — into MicroPIM’s product model. NetSuite item records, SAP article master data, Dynamics 365 product catalogs, and Odoo product templates all have different schemas. MicroPIM’s integration layer handles the translation so your catalog always reflects the current state of your ERP without requiring manual intervention.

ERP Integration Use Cases

NetSuite — pull item master records, pricing from price levels, and bin-based inventory quantities into MicroPIM for enrichment and multi-channel distribution. See the NetSuite to e-commerce integration guide for the full technical setup.

SAP Business One — synchronize article master data and pricing conditions from SAP into MicroPIM, then publish enriched product data to your e-commerce channels. Details in the SAP Business One PIM integration guide.

Microsoft Dynamics 365 — connect Dynamics product catalogs and inventory data to MicroPIM for automated catalog enrichment and distribution. See the Dynamics 365 product management guide.

Odoo — sync Odoo product templates and variants into MicroPIM, apply enrichment, and export to your storefront. Covered in the Odoo product sync guide.

When API Integration Is the Right Choice

API integration requires more initial configuration than the other methods, but delivers the highest level of automation and data fidelity. It is the right choice when:

• Your product master data is owned and maintained in an ERP system
• Product data changes frequently and you need near-real-time synchronization
• You have IT resources available to configure and maintain the API connection
• Data governance requirements mean changes must originate in the ERP and flow downstream

Choosing the Right Import Method: Decision Matrix

The table below maps common business scenarios to the import method that fits best.

In many operations, you will use more than one method simultaneously. A business might use One-Link Import to onboard new suppliers quickly, CSV upload for internally prepared product additions, Feed Import for established suppliers who provide structured data, and API Integration for ERP synchronization. MicroPIM’s Import List shows all active import sources together, so managing multiple methods does not create additional overhead.

Troubleshooting Import Failures: Common Issues and Fixes

Even with well-configured imports, failures occur. The Import History view in MicroPIM is the starting point for any troubleshooting — every import run, whether successful or failed, is logged with a status, a record count, and a downloadable error report.

One-Link Import Failures

Scrape returns zero products. The most common cause is that the target URL requires JavaScript rendering to display product listings. MicroPIM’s scraper handles most JavaScript-rendered pages, but some sites with aggressive anti-bot measures will block the request. In these cases, request a data file from the supplier directly and use CSV or Feed Import instead.

Products imported with missing fields. The AI extraction layer could not find a reliable value for one or more fields on the source page. Check the Import History error log for the affected records. If the missing field is present on the source page but formatted unusually, contact support with the URL and field in question.

Duplicate records appearing after re-import. Verify that your duplicate detection settings are configured for the correct matching field. By default, MicroPIM matches on SKU. If the source page does not expose SKUs, switch duplicate detection to match on product name or URL.

CSV/Excel Upload Failures

Import fails immediately with no records processed. This almost always means the file encoding is not UTF-8. Open the file in a text editor, save it as UTF-8, and re-upload. Files saved from older versions of Excel on Windows default to Windows-1252 encoding, which causes parse failures.

Rows fail validation for price fields. Price columns contain non-numeric characters — currency symbols, thousand-separator commas, or blank cells where zero is the intended value. Clean the column before upload: remove currency symbols, replace blank cells with 0, and ensure decimal separators are periods, not commas.

Field mapping is not saving between uploads. Field mapping profiles are tied to the column header row of your source file. If the column headers change between uploads — even by a single character — MicroPIM treats the file as a new format. Standardize your column headers and the mapping will persist.

Feed Import Failures

Scheduled feed not updating. Check the Import History for the feed job. If the last run shows an HTTP error code (403, 404, 503), the feed URL has changed or the server is blocking the request. Verify the URL is still valid and accessible. Some suppliers rotate feed URLs seasonally.

Feed parsed with incorrect field values. The feed structure has changed since you configured the mapping. Suppliers occasionally update their XML or JSON schema without notice. Download the current feed file, inspect the schema, and update your field mapping in MicroPIM to match.

Products not updating on scheduled runs. If the feed uses a last-modified timestamp or a version field, confirm that MicroPIM’s change detection is configured to compare on the correct field. If the supplier’s feed does not include a reliable change indicator, switch to full-replace mode, which re-processes all records on every run.

API Integration Failures

Authentication errors after initial setup. API keys and OAuth tokens expire. Refresh the credentials in MicroPIM’s integration settings and re-test the connection. For systems using OAuth, ensure the authorized scopes include read access to the product and inventory modules.

Partial data — some fields missing. The ERP user account linked to MicroPIM may not have permission to read certain record types or fields. Review the field access permissions for the API user in your ERP and ensure they include all fields referenced in the MicroPIM field mapping.

Import runs but no records appear in catalog. Check whether the ERP API is returning results filtered by a default scope or location. Some ERP systems scope their API responses to a specific site, warehouse, or price level. Verify the API parameters in MicroPIM’s integration settings include the scope that covers your full product catalog.

The right product import method is determined by your data source, your update frequency, and your technical resources — not by a single universal best practice. One-Link Import removes friction from supplier onboarding. CSV upload handles structured file-based workflows. Feed Import automates recurring supplier data ingestion. API Integration keeps enterprise ERP data flowing without manual steps. MicroPIM supports all four in a single platform, with Import History and Import List providing a unified view of every source and every run.

If you are spending more than a few hours a week on product data imports, the configuration investment in the right import method pays back quickly. For the full picture of how MicroPIM handles product data from import through enrichment to multi-channel export, see how to save time on e-commerce product management.

Ready to set up your first import? Start your free 14-day trial — no credit card required, and you can have your first catalog import running in under 15 minutes.

Have questions about a specific import format or ERP connection? Contact our team — we are happy to walk through your setup.