WP All Import plugin review and common issues

Image import in WP All Import downloads remote images to the WordPress media library. If images are not importing: (1) verify the image field contains valid, publicly accessible URLs — test each URL in a browser to confirm it resolves to an image; (2) check if your server can make outbound HTTP requests to the image source — some hosting firewalls block outbound connections; (3) if images are behind authentication or require specific headers, standard URL download will fail — use PHP template to add custom headers; (4) very large image files may timeout during download — increase PHP max_execution_time or reduce batch size to allow more time per record.

WP All Import scheduled imports use WP-Cron. If not running automatically: (1) verify WP-Cron is functional using WP Crontrol plugin — check if the WP All Import cron job appears and is scheduled; (2) low-traffic sites may not trigger WP-Cron frequently enough — set up a real server cron job to call wp-cron.php on a regular interval; (3) if DISABLE_WP_CRON is true in wp-config.php, WP-Cron is disabled — use a server cron instead; (4) check that the scheduled import’s source URL is still returning valid data — if the URL returns an error, the import may silently fail without re-scheduling.

WooCommerce variable product import requires the WooCommerce Add-On for WP All Import Pro. The import must be configured to handle the parent product and its variations as a grouped set. In the import configuration: (1) ensure the WooCommerce add-on is active; (2) set the “Product Type” field to “Variable”; (3) configure the “Unique Identifier” to group variations under the same parent (typically a shared product ID or SKU); (4) use the Repeating Fields section for variations — each variation’s attributes (color, size) and specific fields (price, SKU, stock) are mapped within the repeating element loop.

ACF field import requires WP All Import Pro and the WP All Import ACF Add-On (free, available separately). In the import field mapping, after standard post fields, scroll down to the ACF Fields section — it lists all ACF field groups registered for the post type being imported. Drag import file fields onto the corresponding ACF field. Complex ACF field types (Repeater, Flexible Content, Gallery) use WP All Import’s repeating element builder. For ACF fields with JSON configuration, use WP All Import’s developer function templates to manipulate data into the exact format ACF expects.

In the field mapping step, each mapped field allows clicking “Function” to add a PHP snippet that transforms the value before it is saved. Examples: (1) [strtoupper({title[1]})] — converts a title to uppercase; (2) [number_format({price[1]}, 2)] — formats a number to 2 decimal places; (3) [str_replace(“,”, “.”, {price[1]})] — replaces European decimal comma with a period for WooCommerce price fields; (4) Custom functions registered in your theme functions.php are available for use in these templates. This power makes WP All Import capable of handling virtually any data transformation without external preprocessing.

Yes — WP All Import’s “Unique Identifier” configuration handles deduplication. Configure the field that uniquely identifies each product (SKU, product ID, or custom field). When an import runs, WP All Import checks if a product with that unique identifier already exists. If found, it updates the existing product with new data. If not found, it creates a new product. This update behavior is essential for scheduled imports from supplier feeds where product data (prices, stock levels) changes regularly.

Yes — WP All Import handles large imports through batch processing. Configure the batch size (records per processing batch) in the import settings based on your hosting resources. For 10,000+ products, use batches of 100-200 and allow the import to complete across multiple automatic batches. For shared hosting, smaller batches prevent timeout issues. Managed WordPress hosting (Kinsta, WP Engine) handles larger batches more reliably. Initial imports of 100,000+ products may take hours but scheduled subsequent imports (which only process changed records) are faster.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.