Product Import Export for WooCommerce plugin review and common issues

WebToffee’s import provides a post-import summary showing success and failure counts. Check: (1) the import log (available after import completion) for rows that failed and their specific error messages; (2) verify the CSV column headers exactly match the expected field names — mismatched headers cause data to be ignored or placed in wrong fields; (3) download WebToffee’s sample CSV template to verify the expected format for each field; (4) test with a small subset (10-20 rows) of the catalog to identify problems before importing thousands of products; (5) check for encoding issues — the CSV must be UTF-8 encoded to handle special characters.

Image URL import downloads images from remote URLs and saves them to the WordPress media library. Failures occur when: (1) the image URLs in the CSV are not publicly accessible (require authentication or are on a local server); (2) the WordPress server cannot make outbound HTTP requests to the image URLs — check hosting firewall settings; (3) the image URL format is incorrect (missing protocol, special characters not URL-encoded); (4) the server’s PHP configuration has a short default_socket_timeout that cuts off image downloads for slow remote servers; (5) incorrect file permissions on wp-content/uploads prevent saving downloaded images.

Variable products in WooCommerce CSV require a specific format: (1) one row for the parent variable product with type = “variable” — no price or SKU on the parent; (2) subsequent rows for each variation with type = “variation” and the parent’s SKU in a parent field; (3) each variation row has its specific attribute values, price, and SKU; (4) download WebToffee’s sample variable product CSV to see the exact format. Common errors: missing parent-child relationship column, incorrect attribute formatting, or not setting each variation row’s type to “variation” explicitly.

Go to WebToffee Product Import Export → Export Products. In the export filters section, select Category → [your specific category]. Additional filters allow narrowing by product status (published only), stock status, or date range. Configure which fields to include in the export (or use “Select All” for a complete export). Click Export to download the filtered CSV. Modify prices or other fields in Excel/Google Sheets, then import the updated CSV back using the Import function with “Update existing products” as the duplicate handling setting.

Scheduled imports require WebToffee Product Import Export Pro. Go to the Pro import settings and create a new scheduled import. Configure: (1) the FTP server details (host, username, password, path to the CSV/XML file); (2) the import frequency (daily, weekly, or custom cron schedule); (3) the field mapping for the supplier’s file format; (4) the duplicate handling behavior (update existing products, create new, or skip duplicates). WebToffee Pro processes the import automatically according to the schedule, ensuring your product catalog stays synchronized with the supplier’s data.

WebToffee’s importer handles more complex scenarios better than WooCommerce’s built-in CSV importer, particularly for variable products with many variations, remote image importing, and large catalog performance. WooCommerce’s built-in importer is sufficient for simple stores with straightforward product structures. For stores with complex attribute combinations, large catalogs, or regular supplier synchronization needs, WebToffee’s importer provides better reliability and more options.

WooCommerce Subscription product type support requires WebToffee Pro. The Pro version handles subscription interval, period, trial, and signup fee fields in both import and export. The free version can import standard product types (simple, variable, grouped, external) but does not support WooCommerce Subscriptions’ custom product type and its specialized meta fields.

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.