Smart Product Import Export for WooCommerce

Yes, WooCommerce must be installed and active.

The plugin supports CSV files with comma, semicolon, tab, or pipe delimiters. UTF-8 and UTF-8 BOM encodings are supported.

Yes. Upload an XML file whose root element is <products>, containing one <product> element per product with child elements such as <id/>, <name/>, <sku/>, <price/>, <description/>, <category/>, <quantity/>, and <status/>. Elements are auto-mapped to WooCommerce product fields during preview.

Yes. Upload an .xlsx workbook whose first worksheet contains a header row with column names, followed by one product per row. Blank cells are treated as empty values, and the same validation and mapping steps apply as for CSV imports. Products can also be exported as .xlsx from the export screen.

Yes. Both screens include an FTP / SFTP section where you can enter the protocol (FTP, FTPS, or SFTP), host, port, username, password, and the remote file path or destination directory. Import files are fetched into the regular import flow, and completed exports can be pushed to the remote server; the destination directory must already exist. SFTP requires the PHP SSH2 extension on the server. Connection details are used only for the duration of the transfer and are never stored or written to logs, and connection or authentication failures are reported without exposing credentials.

Yes. Open the Import from URL section on the import screen and paste a link. If the URL points to a CSV, Excel (.xlsx), or XML file, it is downloaded and validated, then continues through the regular preview and mapping flow. If the URL points to a product page, the product details (name, SKU, price, description, and images) are extracted automatically from the page's schema.org Product data (JSON-LD) or OpenGraph meta tags, and you review them like any other import. URLs are validated before the request is made — only public HTTP/HTTPS addresses are allowed, and private or local addresses are blocked (SSRF protection). Clear errors are reported when the page cannot be reached, the server returns an HTTP error, or no product details could be extracted from the page.

Yes. Open Schedules under Product Import/Export to create schedules that run hourly, daily, or weekly at a set time in a timezone you choose. Scheduled imports use a saved supplier file, a URL that is fetched fresh on every run, or an FTP/FTPS/SFTP download together with a saved mapping; products are matched (by SKU by default) and only the mapped fields are updated, so recurring stock/price files update existing products instead of creating duplicates. Scheduled exports pick the product data and file format (CSV, Excel, or XML) and generate the file automatically at the scheduled time, optionally uploading it to an FTP/FTPS/SFTP destination afterwards. Each run is recorded in the schedule history with its time, status, records processed, and errors, and you can configure a failure alert email (alerts never contain credentials or connection details). Overlapping runs are prevented automatically, and failed runs are retried a limited number of times before an alert is sent.

WordPress cron (WP-Cron) is triggered by visits to your site, orders, and other traffic — scheduled runs may be delayed on stores with little or no traffic. For reliable timing, disable WP-Cron by adding define("WP_CRON", false); to wp-config.php and create a system cron job (or a scheduled task on your server) that hits your site every minute. If Action Scheduler is available (it ships with WooCommerce), scheduled runs are queued through it for more reliable background processing.

Yes — unattended scheduled runs need the connection details on hand, so schedule credentials are stored in the database to be used at run time only. They are never displayed again after saving, never written to logs, and never included in history entries, failure alerts, or emails. For one-off transfers started manually from the import/export screens, nothing is stored at all.

Yes. Both the import and export screens include an "Import Type" / "Export Type" selector where you can switch between Products and Product Reviews. Review exports support CSV, Excel, and XML and can be filtered by review status (approved, pending, spam, trash) and review date range. For imports, upload a file with review columns such as review ID, product SKU or Product ID, reviewer name, email, review content, rating (1-5), date, status, website, IP address, and verified owner; the columns are auto-mapped to review fields during preview. Every row is validated before the import runs — rows that are invalid (for example a missing reviewer, an invalid rating, or a product that does not exist) or that duplicate an existing review (matched by review ID, or by product and reviewer email) are reported and skipped or failed according to your duplicate and error handling settings.

Yes, the plugin fully supports variable products and their variations. Parent products and variations can be imported in the same CSV file.

The default maximum file size is 100MB, but this can be adjusted in the plugin settings.

Yes, you can save field mappings and load them for future imports.

Yes, files with more than 100 rows are processed in the background using Action Scheduler or WordPress cron.